1 Changes in version 0.2.3.17-beta - 2012-06-15
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 the documentation for the --hush and --quiet command line
58 options, which changed their behavior back in 0.2.3.3-alpha.
59 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
63 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
64 more information to it, so that we can track it down in case it
65 returns again. Mitigates bug 5235.
66 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
67 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
68 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
69 - Warn the user when HTTPProxy, but no other proxy type, is
70 configured. This can cause surprising behavior: it doesn't send
71 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
72 directory traffic only. Resolves ticket 4663.
73 - Issue a notice if a guard completes less than 40% of your circuits.
74 Threshold is configurable by torrc option PathBiasNoticeRate and
75 consensus parameter pb_noticepct. There is additional, off-by-
76 default code to disable guards which fail too many circuits.
77 Addresses ticket 5458.
78 - Update to the June 6 2012 Maxmind GeoLite Country database.
80 o Code simplifications and refactoring:
81 - Remove validate_pluggable_transports_config(): its warning
82 message is now handled by connection_or_connect().
85 Changes in version 0.2.2.37 - 2012-06-06
86 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
87 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
91 - Work around a bug in OpenSSL that broke renegotiation with TLS
92 1.1 and TLS 1.2. Without this workaround, all attempts to speak
93 the v2 Tor connection protocol when both sides were using OpenSSL
94 1.0.1 would fail. Resolves ticket 6033.
95 - When waiting for a client to renegotiate, don't allow it to add
96 any bytes to the input buffer. This fixes a potential DoS issue.
97 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
98 - Fix an edge case where if we fetch or publish a hidden service
99 descriptor, we might build a 4-hop circuit and then use that circuit
100 for exiting afterwards -- even if the new last hop doesn't obey our
101 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
104 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
105 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
108 - Tell GCC and Clang to check for any errors in format strings passed
109 to the tor_v*(print|scan)f functions.
112 Changes in version 0.2.3.16-alpha - 2012-06-05
113 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
114 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
115 currently). It also fixes a variety of smaller bugs and other cleanups
116 that get us closer to a release candidate.
118 o Major bugfixes (general):
119 - Work around a bug in OpenSSL that broke renegotiation with TLS
120 1.1 and TLS 1.2. Without this workaround, all attempts to speak
121 the v2 Tor connection protocol when both sides were using OpenSSL
122 1.0.1 would fail. Resolves ticket 6033.
123 - When waiting for a client to renegotiate, don't allow it to add
124 any bytes to the input buffer. This fixes a potential DoS issue.
125 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
126 - Pass correct OR address to managed proxies (like obfsproxy),
127 even when ORListenAddress is used. Fixes bug 4865; bugfix on
129 - The advertised platform of a router now includes only its operating
130 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
131 service pack level (for Windows) or its CPU architecture (for Unix).
132 We also no longer include the "git-XYZ" tag in the version. Resolves
135 o Major bugfixes (clients):
136 - If we are unable to find any exit that supports our predicted ports,
137 stop calling them predicted, so that we don't loop and build
138 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
139 which introduced predicted ports.
140 - Fix an edge case where if we fetch or publish a hidden service
141 descriptor, we might build a 4-hop circuit and then use that circuit
142 for exiting afterwards -- even if the new last hop doesn't obey our
143 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
144 - Check at each new consensus whether our entry guards were picked
145 long enough ago that we should rotate them. Previously, we only
146 did this check at startup, which could lead to us holding a guard
147 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
148 - When fetching a bridge descriptor from a bridge authority,
149 always do so anonymously, whether we have been able to open
150 circuits or not. Partial fix for bug 1938; bugfix on 2.0.7-alpha.
151 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
152 but we'll need to wait for bug 6010 before it's actually usable.
154 o Major bugfixes (directory authorities):
155 - When computing weight parameters, behave more robustly in the
156 presence of a bad bwweightscale value. Previously, the authorities
157 would crash if they agreed on a sufficiently broken weight_scale
158 value: now, they use a reasonable default and carry on. Partial
159 fix for 5786; bugfix on 0.2.2.17-alpha.
160 - Check more thoroughly to prevent a rogue authority from
161 double-voting on any consensus directory parameter. Previously,
162 authorities would crash in this case if the total number of
163 votes for any parameter exceeded the number of active voters,
164 but would let it pass otherwise. Partial fix for bug 5786; bugfix
168 - Rate-limit log messages when asked to connect anonymously to
169 a private address. When these hit, they tended to hit fast and
170 often. Also, don't bother trying to connect to addresses that we
171 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
172 reply makes us think we have been lied to, even when the address the
173 client tried to connect to was "localhost." Resolves ticket 2822.
174 - Allow packagers to insert an extra string in server descriptor
175 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
176 Resolves the rest of ticket 2988.
177 - Raise the threshold of server descriptors needed (75%) and exit
178 server descriptors needed (50%) before we will declare ourselves
179 bootstrapped. This will make clients start building circuits a
180 little later, but makes the initially constructed circuits less
181 skewed and less in conflict with further directory fetches. Fixes
183 - Close any connection that sends unrecognized junk before the
184 handshake. Solves an issue noted in bug 4369.
185 - Improve log messages about managed transports. Resolves ticket 5070.
186 - Tag a bridge's descriptor as "never to be sent unencrypted".
187 This shouldn't matter, since bridges don't open non-anonymous
188 connections to the bridge authority and don't allow unencrypted
189 directory connections from clients, but we might as well make
190 sure. Closes bug 5139.
191 - Expose our view of whether we have gone dormant to the controller,
192 via a new "GETINFO dormant" value. Torbutton and other controllers
193 can use this to avoid doing periodic requests through Tor while
194 it's dormant (bug 4718). Fixes bug 5954.
195 - Tell GCC and Clang to check for any errors in format strings passed
196 to the tor_v*(print|scan)f functions.
197 - Update to the May 1 2012 Maxmind GeoLite Country database.
199 o Minor bugfixes (already included in 0.2.2.36):
200 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
201 Fixes bug 5346; bugfix on 0.0.8pre3.
202 - Correct parsing of certain date types in parse_http_time().
203 Without this patch, If-Modified-Since would behave
204 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
205 Esteban Manchado Velázques.
206 - Make our number-parsing functions always treat too-large values
207 as an error, even when those values exceed the width of the
208 underlying type. Previously, if the caller provided these
209 functions with minima or maxima set to the extreme values of the
210 underlying integer type, these functions would return those
211 values on overflow rather than treating overflow as an error.
212 Fixes part of bug 5786; bugfix on 0.0.9.
213 - If we hit the error case where routerlist_insert() replaces an
214 existing (old) server descriptor, make sure to remove that
215 server descriptor from the old_routers list. Fix related to bug
216 1776. Bugfix on 0.2.2.18-alpha.
217 - Clarify the behavior of MaxCircuitDirtiness with hidden service
218 circuits. Fixes issue 5259.
220 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
221 - Prevent a null-pointer dereference when receiving a data cell
222 for a nonexistent stream when the circuit in question has an
223 empty deliver window. We don't believe this is triggerable,
224 since we don't currently allow deliver windows to become empty,
225 but the logic is tricky enough that it's better to make the code
226 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
227 - Fix a memory leak when trying to launch a DNS request when the
228 network is disabled or the nameservers are unconfigurable. Fixes
229 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
230 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
231 - Don't hold a Windows file handle open for every file mapping;
232 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
234 - Avoid O(n^2) performance characteristics when parsing a large
235 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
236 - Format more doubles with %f, not %lf. Patch from grarpamp to make
237 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
239 - Make our replacement implementation of strtok_r() compatible with
240 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
241 bugfix on 0.2.2.1-alpha.
242 - Fix a NULL-pointer dereference on a badly formed
243 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
244 bugfix on 0.2.2.9-alpha.
245 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
246 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
247 - Defensively refactor rend_mid_rendezvous() so that protocol
248 violations and length checks happen in the beginning. Fixes
250 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
251 that IPv6 stuff will compile on MSVC, and compilation issues
252 will be easier to track down. Fixes bug 5861.
254 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
255 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
256 resource exhaustion, so that clients can adjust their load to
257 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
258 started using END_STREAM_REASON_RESOURCELIMIT.
259 - Don't check for whether the address we're using for outbound
260 connections has changed until after the outbound connection has
261 completed. On Windows, getsockname() doesn't succeed until the
262 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
263 - If the configuration tries to set MyFamily on a bridge, refuse to
264 do so, and warn about the security implications. Fixes bug 4657;
265 bugfix on 0.2.0.3-alpha.
266 - If the client fails to set a reasonable set of ciphersuites
267 during its v2 handshake renegotiation, allow the renegotiation to
268 continue nevertheless (i.e. send all the required certificates).
269 Fixes bug 4591; bugfix on 0.2.0.20-rc.
270 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
271 option is set to 0 (which Vidalia version 0.2.16 now does when
272 a SAVECONF attempt fails), perform other actions that SIGHUP
273 usually causes (like reopening the logs). Fixes bug 5095; bugfix
275 - If we fail to write a microdescriptor to the disk cache, do not
276 continue replacing the old microdescriptor file. Fixes bug 2954;
277 bugfix on 0.2.2.6-alpha.
278 - Exit nodes don't need to fetch certificates for authorities that
279 they don't recognize; only directory authorities, bridges,
280 and caches need to do that. Fixes part of bug 2297; bugfix on
282 - Correctly handle checking the permissions on the parent
283 directory of a control socket in the root directory. Bug found
284 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
286 - When told to add a bridge with the same digest as a preexisting
287 bridge but a different addr:port, change the addr:port as
288 requested. Previously we would not notice the change. Fixes half
289 of bug 5603; fix on 0.2.2.26-beta.
290 - End AUTHCHALLENGE error messages (in the control protocol) with
291 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
293 o Minor bugfixes (on 0.2.3.x):
294 - Turn an assertion (that the number of handshakes received as a
295 server is not < 1) into a warning. Fixes bug 4873; bugfix on
297 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
298 we had reversed them when the answer was cached.) Fixes bug
299 5723; bugfix on 0.2.3.1-alpha.
300 - Work correctly on Linux systems with accept4 support advertised in
301 their headers, but without accept4 support in the kernel. Fix
302 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
303 - When told to add a bridge with the same addr:port as a preexisting
304 bridge but a different transport, change the transport as
305 requested. Previously we would not notice the change. Fixes half
306 of bug 5603; fix on 0.2.3.2-alpha.
307 - Avoid a "double-reply" warning when replying to a SOCKS request
308 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
309 bugfix on 0.2.3.4-alpha.
310 - Fix a bug where a bridge authority crashes if it has seen no
311 directory requests when it's time to write statistics to disk.
312 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
314 - Don't try to open non-control listeners when DisableNetwork is set.
315 Previously, we'd open all listeners, then immediately close them.
316 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
317 - Don't abort the managed proxy protocol if the managed proxy
318 sends us an unrecognized line; ignore it instead. Fixes bug
319 5910; bugfix on 0.2.3.9-alpha.
320 - Fix a compile warning in crypto.c when compiling with clang 3.1.
321 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
322 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
323 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
324 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
325 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
326 - Resolve numerous small warnings and build issues with MSVC. Resolves
329 o Documentation fixes:
330 - Improve the manual's documentation for the NT Service command-line
331 options. Addresses ticket 3964.
332 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
333 - Document the changes to the ORPort and DirPort options, and the
334 fact that {OR/Dir}ListenAddress is now unnecessary (and
335 therefore deprecated). Resolves ticket 5597.
338 - Remove the torrc.bridge file: we don't use it for anything, and
339 it had become badly desynchronized from torrc.sample. Resolves
343 Changes in version 0.2.2.36 - 2012-05-24
344 Tor 0.2.2.36 updates the addresses for two of the eight directory
345 authorities, fixes some potential anonymity and security issues,
346 and fixes several crash bugs.
348 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
349 known flaws, and nobody should be using them. You should upgrade. If
350 you're using a Linux or BSD and its packages are obsolete, stop using
351 those packages and upgrade anyway.
353 o Directory authority changes:
354 - Change IP address for maatuska (v3 directory authority).
355 - Change IP address for ides (v3 directory authority), and rename
359 - When building or running with any version of OpenSSL earlier
360 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
361 versions have a bug (CVE-2011-4576) in which their block cipher
362 padding includes uninitialized data, potentially leaking sensitive
363 information to any peer with whom they make a SSLv3 connection. Tor
364 does not use SSL v3 by default, but a hostile client or server
365 could force an SSLv3 connection in order to gain information that
366 they shouldn't have been able to get. The best solution here is to
367 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
368 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
369 to make sure that the bug can't happen.
370 - Never use a bridge or a controller-supplied node as an exit, even
371 if its exit policy allows it. Found by wanoskarnet. Fixes bug
372 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
373 and 0.2.0.3-alpha (for bridge-purpose descriptors).
374 - Only build circuits if we have a sufficient threshold of the total
375 descriptors that are marked in the consensus with the "Exit"
376 flag. This mitigates an attack proposed by wanoskarnet, in which
377 all of a client's bridges collude to restrict the exit nodes that
378 the client knows about. Fixes bug 5343.
379 - Provide controllers with a safer way to implement the cookie
380 authentication mechanism. With the old method, if another locally
381 running program could convince a controller that it was the Tor
382 process, then that program could trick the controller into telling
383 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
384 authentication method uses a challenge-response approach to prevent
385 this attack. Fixes bug 5185; implements proposal 193.
388 - Avoid logging uninitialized data when unable to decode a hidden
389 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
390 - Avoid a client-side assertion failure when receiving an INTRODUCE2
391 cell on a general purpose circuit. Fixes bug 5644; bugfix on
393 - Fix builds when the path to sed, openssl, or sha1sum contains
394 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
396 - Correct our replacements for the timeradd() and timersub() functions
397 on platforms that lack them (for example, Windows). The timersub()
398 function is used when expiring circuits, while timeradd() is
399 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
400 bugfix on 0.2.2.24-alpha.
401 - Fix the SOCKET_OK test that we use to tell when socket
402 creation fails so that it works on Win64. Fixes part of bug 4533;
403 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
406 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
407 Fixes bug 5346; bugfix on 0.0.8pre3.
408 - Make our number-parsing functions always treat too-large values
409 as an error, even when those values exceed the width of the
410 underlying type. Previously, if the caller provided these
411 functions with minima or maxima set to the extreme values of the
412 underlying integer type, these functions would return those
413 values on overflow rather than treating overflow as an error.
414 Fixes part of bug 5786; bugfix on 0.0.9.
415 - Older Linux kernels erroneously respond to strange nmap behavior
416 by having accept() return successfully with a zero-length
417 socket. When this happens, just close the connection. Previously,
418 we would try harder to learn the remote address: but there was
419 no such remote address to learn, and our method for trying to
420 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
421 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
422 - Correct parsing of certain date types in parse_http_time().
423 Without this patch, If-Modified-Since would behave
424 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
425 Esteban Manchado Velázques.
426 - Change the BridgePassword feature (part of the "bridge community"
427 design, which is not yet implemented) to use a time-independent
428 comparison. The old behavior might have allowed an adversary
429 to use timing to guess the BridgePassword value. Fixes bug 5543;
430 bugfix on 0.2.0.14-alpha.
431 - Detect and reject certain misformed escape sequences in
432 configuration values. Previously, these values would cause us
433 to crash if received in a torrc file or over an authenticated
434 control port. Bug found by Esteban Manchado Velázquez, and
435 independently by Robert Connolly from Matta Consulting who further
436 noted that it allows a post-authentication heap overflow. Patch
437 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
438 bugfix on 0.2.0.16-alpha.
439 - Fix a compile warning when using the --enable-openbsd-malloc
440 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
441 - During configure, detect when we're building with clang version
442 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
443 CFLAGS. clang doesn't support them yet.
444 - When sending an HTTP/1.1 proxy request, include a Host header.
445 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
446 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
447 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
448 - If we hit the error case where routerlist_insert() replaces an
449 existing (old) server descriptor, make sure to remove that
450 server descriptor from the old_routers list. Fix related to bug
451 1776. Bugfix on 0.2.2.18-alpha.
453 o Minor bugfixes (documentation and log messages):
454 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
455 Fixes bug 4856; bugfix on Tor 0.0.6.
456 - Update "ClientOnly" man page entry to explain that there isn't
457 really any point to messing with it. Resolves ticket 5005.
458 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
459 directory authority option (introduced in Tor 0.2.2.34).
460 - Downgrade the "We're missing a certificate" message from notice
461 to info: people kept mistaking it for a real problem, whereas it
462 is seldom the problem even when we are failing to bootstrap. Fixes
463 bug 5067; bugfix on 0.2.0.10-alpha.
464 - Correctly spell "connect" in a log message on failure to create a
465 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
466 - Clarify the behavior of MaxCircuitDirtiness with hidden service
467 circuits. Fixes issue 5259.
470 - Directory authorities now reject versions of Tor older than
471 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
472 inclusive. These versions accounted for only a small fraction of
473 the Tor network, and have numerous known security issues. Resolves
475 - Update to the May 1 2012 Maxmind GeoLite Country database.
478 - When sending or relaying a RELAY_EARLY cell, we used to convert
479 it to a RELAY cell if the connection was using the v1 link
480 protocol. This was a workaround for older versions of Tor, which
481 didn't handle RELAY_EARLY cells properly. Now that all supported
482 versions can handle RELAY_EARLY cells, and now that we're enforcing
483 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
484 remove this workaround. Addresses bug 4786.
487 Changes in version 0.2.3.15-alpha - 2012-04-30
488 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
489 the development branch build on Windows again.
491 o Minor bugfixes (on 0.2.2.x and earlier):
492 - Make sure that there are no unhandled pending TLS errors before
493 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
494 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
495 Bugfix on 0.1.0.5-rc; fixes bug 4528.
496 - Fix an assert that directory authorities could trigger on sighup
497 during some configuration state transitions. We now don't treat
498 it as a fatal error when the new descriptor we just generated in
499 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
500 - After we pick a directory mirror, we would refuse to use it if
501 it's in our ExcludeExitNodes list, resulting in mysterious failures
502 to bootstrap for people who just wanted to avoid exiting from
503 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
504 - When building with --enable-static-tor on OpenBSD, do not
505 erroneously attempt to link -lrt. Fixes bug 5103.
507 o Minor bugfixes (on 0.2.3.x):
508 - When Tor is built with kernel headers from a recent (last few
509 years) Linux kernel, do not fail to run on older (pre-2.6.28
510 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
511 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
513 - Fix compilation with miniupnpc version 1.6; patch from
514 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
515 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
516 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
517 - Fix compilation on platforms without unistd.h, or where environ
518 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
521 - Directory authorities are now a little more lenient at accepting
522 older router descriptors, or newer router descriptors that don't
523 make big changes. This should help ameliorate past and future
524 issues where routers think they have uploaded valid descriptors,
525 but the authorities don't think so. Fix for ticket 2479.
526 - Make the code that clients use to detect an address change be
527 IPv6-aware, so that it won't fill clients' logs with error
528 messages when trying to get the IPv4 address of an IPv6
529 connection. Implements ticket 5537.
532 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
533 authorities needed to use it for a while to keep the network working
534 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
535 that was six months ago. As of now, it should no longer be needed
539 Changes in version 0.2.3.14-alpha - 2012-04-23
540 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
541 candidate. It also dramatically speeds up AES: fast relays should
542 consider switching to the newer OpenSSL library.
544 o Directory authority changes:
545 - Change IP address for ides (v3 directory authority), and rename
549 - Avoid logging uninitialized data when unable to decode a hidden
550 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
551 - Avoid a client-side assertion failure when receiving an INTRODUCE2
552 cell on a general purpose circuit. Fixes bug 5644; bugfix on
554 - If authorities are unable to get a v2 consensus document from other
555 directory authorities, they no longer fall back to fetching
556 them from regular directory caches. Fixes bug 5635; bugfix on
557 0.2.2.26-beta, where routers stopped downloading v2 consensus
559 - When we start a Tor client with a normal consensus already cached,
560 be willing to download a microdescriptor consensus. Fixes bug 4011;
561 fix on 0.2.3.1-alpha.
563 o Major features (performance):
564 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
565 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
566 vectorized AES implementations as appropriate. These can be much,
567 much faster than other AES implementations.
569 o Minor bugfixes (0.2.2.x and earlier):
570 - Don't launch more than 10 service-side introduction-point circuits
571 for a hidden service in five minutes. Previously, we would consider
572 launching more introduction-point circuits if at least one second
573 had passed without any introduction-point circuits failing. Fixes
574 bug 4607; bugfix on 0.0.7pre1.
575 - Change the BridgePassword feature (part of the "bridge community"
576 design, which is not yet implemented) to use a time-independent
577 comparison. The old behavior might have allowed an adversary
578 to use timing to guess the BridgePassword value. Fixes bug 5543;
579 bugfix on 0.2.0.14-alpha.
580 - Enforce correct return behavior of tor_vsscanf() when the '%%'
581 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
582 - When sending an HTTP/1.1 proxy request, include a Host header.
583 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
584 - Don't log that we have "decided to publish new relay descriptor"
585 unless we are actually publishing a descriptor. Fixes bug 3942;
586 bugfix on 0.2.2.28-beta.
588 o Minor bugfixes (0.2.3.x):
589 - Fix a bug where a bridge authority crashes (on a failed assert)
590 if it has seen no directory requests when it's time to write
591 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
592 - Fix bug stomping on ORPort option NoListen and ignoring option
593 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
594 - In the testsuite, provide a large enough buffer in the tor_sscanf
595 unit test. Otherwise we'd overrun that buffer and crash during
596 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
598 - Make sure we create the keys directory if it doesn't exist and we're
599 about to store the dynamic Diffie-Hellman parameters. Fixes bug
600 5572; bugfix on 0.2.3.13-alpha.
601 - Fix a small memory leak when trying to decode incorrect base16
602 authenticator during SAFECOOKIE authentication. Found by
603 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
606 - Add more information to a log statement that might help track down
607 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
608 non-IP address" messages (or any Bug messages, for that matter!),
609 please let us know about it.
610 - Relays now understand an IPv6 address when they get one from a
611 directory server. Resolves ticket 4875.
612 - Resolve IPv6 addresses in bridge and entry statistics to country
613 code "??" which means we at least count them. Resolves ticket 5053;
614 improves on 0.2.3.9-alpha.
615 - Update to the April 3 2012 Maxmind GeoLite Country database.
616 - Begin a doc/state-contents.txt file to explain the contents of
617 the Tor state file. Fixes bug 2987.
619 o Default torrc changes:
620 - Stop listing "socksport 9050" in torrc.sample. We open a socks
621 port on 9050 by default anyway, so this should not change anything
623 - Stop mentioning the deprecated *ListenAddress options in
624 torrc.sample. Fixes bug 5438.
625 - Document unit of bandwidth related options in sample torrc.
629 - The "torify" script no longer supports the "tsocks" socksifier
630 tool, since tsocks doesn't support DNS and UDP right for Tor.
631 Everyone should be using torsocks instead. Fixes bugs 3530 and
632 5180. Based on a patch by "ugh".
635 - Change the symmetric cipher interface so that creating and
636 initializing a stream cipher are no longer separate functions.
637 - Remove all internal support for unpadded RSA. We never used it, and
638 it would be a bad idea to start.
641 Changes in version 0.2.3.13-alpha - 2012-03-26
642 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
643 in managed pluggable transports, as well as providing other cleanups
644 that get us closer to a release candidate.
646 o Directory authority changes:
647 - Change IP address for maatuska (v3 directory authority).
650 - Provide controllers with a safer way to implement the cookie
651 authentication mechanism. With the old method, if another locally
652 running program could convince a controller that it was the Tor
653 process, then that program could trick the controller into telling
654 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
655 authentication method uses a challenge-response approach to prevent
656 this attack. Fixes bug 5185, implements proposal 193.
657 - Never use a bridge or a controller-supplied node as an exit, even
658 if its exit policy allows it. Found by wanoskarnet. Fixes bug
659 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
660 and 0.2.0.3-alpha (for bridge-purpose descriptors).
661 - Only build circuits if we have a sufficient threshold of the total
662 descriptors that are marked in the consensus with the "Exit"
663 flag. This mitigates an attack proposed by wanoskarnet, in which
664 all of a client's bridges collude to restrict the exit nodes that
665 the client knows about. Fixes bug 5343.
667 o Major bugfixes (on Tor 0.2.3.x):
668 - Avoid an assert when managed proxies like obfsproxy are configured,
669 and we receive HUP signals or setconf attempts too rapidly. This
670 situation happens most commonly when Vidalia tries to attach to
671 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
672 bugfix on 0.2.3.6-alpha.
673 - Fix a relay-side pluggable transports bug where managed proxies were
674 unreachable from the Internet, because Tor asked them to bind on
675 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
676 - Stop discarding command-line arguments when TestingTorNetwork
677 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
678 0.2.3.9-alpha, where task 4552 added support for two layers of
680 - Resume allowing the unit tests to run in gdb. This was accidentally
681 made impossible when the DisableDebuggerAttachment option was
682 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
683 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
684 0.2.3.11-alpha. Reported by Anthony G. Basile.
686 o Minor bugfixes (on 0.2.2.x and earlier):
687 - Ensure we don't cannibalize circuits that are longer than three hops
688 already, so we don't end up making circuits with 5 or more
689 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
690 0.1.0.1-rc which introduced cannibalization.
691 - Detect and reject certain misformed escape sequences in
692 configuration values. Previously, these values would cause us
693 to crash if received in a torrc file or over an authenticated
694 control port. Bug found by Esteban Manchado Velázquez, and
695 independently by Robert Connolly from Matta Consulting who further
696 noted that it allows a post-authentication heap overflow. Patch
697 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
698 bugfix on 0.2.0.16-alpha.
699 - Fix a compile warning when using the --enable-openbsd-malloc
700 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
701 - Directory caches no longer refuse to clean out descriptors because
702 of missing v2 networkstatus documents, unless they're configured
703 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
704 0.2.2.26-beta. Patch by Daniel Bryg.
705 - Update to the latest version of the tinytest unit testing framework.
706 This includes a couple of bugfixes that can be relevant for
707 running forked unit tests on Windows, and removes all reserved
710 o Minor bugfixes (on 0.2.3.x):
711 - On a failed pipe() call, don't leak file descriptors. Fixes bug
712 4296; bugfix on 0.2.3.1-alpha.
713 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
714 until after we have received a CERTS cell. Fixes bug 4361; bugfix
715 on 0.2.3.6-alpha. Patch by "frosty".
716 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
717 option, so that the IP stack doesn't decide to use it for IPv4
718 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
719 - Ensure that variables set in Tor's environment cannot override
720 environment variables that Tor passes to a managed
721 pluggable-transport proxy. Previously, Tor would pass every
722 variable in its environment to managed proxies along with the new
723 ones, in such a way that on many operating systems, the inherited
724 environment variables would override those which Tor tried to
725 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
726 bugfix on 0.2.3.9-alpha for Windows.
729 - A wide variety of new unit tests by Esteban Manchado Velázquez.
730 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
731 - Update to the March 6 2012 Maxmind GeoLite Country database.
734 Changes in version 0.2.3.12-alpha - 2012-02-13
735 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
736 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
737 when Tor is configured to use a pluggable transport like obfsproxy.
740 - Fix builds when the path to sed, openssl, or sha1sum contains
741 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
743 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
744 connections. This change should allow busy exit relays to stop
745 running out of available sockets as quickly. Fixes bug 4950;
746 bugfix on 0.2.2.26-beta.
747 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
748 would ask the bridge for microdescriptors, which are only supported
749 in 0.2.3.x, and then fail to bootstrap when it didn't get the
750 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
751 - Properly set up obfsproxy's environment when in managed mode. The
752 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
753 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
754 5076 and 5082; bugfix on 0.2.3.6-alpha.
757 - Use the dead_strip option when building Tor on OS X. This reduces
758 binary size by almost 19% when linking openssl and libevent
759 statically, which we do for Tor Browser Bundle.
760 - Fix broken URLs in the sample torrc file, and tell readers about
761 the OutboundBindAddress, ExitPolicyRejectPrivate, and
762 PublishServerDescriptor options. Addresses bug 4652.
763 - Update to the February 7 2012 Maxmind GeoLite Country database.
766 - Downgrade the "We're missing a certificate" message from notice
767 to info: people kept mistaking it for a real problem, whereas it
768 is seldom the problem even when we are failing to bootstrap. Fixes
769 bug 5067; bugfix on 0.2.0.10-alpha.
770 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
771 managed pluggable transport server proxy's environment.
772 Previously, we would put it there, even though Tor doesn't
773 implement an 'extended server port' yet, and even though Tor
774 almost certainly isn't listening at that address. For now, we set
775 it to an empty string to avoid crashing older obfsproxies. Bugfix
777 - Log the heartbeat message every HeartbeatPeriod seconds, not every
778 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
779 0.2.3.1-alpha. Bug reported by Scott Bennett.
780 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
781 bugfix on 0.2.3.11-alpha.
782 - Update "ClientOnly" man page entry to explain that there isn't
783 really any point to messing with it. Resolves ticket 5005.
784 - Use the correct CVE number for CVE-2011-4576 in our comments and
785 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
788 o Code simplifications and refactoring:
789 - Use the _WIN32 macro throughout our code to detect Windows.
790 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
794 Changes in version 0.2.3.11-alpha - 2012-01-22
795 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
796 the last step of the plan to limit maximum circuit length, includes
797 a wide variety of hidden service performance and correctness fixes,
798 works around an OpenSSL security flaw if your distro is too stubborn
799 to upgrade, and fixes a bunch of smaller issues.
802 - Now that Tor 0.2.0.x is completely deprecated, enable the final
803 part of "Proposal 110: Avoiding infinite length circuits" by
804 refusing all circuit-extend requests that do not use a relay_early
805 cell. This change helps Tor resist a class of denial-of-service
806 attacks by limiting the maximum circuit length.
807 - Adjust the number of introduction points that a hidden service
808 will try to maintain based on how long its introduction points
809 remain in use and how many introductions they handle. Fixes
811 - Try to use system facilities for enumerating local interface
812 addresses, before falling back to our old approach (which was
813 binding a UDP socket, and calling getsockname() on it). That
814 approach was scaring OS X users whose draconian firewall
815 software warned about binding to UDP sockets, regardless of
816 whether packets were sent. Now we try to use getifaddrs(),
817 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
818 system supports. Resolves ticket 1827.
820 o Major security workaround:
821 - When building or running with any version of OpenSSL earlier
822 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
823 versions have a bug (CVE-2011-4576) in which their block cipher
824 padding includes uninitialized data, potentially leaking sensitive
825 information to any peer with whom they make a SSLv3 connection. Tor
826 does not use SSL v3 by default, but a hostile client or server
827 could force an SSLv3 connection in order to gain information that
828 they shouldn't have been able to get. The best solution here is to
829 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
830 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
831 to make sure that the bug can't happen.
834 - Fix the SOCKET_OK test that we use to tell when socket
835 creation fails so that it works on Win64. Fixes part of bug 4533;
836 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
837 - Correct our replacements for the timeradd() and timersub() functions
838 on platforms that lack them (for example, Windows). The timersub()
839 function is used when expiring circuits, while timeradd() is
840 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
841 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
842 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
843 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
844 bug at runtime, not compile time, because some distributions hack
845 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
846 on 0.2.3.9-alpha. Found by Pascal.
848 o Minor features (controller):
849 - Use absolute path names when reporting the torrc filename in the
850 control protocol, so a controller can more easily find the torrc
851 file. Resolves bug 1101.
852 - Extend the control protocol to report flags that control a circuit's
853 path selection in CIRC events and in replies to 'GETINFO
854 circuit-status'. Implements part of ticket 2411.
855 - Extend the control protocol to report the hidden service address
856 and current state of a hidden-service-related circuit in CIRC
857 events and in replies to 'GETINFO circuit-status'. Implements part
859 - When reporting the path to the cookie file to the controller,
860 give an absolute path. Resolves ticket 4881.
861 - Allow controllers to request an event notification whenever a
862 circuit is cannibalized or its purpose is changed. Implements
864 - Include the creation time of a circuit in CIRC and CIRC2
865 control-port events and the list produced by the 'GETINFO
866 circuit-status' control-port command.
868 o Minor features (directory authorities):
869 - Directory authorities now reject versions of Tor older than
870 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
871 inclusive. These versions accounted for only a small fraction of
872 the Tor network, and have numerous known security issues. Resolves
874 - Authority operators can now vote for all relays in a given
875 set of countries to be BadDir/BadExit/Invalid/Rejected.
876 - Provide two consensus parameters (FastFlagMinThreshold and
877 FastFlagMaxThreshold) to control the range of allowable bandwidths
878 for the Fast directory flag. These allow authorities to run
879 experiments on appropriate requirements for being a "Fast" node.
880 The AuthDirFastGuarantee config value still applies.
881 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
882 directory authority option (introduced in Tor 0.2.2.34).
884 o Minor features (other):
885 - Don't disable the DirPort when we cannot exceed our AccountingMax
886 limit during this interval because the effective bandwidthrate is
887 low enough. This is useful in a situation where AccountMax is only
888 used as an additional safeguard or to provide statistics.
889 - Prepend an informative header to generated dynamic_dh_params files.
890 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
891 EntryNodes will have no effect. Resolves issue 2571.
892 - Log more useful messages when we fail to disable debugger
894 - Log which authority we're missing votes from when we go to fetch
895 them from the other auths.
896 - Log (at debug level) whenever a circuit's purpose is changed.
897 - Add missing documentation for the MaxClientCircuitsPending,
898 UseMicrodescriptors, UserspaceIOCPBuffers, and
899 _UseFilteringSSLBufferevents options, all introduced during
901 - Update to the January 3 2012 Maxmind GeoLite Country database.
903 o Minor bugfixes (hidden services):
904 - Don't close hidden service client circuits which have almost
905 finished connecting to their destination when they reach
906 the normal circuit-build timeout. Previously, we would close
907 introduction circuits which are waiting for an acknowledgement
908 from the introduction point, and rendezvous circuits which have
909 been specified in an INTRODUCE1 cell sent to a hidden service,
910 after the normal CBT. Now, we mark them as 'timed out', and launch
911 another rendezvous attempt in parallel. This behavior change can
912 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
913 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
914 - Don't close hidden-service-side rendezvous circuits when they
915 reach the normal circuit-build timeout. This behaviour change can
916 be disabled using the new
917 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
918 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
919 - Make sure we never mark the wrong rendezvous circuit as having
920 had its introduction cell acknowleged by the introduction-point
921 relay. Previously, when we received an INTRODUCE_ACK cell on a
922 client-side hidden-service introduction circuit, we might have
923 marked a rendezvous circuit other than the one we specified in
924 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
925 a warning message and interfered with the hidden service
926 connection-establishment process. Fixes bug 4759; bugfix on
927 0.2.3.3-alpha, when we added the stream-isolation feature which
928 might cause Tor to open multiple rendezvous circuits for the same
930 - Don't trigger an assertion failure when we mark a new client-side
931 hidden-service introduction circuit for close during the process
932 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
935 o Minor bugfixes (log messages):
936 - Correctly spell "connect" in a log message on failure to create a
937 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
939 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
940 Fixes bug 4856; bugfix on Tor 0.0.6.
941 - Fix the log message describing how we work around discovering
942 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
943 4837; bugfix on 0.2.2.9-alpha.
944 - When logging about a disallowed .exit name, do not also call it
945 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
947 o Minor bugfixes (build fixes):
948 - During configure, detect when we're building with clang version
949 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
950 CFLAGS. clang doesn't support them yet.
951 - During configure, search for library containing cos function as
952 libm lives in libcore on some platforms (BeOS/Haiku). Linking
953 against libm was hard-coded before. Fixes the first part of bug
954 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
956 - Detect attempts to build Tor on (as yet hypothetical) versions
957 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
958 fix for bug 4533. Bugfix on 0.2.2.28-beta.
959 - Preprocessor directives should not be put inside the arguments
960 of a macro. This would break compilation with GCC releases prior
961 to version 3.3. We would never recommend such an old GCC version,
962 but it is apparently required for binary compatibility on some
963 platforms (namely, certain builds of Haiku). Fixes the other part
964 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
967 o Minor bugfixes (other):
968 - Older Linux kernels erroneously respond to strange nmap behavior
969 by having accept() return successfully with a zero-length
970 socket. When this happens, just close the connection. Previously,
971 we would try harder to learn the remote address: but there was
972 no such remote address to learn, and our method for trying to
973 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
974 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
975 - Fix null-pointer access that could occur if TLS allocation failed.
976 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
977 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
978 accidentally been reverted.
979 - Fix our implementation of crypto_random_hostname() so it can't
980 overflow on ridiculously large inputs. (No Tor version has ever
981 provided this kind of bad inputs, but let's be correct in depth.)
982 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
983 - Find more places in the code that should have been testing for
984 invalid sockets using the SOCKET_OK macro. Required for a fix
985 for bug 4533. Bugfix on 0.2.2.28-beta.
986 - Fix an assertion failure when, while running with bufferevents, a
987 connection finishes connecting after it is marked for close, but
988 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
989 - test_util_spawn_background_ok() hardcoded the expected value
990 for ENOENT to 2. This isn't portable as error numbers are
991 platform specific, and particularly the hurd has ENOENT at
992 0x40000002. Construct expected string at runtime, using the correct
993 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
994 - Reject attempts to disable DisableDebuggerAttachment while Tor is
995 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
996 - Use an appropriate-width type for sockets in tor-fw-helper on
997 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1000 - When sending or relaying a RELAY_EARLY cell, we used to convert
1001 it to a RELAY cell if the connection was using the v1 link
1002 protocol. This was a workaround for older versions of Tor, which
1003 didn't handle RELAY_EARLY cells properly. Now that all supported
1004 versions can handle RELAY_EARLY cells, and now that we're enforcing
1005 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1006 remove this workaround. Addresses bug 4786.
1008 o Code simplifications and refactoring:
1009 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1010 own homebrewed ssl_state_to_string() replacement. Patch from
1011 Emile Snyder. Fixes bug 4653.
1012 - Use macros to indicate OpenSSL versions, so we don't need to worry
1013 about accidental hexadecimal bit shifts.
1014 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1016 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1017 - Use the smartlist_add_asprintf() alias more consistently.
1018 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1019 invalid value, rather than just -1.
1020 - Rename a handful of old identifiers, mostly related to crypto
1021 structures and crypto functions. By convention, our "create an
1022 object" functions are called "type_new()", our "free an object"
1023 functions are called "type_free()", and our types indicate that
1024 they are types only with a final "_t". But a handful of older
1025 types and functions broke these rules, with function names like
1026 "type_create" or "subsystem_op_type", or with type names like
1030 Changes in version 0.2.3.10-alpha - 2011-12-16
1031 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1032 Tor's buffers code. Absolutely everybody should upgrade.
1034 The bug relied on an incorrect calculation when making data continuous
1035 in one of our IO buffers, if the first chunk of the buffer was
1036 misaligned by just the wrong amount. The miscalculation would allow an
1037 attacker to overflow a piece of heap-allocated memory. To mount this
1038 attack, the attacker would need to either open a SOCKS connection to
1039 Tor's SocksPort (usually restricted to localhost), or target a Tor
1040 instance configured to make its connections through a SOCKS proxy
1041 (which Tor does not do by default).
1043 Good security practice requires that all heap-overflow bugs should be
1044 presumed to be exploitable until proven otherwise, so we are treating
1045 this as a potential code execution attack. Please upgrade immediately!
1046 This bug does not affect bufferevents-based builds of Tor. Special
1047 thanks to "Vektor" for reporting this issue to us!
1049 This release also contains a few minor bugfixes for issues discovered
1053 - Fix a heap overflow bug that could occur when trying to pull
1054 data into the first chunk of a buffer, when that chunk had
1055 already had some data drained from it. Fixes CVE-2011-2778;
1056 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1059 - If we can't attach streams to a rendezvous circuit when we
1060 finish connecting to a hidden service, clear the rendezvous
1061 circuit's stream-isolation state and try to attach streams
1062 again. Previously, we cleared rendezvous circuits' isolation
1063 state either too early (if they were freshly built) or not at all
1064 (if they had been built earlier and were cannibalized). Bugfix on
1065 0.2.3.3-alpha; fixes bug 4655.
1066 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1067 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1068 - Fix an assertion failure when a relay with accounting enabled
1069 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1072 - Update to the December 6 2011 Maxmind GeoLite Country database.
1075 Changes in version 0.2.2.35 - 2011-12-16
1076 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1077 buffers code. Absolutely everybody should upgrade.
1079 The bug relied on an incorrect calculation when making data continuous
1080 in one of our IO buffers, if the first chunk of the buffer was
1081 misaligned by just the wrong amount. The miscalculation would allow an
1082 attacker to overflow a piece of heap-allocated memory. To mount this
1083 attack, the attacker would need to either open a SOCKS connection to
1084 Tor's SocksPort (usually restricted to localhost), or target a Tor
1085 instance configured to make its connections through a SOCKS proxy
1086 (which Tor does not do by default).
1088 Good security practice requires that all heap-overflow bugs should be
1089 presumed to be exploitable until proven otherwise, so we are treating
1090 this as a potential code execution attack. Please upgrade immediately!
1091 This bug does not affect bufferevents-based builds of Tor. Special
1092 thanks to "Vektor" for reporting this issue to us!
1094 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1095 crash bugs for unusual configurations, and a long-term bug that
1096 would prevent Tor from starting on Windows machines with draconian
1099 With this release, we remind everyone that 0.2.0.x has reached its
1100 formal end-of-life. Those Tor versions have many known flaws, and
1101 nobody should be using them. You should upgrade -- ideally to the
1102 0.2.2.x series. If you're using a Linux or BSD and its packages are
1103 obsolete, stop using those packages and upgrade anyway.
1105 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1106 longer receive support after some time in early 2012.
1109 - Fix a heap overflow bug that could occur when trying to pull
1110 data into the first chunk of a buffer, when that chunk had
1111 already had some data drained from it. Fixes CVE-2011-2778;
1112 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1113 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1114 that it doesn't attempt to allocate a socketpair. This could cause
1115 some problems on Windows systems with overzealous firewalls. Fix for
1116 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1118 - If we mark an OR connection for close based on a cell we process,
1119 don't process any further cells on it. We already avoid further
1120 reads on marked-for-close connections, but now we also discard the
1121 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1122 which was the first version where we might mark a connection for
1123 close based on processing a cell on it.
1124 - Correctly sanity-check that we don't underflow on a memory
1125 allocation (and then assert) for hidden service introduction
1126 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1127 bugfix on 0.2.1.5-alpha.
1128 - Fix a memory leak when we check whether a hidden service
1129 descriptor has any usable introduction points left. Fixes bug
1130 4424. Bugfix on 0.2.2.25-alpha.
1131 - Don't crash when we're running as a relay and don't have a GeoIP
1132 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1133 we've had in the 0.2.3.x branch already.
1134 - When running as a client, do not print a misleading (and plain
1135 wrong) log message that we're collecting "directory request"
1136 statistics: clients don't collect statistics. Also don't create a
1137 useless (because empty) stats file in the stats/ directory. Fixes
1138 bug 4353; bugfix on 0.2.2.34.
1141 - Detect failure to initialize Libevent. This fix provides better
1142 detection for future instances of bug 4457.
1143 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1144 function. This was eating up hideously large amounts of time on some
1145 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1146 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1147 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1149 - Don't warn about unused log_mutex in log.c when building with
1150 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1151 0.1.0.6-rc which introduced --disable-threads.
1152 - When configuring, starting, or stopping an NT service, stop
1153 immediately after the service configuration attempt has succeeded
1154 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1155 - When sending a NETINFO cell, include the original address
1156 received for the other side, not its canonical address. Found
1157 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1158 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1159 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1160 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1161 occurred when a client tried to fetch a descriptor for a bridge
1162 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1163 - Backport fixes for a pair of compilation warnings on Windows.
1164 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1165 - If we had ever tried to call tor_addr_to_str on an address of
1166 unknown type, we would have done a strdup on an uninitialized
1167 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1168 Reported by "troll_un".
1169 - Correctly detect and handle transient lookup failures from
1170 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1171 Reported by "troll_un".
1172 - Fix null-pointer access that could occur if TLS allocation failed.
1173 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1174 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1175 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1178 - Add two new config options for directory authorities:
1179 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1180 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1181 that is always sufficient to satisfy the bandwidth requirement for
1182 the Guard flag. Now it will be easier for researchers to simulate
1183 Tor networks with different values. Resolves ticket 4484.
1184 - When Tor ignores a hidden service specified in its configuration,
1185 include the hidden service's directory in the warning message.
1186 Previously, we would only tell the user that some hidden service
1187 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1188 - Update to the December 6 2011 Maxmind GeoLite Country database.
1190 o Packaging changes:
1191 - Make it easier to automate expert package builds on Windows,
1192 by removing an absolute path from makensis.exe command.
1195 Changes in version 0.2.3.9-alpha - 2011-12-08
1196 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1197 a "DisableNetwork" security feature that bundles can use to avoid
1198 touching the network until bridges are configured, moves forward on
1199 the pluggable transport design, fixes a flaw in the hidden service
1200 design that unnecessarily prevented clients with wrong clocks from
1201 reaching hidden services, and fixes a wide variety of other issues.
1204 - Clients can now connect to private bridges over IPv6. Bridges
1205 still need at least one IPv4 address in order to connect to
1206 other relays. Note that we don't yet handle the case where the
1207 user has two bridge lines for the same bridge (one IPv4, one
1208 IPv6). Implements parts of proposal 186.
1209 - New "DisableNetwork" config option to prevent Tor from launching any
1210 connections or accepting any connections except on a control port.
1211 Bundles and controllers can set this option before letting Tor talk
1212 to the rest of the network, for example to prevent any connections
1213 to a non-bridge address. Packages like Orbot can also use this
1214 option to instruct Tor to save power when the network is off.
1215 - Clients and bridges can now be configured to use a separate
1216 "transport" proxy. This approach makes the censorship arms race
1217 easier by allowing bridges to use protocol obfuscation plugins. It
1218 implements the "managed proxy" part of proposal 180 (ticket 3472).
1219 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1220 implementation. It makes AES_CTR about 7% faster than our old one
1221 (which was about 10% faster than the one OpenSSL used to provide).
1222 Resolves ticket 4526.
1223 - Add a "tor2web mode" for clients that want to connect to hidden
1224 services non-anonymously (and possibly more quickly). As a safety
1225 measure to try to keep users from turning this on without knowing
1226 what they are doing, tor2web mode must be explicitly enabled at
1227 compile time, and a copy of Tor compiled to run in tor2web mode
1228 cannot be used as a normal Tor client. Implements feature 2553.
1229 - Add experimental support for running on Windows with IOCP and no
1230 kernel-space socket buffers. This feature is controlled by a new
1231 "UserspaceIOCPBuffers" config option (off by default), which has
1232 no effect unless Tor has been built with support for bufferevents,
1233 is running on Windows, and has enabled IOCP. This may, in the long
1234 run, help solve or mitigate bug 98.
1235 - Use a more secure consensus parameter voting algorithm. Now at
1236 least three directory authorities or a majority of them must
1237 vote on a given parameter before it will be included in the
1238 consensus. Implements proposal 178.
1241 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1242 They used to check that the timestamp was within 30 minutes
1243 of their system clock, so they could cap the size of their
1244 replay-detection cache, but that approach unnecessarily refused
1245 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1246 the v3 intro-point protocol (the first one which sent a timestamp
1247 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1248 - Only use the EVP interface when AES acceleration is enabled,
1249 to avoid a 5-7% performance regression. Resolves issue 4525;
1250 bugfix on 0.2.3.8-alpha.
1252 o Privacy/anonymity features (bridge detection):
1253 - Make bridge SSL certificates a bit more stealthy by using random
1254 serial numbers, in the same fashion as OpenSSL when generating
1255 self-signed certificates. Implements ticket 4584.
1256 - Introduce a new config option "DynamicDHGroups", enabled by
1257 default, which provides each bridge with a unique prime DH modulus
1258 to be used during SSL handshakes. This option attempts to help
1259 against censors who might use the Apache DH modulus as a static
1260 identifier for bridges. Addresses ticket 4548.
1262 o Minor features (new/different config options):
1263 - New configuration option "DisableDebuggerAttachment" (on by default)
1264 to prevent basic debugging attachment attempts by other processes.
1265 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1266 - Allow MapAddress directives to specify matches against super-domains,
1267 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1268 Implements issue 933.
1269 - Slightly change behavior of "list" options (that is, config
1270 options that can appear more than once) when they appear both in
1271 torrc and on the command line. Previously, the command-line options
1272 would be appended to the ones from torrc. Now, the command-line
1273 options override the torrc options entirely. This new behavior
1274 allows the user to override list options (like exit policies and
1275 ports to listen on) from the command line, rather than simply
1276 appending to the list.
1277 - You can get the old (appending) command-line behavior for "list"
1278 options by prefixing the option name with a "+".
1279 - You can remove all the values for a "list" option from the command
1280 line without adding any new ones by prefixing the option name
1282 - Add experimental support for a "defaults" torrc file to be parsed
1283 before the regular torrc. Torrc options override the defaults file's
1284 options in the same way that the command line overrides the torrc.
1285 The SAVECONF controller command saves only those options which
1286 differ between the current configuration and the defaults file. HUP
1287 reloads both files. (Note: This is an experimental feature; its
1288 behavior will probably be refined in future 0.2.3.x-alpha versions
1289 to better meet packagers' needs.) Implements task 4552.
1292 - Try to make the introductory warning message that Tor prints on
1293 startup more useful for actually finding help and information.
1294 Resolves ticket 2474.
1295 - Running "make version" now displays the version of Tor that
1296 we're about to build. Idea from katmagic; resolves issue 4400.
1297 - Expire old or over-used hidden service introduction points.
1298 Required by fix for bug 3460.
1299 - Move the replay-detection cache for the RSA-encrypted parts of
1300 INTRODUCE2 cells to the introduction point data structures.
1301 Previously, we would use one replay-detection cache per hidden
1302 service. Required by fix for bug 3460.
1303 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1304 public key replay-detection cache from 60 minutes to 5 minutes. This
1305 replay-detection cache is now used only to detect multiple
1306 INTRODUCE2 cells specifying the same rendezvous point, so we can
1307 avoid launching multiple simultaneous attempts to connect to it.
1309 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1310 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1311 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1313 - Fix a minor formatting issue in one of tor-gencert's error messages.
1315 - Prevent a false positive from the check-spaces script, by disabling
1316 the "whitespace between function name and (" check for functions
1318 - Fix a log message suggesting that people contact a non-existent
1319 email address. Fixes bug 3448.
1320 - Fix null-pointer access that could occur if TLS allocation failed.
1321 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1322 - Report a real bootstrap problem to the controller on router
1323 identity mismatch. Previously we just said "foo", which probably
1324 made a lot of sense at the time. Fixes bug 4169; bugfix on
1326 - If we had ever tried to call tor_addr_to_str() on an address of
1327 unknown type, we would have done a strdup() on an uninitialized
1328 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1329 Reported by "troll_un".
1330 - Correctly detect and handle transient lookup failures from
1331 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1332 Reported by "troll_un".
1333 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1334 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1335 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1336 bug 4532; found by "troll_un".
1338 o Minor bugfixes (on Tor 0.2.3.x):
1339 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1341 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1342 circuit for use as a hidden service client's rendezvous point.
1343 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1344 with help from wanoskarnet.
1345 - Restore behavior of overriding SocksPort, ORPort, and similar
1346 options from the command line. Bugfix on 0.2.3.3-alpha.
1349 - Properly handle the case where the build-tree is not the same
1350 as the source tree when generating src/common/common_sha1.i,
1351 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1352 bugfix on 0.2.0.1-alpha.
1354 o Code simplifications, cleanups, and refactorings:
1355 - Remove the pure attribute from all functions that used it
1356 previously. In many cases we assigned it incorrectly, because the
1357 functions might assert or call impure functions, and we don't have
1358 evidence that keeping the pure attribute is worthwhile. Implements
1359 changes suggested in ticket 4421.
1360 - Remove some dead code spotted by coverity. Fixes cid 432.
1361 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1364 Changes in version 0.2.3.8-alpha - 2011-11-22
1365 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1366 socketpair-related bug that has been bothering Windows users. It adds
1367 support to serve microdescriptors to controllers, so Vidalia's network
1368 map can resume listing relays (once Vidalia implements its side),
1369 and adds better support for hardware AES acceleration. Finally, it
1370 starts the process of adjusting the bandwidth cutoff for getting the
1371 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1372 that tiny relays harm performance more than they help network capacity.
1375 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1376 that it doesn't attempt to allocate a socketpair. This could cause
1377 some problems on Windows systems with overzealous firewalls. Fix for
1378 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1380 - Correctly sanity-check that we don't underflow on a memory
1381 allocation (and then assert) for hidden service introduction
1382 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1383 bugfix on 0.2.1.5-alpha.
1384 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1385 flag. In the past few years the average relay speed has picked
1386 up, and while the "top 7/8 of the network get the Fast flag" and
1387 "all relays with 20KB or more of capacity get the Fast flag" rules
1388 used to have the same result, now the top 7/8 of the network has
1389 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1390 - Fix a rare assertion failure when checking whether a v0 hidden
1391 service descriptor has any usable introduction points left, and
1392 we don't have enough information to build a circuit to the first
1393 intro point named in the descriptor. The HS client code in
1394 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1395 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1396 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1397 - Make bridge authorities not crash when they are asked for their own
1398 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1399 - When running as a client, do not print a misleading (and plain
1400 wrong) log message that we're collecting "directory request"
1401 statistics: clients don't collect statistics. Also don't create a
1402 useless (because empty) stats file in the stats/ directory. Fixes
1403 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1406 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1407 for a relay by identity digest or nickname. Previously,
1408 microdescriptors were only available by their own digests, so a
1409 controller would have to ask for and parse the whole microdescriptor
1410 consensus in order to look up a single relay's microdesc. Fixes
1411 bug 3832; bugfix on 0.2.3.1-alpha.
1412 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1413 operations can use hardware acceleration (if present). Resolves
1416 o Minor bugfixes (on 0.2.2.x and earlier):
1417 - Detect failure to initialize Libevent. This fix provides better
1418 detection for future instances of bug 4457.
1419 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1420 function. This was eating up hideously large amounts of time on some
1421 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1422 - Don't warn about unused log_mutex in log.c when building with
1423 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1424 0.1.0.6-rc which introduced --disable-threads.
1425 - Allow manual 'authenticate' commands to the controller interface
1426 from netcat (nc) as well as telnet. We were rejecting them because
1427 they didn't come with the expected whitespace at the end of the
1428 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1429 - Fix some (not actually triggerable) buffer size checks in usage of
1430 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1432 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1433 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1434 - When configuring, starting, or stopping an NT service, stop
1435 immediately after the service configuration attempt has succeeded
1436 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1437 - When sending a NETINFO cell, include the original address
1438 received for the other side, not its canonical address. Found
1439 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1440 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1441 can pick them up when the tests aren't disabled. Bugfix on
1442 0.2.2.4-alpha which introduced tinytest.
1443 - Fix a memory leak when we check whether a hidden service
1444 descriptor has any usable introduction points left. Fixes bug
1445 4424. Bugfix on 0.2.2.25-alpha.
1446 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1447 occurred when a client tried to fetch a descriptor for a bridge
1448 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1450 o Minor bugfixes (on 0.2.3.x):
1451 - Make util unit tests build correctly with MSVC. Bugfix on
1452 0.2.3.3-alpha. Patch by Gisle Vanem.
1453 - Successfully detect AUTH_CHALLENGE cells with no recognized
1454 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
1456 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
1457 it should still send a NETINFO cell to allow the connection to
1458 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
1460 - Log less loudly when we get an invalid authentication certificate
1461 from a source other than a directory authority: it's not unusual
1462 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
1464 - Tolerate servers with more clock skew in their authentication
1465 certificates than previously. Fixes bug 4371; bugfix on
1467 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
1468 on 0.2.3.4-alpha and 0.2.3.6-alpha.
1471 - Add two new config options for directory authorities:
1472 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1473 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1474 that is always sufficient to satisfy the bandwidth requirement for
1475 the Guard flag. Now it will be easier for researchers to simulate
1476 Tor networks with different values. Resolves ticket 4484.
1477 - When Tor ignores a hidden service specified in its configuration,
1478 include the hidden service's directory in the warning message.
1479 Previously, we would only tell the user that some hidden service
1480 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1481 - When we fail to initialize Libevent, retry with IOCP disabled so we
1482 don't need to turn on multi-threading support in Libevent, which in
1483 turn requires a working socketpair(). This is a workaround for bug
1484 4457, which affects Libevent versions from 2.0.1-alpha through
1486 - Detect when we try to build on a platform that doesn't define
1487 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1488 - Update to the November 1 2011 Maxmind GeoLite Country database.
1490 o Packaging changes:
1491 - Make it easier to automate expert package builds on Windows,
1492 by removing an absolute path from makensis.exe command.
1494 o Code simplifications and refactoring:
1495 - Remove some redundant #include directives throughout the code.
1496 Patch from Andrea Gelmini.
1497 - Unconditionally use OpenSSL's AES implementation instead of our
1498 old built-in one. OpenSSL's AES has been better for a while, and
1499 relatively few servers should still be on any version of OpenSSL
1500 that doesn't have good optimized assembly AES.
1501 - Use the name "CERTS" consistently to refer to the new cell type;
1502 we were calling it CERT in some places and CERTS in others.
1505 - Numerous new unit tests for functions in util.c and address.c by
1507 - The long-disabled benchmark tests are now split into their own
1508 ./src/test/bench binary.
1509 - The benchmark tests can now use more accurate timers than
1510 gettimeofday() when such timers are available.
1513 Changes in version 0.2.3.7-alpha - 2011-10-30
1514 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1515 the new v3 handshake. It also resolves yet another bridge address
1519 - If we mark an OR connection for close based on a cell we process,
1520 don't process any further cells on it. We already avoid further
1521 reads on marked-for-close connections, but now we also discard the
1522 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1523 which was the first version where we might mark a connection for
1524 close based on processing a cell on it.
1525 - Fix a double-free bug that would occur when we received an invalid
1526 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1527 bugfix on 0.2.3.6-alpha.
1528 - Bridges no longer include their address in NETINFO cells on outgoing
1529 OR connections, to allow them to blend in better with clients.
1530 Removes another avenue for enumerating bridges. Reported by
1531 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1532 cells were introduced.
1535 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1536 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1539 Changes in version 0.2.3.6-alpha - 2011-10-26
1540 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1541 anonymity vulnerability where an attacker can deanonymize Tor
1542 users. Everybody should upgrade.
1544 This release also features support for a new v3 connection handshake
1545 protocol, and fixes to make hidden service connections more robust.
1548 - Implement a new handshake protocol (v3) for authenticating Tors to
1549 each other over TLS. It should be more resistant to fingerprinting
1550 than previous protocols, and should require less TLS hacking for
1551 future Tor implementations. Implements proposal 176.
1552 - Allow variable-length padding cells to disguise the length of
1553 Tor's TLS records. Implements part of proposal 184.
1555 o Privacy/anonymity fixes (clients):
1556 - Clients and bridges no longer send TLS certificate chains on
1557 outgoing OR connections. Previously, each client or bridge would
1558 use the same cert chain for all outgoing OR connections until
1559 its IP address changes, which allowed any relay that the client
1560 or bridge contacted to determine which entry guards it is using.
1561 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1562 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1563 no longer considers that connection as suitable for satisfying a
1564 circuit EXTEND request. Now relays can protect clients from the
1565 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1566 - Directory authorities no longer assign the Guard flag to relays
1567 that haven't upgraded to the above "refuse EXTEND requests
1568 to client connections" fix. Now directory authorities can
1569 protect clients from the CVE-2011-2768 issue even if neither
1570 the clients nor the relays have upgraded yet. There's a new
1571 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1572 to let us transition smoothly, else tomorrow there would be no
1575 o Major bugfixes (hidden services):
1576 - Improve hidden service robustness: when an attempt to connect to
1577 a hidden service ends, be willing to refetch its hidden service
1578 descriptors from each of the HSDir relays responsible for them
1579 immediately. Previously, we would not consider refetching the
1580 service's descriptors from each HSDir for 15 minutes after the last
1581 fetch, which was inconvenient if the hidden service was not running
1582 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1583 - When one of a hidden service's introduction points appears to be
1584 unreachable, stop trying it. Previously, we would keep trying
1585 to build circuits to the introduction point until we lost the
1586 descriptor, usually because the user gave up and restarted Tor.
1587 Partly fixes bug 3825.
1588 - Don't launch a useless circuit after failing to use one of a
1589 hidden service's introduction points. Previously, we would
1590 launch a new introduction circuit, but not set the hidden service
1591 which that circuit was intended to connect to, so it would never
1592 actually be used. A different piece of code would then create a
1593 new introduction circuit correctly. Bug reported by katmagic and
1594 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1596 o Major bugfixes (other):
1597 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1598 that they initiated. Relays could distinguish incoming bridge
1599 connections from client connections, creating another avenue for
1600 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1601 Found by "frosty_un".
1602 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1603 tor gets started. This prevents a wrong average bandwidth
1604 estimate, which would cause relays to always start a new accounting
1605 interval at the earliest possible moment. Fixes bug 2003; bugfix
1606 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1607 immensely in tracking this bug down.
1608 - Fix a crash bug when changing node restrictions while a DNS lookup
1609 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1612 o Minor bugfixes (on 0.2.2.x and earlier):
1613 - When a hidden service turns an extra service-side introduction
1614 circuit into a general-purpose circuit, free the rend_data and
1615 intro_key fields first, so we won't leak memory if the circuit
1616 is cannibalized for use as another service-side introduction
1617 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1618 - Rephrase the log message emitted if the TestSocks check is
1619 successful. Patch from Fabian Keil; fixes bug 4094.
1620 - Bridges now skip DNS self-tests, to act a little more stealthily.
1621 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1622 bridges. Patch by "warms0x".
1623 - Remove a confusing dollar sign from the example fingerprint in the
1624 man page, and also make the example fingerprint a valid one. Fixes
1625 bug 4309; bugfix on 0.2.1.3-alpha.
1626 - Fix internal bug-checking logic that was supposed to catch
1627 failures in digest generation so that it will fail more robustly
1628 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1629 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1630 - Report any failure in init_keys() calls launched because our
1631 IP address has changed. Spotted by Coverity Scan. Bugfix on
1632 0.1.1.4-alpha; fixes CID 484.
1634 o Minor bugfixes (on 0.2.3.x):
1635 - Fix a bug in configure.in that kept it from building a configure
1636 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1637 bugfix on 0.2.3.1-alpha.
1638 - Don't warn users that they are exposing a client port to the
1639 Internet if they have specified an RFC1918 address. Previously,
1640 we would warn if the user had specified any non-loopback
1641 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1642 - Fix memory leaks in the failing cases of the new SocksPort and
1643 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1644 fixes coverity CIDs 485, 486, and 487.
1647 - When a hidden service's introduction point times out, consider
1648 trying it again during the next attempt to connect to the
1649 HS. Previously, we would not try it again unless a newly fetched
1650 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1651 - The next version of Windows will be called Windows 8, and it has
1652 a major version of 6, minor version of 2. Correctly identify that
1653 version instead of calling it "Very recent version". Resolves
1654 ticket 4153; reported by funkstar.
1655 - The Bridge Authority now writes statistics on how many bridge
1656 descriptors it gave out in total, and how many unique descriptors
1657 it gave out. It also lists how often the most and least commonly
1658 fetched descriptors were given out, as well as the median and
1659 25th/75th percentile. Implements tickets 4200 and 4294.
1660 - Update to the October 4 2011 Maxmind GeoLite Country database.
1662 o Code simplifications and refactoring:
1663 - Remove some old code to remember statistics about which descriptors
1664 we've served as a directory mirror. The feature wasn't used and
1665 is outdated now that microdescriptors are around.
1666 - Rename Tor functions that turn strings into addresses, so that
1667 "parse" indicates that no hostname resolution occurs, and
1668 "lookup" indicates that hostname resolution may occur. This
1669 should help prevent mistakes in the future. Fixes bug 3512.
1672 Changes in version 0.2.2.34 - 2011-10-26
1673 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1674 can deanonymize Tor users. Everybody should upgrade.
1676 The attack relies on four components: 1) Clients reuse their TLS cert
1677 when talking to different relays, so relays can recognize a user by
1678 the identity key in her cert. 2) An attacker who knows the client's
1679 identity key can probe each guard relay to see if that identity key
1680 is connected to that guard relay right now. 3) A variety of active
1681 attacks in the literature (starting from "Low-Cost Traffic Analysis
1682 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1683 discover the guard relays that a Tor user visiting the website is using.
1684 4) Clients typically pick three guards at random, so the set of guards
1685 for a given user could well be a unique fingerprint for her. This
1686 release fixes components #1 and #2, which is enough to block the attack;
1687 the other two remain as open research problems. Special thanks to
1688 "frosty_un" for reporting the issue to us!
1690 Clients should upgrade so they are no longer recognizable by the TLS
1691 certs they present. Relays should upgrade so they no longer allow a
1692 remote attacker to probe them to test whether unpatched clients are
1693 currently connected to them.
1695 This release also fixes several vulnerabilities that allow an attacker
1696 to enumerate bridge relays. Some bridge enumeration attacks still
1697 remain; see for example proposal 188.
1699 o Privacy/anonymity fixes (clients):
1700 - Clients and bridges no longer send TLS certificate chains on
1701 outgoing OR connections. Previously, each client or bridge would
1702 use the same cert chain for all outgoing OR connections until
1703 its IP address changes, which allowed any relay that the client
1704 or bridge contacted to determine which entry guards it is using.
1705 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1706 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1707 no longer considers that connection as suitable for satisfying a
1708 circuit EXTEND request. Now relays can protect clients from the
1709 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1710 - Directory authorities no longer assign the Guard flag to relays
1711 that haven't upgraded to the above "refuse EXTEND requests
1712 to client connections" fix. Now directory authorities can
1713 protect clients from the CVE-2011-2768 issue even if neither
1714 the clients nor the relays have upgraded yet. There's a new
1715 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1716 to let us transition smoothly, else tomorrow there would be no
1719 o Privacy/anonymity fixes (bridge enumeration):
1720 - Bridge relays now do their directory fetches inside Tor TLS
1721 connections, like all the other clients do, rather than connecting
1722 directly to the DirPort like public relays do. Removes another
1723 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1724 - Bridges relays now build circuits for themselves in a more similar
1725 way to how clients build them. Removes another avenue for
1726 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1727 when bridges were introduced.
1728 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1729 that they initiated. Relays could distinguish incoming bridge
1730 connections from client connections, creating another avenue for
1731 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1732 Found by "frosty_un".
1735 - Fix a crash bug when changing node restrictions while a DNS lookup
1736 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1738 - Don't launch a useless circuit after failing to use one of a
1739 hidden service's introduction points. Previously, we would
1740 launch a new introduction circuit, but not set the hidden service
1741 which that circuit was intended to connect to, so it would never
1742 actually be used. A different piece of code would then create a
1743 new introduction circuit correctly. Bug reported by katmagic and
1744 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1747 - Change an integer overflow check in the OpenBSD_Malloc code so
1748 that GCC is less likely to eliminate it as impossible. Patch
1749 from Mansour Moufid. Fixes bug 4059.
1750 - When a hidden service turns an extra service-side introduction
1751 circuit into a general-purpose circuit, free the rend_data and
1752 intro_key fields first, so we won't leak memory if the circuit
1753 is cannibalized for use as another service-side introduction
1754 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1755 - Bridges now skip DNS self-tests, to act a little more stealthily.
1756 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1757 bridges. Patch by "warms0x".
1758 - Fix internal bug-checking logic that was supposed to catch
1759 failures in digest generation so that it will fail more robustly
1760 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1761 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1762 - Report any failure in init_keys() calls launched because our
1763 IP address has changed. Spotted by Coverity Scan. Bugfix on
1764 0.1.1.4-alpha; fixes CID 484.
1766 o Minor bugfixes (log messages and documentation):
1767 - Remove a confusing dollar sign from the example fingerprint in the
1768 man page, and also make the example fingerprint a valid one. Fixes
1769 bug 4309; bugfix on 0.2.1.3-alpha.
1770 - The next version of Windows will be called Windows 8, and it has
1771 a major version of 6, minor version of 2. Correctly identify that
1772 version instead of calling it "Very recent version". Resolves
1773 ticket 4153; reported by funkstar.
1774 - Downgrade log messages about circuit timeout calibration from
1775 "notice" to "info": they don't require or suggest any human
1776 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1777 bugfix on 0.2.2.14-alpha.
1780 - Turn on directory request statistics by default and include them in
1781 extra-info descriptors. Don't break if we have no GeoIP database.
1782 Backported from 0.2.3.1-alpha; implements ticket 3951.
1783 - Update to the October 4 2011 Maxmind GeoLite Country database.
1786 Changes in version 0.2.1.31 - 2011-10-26
1787 Tor 0.2.1.31 backports important security and privacy fixes for
1788 oldstable. This release is intended only for package maintainers and
1789 others who cannot use the 0.2.2 stable series. All others should be
1790 using Tor 0.2.2.x or newer.
1792 o Security fixes (also included in 0.2.2.x):
1793 - Replace all potentially sensitive memory comparison operations
1794 with versions whose runtime does not depend on the data being
1795 compared. This will help resist a class of attacks where an
1796 adversary can use variations in timing information to learn
1797 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1798 implementation by Robert Ransom based partially on code by DJB.)
1799 - Fix an assert in parsing router descriptors containing IPv6
1800 addresses. This one took down the directory authorities when
1801 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1803 o Privacy/anonymity fixes (also included in 0.2.2.x):
1804 - Clients and bridges no longer send TLS certificate chains on
1805 outgoing OR connections. Previously, each client or bridge would
1806 use the same cert chain for all outgoing OR connections until
1807 its IP address changes, which allowed any relay that the client
1808 or bridge contacted to determine which entry guards it is using.
1809 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1810 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1811 no longer considers that connection as suitable for satisfying a
1812 circuit EXTEND request. Now relays can protect clients from the
1813 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1814 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1815 that they initiated. Relays could distinguish incoming bridge
1816 connections from client connections, creating another avenue for
1817 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1818 Found by "frosty_un".
1819 - When receiving a hidden service descriptor, check that it is for
1820 the hidden service we wanted. Previously, Tor would store any
1821 hidden service descriptors that a directory gave it, whether it
1822 wanted them or not. This wouldn't have let an attacker impersonate
1823 a hidden service, but it did let directories pre-seed a client
1824 with descriptors that it didn't want. Bugfix on 0.0.6.
1825 - Avoid linkability based on cached hidden service descriptors: forget
1826 all hidden service descriptors cached as a client when processing a
1827 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1828 - Make the bridge directory authority refuse to answer directory
1829 requests for "all" descriptors. It used to include bridge
1830 descriptors in its answer, which was a major information leak.
1831 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1832 - Don't attach new streams to old rendezvous circuits after SIGNAL
1833 NEWNYM. Previously, we would keep using an existing rendezvous
1834 circuit if it remained open (i.e. if it were kept open by a
1835 long-lived stream, or if a new stream were attached to it before
1836 Tor could notice that it was old and no longer in use). Bugfix on
1837 0.1.1.15-rc; fixes bug 3375.
1839 o Minor bugfixes (also included in 0.2.2.x):
1840 - When we restart our relay, we might get a successful connection
1841 from the outside before we've started our reachability tests,
1842 triggering a warning: "ORPort found reachable, but I have no
1843 routerinfo yet. Failing to inform controller of success." This
1844 bug was harmless unless Tor is running under a controller
1845 like Vidalia, in which case the controller would never get a
1846 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1848 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1849 enabled. Fixes bug 1526.
1850 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1851 anything since 0.2.1.16-rc.
1852 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1853 None of the cases where we did this before were wrong, but by making
1854 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1855 - Fix a rare crash bug that could occur when a client was configured
1856 with a large number of bridges. Fixes bug 2629; bugfix on
1857 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1858 - Correct the warning displayed when a rendezvous descriptor exceeds
1859 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1861 - Fix an uncommon assertion failure when running with DNSPort under
1862 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1863 - When warning about missing zlib development packages during compile,
1864 give the correct package names. Bugfix on 0.2.0.1-alpha.
1865 - Require that introduction point keys and onion keys have public
1866 exponent 65537. Bugfix on 0.2.0.10-alpha.
1867 - Do not crash when our configuration file becomes unreadable, for
1868 example due to a permissions change, between when we start up
1869 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1871 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1873 - Always NUL-terminate the sun_path field of a sockaddr_un before
1874 passing it to the kernel. (Not a security issue: kernels are
1875 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1876 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1877 - Don't stack-allocate the list of supplementary GIDs when we're
1878 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1879 could take up to 256K, which is way too much stack. Found by
1880 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1882 o Minor bugfixes (only in 0.2.1.x):
1883 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
1884 rely on them. Bugfix on 0.2.1.30.
1885 - Use git revisions instead of svn revisions when generating our
1886 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1888 o Minor features (also included in 0.2.2.x):
1889 - Adjust the expiration time on our SSL session certificates to
1890 better match SSL certs seen in the wild. Resolves ticket 4014.
1891 - Allow nameservers with IPv6 address. Resolves bug 2574.
1892 - Update to the October 4 2011 Maxmind GeoLite Country database.
1895 Changes in version 0.2.3.5-alpha - 2011-09-28
1896 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
1897 bridge relays; fixes an assertion error that many users started hitting
1898 today; and adds the ability to refill token buckets more often than
1899 once per second, allowing significant performance improvements.
1902 - Bridge relays now do their directory fetches inside Tor TLS
1903 connections, like all the other clients do, rather than connecting
1904 directly to the DirPort like public relays do. Removes another
1905 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1906 - Bridges relays now build circuits for themselves in a more similar
1907 way to how clients build them. Removes another avenue for
1908 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1909 when bridges were introduced.
1912 - Fix an "Assertion md->held_by_node == 1 failed" error that could
1913 occur when the same microdescriptor was referenced by two node_t
1914 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
1916 o Major features (networking):
1917 - Add a new TokenBucketRefillInterval option to refill token buckets
1918 more frequently than once per second. This should improve network
1919 performance, alleviate queueing problems, and make traffic less
1920 bursty. Implements proposal 183; closes ticket 3630. Design by
1921 Florian Tschorsch and Björn Scheuermann; implementation by
1925 - Change an integer overflow check in the OpenBSD_Malloc code so
1926 that GCC is less likely to eliminate it as impossible. Patch
1927 from Mansour Moufid. Fixes bug 4059.
1929 o Minor bugfixes (usability):
1930 - Downgrade log messages about circuit timeout calibration from
1931 "notice" to "info": they don't require or suggest any human
1932 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1933 bugfix on 0.2.2.14-alpha.
1935 o Minor features (diagnostics):
1936 - When the system call to create a listener socket fails, log the
1937 error message explaining why. This may help diagnose bug 4027.
1940 Changes in version 0.2.3.4-alpha - 2011-09-13
1941 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
1942 tweak to Tor's TLS handshake that makes relays and bridges that run
1943 this new version reachable from Iran again. It also fixes a few new
1944 bugs in 0.2.3.x, and teaches relays to recognize when they're not
1945 listed in the network consensus and republish.
1947 o Major bugfixes (also part of 0.2.2.33):
1948 - Avoid an assertion failure when reloading a configuration with
1949 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1950 3923; bugfix on 0.2.2.25-alpha.
1952 o Minor features (security, also part of 0.2.2.33):
1953 - Check for replays of the public-key encrypted portion of an
1954 INTRODUCE1 cell, in addition to the current check for replays of
1955 the g^x value. This prevents a possible class of active attacks
1956 by an attacker who controls both an introduction point and a
1957 rendezvous point, and who uses the malleability of AES-CTR to
1958 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1959 that these attacks is infeasible (requiring the attacker to send
1960 on the order of zettabytes of altered cells in a short interval),
1961 but we'd rather block them off in case there are any classes of
1962 this attack that we missed. Reported by Willem Pinckaers.
1964 o Minor features (also part of 0.2.2.33):
1965 - Adjust the expiration time on our SSL session certificates to
1966 better match SSL certs seen in the wild. Resolves ticket 4014.
1967 - Change the default required uptime for a relay to be accepted as
1968 a HSDir (hidden service directory) from 24 hours to 25 hours.
1969 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1970 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1971 authorities to abstain from voting on assignment of the HSDir
1972 consensus flag. Related to bug 2649.
1973 - Update to the September 6 2011 Maxmind GeoLite Country database.
1975 o Minor bugfixes (also part of 0.2.2.33):
1976 - Demote the 'replay detected' log message emitted when a hidden
1977 service receives the same Diffie-Hellman public key in two different
1978 INTRODUCE2 cells to info level. A normal Tor client can cause that
1979 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1980 fixes part of bug 2442.
1981 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1982 level. There is nothing that a hidden service's operator can do
1983 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1985 - Clarify a log message specifying the characters permitted in
1986 HiddenServiceAuthorizeClient client names. Previously, the log
1987 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1988 given the impression that every ASCII character between "+" and "_"
1989 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1991 o Build fixes (also part of 0.2.2.33):
1992 - Clean up some code issues that prevented Tor from building on older
1993 BSDs. Fixes bug 3894; reported by "grarpamp".
1994 - Search for a platform-specific version of "ar" when cross-compiling.
1995 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1998 - Fix a bug where the SocksPort option (for example) would get
1999 ignored and replaced by the default if a SocksListenAddress
2000 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2004 - Relays now try regenerating and uploading their descriptor more
2005 frequently if they are not listed in the consensus, or if the
2006 version of their descriptor listed in the consensus is too
2007 old. This fix should prevent situations where a server declines
2008 to re-publish itself because it has done so too recently, even
2009 though the authorities decided not to list its recent-enough
2010 descriptor. Fix for bug 3327.
2013 - Relays now include a reason for regenerating their descriptors
2014 in an HTTP header when uploading to the authorities. This will
2015 make it easier to debug descriptor-upload issues in the future.
2016 - When starting as root and then changing our UID via the User
2017 control option, and we have a ControlSocket configured, make sure
2018 that the ControlSocket is owned by the same account that Tor will
2019 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2022 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2023 utility function used in the control-port code). This shouldn't
2024 ever happen unless Tor is completely out of memory, but if it did
2025 happen and Tor somehow recovered from it, Tor could have sent a log
2026 message to a control port in the middle of a reply to a controller
2027 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2028 - Make 'FetchUselessDescriptors' cause all descriptor types and
2029 all consensus types (including microdescriptors) to get fetched.
2030 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2033 - Make a new "entry connection" struct as an internal subtype of "edge
2034 connection", to simplify the code and make exit connections smaller.
2037 Changes in version 0.2.2.33 - 2011-09-13
2038 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2039 TLS handshake that makes relays and bridges that run this new version
2040 reachable from Iran again.
2043 - Avoid an assertion failure when reloading a configuration with
2044 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2045 3923; bugfix on 0.2.2.25-alpha.
2047 o Minor features (security):
2048 - Check for replays of the public-key encrypted portion of an
2049 INTRODUCE1 cell, in addition to the current check for replays of
2050 the g^x value. This prevents a possible class of active attacks
2051 by an attacker who controls both an introduction point and a
2052 rendezvous point, and who uses the malleability of AES-CTR to
2053 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2054 that these attacks are infeasible (requiring the attacker to send
2055 on the order of zettabytes of altered cells in a short interval),
2056 but we'd rather block them off in case there are any classes of
2057 this attack that we missed. Reported by Willem Pinckaers.
2060 - Adjust the expiration time on our SSL session certificates to
2061 better match SSL certs seen in the wild. Resolves ticket 4014.
2062 - Change the default required uptime for a relay to be accepted as
2063 a HSDir (hidden service directory) from 24 hours to 25 hours.
2064 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2065 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2066 authorities to abstain from voting on assignment of the HSDir
2067 consensus flag. Related to bug 2649.
2068 - Update to the September 6 2011 Maxmind GeoLite Country database.
2070 o Minor bugfixes (documentation and log messages):
2071 - Correct the man page to explain that HashedControlPassword and
2072 CookieAuthentication can both be set, in which case either method
2073 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2074 when we decided to allow these config options to both be set. Issue
2076 - Demote the 'replay detected' log message emitted when a hidden
2077 service receives the same Diffie-Hellman public key in two different
2078 INTRODUCE2 cells to info level. A normal Tor client can cause that
2079 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2080 fixes part of bug 2442.
2081 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2082 level. There is nothing that a hidden service's operator can do
2083 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2085 - Clarify a log message specifying the characters permitted in
2086 HiddenServiceAuthorizeClient client names. Previously, the log
2087 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2088 given the impression that every ASCII character between "+" and "_"
2089 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2092 - Provide a substitute implementation of lround() for MSVC, which
2093 apparently lacks it. Patch from Gisle Vanem.
2094 - Clean up some code issues that prevented Tor from building on older
2095 BSDs. Fixes bug 3894; reported by "grarpamp".
2096 - Search for a platform-specific version of "ar" when cross-compiling.
2097 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2100 Changes in version 0.2.3.3-alpha - 2011-09-01
2101 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2102 security, and provides client-side support for the microdescriptor
2103 and optimistic data features introduced earlier in the 0.2.3.x
2104 series. It also includes numerous critical bugfixes in the (optional)
2105 bufferevent-based networking backend.
2107 o Major features (stream isolation):
2108 - You can now configure Tor so that streams from different
2109 applications are isolated on different circuits, to prevent an
2110 attacker who sees your streams as they leave an exit node from
2111 linking your sessions to one another. To do this, choose some way
2112 to distinguish the applications: have them connect to different
2113 SocksPorts, or have one of them use SOCKS4 while the other uses
2114 SOCKS5, or have them pass different authentication strings to the
2115 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2116 degree of isolation you need. This implements Proposal 171.
2117 - There's a new syntax for specifying multiple client ports (such as
2118 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2119 multiple *Port entries with full addr:port syntax on each.
2120 The old *ListenAddress format is still supported, but you can't
2121 mix it with the new *Port syntax.
2123 o Major features (other):
2124 - Enable microdescriptor fetching by default for clients. This allows
2125 clients to download a much smaller amount of directory information.
2126 To disable it (and go back to the old-style consensus and
2127 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2128 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2129 "PortForwarding" config option), now supports Windows.
2130 - When using an exit relay running 0.2.3.x, clients can now
2131 "optimistically" send data before the exit relay reports that
2132 the stream has opened. This saves a round trip when starting
2133 connections where the client speaks first (such as web browsing).
2134 This behavior is controlled by a consensus parameter (currently
2135 disabled). To turn it on or off manually, use the "OptimisticData"
2136 torrc option. Implements proposal 181; code by Ian Goldberg.
2138 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2139 - When using IOCP on Windows, we need to enable Libevent windows
2141 - The IOCP backend now works even when the user has not specified
2142 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2143 Fixes part of bug 3752.
2144 - Correctly record the bytes we've read and written when using
2145 bufferevents, so that we can include them in our bandwidth history
2146 and advertised bandwidth. Fixes bug 3803.
2147 - Apply rate-limiting only at the bottom of a chain of filtering
2148 bufferevents. This prevents us from filling up internal read
2149 buffers and violating rate-limits when filtering bufferevents
2150 are enabled. Fixes part of bug 3804.
2151 - Add high-watermarks to the output buffers for filtered
2152 bufferevents. This prevents us from filling up internal write
2153 buffers and wasting CPU cycles when filtering bufferevents are
2154 enabled. Fixes part of bug 3804.
2155 - Correctly notice when data has been written from a bufferevent
2156 without flushing it completely. Fixes bug 3805.
2157 - Fix a bug where server-side tunneled bufferevent-based directory
2158 streams would get closed prematurely. Fixes bug 3814.
2159 - Fix a use-after-free error with per-connection rate-limiting
2160 buckets. Fixes bug 3888.
2162 o Major bugfixes (also part of 0.2.2.31-rc):
2163 - If we're configured to write our ControlPorts to disk, only write
2164 them after switching UID and creating the data directory. This way,
2165 we don't fail when starting up with a nonexistent DataDirectory
2166 and a ControlPortWriteToFile setting based on that directory. Fixes
2167 bug 3747; bugfix on Tor 0.2.2.26-beta.
2170 - Added a new CONF_CHANGED event so that controllers can be notified
2171 of any configuration changes made by other controllers, or by the
2172 user. Implements ticket 1692.
2173 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2174 leak when using bufferevents, and lets Libevent worry about how to
2175 best copy data out of a buffer.
2176 - Replace files in stats/ rather than appending to them. Now that we
2177 include statistics in extra-info descriptors, it makes no sense to
2178 keep old statistics forever. Implements ticket 2930.
2180 o Minor features (build compatibility):
2181 - Limited, experimental support for building with nmake and MSVC.
2182 - Provide a substitute implementation of lround() for MSVC, which
2183 apparently lacks it. Patch from Gisle Vanem.
2185 o Minor features (also part of 0.2.2.31-rc):
2186 - Update to the August 2 2011 Maxmind GeoLite Country database.
2188 o Minor bugfixes (on 0.2.3.x-alpha):
2189 - Fix a spurious warning when parsing SOCKS requests with
2190 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2191 - Get rid of a harmless warning that could happen on relays running
2192 with bufferevents. The warning was caused by someone doing an http
2193 request to a relay's orport. Also don't warn for a few related
2194 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2196 o Minor bugfixes (on 2.2.x and earlier):
2197 - Correct the man page to explain that HashedControlPassword and
2198 CookieAuthentication can both be set, in which case either method
2199 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2200 when we decided to allow these config options to both be set. Issue
2202 - The "--quiet" and "--hush" options now apply not only to Tor's
2203 behavior before logs are configured, but also to Tor's behavior in
2204 the absense of configured logs. Fixes bug 3550; bugfix on
2207 o Minor bugfixes (also part of 0.2.2.31-rc):
2208 - Write several files in text mode, on OSes that distinguish text
2209 mode from binary mode (namely, Windows). These files are:
2210 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2211 that collect those statistics; 'client_keys' and 'hostname' for
2212 hidden services that use authentication; and (in the tor-gencert
2213 utility) newly generated identity and signing keys. Previously,
2214 we wouldn't specify text mode or binary mode, leading to an
2215 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2216 the DirRecordUsageByCountry option which would have triggered
2217 the assertion failure was added), although this assertion failure
2218 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2219 - Selectively disable deprecation warnings on OS X because Lion
2220 started deprecating the shipped copy of openssl. Fixes bug 3643.
2221 - Remove an extra pair of quotation marks around the error
2222 message in control-port STATUS_GENERAL BUG events. Bugfix on
2223 0.1.2.6-alpha; fixes bug 3732.
2224 - When unable to format an address as a string, report its value
2225 as "???" rather than reusing the last formatted address. Bugfix
2228 o Code simplifications and refactoring:
2229 - Rewrite the listener-selection logic so that parsing which ports
2230 we want to listen on is now separate from binding to the ports
2234 - Building Tor with bufferevent support now requires Libevent
2235 2.0.13-stable or later. Previous versions of Libevent had bugs in
2236 SSL-related bufferevents and related issues that would make Tor
2237 work badly with bufferevents. Requiring 2.0.13-stable also allows
2238 Tor with bufferevents to take advantage of Libevent APIs
2239 introduced after 2.0.8-rc.
2242 Changes in version 0.2.2.32 - 2011-08-27
2243 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2244 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2245 a founder of the PETS community, a leader in our field, a mentor,
2246 and a friend. He left us with these words: "I had the possibility
2247 to contribute to this world that is not as it should be. I hope I
2248 could help in some areas to make the world a better place, and that
2249 I could also encourage other people to be engaged in improving the
2250 world. Please, stay engaged. This world needs you, your love, your
2251 initiative -- now I cannot be part of that anymore."
2253 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2254 ready. More than two years in the making, this release features improved
2255 client performance and hidden service reliability, better compatibility
2256 for Android, correct behavior for bridges that listen on more than
2257 one address, more extensible and flexible directory object handling,
2258 better reporting of network statistics, improved code security, and
2259 many many other features and bugfixes.
2262 Changes in version 0.2.2.31-rc - 2011-08-17
2263 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2264 for the Tor 0.2.2.x series.
2267 - Remove an extra pair of quotation marks around the error
2268 message in control-port STATUS_GENERAL BUG events. Bugfix on
2269 0.1.2.6-alpha; fixes bug 3732.
2270 - If we're configured to write our ControlPorts to disk, only write
2271 them after switching UID and creating the data directory. This way,
2272 we don't fail when starting up with a nonexistent DataDirectory
2273 and a ControlPortWriteToFile setting based on that directory. Fixes
2274 bug 3747; bugfix on Tor 0.2.2.26-beta.
2277 - Update to the August 2 2011 Maxmind GeoLite Country database.
2280 - Allow GETINFO fingerprint to return a fingerprint even when
2281 we have not yet built a router descriptor. Fixes bug 3577;
2282 bugfix on 0.2.0.1-alpha.
2283 - Write several files in text mode, on OSes that distinguish text
2284 mode from binary mode (namely, Windows). These files are:
2285 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2286 that collect those statistics; 'client_keys' and 'hostname' for
2287 hidden services that use authentication; and (in the tor-gencert
2288 utility) newly generated identity and signing keys. Previously,
2289 we wouldn't specify text mode or binary mode, leading to an
2290 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2291 the DirRecordUsageByCountry option which would have triggered
2292 the assertion failure was added), although this assertion failure
2293 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2294 - Selectively disable deprecation warnings on OS X because Lion
2295 started deprecating the shipped copy of openssl. Fixes bug 3643.
2296 - When unable to format an address as a string, report its value
2297 as "???" rather than reusing the last formatted address. Bugfix
2301 Changes in version 0.2.3.2-alpha - 2011-07-18
2302 Tor 0.2.3.2-alpha introduces two new experimental features:
2303 microdescriptors and pluggable transports. It also continues cleaning
2304 up a variety of recently introduced features.
2307 - Clients can now use microdescriptors instead of regular descriptors
2308 to build circuits. Microdescriptors are authority-generated
2309 summaries of regular descriptors' contents, designed to change
2310 very rarely (see proposal 158 for details). This feature is
2311 designed to save bandwidth, especially for clients on slow internet
2312 connections. It's off by default for now, since nearly no caches
2313 support it, but it will be on-by-default for clients in a future
2314 version. You can use the UseMicrodescriptors option to turn it on.
2315 - Tor clients using bridges can now be configured to use a separate
2316 'transport' proxy for each bridge. This approach helps to resist
2317 censorship by allowing bridges to use protocol obfuscation
2318 plugins. It implements part of proposal 180. Implements ticket 2841.
2319 - While we're trying to bootstrap, record how many TLS connections
2320 fail in each state, and report which states saw the most failures
2321 in response to any bootstrap failures. This feature may speed up
2322 diagnosis of censorship events. Implements ticket 3116.
2324 o Major bugfixes (on 0.2.3.1-alpha):
2325 - When configuring a large set of nodes in EntryNodes (as with
2326 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2327 random subset to be guards, and choose them in random
2328 order. Fixes bug 2798.
2329 - Tor could crash when remembering a consensus in a non-used consensus
2330 flavor without having a current consensus set. Fixes bug 3361.
2331 - Comparing an unknown address to a microdescriptor's shortened exit
2332 policy would always give a "rejected" result. Fixes bug 3599.
2333 - Using microdescriptors as a client no longer prevents Tor from
2334 uploading and downloading hidden service descriptors. Fixes
2338 - Allow nameservers with IPv6 address. Resolves bug 2574.
2339 - Accept attempts to include a password authenticator in the
2340 handshake, as supported by SOCKS5. This handles SOCKS clients that
2341 don't know how to omit a password when authenticating. Resolves
2343 - When configuring a large set of nodes in EntryNodes, and there are
2344 enough of them listed as Guard so that we don't need to consider
2345 the non-guard entries, prefer the ones listed with the Guard flag.
2346 - Check for and recover from inconsistency in the microdescriptor
2347 cache. This will make it harder for us to accidentally free a
2348 microdescriptor without removing it from the appropriate data
2349 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2350 - Log SSL state transitions at log level DEBUG, log domain
2351 HANDSHAKE. This can be useful for debugging censorship events.
2352 Implements ticket 3264.
2353 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2354 implements ticket 3439.
2356 o Minor bugfixes (on 0.2.3.1-alpha):
2357 - Do not free all general-purpose regular descriptors just
2358 because microdescriptor use is enabled. Fixes bug 3113.
2359 - Correctly link libevent_openssl when --enable-static-libevent
2360 is passed to configure. Fixes bug 3118.
2361 - Bridges should not complain during their heartbeat log messages that
2362 they are unlisted in the consensus: that's more or less the point
2363 of being a bridge. Fixes bug 3183.
2364 - Report a SIGNAL event to controllers when acting on a delayed
2365 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2366 event to the controller if we acted on a SIGNAL NEWNYM command
2367 immediately, and otherwise not report a SIGNAL event for the
2368 command at all. Fixes bug 3349.
2369 - Fix a crash when handling the SIGNAL controller command or
2370 reporting ERR-level status events with bufferevents enabled. Found
2371 by Robert Ransom. Fixes bug 3367.
2372 - Always ship the tor-fw-helper manpage in our release tarballs.
2373 Fixes bug 3389. Reported by Stephen Walker.
2374 - Fix a class of double-mark-for-close bugs when bufferevents
2375 are enabled. Fixes bug 3403.
2376 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2377 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2378 control-port command. Fixes part of bug 3465.
2379 - Prevent using negative indices during unit test runs when read_all()
2380 fails. Spotted by coverity.
2381 - Fix a rare memory leak when checking the nodelist without it being
2382 present. Found by coverity.
2383 - Only try to download a microdescriptor-flavored consensus from
2384 a directory cache that provides them.
2386 o Minor bugfixes (on 0.2.2.x and earlier):
2387 - Assert that hidden-service-related operations are not performed
2388 using single-hop circuits. Previously, Tor would assert that
2389 client-side streams are not attached to single-hop circuits,
2390 but not that other sensitive operations on the client and service
2391 side are not performed using single-hop circuits. Fixes bug 3332;
2393 - Don't publish a new relay descriptor when we reload our onion key,
2394 unless the onion key has actually changed. Fixes bug 3263 and
2395 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2396 - Allow GETINFO fingerprint to return a fingerprint even when
2397 we have not yet built a router descriptor. Fixes bug 3577;
2398 bugfix on 0.2.0.1-alpha.
2399 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2400 on 0.2.2.4-alpha; fixes bug 3427.
2402 o Code simplification and refactoring:
2403 - Use tor_sscanf() in place of scanf() in more places through the
2404 code. This makes us a little more locale-independent, and
2405 should help shut up code-analysis tools that can't tell
2406 a safe sscanf string from a dangerous one.
2407 - Use tt_assert(), not tor_assert(), for checking for test failures.
2408 This makes the unit tests more able to go on in the event that
2410 - Split connection_about_to_close() into separate functions for each
2414 - On Windows, we now define the _WIN32_WINNT macros only if they
2415 are not already defined. This lets the person building Tor decide,
2416 if they want, to require a later version of Windows.
2419 Changes in version 0.2.2.30-rc - 2011-07-07
2420 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2421 series. It fixes a few smaller bugs, but generally appears stable.
2422 Please test it and let us know whether it is!
2425 - Send a SUCCEEDED stream event to the controller when a reverse
2426 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2427 discovered by katmagic.
2428 - Always NUL-terminate the sun_path field of a sockaddr_un before
2429 passing it to the kernel. (Not a security issue: kernels are
2430 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2431 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2432 - Don't stack-allocate the list of supplementary GIDs when we're
2433 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2434 could take up to 256K, which is way too much stack. Found by
2435 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2436 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
2437 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
2438 fixes part of bug 3465.
2439 - Fix a memory leak when receiving a descriptor for a hidden
2440 service we didn't ask for. Found by Coverity; CID #30. Bugfix
2444 - Update to the July 1 2011 Maxmind GeoLite Country database.
2447 Changes in version 0.2.2.29-beta - 2011-06-20
2448 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
2449 have bridge lines in their torrc but don't want to use them; gets
2450 us closer to having the control socket feature working on Debian;
2451 and fixes a variety of smaller bugs.
2454 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
2455 When we changed the default behavior to "use bridges if any
2456 are listed in the torrc", we surprised users who had bridges
2457 in their torrc files but who didn't actually want to use them.
2458 Partial resolution for bug 3354.
2461 - Don't attach new streams to old rendezvous circuits after SIGNAL
2462 NEWNYM. Previously, we would keep using an existing rendezvous
2463 circuit if it remained open (i.e. if it were kept open by a
2464 long-lived stream, or if a new stream were attached to it before
2465 Tor could notice that it was old and no longer in use). Bugfix on
2466 0.1.1.15-rc; fixes bug 3375.
2469 - Fix a bug when using ControlSocketsGroupWritable with User. The
2470 directory's group would be checked against the current group, not
2471 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
2472 bugfix on 0.2.2.26-beta.
2473 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2474 expect it to emit a CRLF iff the format string ends with CRLF;
2475 it actually emitted a CRLF iff (a) the format string ended with
2476 CRLF or (b) the resulting string was over 1023 characters long or
2477 (c) the format string did not end with CRLF *and* the resulting
2478 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2479 fixes part of bug 3407.
2480 - Make send_control_event_impl()'s behaviour sane. Its callers
2481 expect it to always emit a CRLF at the end of the string; it
2482 might have emitted extra control characters as well. Bugfix on
2483 0.1.1.9-alpha; fixes another part of bug 3407.
2484 - Make crypto_rand_int() check the value of its input correctly.
2485 Previously, it accepted values up to UINT_MAX, but could return a
2486 negative number if given a value above INT_MAX+1. Found by George
2487 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2488 - Avoid a segfault when reading a malformed circuit build state
2489 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2491 - When asked about a DNS record type we don't support via a
2492 client DNSPort, reply with NOTIMPL rather than an empty
2493 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2494 - Fix a rare memory leak during stats writing. Found by coverity.
2497 - Update to the June 1 2011 Maxmind GeoLite Country database.
2499 o Code simplifications and refactoring:
2500 - Remove some dead code as indicated by coverity.
2501 - Remove a few dead assignments during router parsing. Found by
2503 - Add some forgotten return value checks during unit tests. Found
2505 - Don't use 1-bit wide signed bit fields. Found by coverity.
2508 Changes in version 0.2.2.28-beta - 2011-06-04
2509 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2510 fixed a big bug in whether relays stay in the consensus consistently,
2511 we moved closer to handling bridges and hidden services correctly,
2512 and we started the process of better handling the dreaded "my Vidalia
2513 died, and now my Tor demands a password when I try to reconnect to it"
2517 - Don't decide to make a new descriptor when receiving a HUP signal.
2518 This bug has caused a lot of 0.2.2.x relays to disappear from the
2519 consensus periodically. Fixes the most common case of triggering
2520 bug 1810; bugfix on 0.2.2.7-alpha.
2521 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2522 - Don't try to build descriptors if "ORPort auto" is set and we
2523 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2525 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2526 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2527 - Apply circuit timeouts to opened hidden-service-related circuits
2528 based on the correct start time. Previously, we would apply the
2529 circuit build timeout based on time since the circuit's creation;
2530 it was supposed to be applied based on time since the circuit
2531 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2532 - Use the same circuit timeout for client-side introduction
2533 circuits as for other four-hop circuits, rather than the timeout
2534 for single-hop directory-fetch circuits; the shorter timeout may
2535 have been appropriate with the static circuit build timeout in
2536 0.2.1.x and earlier, but caused many hidden service access attempts
2537 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2538 on 0.2.2.2-alpha; fixes another part of bug 1297.
2539 - In ticket 2511 we fixed a case where you could use an unconfigured
2540 bridge if you had configured it as a bridge the last time you ran
2541 Tor. Now fix another edge case: if you had configured it as a bridge
2542 but then switched to a different bridge via the controller, you
2543 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2547 - Add an __OwningControllerProcess configuration option and a
2548 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2549 that when it exits, Tor will shut down. Implements feature 3049.
2550 - If "UseBridges 1" is set and no bridges are configured, Tor will
2551 now refuse to build any circuits until some bridges are set.
2552 If "UseBridges auto" is set, Tor will use bridges if they are
2553 configured and we are not running as a server, but otherwise will
2554 make circuits as usual. The new default is "auto". Patch by anonym,
2555 so the Tails LiveCD can stop automatically revealing you as a Tor
2559 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2560 - Remove a trailing asterisk from "exit-policy/default" in the
2561 output of the control port command "GETINFO info/names". Bugfix
2563 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2565 - Warn when the user configures two HiddenServiceDir lines that point
2566 to the same directory. Bugfix on 0.0.6 (the version introducing
2567 HiddenServiceDir); fixes bug 3289.
2568 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2569 part of bug 2748; bugfix on 0.2.0.10-alpha.
2570 - Log malformed requests for rendezvous descriptors as protocol
2571 warnings, not warnings. Also, use a more informative log message
2572 in case someone sees it at log level warning without prior
2573 info-level messages. Fixes the other part of bug 2748; bugfix
2575 - Clear the table recording the time of the last request for each
2576 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2577 Previously, we would clear our HS descriptor cache on SIGNAL
2578 NEWNYM, but if we had previously retrieved a descriptor (or tried
2579 to) from every directory responsible for it, we would refuse to
2580 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2582 - Fix a log message that said "bits" while displaying a value in
2583 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2585 - When checking for 1024-bit keys, check for 1024 bits, not 128
2586 bytes. This allows Tor to correctly discard keys of length 1017
2587 through 1023. Bugfix on 0.0.9pre5.
2590 - Relays now log the reason for publishing a new relay descriptor,
2591 so we have a better chance of hunting down instances of bug 1810.
2592 Resolves ticket 3252.
2593 - Revise most log messages that refer to nodes by nickname to
2594 instead use the "$key=nickname at address" format. This should be
2595 more useful, especially since nicknames are less and less likely
2596 to be unique. Resolves ticket 3045.
2597 - Log (at info level) when purging pieces of hidden-service-client
2598 state because of SIGNAL NEWNYM.
2601 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2602 anything since 0.2.1.16-rc.
2605 Changes in version 0.2.2.27-beta - 2011-05-18
2606 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2607 release, and also adds a few more general bugfixes.
2610 - Fix a crash bug when changing bridges in a running Tor process.
2611 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2612 - When the controller configures a new bridge, don't wait 10 to 60
2613 seconds before trying to fetch its descriptor. Bugfix on
2614 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2617 - Require that onion keys have exponent 65537 in microdescriptors too.
2618 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2619 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2620 Changed the limit to 512 characters by removing base64 newlines.
2621 Fixes bug 2752. Fix by Michael Yakubovich.
2622 - When a client starts or stops using bridges, never use a circuit
2623 that was built before the configuration change. This behavior could
2624 put at risk a user who uses bridges to ensure that her traffic
2625 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2629 Changes in version 0.2.2.26-beta - 2011-05-17
2630 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2631 also introduces a new "socksport auto" approach that should make it
2632 easier to run multiple Tors on the same system, and does a lot of
2633 cleanup to get us closer to a release candidate.
2635 o Security/privacy fixes:
2636 - Replace all potentially sensitive memory comparison operations
2637 with versions whose runtime does not depend on the data being
2638 compared. This will help resist a class of attacks where an
2639 adversary can use variations in timing information to learn
2640 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2641 implementation by Robert Ransom based partially on code by DJB.)
2642 - When receiving a hidden service descriptor, check that it is for
2643 the hidden service we wanted. Previously, Tor would store any
2644 hidden service descriptors that a directory gave it, whether it
2645 wanted them or not. This wouldn't have let an attacker impersonate
2646 a hidden service, but it did let directories pre-seed a client
2647 with descriptors that it didn't want. Bugfix on 0.0.6.
2648 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2649 DNS cache entries, and virtual address mappings: that's what
2650 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2653 - The options SocksPort, ControlPort, and so on now all accept a
2654 value "auto" that opens a socket on an OS-selected port. A
2655 new ControlPortWriteToFile option tells Tor to write its
2656 actual control port or ports to a chosen file. If the option
2657 ControlPortFileGroupReadable is set, the file is created as
2658 group-readable. Now users can run two Tor clients on the same
2659 system without needing to manually mess with parameters. Resolves
2660 part of ticket 3076.
2661 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2662 help busy exit nodes avoid running out of useable ports just
2663 because all the ports have been used in the near past. Resolves
2667 - New "GETINFO net/listeners/(type)" controller command to return
2668 a list of addresses and ports that are bound for listeners for a
2669 given connection type. This is useful when the user has configured
2670 "SocksPort auto" and the controller needs to know which port got
2671 chosen. Resolves another part of ticket 3076.
2672 - Add a new ControlSocketsGroupWritable configuration option: when
2673 it is turned on, ControlSockets are group-writeable by the default
2674 group of the current user. Patch by Jérémy Bobbio; implements
2676 - Tor now refuses to create a ControlSocket in a directory that is
2677 world-readable (or group-readable if ControlSocketsGroupWritable
2678 is 0). This is necessary because some operating systems do not
2679 enforce permissions on an AF_UNIX sockets. Permissions on the
2680 directory holding the socket, however, seems to work everywhere.
2681 - Rate-limit a warning about failures to download v2 networkstatus
2682 documents. Resolves part of bug 1352.
2683 - Backport code from 0.2.3.x that allows directory authorities to
2684 clean their microdescriptor caches. Needed to resolve bug 2230.
2685 - When an HTTPS proxy reports "403 Forbidden", we now explain
2686 what it means rather than calling it an unexpected status code.
2687 Closes bug 2503. Patch from Michael Yakubovich.
2688 - Update to the May 1 2011 Maxmind GeoLite Country database.
2691 - Authorities now clean their microdesc cache periodically and when
2692 reading from disk initially, not only when adding new descriptors.
2693 This prevents a bug where we could lose microdescriptors. Bugfix
2694 on 0.2.2.6-alpha. Fixes bug 2230.
2695 - Do not crash when our configuration file becomes unreadable, for
2696 example due to a permissions change, between when we start up
2697 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2699 - Avoid a bug that would keep us from replacing a microdescriptor
2700 cache on Windows. (We would try to replace the file while still
2701 holding it open. That's fine on Unix, but Windows doesn't let us
2702 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2703 - Add missing explanations for the authority-related torrc options
2704 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2705 man page. Resolves issue 2379.
2706 - As an authority, do not upload our own vote or signature set to
2707 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2708 it would get flagged as a duplicate. Resolves bug 3026.
2709 - Accept hidden service descriptors if we think we might be a hidden
2710 service directory, regardless of what our consensus says. This
2711 helps robustness, since clients and hidden services can sometimes
2712 have a more up-to-date view of the network consensus than we do,
2713 and if they think that the directory authorities list us a HSDir,
2714 we might actually be one. Related to bug 2732; bugfix on
2716 - When a controller changes TrackHostExits, remove mappings for
2717 hosts that should no longer have their exits tracked. Bugfix on
2719 - When a controller changes VirtualAddrNetwork, remove any mappings
2720 for hosts that were automapped to the old network. Bugfix on
2722 - When a controller changes one of the AutomapHosts* options, remove
2723 any mappings for hosts that should no longer be automapped. Bugfix
2725 - Do not reset the bridge descriptor download status every time we
2726 re-parse our configuration or get a configuration change. Fixes
2727 bug 3019; bugfix on 0.2.0.3-alpha.
2729 o Minor bugfixes (code cleanup):
2730 - When loading the microdesc journal, remember its current size.
2731 In 0.2.2, this helps prevent the microdesc journal from growing
2732 without limit on authorities (who are the only ones to use it in
2733 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2734 Fix posted by "cypherpunks."
2735 - The microdesc journal is supposed to get rebuilt only if it is
2736 at least _half_ the length of the store, not _twice_ the length
2737 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2738 - Fix a potential null-pointer dereference while computing a
2739 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2741 - Avoid a possible null-pointer dereference when rebuilding the mdesc
2742 cache without actually having any descriptors to cache. Bugfix on
2743 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
2744 - If we fail to compute the identity digest of a v3 legacy keypair,
2745 warn, and don't use a buffer-full of junk instead. Bugfix on
2746 0.2.1.1-alpha; fixes bug 3106.
2747 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2748 where if the function had ever in the future been used to check
2749 for the presence of a too-large number, it would have given an
2750 incorrect result. (Fortunately, we only used it for 16-bit
2751 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2752 - Require that introduction point keys and onion handshake keys
2753 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2757 - Caches no longer download and serve v2 networkstatus documents
2758 unless FetchV2Networkstatus flag is set: these documents haven't
2759 haven't been used by clients or relays since 0.2.0.x. Resolves
2763 Changes in version 0.2.3.1-alpha - 2011-05-05
2764 Tor 0.2.3.1-alpha adds some new experimental features, including support
2765 for an improved network IO backend, IOCP networking on Windows,
2766 microdescriptor caching, "fast-start" support for streams, and automatic
2767 home router configuration. There are also numerous internal improvements
2768 to try to make the code easier for developers to work with.
2770 This is the first alpha release in a new series, so expect there to be
2771 bugs. Users who would rather test out a more stable branch should
2772 stay with 0.2.2.x for now.
2775 - Tor can now optionally build with the "bufferevents" buffered IO
2776 backend provided by Libevent 2. To use this feature, make sure you
2777 have the latest possible version of Libevent, and pass the
2778 --enable-bufferevents flag to configure when building Tor from
2779 source. This feature will make our networking code more flexible,
2780 let us stack layers on each other, and let us use more efficient
2781 zero-copy transports where available.
2782 - As an experimental feature, Tor can use IOCP for networking on Windows.
2783 Once this code is tuned and optimized, it promises much better
2784 performance than the select-based backend we've used in the past. To
2785 try this feature, you must build Tor with Libevent 2, configure Tor
2786 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
2787 your torrc. There are known bugs here: only try this if you can help
2788 debug it as it breaks.
2789 - The EntryNodes option can now include country codes like {de} or IP
2790 addresses or network masks. Previously we had disallowed these options
2791 because we didn't have an efficient way to keep the list up to
2792 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
2793 - Exit nodes now accept and queue data on not-yet-connected streams.
2794 Previously, the client wasn't allowed to send data until the stream was
2795 connected, which slowed down all connections. This change will enable
2796 clients to perform a "fast-start" on streams and send data without
2797 having to wait for a confirmation that the stream has opened. (Patch
2798 from Ian Goldberg; implements the server side of Proposal 174.)
2799 - Tor now has initial support for automatic port mapping on the many
2800 home routers that support NAT-PMP or UPnP. (Not yet supported on
2801 Windows). To build the support code, you'll need to have libnatpnp
2802 library and/or the libminiupnpc library, and you'll need to enable the
2803 feature specifically by passing "--enable-upnp" and/or
2804 "--enable-natpnp" to configure. To turn it on, use the new
2805 PortForwarding option.
2806 - Caches now download, cache, and serve multiple "flavors" of the
2807 consensus, including a flavor that describes microdescriptors.
2808 - Caches now download, cache, and serve microdescriptors -- small
2809 summaries of router descriptors that are authenticated by all of the
2810 directory authorities. Once enough caches are running this code,
2811 clients will be able to save significant amounts of directory bandwidth
2812 by downloading microdescriptors instead of router descriptors.
2815 - Make logging resolution configurable with a new LogTimeGranularity
2816 option, and change the default from 1 millisecond to 1 second.
2817 Implements enhancement 1668.
2818 - We log which torrc file we're using on startup. Implements ticket
2820 - Ordinarily, Tor does not count traffic from private addresses (like
2821 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2822 There is now a new option, CountPrivateBandwidth, to disable this
2823 behavior. Patch from Daniel Cagara.
2824 - New --enable-static-tor configure option for building Tor as
2825 statically as possible. Idea, general hackery and thoughts from
2826 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2828 - If you set the NumCPUs option to 0, Tor will now try to detect how
2829 many CPUs you have. This is the new default behavior.
2830 - Turn on directory request statistics by default and include them in
2831 extra-info descriptors. Don't break if we have no GeoIP database.
2832 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2833 bidirectional use of connections to disk every 24 hours.
2834 - Add a GeoIP file digest to the extra-info descriptor. Implements
2836 - The NodeFamily option -- which let you declare that you want to
2837 consider nodes to be part of a family whether they list themselves
2838 that way or not -- now allows IP address ranges and country codes.
2839 - Add a new 'Heartbeat' log message type to periodically log a message
2840 describing Tor's status at level Notice. This feature is meant for
2841 operators who log at notice, and want to make sure that their Tor
2842 server is still working. Implementation by George Kadianakis.
2844 o Minor bugfixes (on 0.2.2.25-alpha):
2845 - When loading the microdesc journal, remember its current size.
2846 In 0.2.2, this helps prevent the microdesc journal from growing
2847 without limit on authorities (who are the only ones to use it in
2848 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2849 Fix posted by "cypherpunks."
2850 - The microdesc journal is supposed to get rebuilt only if it is
2851 at least _half_ the length of the store, not _twice_ the length
2852 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2853 - If as an authority we fail to compute the identity digest of a v3
2854 legacy keypair, warn, and don't use a buffer-full of junk instead.
2855 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
2856 - Authorities now clean their microdesc cache periodically and when
2857 reading from disk initially, not only when adding new descriptors.
2858 This prevents a bug where we could lose microdescriptors. Bugfix
2861 o Minor features (controller):
2862 - Add a new SIGNAL event to the controller interface so that
2863 controllers can be notified when Tor handles a signal. Resolves
2864 issue 1955. Patch by John Brooks.
2865 - Add a new GETINFO option to get total bytes read and written. Patch
2866 from pipe, revised by atagar. Resolves ticket 2345.
2867 - Implement some GETINFO controller fields to provide information about
2868 the Tor process's pid, euid, username, and resource limits.
2871 - Our build system requires automake 1.6 or later to create the
2872 Makefile.in files. Previously, you could have used 1.4.
2873 This only affects developers and people building Tor from git;
2874 people who build Tor from the source distribution without changing
2875 the Makefile.am files should be fine.
2876 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
2877 so on. This is more robust against some of the failure modes
2878 associated with running the autotools pieces on their own.
2880 o Minor packaging issues:
2881 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
2882 already created. Patch from Andreas Stieger. Fixes bug 2573.
2884 o Code simplifications and refactoring:
2885 - A major revision to our internal node-selecting and listing logic.
2886 Tor already had at least two major ways to look at the question of
2887 "which Tor servers do we know about": a list of router descriptors,
2888 and a list of entries in the current consensus. With
2889 microdescriptors, we're adding a third. Having so many systems
2890 without an abstraction layer over them was hurting the codebase.
2891 Now, we have a new "node_t" abstraction that presents a consistent
2892 interface to a client's view of a Tor node, and holds (nearly) all
2893 of the mutable state formerly in routerinfo_t and routerstatus_t.
2894 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2895 no longer link against Libevent: they never used it, but
2896 our library structure used to force them to link it.
2899 - Remove some old code to work around even older versions of Tor that
2900 used forked processes to handle DNS requests. Such versions of Tor
2901 are no longer in use as servers.
2903 o Documentation fixes:
2904 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2905 - Add missing documentation for the authority-related torrc options
2906 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
2910 Changes in version 0.2.2.25-alpha - 2011-04-29
2911 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
2912 robust, routers no longer overreport their bandwidth, Win7 should crash
2913 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
2914 now prevents hidden service-related activity from being linkable. It
2915 provides more information to Vidalia so you can see if your bridge is
2916 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
2917 StrictNodes configuration options to make them more reliable, more
2918 understandable, and more regularly applied. If you use those options,
2919 please see the revised documentation for them in the manual page.
2922 - Relays were publishing grossly inflated bandwidth values because
2923 they were writing their state files wrong--now they write the
2924 correct value. Also, resume reading bandwidth history from the
2925 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
2926 - Improve hidden service robustness: When we find that we have
2927 extended a hidden service's introduction circuit to a relay not
2928 listed as an introduction point in the HS descriptor we currently
2929 have, retry with an introduction point from the current
2930 descriptor. Previously we would just give up. Fixes bugs 1024 and
2931 1930; bugfix on 0.2.0.10-alpha.
2932 - Clients now stop trying to use an exit node associated with a given
2933 destination by TrackHostExits if they fail to reach that exit node.
2934 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
2935 - Fix crash bug on platforms where gmtime and localtime can return
2936 NULL. Windows 7 users were running into this one. Fixes part of bug
2937 2077. Bugfix on all versions of Tor. Found by boboper.
2939 o Security and stability fixes:
2940 - Don't double-free a parsable, but invalid, microdescriptor, even if
2941 it is followed in the blob we're parsing by an unparsable
2942 microdescriptor. Fixes an issue reported in a comment on bug 2954.
2943 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
2944 - If the Nickname configuration option isn't given, Tor would pick a
2945 nickname based on the local hostname as the nickname for a relay.
2946 Because nicknames are not very important in today's Tor and the
2947 "Unnamed" nickname has been implemented, this is now problematic
2948 behavior: It leaks information about the hostname without being
2949 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
2950 introduced the Unnamed nickname. Reported by tagnaq.
2951 - Fix an uncommon assertion failure when running with DNSPort under
2952 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2953 - Avoid linkability based on cached hidden service descriptors: forget
2954 all hidden service descriptors cached as a client when processing a
2955 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2958 - Export GeoIP information on bridge usage to controllers even if we
2959 have not yet been running for 24 hours. Now Vidalia bridge operators
2960 can get more accurate and immediate feedback about their
2961 contributions to the network.
2963 o Major features and bugfixes (node selection):
2964 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2965 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
2966 options. Previously, we had been ambiguous in describing what
2967 counted as an "exit" node, and what operations exactly "StrictNodes
2968 0" would permit. This created confusion when people saw nodes built
2969 through unexpected circuits, and made it hard to tell real bugs from
2970 surprises. Now the intended behavior is:
2971 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2972 a node that delivers user traffic outside the Tor network.
2973 . "Entry", in the context of EntryNodes, means a node used as the
2974 first hop of a multihop circuit. It doesn't include direct
2975 connections to directory servers.
2976 . "ExcludeNodes" applies to all nodes.
2977 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2978 StrictNodes is set, Tor should avoid all nodes listed in
2979 ExcludeNodes, even when it will make user requests fail. When
2980 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2981 whenever it can, except when it must use an excluded node to
2982 perform self-tests, connect to a hidden service, provide a
2983 hidden service, fulfill a .exit request, upload directory
2984 information, or fetch directory information.
2985 Collectively, the changes to implement the behavior fix bug 1090.
2986 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2987 a node is listed in both, it's treated as excluded.
2988 - ExcludeNodes now applies to directory nodes -- as a preference if
2989 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2990 Don't exclude all the directory authorities and set StrictNodes to 1
2991 unless you really want your Tor to break.
2992 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2993 - ExcludeExitNodes now overrides .exit requests.
2994 - We don't use bridges listed in ExcludeNodes.
2995 - When StrictNodes is 1:
2996 . We now apply ExcludeNodes to hidden service introduction points
2997 and to rendezvous points selected by hidden service users. This
2998 can make your hidden service less reliable: use it with caution!
2999 . If we have used ExcludeNodes on ourself, do not try relay
3000 reachability self-tests.
3001 . If we have excluded all the directory authorities, we will not
3002 even try to upload our descriptor if we're a relay.
3003 . Do not honor .exit requests to an excluded node.
3004 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3005 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3006 - When the set of permitted nodes changes, we now remove any mappings
3007 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3009 - We never cannibalize a circuit that had excluded nodes on it, even
3010 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3011 - Revert a change where we would be laxer about attaching streams to
3012 circuits than when building the circuits. This was meant to prevent
3013 a set of bugs where streams were never attachable, but our improved
3014 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3015 - Keep track of how many times we launch a new circuit to handle a
3016 given stream. Too many launches could indicate an inconsistency
3017 between our "launch a circuit to handle this stream" logic and our
3018 "attach this stream to one of the available circuits" logic.
3019 - Improve log messages related to excluded nodes.
3022 - Fix a spurious warning when moving from a short month to a long
3023 month on relays with month-based BandwidthAccounting. Bugfix on
3024 0.2.2.17-alpha; fixes bug 3020.
3025 - When a client finds that an origin circuit has run out of 16-bit
3026 stream IDs, we now mark it as unusable for new streams. Previously,
3027 we would try to close the entire circuit. Bugfix on 0.0.6.
3028 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3029 Bugfix on 0.2.2.24-alpha.
3030 - Be more careful about reporting the correct error from a failed
3031 connect() system call. Under some circumstances, it was possible to
3032 look at an incorrect value for errno when sending the end reason.
3033 Bugfix on 0.1.0.1-rc.
3034 - Correctly handle an "impossible" overflow cases in connection byte
3035 counting, where we write or read more than 4GB on an edge connection
3036 in a single second. Bugfix on 0.1.2.8-beta.
3037 - Correct the warning displayed when a rendezvous descriptor exceeds
3038 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3040 - Clients and hidden services now use HSDir-flagged relays for hidden
3041 service descriptor downloads and uploads even if the relays have no
3042 DirPort set and the client has disabled TunnelDirConns. This will
3043 eventually allow us to give the HSDir flag to relays with no
3044 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3045 - Downgrade "no current certificates known for authority" message from
3046 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3047 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3048 2917. Bugfix on 0.1.1.1-alpha.
3049 - Only limit the lengths of single HS descriptors, even when multiple
3050 HS descriptors are published to an HSDir relay in a single POST
3051 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3052 - Write the current time into the LastWritten line in our state file,
3053 rather than the time from the previous write attempt. Also, stop
3054 trying to use a time of -1 in our log statements. Fixes bug 3039;
3055 bugfix on 0.2.2.14-alpha.
3056 - Be more consistent in our treatment of file system paths. "~" should
3057 get expanded to the user's home directory in the Log config option.
3058 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3059 feature for the -f and --DataDirectory options.
3062 - Make sure every relay writes a state file at least every 12 hours.
3063 Previously, a relay could go for weeks without writing its state
3064 file, and on a crash could lose its bandwidth history, capacity
3065 estimates, client country statistics, and so on. Addresses bug 3012.
3066 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3067 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3068 clients are already deprecated because of security bugs.
3069 - Don't allow v0 hidden service authorities to act as clients.
3070 Required by fix for bug 3000.
3071 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3072 by fix for bug 3000.
3073 - Ensure that no empty [dirreq-](read|write)-history lines are added
3074 to an extrainfo document. Implements ticket 2497.
3076 o Code simplification and refactoring:
3077 - Remove workaround code to handle directory responses from servers
3078 that had bug 539 (they would send HTTP status 503 responses _and_
3079 send a body too). Since only server versions before
3080 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3081 keep the workaround in place.
3082 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3083 handling calculations where we have a known amount of clock skew and
3084 an allowed amount of unknown skew. But we only used it in three
3085 places, and we never adjusted the known/unknown skew values. This is
3086 still something we might want to do someday, but if we do, we'll
3087 want to do it differently.
3088 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3089 None of the cases where we did this before were wrong, but by making
3090 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3091 - Use GetTempDir to find the proper temporary directory location on
3092 Windows when generating temporary files for the unit tests. Patch by
3096 Changes in version 0.2.2.24-alpha - 2011-04-08
3097 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3098 prevented Tor clients from effectively using "multihomed" bridges,
3099 that is, bridges that listen on multiple ports or IP addresses so users
3100 can continue to use some of their addresses even if others get blocked.
3103 - Fix a bug where bridge users who configure the non-canonical
3104 address of a bridge automatically switch to its canonical
3105 address. If a bridge listens at more than one address, it should be
3106 able to advertise those addresses independently and any non-blocked
3107 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3109 - If you configured Tor to use bridge A, and then quit and
3110 configured Tor to use bridge B instead, it would happily continue
3111 to use bridge A if it's still reachable. While this behavior is
3112 a feature if your goal is connectivity, in some scenarios it's a
3113 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3114 - Directory authorities now use data collected from their own
3115 uptime observations when choosing whether to assign the HSDir flag
3116 to relays, instead of trusting the uptime value the relay reports in
3117 its descriptor. This change helps prevent an attack where a small
3118 set of nodes with frequently-changing identity keys can blackhole
3119 a hidden service. (Only authorities need upgrade; others will be
3120 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3123 - When we restart our relay, we might get a successful connection
3124 from the outside before we've started our reachability tests,
3125 triggering a warning: "ORPort found reachable, but I have no
3126 routerinfo yet. Failing to inform controller of success." This
3127 bug was harmless unless Tor is running under a controller
3128 like Vidalia, in which case the controller would never get a
3129 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3131 - Make directory authorities more accurate at recording when
3132 relays that have failed several reachability tests became
3133 unreachable, so we can provide more accuracy at assigning Stable,
3134 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3135 - Fix an issue that prevented static linking of libevent on
3136 some platforms (notably Linux). Fixes bug 2698; bugfix on
3137 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3138 the --with-static-libevent configure option).
3139 - We now ask the other side of a stream (the client or the exit)
3140 for more data on that stream when the amount of queued data on
3141 that stream dips low enough. Previously, we wouldn't ask the
3142 other side for more data until either it sent us more data (which
3143 it wasn't supposed to do if it had exhausted its window!) or we
3144 had completely flushed all our queued data. This flow control fix
3145 should improve throughput. Fixes bug 2756; bugfix on the earliest
3146 released versions of Tor (svn commit r152).
3147 - Avoid a double-mark-for-free warning when failing to attach a
3148 transparent proxy connection. (We thought we had fixed this in
3149 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3150 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3151 bug) and 0.2.2.23-alpha (the incorrect fix).
3152 - When warning about missing zlib development packages during compile,
3153 give the correct package names. Bugfix on 0.2.0.1-alpha.
3156 - Directory authorities now log the source of a rejected POSTed v3
3158 - Make compilation with clang possible when using
3159 --enable-gcc-warnings by removing two warning options that clang
3160 hasn't implemented yet and by fixing a few warnings. Implements
3162 - When expiring circuits, use microsecond timers rather than
3163 one-second timers. This can avoid an unpleasant situation where a
3164 circuit is launched near the end of one second and expired right
3165 near the beginning of the next, and prevent fluctuations in circuit
3167 - Use computed circuit-build timeouts to decide when to launch
3168 parallel introduction circuits for hidden services. (Previously,
3169 we would retry after 15 seconds.)
3170 - Update to the April 1 2011 Maxmind GeoLite Country database.
3173 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3174 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3176 o Documentation changes:
3177 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3178 - Resolve all doxygen warnings except those for missing documentation.
3180 - Add doxygen documentation for more functions, fields, and types.
3183 Changes in version 0.2.2.23-alpha - 2011-03-08
3184 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3185 they restart they don't lose their bandwidth capacity estimate. This
3186 release also fixes a diverse set of user-facing bugs, ranging from
3187 relays overrunning their rate limiting to clients falsely warning about
3188 clock skew to bridge descriptor leaks by our bridge directory authority.
3191 - Stop sending a CLOCK_SKEW controller status event whenever
3192 we fetch directory information from a relay that has a wrong clock.
3193 Instead, only inform the controller when it's a trusted authority
3194 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3195 the rest of bug 1074.
3196 - Fix an assert in parsing router descriptors containing IPv6
3197 addresses. This one took down the directory authorities when
3198 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3199 - Make the bridge directory authority refuse to answer directory
3200 requests for "all" descriptors. It used to include bridge
3201 descriptors in its answer, which was a major information leak.
3202 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3203 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3204 Tor would ignore their RelayBandwidthBurst setting,
3205 potentially using more bandwidth than expected. Bugfix on
3206 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3207 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3208 hidserv" in her torrc. The 'hidserv' argument never controlled
3209 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3212 - Relays now save observed peak bandwidth throughput rates to their
3213 state file (along with total usage, which was already saved)
3214 so that they can determine their correct estimated bandwidth on
3215 restart. Resolves bug 1863, where Tor relays would reset their
3216 estimated bandwidth to 0 after restarting.
3217 - Directory authorities now take changes in router IP address and
3218 ORPort into account when determining router stability. Previously,
3219 if a router changed its IP or ORPort, the authorities would not
3220 treat it as having any downtime for the purposes of stability
3221 calculation, whereas clients would experience downtime since the
3222 change could take a while to propagate to them. Resolves issue 1035.
3223 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3224 Prevention (DEP) by default on Windows to make it harder for
3225 attackers to exploit vulnerabilities. Patch from John Brooks.
3227 o Minor bugfixes (on 0.2.1.x and earlier):
3228 - Fix a rare crash bug that could occur when a client was configured
3229 with a large number of bridges. Fixes bug 2629; bugfix on
3230 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3231 - Avoid a double mark-for-free warning when failing to attach a
3232 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3234 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3235 found by "cypherpunks". This bug was introduced before the first
3236 Tor release, in svn commit r110.
3237 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3238 don't mention them in the manpage. Fixes bug 2450; issue
3239 spotted by keb and G-Lo.
3240 - Fix a bug in bandwidth history state parsing that could have been
3241 triggered if a future version of Tor ever changed the timing
3242 granularity at which bandwidth history is measured. Bugfix on
3244 - When a relay decides that its DNS is too broken for it to serve
3245 as an exit server, it advertised itself as a non-exit, but
3246 continued to act as an exit. This could create accidental
3247 partitioning opportunities for users. Instead, if a relay is
3248 going to advertise reject *:* as its exit policy, it should
3249 really act with exit policy "reject *:*". Fixes bug 2366.
3250 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3251 - In the special case where you configure a public exit relay as your
3252 bridge, Tor would be willing to use that exit relay as the last
3253 hop in your circuit as well. Now we fail that circuit instead.
3254 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3255 - Fix a bug with our locking implementation on Windows that couldn't
3256 correctly detect when a file was already locked. Fixes bug 2504,
3257 bugfix on 0.2.1.6-alpha.
3258 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3259 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3261 - Set target port in get_interface_address6() correctly. Bugfix
3262 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3263 - Directory authorities are now more robust to hops back in time
3264 when calculating router stability. Previously, if a run of uptime
3265 or downtime appeared to be negative, the calculation could give
3266 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3268 - Fix an assert that got triggered when using the TestingTorNetwork
3269 configuration option and then issuing a GETINFO config-text control
3270 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3272 o Minor bugfixes (on 0.2.2.x):
3273 - Clients should not weight BadExit nodes as Exits in their node
3274 selection. Similarly, directory authorities should not count BadExit
3275 bandwidth as Exit bandwidth when computing bandwidth-weights.
3276 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3277 - Correctly clear our dir_read/dir_write history when there is an
3278 error parsing any bw history value from the state file. Bugfix on
3280 - Resolve a bug in verifying signatures of directory objects
3281 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3282 Fixes bug 2409. Found by "piebeer".
3283 - Bridge authorities no longer crash on SIGHUP when they try to
3284 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3288 - Log less aggressively about circuit timeout changes, and improve
3289 some other circuit timeout messages. Resolves bug 2004.
3290 - Log a little more clearly about the times at which we're no longer
3291 accepting new connections. Resolves bug 2181.
3292 - Reject attempts at the client side to open connections to private
3293 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3294 a randomly chosen exit node. Attempts to do so are always
3295 ill-defined, generally prevented by exit policies, and usually
3296 in error. This will also help to detect loops in transparent
3297 proxy configurations. You can disable this feature by setting
3298 "ClientRejectInternalAddresses 0" in your torrc.
3299 - Always treat failure to allocate an RSA key as an unrecoverable
3301 - Update to the March 1 2011 Maxmind GeoLite Country database.
3303 o Minor features (log subsystem):
3304 - Add documentation for configuring logging at different severities in
3305 different log domains. We've had this feature since 0.2.1.1-alpha,
3306 but for some reason it never made it into the manpage. Fixes
3308 - Make it simpler to specify "All log domains except for A and B".
3309 Previously you needed to say "[*,~A,~B]". Now you can just say
3311 - Add a "LogMessageDomains 1" option to include the domains of log
3312 messages along with the messages. Without this, there's no way
3313 to use log domains without reading the source or doing a lot
3316 o Packaging changes:
3317 - Stop shipping the Tor specs files and development proposal documents
3318 in the tarball. They are now in a separate git repository at
3319 git://git.torproject.org/torspec.git
3322 Changes in version 0.2.1.30 - 2011-02-23
3323 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3324 change is a slight tweak to Tor's TLS handshake that makes relays
3325 and bridges that run this new version reachable from Iran again.
3326 We don't expect this tweak will win the arms race long-term, but it
3327 buys us time until we roll out a better solution.
3330 - Stop sending a CLOCK_SKEW controller status event whenever
3331 we fetch directory information from a relay that has a wrong clock.
3332 Instead, only inform the controller when it's a trusted authority
3333 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3334 the rest of bug 1074.
3335 - Fix a bounds-checking error that could allow an attacker to
3336 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3338 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3339 Tor would ignore their RelayBandwidthBurst setting,
3340 potentially using more bandwidth than expected. Bugfix on
3341 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3342 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3343 hidserv" in her torrc. The 'hidserv' argument never controlled
3344 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3347 - Adjust our TLS Diffie-Hellman parameters to match those used by
3349 - Update to the February 1 2011 Maxmind GeoLite Country database.
3352 - Check for and reject overly long directory certificates and
3353 directory tokens before they have a chance to hit any assertions.
3354 Bugfix on 0.2.1.28. Found by "doorss".
3355 - Bring the logic that gathers routerinfos and assesses the
3356 acceptability of circuits into line. This prevents a Tor OP from
3357 getting locked in a cycle of choosing its local OR as an exit for a
3358 path (due to a .exit request) and then rejecting the circuit because
3359 its OR is not listed yet. It also prevents Tor clients from using an
3360 OR running in the same instance as an exit (due to a .exit request)
3361 if the OR does not meet the same requirements expected of an OR
3362 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3364 o Packaging changes:
3365 - Stop shipping the Tor specs files and development proposal documents
3366 in the tarball. They are now in a separate git repository at
3367 git://git.torproject.org/torspec.git
3368 - Do not include Git version tags as though they are SVN tags when
3369 generating a tarball from inside a repository that has switched
3370 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3373 Changes in version 0.2.2.22-alpha - 2011-01-25
3374 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3375 main other change is a slight tweak to Tor's TLS handshake that makes
3376 relays and bridges that run this new version reachable from Iran again.
3377 We don't expect this tweak will win the arms race long-term, but it
3378 will buy us a bit more time until we roll out a better solution.
3381 - Fix a bounds-checking error that could allow an attacker to
3382 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3384 - Don't assert when changing from bridge to relay or vice versa
3385 via the controller. The assert happened because we didn't properly
3386 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3387 bug 2433. Reported by bastik.
3390 - Adjust our TLS Diffie-Hellman parameters to match those used by
3392 - Provide a log message stating which geoip file we're parsing
3393 instead of just stating that we're parsing the geoip file.
3394 Implements ticket 2432.
3397 - Check for and reject overly long directory certificates and
3398 directory tokens before they have a chance to hit any assertions.
3399 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3402 Changes in version 0.2.2.21-alpha - 2011-01-15
3403 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3404 continues our recent code security audit work. The main fix resolves
3405 a remote heap overflow vulnerability that can allow remote code
3406 execution (CVE-2011-0427). Other fixes address a variety of assert
3407 and crash bugs, most of which we think are hard to exploit remotely.
3409 o Major bugfixes (security), also included in 0.2.1.29:
3410 - Fix a heap overflow bug where an adversary could cause heap
3411 corruption. This bug probably allows remote code execution
3412 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3414 - Prevent a denial-of-service attack by disallowing any
3415 zlib-compressed data whose compression factor is implausibly
3416 high. Fixes part of bug 2324; reported by "doorss".
3417 - Zero out a few more keys in memory before freeing them. Fixes
3418 bug 2384 and part of bug 2385. These key instances found by
3419 "cypherpunks", based on Andrew Case's report about being able
3420 to find sensitive data in Tor's memory space if you have enough
3421 permissions. Bugfix on 0.0.2pre9.
3423 o Major bugfixes (crashes), also included in 0.2.1.29:
3424 - Prevent calls to Libevent from inside Libevent log handlers.
3425 This had potential to cause a nasty set of crashes, especially
3426 if running Libevent with debug logging enabled, and running
3427 Tor with a controller watching for low-severity log messages.
3428 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3429 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3430 underflow errors there too. Fixes the other part of bug 2324.
3431 - Fix a bug where we would assert if we ever had a
3432 cached-descriptors.new file (or another file read directly into
3433 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3434 on 0.2.1.25. Found by doorss.
3435 - Fix some potential asserts and parsing issues with grossly
3436 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3439 o Minor bugfixes (other), also included in 0.2.1.29:
3440 - Fix a bug with handling misformed replies to reverse DNS lookup
3441 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3442 bug reported by doorss.
3443 - Fix compilation on mingw when a pthreads compatibility library
3444 has been installed. (We don't want to use it, so we shouldn't
3445 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3446 - Fix a bug where we would declare that we had run out of virtual
3447 addresses when the address space was only half-exhausted. Bugfix
3449 - Correctly handle the case where AutomapHostsOnResolve is set but
3450 no virtual addresses are available. Fixes bug 2328; bugfix on
3451 0.1.2.1-alpha. Bug found by doorss.
3452 - Correctly handle wrapping around when we run out of virtual
3453 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3455 o Minor features, also included in 0.2.1.29:
3456 - Update to the January 1 2011 Maxmind GeoLite Country database.
3457 - Introduce output size checks on all of our decryption functions.
3459 o Build changes, also included in 0.2.1.29:
3460 - Tor does not build packages correctly with Automake 1.6 and earlier;
3461 added a check to Makefile.am to make sure that we're building with
3462 Automake 1.7 or later.
3463 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3464 because we built it with a too-old version of automake. Thus that
3465 release broke ./configure --enable-openbsd-malloc, which is popular
3466 among really fast exit relays on Linux.
3468 o Major bugfixes, new in 0.2.2.21-alpha:
3469 - Prevent crash/heap corruption when the cbtnummodes consensus
3470 parameter is set to 0 or large values. Fixes bug 2317; bugfix
3473 o Major features, new in 0.2.2.21-alpha:
3474 - Introduce minimum/maximum values that clients will believe
3475 from the consensus. Now we'll have a better chance to avoid crashes
3476 or worse when a consensus param has a weird value.
3478 o Minor features, new in 0.2.2.21-alpha:
3479 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3480 used on bridges, and it makes bridge scanning somewhat easier.
3481 - If writing the state file to disk fails, wait up to an hour before
3482 retrying again, rather than trying again each second. Fixes bug
3483 2346; bugfix on Tor 0.1.1.3-alpha.
3484 - Make Libevent log messages get delivered to controllers later,
3485 and not from inside the Libevent log handler. This prevents unsafe
3486 reentrant Libevent calls while still letting the log messages
3488 - Detect platforms that brokenly use a signed size_t, and refuse to
3489 build there. Found and analyzed by doorss and rransom.
3490 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3493 o Minor bugfixes, new in 0.2.2.21-alpha:
3494 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3495 than waiting forever for them to finish. Fixes bug 2330; bugfix
3496 on 0.2.0.16-alpha. Found by doorss.
3497 - Add assertions to check for overflow in arguments to
3498 base32_encode() and base32_decode(); fix a signed-unsigned
3499 comparison there too. These bugs are not actually reachable in Tor,
3500 but it's good to prevent future errors too. Found by doorss.
3501 - Correctly detect failures to create DNS requests when using Libevent
3502 versions before v2. (Before Libevent 2, we used our own evdns
3503 implementation. Its return values for Libevent's evdns_resolve_*()
3504 functions are not consistent with those from Libevent.) Fixes bug
3505 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3507 o Documentation, new in 0.2.2.21-alpha:
3508 - Document the default socks host and port (127.0.0.1:9050) for
3512 Changes in version 0.2.1.29 - 2011-01-15
3513 Tor 0.2.1.29 continues our recent code security audit work. The main
3514 fix resolves a remote heap overflow vulnerability that can allow remote
3515 code execution. Other fixes address a variety of assert and crash bugs,
3516 most of which we think are hard to exploit remotely.
3518 o Major bugfixes (security):
3519 - Fix a heap overflow bug where an adversary could cause heap
3520 corruption. This bug probably allows remote code execution
3521 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3523 - Prevent a denial-of-service attack by disallowing any
3524 zlib-compressed data whose compression factor is implausibly
3525 high. Fixes part of bug 2324; reported by "doorss".
3526 - Zero out a few more keys in memory before freeing them. Fixes
3527 bug 2384 and part of bug 2385. These key instances found by
3528 "cypherpunks", based on Andrew Case's report about being able
3529 to find sensitive data in Tor's memory space if you have enough
3530 permissions. Bugfix on 0.0.2pre9.
3532 o Major bugfixes (crashes):
3533 - Prevent calls to Libevent from inside Libevent log handlers.
3534 This had potential to cause a nasty set of crashes, especially
3535 if running Libevent with debug logging enabled, and running
3536 Tor with a controller watching for low-severity log messages.
3537 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3538 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3539 underflow errors there too. Fixes the other part of bug 2324.
3540 - Fix a bug where we would assert if we ever had a
3541 cached-descriptors.new file (or another file read directly into
3542 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3543 on 0.2.1.25. Found by doorss.
3544 - Fix some potential asserts and parsing issues with grossly
3545 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3548 o Minor bugfixes (other):
3549 - Fix a bug with handling misformed replies to reverse DNS lookup
3550 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3551 bug reported by doorss.
3552 - Fix compilation on mingw when a pthreads compatibility library
3553 has been installed. (We don't want to use it, so we shouldn't
3554 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3555 - Fix a bug where we would declare that we had run out of virtual
3556 addresses when the address space was only half-exhausted. Bugfix
3558 - Correctly handle the case where AutomapHostsOnResolve is set but
3559 no virtual addresses are available. Fixes bug 2328; bugfix on
3560 0.1.2.1-alpha. Bug found by doorss.
3561 - Correctly handle wrapping around to when we run out of virtual
3562 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3563 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3564 because we built it with a too-old version of automake. Thus that
3565 release broke ./configure --enable-openbsd-malloc, which is popular
3566 among really fast exit relays on Linux.
3569 - Update to the January 1 2011 Maxmind GeoLite Country database.
3570 - Introduce output size checks on all of our decryption functions.
3573 - Tor does not build packages correctly with Automake 1.6 and earlier;
3574 added a check to Makefile.am to make sure that we're building with
3575 Automake 1.7 or later.
3578 Changes in version 0.2.2.20-alpha - 2010-12-17
3579 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3580 exploitable bugs. We also fix a variety of other significant bugs,
3581 change the IP address for one of our directory authorities, and update
3582 the minimum version that Tor relays must run to join the network.
3585 - Fix a remotely exploitable bug that could be used to crash instances
3586 of Tor remotely by overflowing on the heap. Remote-code execution
3587 hasn't been confirmed, but can't be ruled out. Everyone should
3588 upgrade. Bugfix on the 0.1.1 series and later.
3589 - Fix a bug that could break accounting on 64-bit systems with large
3590 time_t values, making them hibernate for impossibly long intervals.
3591 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3592 - Fix a logic error in directory_fetches_from_authorities() that
3593 would cause all _non_-exits refusing single-hop-like circuits
3594 to fetch from authorities, when we wanted to have _exits_ fetch
3595 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3597 - Fix a stream fairness bug that would cause newer streams on a given
3598 circuit to get preference when reading bytes from the origin or
3599 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3600 introduced before the first Tor release, in svn revision r152.
3602 o Directory authority changes:
3603 - Change IP address and ports for gabelmoo (v3 directory authority).
3606 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3607 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3608 - Fix an off-by-one error in calculating some controller command
3609 argument lengths. Fortunately, this mistake is harmless since
3610 the controller code does redundant NUL termination too. Found by
3611 boboper. Bugfix on 0.1.1.1-alpha.
3612 - Do not dereference NULL if a bridge fails to build its
3613 extra-info descriptor. Found by an anonymous commenter on
3614 Trac. Bugfix on 0.2.2.19-alpha.
3617 - Update to the December 1 2010 Maxmind GeoLite Country database.
3618 - Directory authorities now reject relays running any versions of
3619 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3620 known bugs that keep RELAY_EARLY cells from working on rendezvous
3621 circuits. Followup to fix for bug 2081.
3622 - Directory authorities now reject relays running any version of Tor
3623 older than 0.2.0.26-rc. That version is the earliest that fetches
3624 current directory information correctly. Fixes bug 2156.
3625 - Report only the top 10 ports in exit-port stats in order not to
3626 exceed the maximum extra-info descriptor length of 50 KB. Implements
3630 Changes in version 0.2.1.28 - 2010-12-17
3631 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3632 exploitable bugs. We also took this opportunity to change the IP address
3633 for one of our directory authorities, and to update the geoip database
3637 - Fix a remotely exploitable bug that could be used to crash instances
3638 of Tor remotely by overflowing on the heap. Remote-code execution
3639 hasn't been confirmed, but can't be ruled out. Everyone should
3640 upgrade. Bugfix on the 0.1.1 series and later.
3642 o Directory authority changes:
3643 - Change IP address and ports for gabelmoo (v3 directory authority).
3646 - Update to the December 1 2010 Maxmind GeoLite Country database.
3649 Changes in version 0.2.1.27 - 2010-11-23
3650 Yet another OpenSSL security patch broke its compatibility with Tor:
3651 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3652 also took this opportunity to fix several crash bugs, integrate a new
3653 directory authority, and update the bundled GeoIP database.
3656 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3657 No longer set the tlsext_host_name extension on server SSL objects;
3658 but continue to set it on client SSL objects. Our goal in setting
3659 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3660 bugfix on 0.2.1.1-alpha.
3661 - Do not log messages to the controller while shrinking buffer
3662 freelists. Doing so would sometimes make the controller connection
3663 try to allocate a buffer chunk, which would mess up the internals
3664 of the freelist and cause an assertion failure. Fixes bug 1125;
3665 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3666 - Learn our external IP address when we're a relay or bridge, even if
3667 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3668 where we introduced bridge relays that don't need to publish to
3669 be useful. Fixes bug 2050.
3670 - Do even more to reject (and not just ignore) annotations on
3671 router descriptors received anywhere but from the cache. Previously
3672 we would ignore such annotations at first, but cache them to disk
3673 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3674 - When you're using bridges and your network goes away and your
3675 bridges get marked as down, recover when you attempt a new socks
3676 connection (if the network is back), rather than waiting up to an
3677 hour to try fetching new descriptors for your bridges. Bugfix on
3678 0.2.0.3-alpha; fixes bug 1981.
3681 - Move to the November 2010 Maxmind GeoLite country db (rather
3682 than the June 2009 ip-to-country GeoIP db) for our statistics that
3683 count how many users relays are seeing from each country. Now we'll
3684 have more accurate data, especially for many African countries.
3686 o New directory authorities:
3687 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3691 - Fix an assertion failure that could occur in directory caches or
3692 bridge users when using a very short voting interval on a testing
3693 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3695 - Enforce multiplicity rules when parsing annotations. Bugfix on
3696 0.2.0.8-alpha. Found by piebeer.
3697 - Allow handshaking OR connections to take a full KeepalivePeriod
3698 seconds to handshake. Previously, we would close them after
3699 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3700 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3702 - When building with --enable-gcc-warnings on OpenBSD, disable
3703 warnings in system headers. This makes --enable-gcc-warnings
3704 pass on OpenBSD 4.8.
3707 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3708 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3709 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3710 Servers can start sending this code when enough clients recognize
3711 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3712 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3713 Patch from mingw-san.
3716 - Remove the old debian/ directory from the main Tor distribution.
3717 The official Tor-for-debian git repository lives at the URL
3718 https://git.torproject.org/debian/tor.git
3719 - Stop shipping the old doc/website/ directory in the tarball. We
3720 changed the website format in late 2010, and what we shipped in
3721 0.2.1.26 really wasn't that useful anyway.
3724 Changes in version 0.2.2.19-alpha - 2010-11-22
3725 Yet another OpenSSL security patch broke its compatibility with Tor:
3726 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
3729 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3730 No longer set the tlsext_host_name extension on server SSL objects;
3731 but continue to set it on client SSL objects. Our goal in setting
3732 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3733 bugfix on 0.2.1.1-alpha.
3736 - Try harder not to exceed the maximum length of 50 KB when writing
3737 statistics to extra-info descriptors. This bug was triggered by very
3738 fast relays reporting exit-port, entry, and dirreq statistics.
3739 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
3740 - Publish a router descriptor even if generating an extra-info
3741 descriptor fails. Previously we would not publish a router
3742 descriptor without an extra-info descriptor; this can cause fast
3743 exit relays collecting exit-port statistics to drop from the
3744 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3747 Changes in version 0.2.2.18-alpha - 2010-11-16
3748 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
3749 us lately, makes unpublished bridge relays able to detect their IP
3750 address, and fixes a wide variety of other bugs to get us much closer
3751 to a stable release.
3754 - Do even more to reject (and not just ignore) annotations on
3755 router descriptors received anywhere but from the cache. Previously
3756 we would ignore such annotations at first, but cache them to disk
3757 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3758 - Do not log messages to the controller while shrinking buffer
3759 freelists. Doing so would sometimes make the controller connection
3760 try to allocate a buffer chunk, which would mess up the internals
3761 of the freelist and cause an assertion failure. Fixes bug 1125;
3762 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3763 - Learn our external IP address when we're a relay or bridge, even if
3764 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3765 where we introduced bridge relays that don't need to publish to
3766 be useful. Fixes bug 2050.
3767 - Maintain separate TLS contexts and certificates for incoming and
3768 outgoing connections in bridge relays. Previously we would use the
3769 same TLS contexts and certs for incoming and outgoing connections.
3770 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3771 - Maintain separate identity keys for incoming and outgoing TLS
3772 contexts in bridge relays. Previously we would use the same
3773 identity keys for incoming and outgoing TLS contexts. Bugfix on
3774 0.2.0.3-alpha; addresses the other half of bug 988.
3775 - Avoid an assertion failure when we as an authority receive a
3776 duplicate upload of a router descriptor that we already have,
3777 but which we previously considered an obsolete descriptor.
3778 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
3779 - Avoid a crash bug triggered by looking at a dangling pointer while
3780 setting the network status consensus. Found by Robert Ransom.
3781 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
3782 - Fix a logic error where servers that _didn't_ act as exits would
3783 try to keep their server lists more aggressively up to date than
3784 exits, when it was supposed to be the other way around. Bugfix
3787 o Minor bugfixes (on Tor 0.2.1.x and earlier):
3788 - When we're trying to guess whether we know our IP address as
3789 a relay, we would log various ways that we failed to guess
3790 our address, but never log that we ended up guessing it
3791 successfully. Now add a log line to help confused and anxious
3792 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3793 - Bring the logic that gathers routerinfos and assesses the
3794 acceptability of circuits into line. This prevents a Tor OP from
3795 getting locked in a cycle of choosing its local OR as an exit for a
3796 path (due to a .exit request) and then rejecting the circuit because
3797 its OR is not listed yet. It also prevents Tor clients from using an
3798 OR running in the same instance as an exit (due to a .exit request)
3799 if the OR does not meet the same requirements expected of an OR
3800 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3801 - Correctly describe errors that occur when generating a TLS object.
3802 Previously we would attribute them to a failure while generating a
3803 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3805 - Enforce multiplicity rules when parsing annotations. Bugfix on
3806 0.2.0.8-alpha. Found by piebeer.
3807 - Fix warnings that newer versions of autoconf produced during
3808 ./autogen.sh. These warnings appear to be harmless in our case,
3809 but they were extremely verbose. Fixes bug 2020.
3811 o Minor bugfixes (on Tor 0.2.2.x):
3812 - Enable protection of small arrays whenever we build with gcc
3813 hardening features, not only when also building with warnings
3814 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
3817 - Make hidden services work better in private Tor networks by not
3818 requiring any uptime to join the hidden service descriptor
3819 DHT. Implements ticket 2088.
3820 - Rate-limit the "your application is giving Tor only an IP address"
3821 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3822 - When AllowSingleHopExits is set, print a warning to explain to the
3823 relay operator why most clients are avoiding her relay.
3824 - Update to the November 1 2010 Maxmind GeoLite Country database.
3826 o Code simplifications and refactoring:
3827 - When we fixed bug 1038 we had to put in a restriction not to send
3828 RELAY_EARLY cells on rend circuits. This was necessary as long
3829 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3830 active. Now remove this obsolete check. Resolves bug 2081.
3831 - Some options used different conventions for uppercasing of acronyms
3832 when comparing manpage and source. Fix those in favor of the
3833 manpage, as it makes sense to capitalize acronyms.
3834 - Remove the torrc.complete file. It hasn't been kept up to date
3835 and users will have better luck checking out the manpage.
3836 - Remove the obsolete "NoPublish" option; it has been flagged
3837 as obsolete and has produced a warning since 0.1.1.18-rc.
3838 - Remove everything related to building the expert bundle for OS X.
3839 It has confused many users, doesn't work right on OS X 10.6,
3840 and is hard to get rid of once installed. Resolves bug 1274.
3843 Changes in version 0.2.2.17-alpha - 2010-09-30
3844 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
3845 to use one-hop circuits (which can put the exit relays at higher risk,
3846 plus unbalance the network); fixes a big bug in bandwidth accounting
3847 for relays that want to limit their monthly bandwidth use; fixes a
3848 big pile of bugs in how clients tolerate temporary network failure;
3849 and makes our adaptive circuit build timeout feature (which improves
3850 client performance if your network is fast while not breaking things
3851 if your network is slow) better handle bad networks.
3854 - Exit relays now try harder to block exit attempts from unknown
3855 relays, to make it harder for people to use them as one-hop proxies
3856 a la tortunnel. Controlled by the refuseunknownexits consensus
3857 parameter (currently enabled), or you can override it on your
3858 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
3860 o Major bugfixes (0.2.1.x and earlier):
3861 - Fix a bug in bandwidth accounting that could make us use twice
3862 the intended bandwidth when our interval start changes due to
3863 daylight saving time. Now we tolerate skew in stored vs computed
3864 interval starts: if the start of the period changes by no more than
3865 50% of the period's duration, we remember bytes that we transferred
3866 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3867 - Always search the Windows system directory for system DLLs, and
3868 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
3869 - When you're using bridges and your network goes away and your
3870 bridges get marked as down, recover when you attempt a new socks
3871 connection (if the network is back), rather than waiting up to an
3872 hour to try fetching new descriptors for your bridges. Bugfix on
3873 0.2.0.3-alpha; fixes bug 1981.
3875 o Major bugfixes (on 0.2.2.x):
3876 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
3878 - Fix a segfault that could happen when operating a bridge relay with
3879 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
3880 - The consensus bandwidth-weights (used by clients to choose fast
3881 relays) entered an unexpected edge case in September where
3882 Exits were much scarcer than Guards, resulting in bad weight
3883 recommendations. Now we compute them using new constraints that
3884 should succeed in all cases. Also alter directory authorities to
3885 not include the bandwidth-weights line if they fail to produce
3886 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
3887 - When weighting bridges during path selection, we used to trust
3888 the bandwidths they provided in their descriptor, only capping them
3889 at 10MB/s. This turned out to be problematic for two reasons:
3890 Bridges could claim to handle a lot more traffic then they
3891 actually would, thus making more clients pick them and have a
3892 pretty effective DoS attack. The other issue is that new bridges
3893 that might not have a good estimate for their bw capacity yet
3894 would not get used at all unless no other bridges are available
3895 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
3897 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
3898 - Ignore cannibalized circuits when recording circuit build times.
3899 This should provide for a minor performance improvement for hidden
3900 service users using 0.2.2.14-alpha, and should remove two spurious
3901 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
3902 - Simplify the logic that causes us to decide if the network is
3903 unavailable for purposes of recording circuit build times. If we
3904 receive no cells whatsoever for the entire duration of a circuit's
3905 full measured lifetime, the network is probably down. Also ignore
3906 one-hop directory fetching circuit timeouts when calculating our
3907 circuit build times. These changes should hopefully reduce the
3908 cases where we see ridiculous circuit build timeouts for people
3909 with spotty wireless connections. Fixes part of bug 1772; bugfix
3911 - Prevent the circuit build timeout from becoming larger than
3912 the maximum build time we have ever seen. Also, prevent the time
3913 period for measurement circuits from becoming larger than twice that
3914 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
3917 - When we run out of directory information such that we can't build
3918 circuits, but then get enough that we can build circuits, log when
3919 we actually construct a circuit, so the user has a better chance of
3920 knowing what's going on. Fixes bug 1362.
3921 - Be more generous with how much bandwidth we'd use up (with
3922 accounting enabled) before entering "soft hibernation". Previously,
3923 we'd refuse new connections and circuits once we'd used up 95% of
3924 our allotment. Now, we use up 95% of our allotment, AND make sure
3925 that we have no more than 500MB (or 3 hours of expected traffic,
3926 whichever is lower) remaining before we enter soft hibernation.
3927 - If we've configured EntryNodes and our network goes away and/or all
3928 our entrynodes get marked down, optimistically retry them all when
3929 a new socks application request appears. Fixes bug 1882.
3930 - Add some more defensive programming for architectures that can't
3931 handle unaligned integer accesses. We don't know of any actual bugs
3932 right now, but that's the best time to fix them. Fixes bug 1943.
3933 - Support line continuations in the torrc config file. If a line
3934 ends with a single backslash character, the newline is ignored, and
3935 the configuration value is treated as continuing on the next line.
3938 o Minor bugfixes (on 0.2.1.x and earlier):
3939 - For bandwidth accounting, calculate our expected bandwidth rate
3940 based on the time during which we were active and not in
3941 soft-hibernation during the last interval. Previously, we were
3942 also considering the time spent in soft-hibernation. If this
3943 was a long time, we would wind up underestimating our bandwidth
3944 by a lot, and skewing our wakeup time towards the start of the
3945 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3947 o Minor bugfixes (on 0.2.2.x):
3948 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
3949 which were disabled by the circuit build timeout changes in
3950 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
3951 - Make sure we don't warn about missing bandwidth weights when
3952 choosing bridges or other relays not in the consensus. Bugfix on
3953 0.2.2.10-alpha; fixes bug 1805.
3954 - In our logs, do not double-report signatures from unrecognized
3955 authorities both as "from unknown authority" and "not
3956 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
3959 Changes in version 0.2.2.16-alpha - 2010-09-17
3960 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
3961 evident at exit relays), and also continues to resolve all the little
3962 bugs that have been filling up trac lately.
3964 o Major bugfixes (stream-level fairness):
3965 - When receiving a circuit-level SENDME for a blocked circuit, try
3966 to package cells fairly from all the streams that had previously
3967 been blocked on that circuit. Previously, we had started with the
3968 oldest stream, and allowed each stream to potentially exhaust
3969 the circuit's package window. This gave older streams on any
3970 given circuit priority over newer ones. Fixes bug 1937. Detected
3971 originally by Camilo Viecco. This bug was introduced before the
3972 first Tor release, in svn commit r152: it is the new winner of
3973 the longest-lived bug prize.
3974 - When the exit relay got a circuit-level sendme cell, it started
3975 reading on the exit streams, even if had 500 cells queued in the
3976 circuit queue already, so the circuit queue just grew and grew in
3977 some cases. We fix this by not re-enabling reading on receipt of a
3978 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3979 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3981 - Newly created streams were allowed to read cells onto circuits,
3982 even if the circuit's cell queue was blocked and waiting to drain.
3983 This created potential unfairness, as older streams would be
3984 blocked, but newer streams would gladly fill the queue completely.
3985 We add code to detect this situation and prevent any stream from
3986 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3990 - Update to the September 1 2010 Maxmind GeoLite Country database.
3991 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3992 not. This would lead to a cookie that is still not group readable.
3993 Closes bug 1843. Suggested by katmagic.
3994 - When logging a rate-limited warning, we now mention how many messages
3995 got suppressed since the last warning.
3996 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3997 do individual connection-level rate limiting of clients. The torrc
3998 config options with the same names trump the consensus params, if
3999 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4000 consensus params which were broken from 0.2.2.7-alpha through
4001 0.2.2.14-alpha. Closes bug 1947.
4002 - When a router changes IP address or port, authorities now launch
4003 a new reachability test for it. Implements ticket 1899.
4004 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4005 2 no signature, 4 required" messages about consensus signatures
4006 easier to read, and make sure they get logged at the same severity
4007 as the messages explaining which keys are which. Fixes bug 1290.
4008 - Don't warn when we have a consensus that we can't verify because
4009 of missing certificates, unless those certificates are ones
4010 that we have been trying and failing to download. Fixes bug 1145.
4011 - If you configure your bridge with a known identity fingerprint,
4012 and the bridge authority is unreachable (as it is in at least
4013 one country now), fall back to directly requesting the descriptor
4014 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4016 - When building with --enable-gcc-warnings on OpenBSD, disable
4017 warnings in system headers. This makes --enable-gcc-warnings
4018 pass on OpenBSD 4.8.
4020 o Minor bugfixes (on 0.2.1.x and earlier):
4021 - Authorities will now attempt to download consensuses if their
4022 own efforts to make a live consensus have failed. This change
4023 means authorities that restart will fetch a valid consensus, and
4024 it means authorities that didn't agree with the current consensus
4025 will still fetch and serve it if it has enough signatures. Bugfix
4026 on 0.2.0.9-alpha; fixes bug 1300.
4027 - Ensure DNS requests launched by "RESOLVE" commands from the
4028 controller respect the __LeaveStreamsUnattached setconf options. The
4029 same goes for requests launched via DNSPort or transparent
4030 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4031 - Allow handshaking OR connections to take a full KeepalivePeriod
4032 seconds to handshake. Previously, we would close them after
4033 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4034 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4036 - Rate-limit "Failed to hand off onionskin" warnings.
4037 - Never relay a cell for a circuit we have already destroyed.
4038 Between marking a circuit as closeable and finally closing it,
4039 it may have been possible for a few queued cells to get relayed,
4040 even though they would have been immediately dropped by the next
4041 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4042 - Never queue a cell for a circuit that's already been marked
4044 - Never vote for a server as "Running" if we have a descriptor for
4045 it claiming to be hibernating, and that descriptor was published
4046 more recently than our last contact with the server. Bugfix on
4047 0.2.0.3-alpha; fixes bug 911.
4048 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4051 o Minor bugfixes (on 0.2.2.x):
4052 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4053 down if a directory fetch fails and you've configured either
4054 bridges or EntryNodes. The intent was to mark the relay as down
4055 _unless_ you're using bridges or EntryNodes, since if you are
4056 then you could quickly run out of entry points.
4057 - Fix the Windows directory-listing code. A bug introduced in
4058 0.2.2.14-alpha could make Windows directory servers forget to load
4059 some of their cached v2 networkstatus files.
4060 - Really allow clients to use relays as bridges. Fixes bug 1776;
4061 bugfix on 0.2.2.15-alpha.
4062 - Demote a warn to info that happens when the CellStatistics option
4063 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4064 Reported by Moritz Bartl.
4065 - On Windows, build correctly either with or without Unicode support.
4066 This is necessary so that Tor can support fringe platforms like
4067 Windows 98 (which has no Unicode), or Windows CE (which has no
4068 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4071 - Add a unit test for cross-platform directory-listing code.
4074 Changes in version 0.2.2.15-alpha - 2010-08-18
4075 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4076 fixes a variety of other bugs that were preventing performance
4077 experiments from moving forward, fixes several bothersome memory leaks,
4078 and generally closes a lot of smaller bugs that have been filling up
4082 - Stop assigning the HSDir flag to relays that disable their
4083 DirPort (and thus will refuse to answer directory requests). This
4084 fix should dramatically improve the reachability of hidden services:
4085 hidden services and hidden service clients pick six HSDir relays
4086 to store and retrieve the hidden service descriptor, and currently
4087 about half of the HSDir relays will refuse to work. Bugfix on
4088 0.2.0.10-alpha; fixes part of bug 1693.
4089 - The PerConnBWRate and Burst config options, along with the
4090 bwconnrate and bwconnburst consensus params, initialized each conn's
4091 token bucket values only when the connection is established. Now we
4092 update them if the config options change, and update them every time
4093 we get a new consensus. Otherwise we can encounter an ugly edge
4094 case where we initialize an OR conn to client-level bandwidth,
4095 but then later the relay joins the consensus and we leave it
4096 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4097 - Fix a regression that caused Tor to rebind its ports if it receives
4098 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4101 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4102 should give us approximately 40-50% more Guard-flagged nodes,
4103 improving the anonymity the Tor network can provide and also
4104 decreasing the dropoff in throughput that relays experience when
4105 they first get the Guard flag.
4106 - Allow enabling or disabling the *Statistics config options while
4110 - Update to the August 1 2010 Maxmind GeoLite Country database.
4111 - Have the controller interface give a more useful message than
4112 "Internal Error" in response to failed GETINFO requests.
4113 - Warn when the same option is provided more than once in a torrc
4114 file, on the command line, or in a single SETCONF statement, and
4115 the option is one that only accepts a single line. Closes bug 1384.
4116 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4117 Patch from mingw-san.
4118 - Add support for the country code "{??}" in torrc options like
4119 ExcludeNodes, to indicate all routers of unknown country. Closes
4121 - Relays report the number of bytes spent on answering directory
4122 requests in extra-info descriptors similar to {read,write}-history.
4123 Implements enhancement 1790.
4125 o Minor bugfixes (on 0.2.1.x and earlier):
4126 - Complain if PublishServerDescriptor is given multiple arguments that
4127 include 0 or 1. This configuration will be rejected in the future.
4128 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4129 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4130 Bugfix on 0.2.0.13-alpha; closes bug 928.
4131 - Change "Application request when we're believed to be offline."
4132 notice to "Application request when we haven't used client
4133 functionality lately.", to clarify that it's not an error. Bugfix
4134 on 0.0.9.3; fixes bug 1222.
4135 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4136 would return "551 Internal error" rather than "552 Unrecognized key
4137 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4138 - Users can't configure a regular relay to be their bridge. It didn't
4139 work because when Tor fetched the bridge descriptor, it found
4140 that it already had it, and didn't realize that the purpose of the
4141 descriptor had changed. Now we replace routers with a purpose other
4142 than bridge with bridge descriptors when fetching them. Bugfix on
4143 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4144 refetch the descriptor with router purpose 'general', disabling
4146 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4147 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4148 on 0.2.0.10-alpha; fixes bug 1808.
4149 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4150 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4151 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4152 Servers can start sending this code when enough clients recognize
4153 it. Also update the spec to reflect this new reason. Bugfix on
4154 0.1.0.1-rc; fixes part of bug 1793.
4155 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4156 when we switch from being a public relay to a bridge. Otherwise
4157 there will still be clients that see the relay in their consensus,
4158 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4160 - Instead of giving an assertion failure on an internal mismatch
4161 on estimated freelist size, just log a BUG warning and try later.
4162 Mitigates but does not fix bug 1125.
4163 - Fix an assertion failure that could occur in caches or bridge users
4164 when using a very short voting interval on a testing network.
4165 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4167 o Minor bugfixes (on 0.2.2.x):
4168 - Alter directory authorities to always consider Exit-flagged nodes
4169 as potential Guard nodes in their votes. The actual decision to
4170 use Exits as Guards is done in the consensus bandwidth weights.
4171 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4172 - When the controller is reporting the purpose of circuits that
4173 didn't finish building before the circuit build timeout, it was
4174 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4175 - Our libevent version parsing code couldn't handle versions like
4176 1.4.14b-stable and incorrectly warned the user about using an
4177 old and broken version of libevent. Treat 1.4.14b-stable like
4178 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4180 - Don't use substitution references like $(VAR:MOD) when
4181 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4182 '$(:x)' to 'x' rather than the empty string. This bites us in
4183 doc/ when configured with --disable-asciidoc. Bugfix on
4184 0.2.2.9-alpha; fixes bug 1773.
4185 - Remove a spurious hidden service server-side log notice about
4186 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4188 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4190 - Correctly report written bytes on linked connections. Found while
4191 implementing 1790. Bugfix on 0.2.2.4-alpha.
4192 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4193 one in dirvote_add_signatures_to_pending_consensus(), and one every
4194 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4195 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4197 o Code simplifications and refactoring:
4198 - Take a first step towards making or.h smaller by splitting out
4199 function definitions for all source files in src/or/. Leave
4200 structures and defines in or.h for now.
4201 - Remove a bunch of unused function declarations as well as a block of
4202 #if 0'd code from the unit tests. Closes bug 1824.
4203 - New unit tests for exit-port history statistics; refactored exit
4204 statistics code to be more easily tested.
4205 - Remove the old debian/ directory from the main Tor distribution.
4206 The official Tor-for-debian git repository lives at the URL
4207 https://git.torproject.org/debian/tor.git
4210 Changes in version 0.2.2.14-alpha - 2010-07-12
4211 Tor 0.2.2.14-alpha greatly improves client-side handling of
4212 circuit build timeouts, which are used to estimate speed and improve
4213 performance. We also move to a much better GeoIP database, port Tor to
4214 Windows CE, introduce new compile flags that improve code security,
4215 add an eighth v3 directory authority, and address a lot of more
4219 - Tor directory authorities no longer crash when started with a
4220 cached-microdesc-consensus file in their data directory. Bugfix
4221 on 0.2.2.6-alpha; fixes bug 1532.
4222 - Treat an unset $HOME like an empty $HOME rather than triggering an
4223 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4224 - Ignore negative and large circuit build timeout values that can
4225 happen during a suspend or hibernate. These values caused various
4226 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4227 - Alter calculation of Pareto distribution parameter 'Xm' for
4228 Circuit Build Timeout learning to use the weighted average of the
4229 top N=3 modes (because we have three entry guards). Considering
4230 multiple modes should improve the timeout calculation in some cases,
4231 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4233 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4234 right censored distribution model. This approach improves over the
4235 synthetic timeout generation approach that was producing insanely
4236 high timeout values. Now we calculate build timeouts using truncated
4237 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4238 - Do not close circuits that are under construction when they reach
4239 the circuit build timeout. Instead, leave them building (but do not
4240 use them) for up until the time corresponding to the 95th percentile
4241 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4242 to provide better data for the new Pareto model. This percentile
4243 can be controlled by the consensus.
4246 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4247 June 2009 ip-to-country GeoIP db) for our statistics that count
4248 how many users relays are seeing from each country. Now we have
4249 more accurate data for many African countries.
4250 - Port Tor to build and run correctly on Windows CE systems, using
4251 the wcecompat library. Contributed by Valerio Lupi.
4252 - New "--enable-gcc-hardening" ./configure flag (off by default)
4253 to turn on gcc compile time hardening options. It ensures
4254 that signed ints have defined behavior (-fwrapv), enables
4255 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4256 with canaries (-fstack-protector-all), turns on ASLR protection if
4257 supported by the kernel (-fPIE, -pie), and adds additional security
4258 related warnings. Verified to work on Mac OS X and Debian Lenny.
4259 - New "--enable-linker-hardening" ./configure flag (off by default)
4260 to turn on ELF specific hardening features (relro, now). This does
4261 not work with Mac OS X or any other non-ELF binary format.
4263 o New directory authorities:
4264 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4268 - New config option "WarnUnsafeSocks 0" disables the warning that
4269 occurs whenever Tor receives a socks handshake using a version of
4270 the socks protocol that can only provide an IP address (rather
4271 than a hostname). Setups that do DNS locally over Tor are fine,
4272 and we shouldn't spam the logs in that case.
4273 - Convert the HACKING file to asciidoc, and add a few new sections
4274 to it, explaining how we use Git, how we make changelogs, and
4275 what should go in a patch.
4276 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4277 event, to give information on the current rate of circuit timeouts
4278 over our stored history.
4279 - Add ability to disable circuit build time learning via consensus
4280 parameter and via a LearnCircuitBuildTimeout config option. Also
4281 automatically disable circuit build time calculation if we are
4282 either a AuthoritativeDirectory, or if we fail to write our state
4283 file. Fixes bug 1296.
4284 - More gracefully handle corrupt state files, removing asserts
4285 in favor of saving a backup and resetting state.
4286 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4290 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4292 - When a2x fails, mention that the user could disable manpages instead
4293 of trying to fix their asciidoc installation.
4294 - Where available, use Libevent 2.0's periodic timers so that our
4295 once-per-second cleanup code gets called even more closely to
4296 once per second than it would otherwise. Fixes bug 943.
4297 - If you run a bridge that listens on multiple IP addresses, and
4298 some user configures a bridge address that uses a different IP
4299 address than your bridge writes in its router descriptor, and the
4300 user doesn't specify an identity key, their Tor would discard the
4301 descriptor because "it isn't one of our configured bridges", and
4302 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4303 Bugfix on 0.2.0.3-alpha.
4304 - If OpenSSL fails to make a duplicate of a private or public key, log
4305 an error message and try to exit cleanly. May help with debugging
4306 if bug 1209 ever remanifests.
4307 - Save a couple bytes in memory allocation every time we escape
4308 certain characters in a string. Patch from Florian Zumbiehl.
4309 - Make it explicit that we don't cannibalize one-hop circuits. This
4310 happens in the wild, but doesn't turn out to be a problem because
4311 we fortunately don't use those circuits. Many thanks to outofwords
4312 for the initial analysis and to swissknife who confirmed that
4313 two-hop circuits are actually created.
4314 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4315 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4316 - Eliminate a case where a circuit build time warning was displayed
4317 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4320 Changes in version 0.2.1.26 - 2010-05-02
4321 Tor 0.2.1.26 addresses the recent connection and memory overload
4322 problems we've been seeing on relays, especially relays with their
4323 DirPort open. If your relay has been crashing, or you turned it off
4324 because it used too many resources, give this release a try.
4326 This release also fixes yet another instance of broken OpenSSL libraries
4327 that was causing some relays to drop out of the consensus.
4330 - Teach relays to defend themselves from connection overload. Relays
4331 now close idle circuits early if it looks like they were intended
4332 for directory fetches. Relays are also more aggressive about closing
4333 TLS connections that have no circuits on them. Such circuits are
4334 unlikely to be re-used, and tens of thousands of them were piling
4335 up at the fast relays, causing the relays to run out of sockets
4336 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4337 their directory fetches over TLS).
4338 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4339 that claim to be earlier than 0.9.8m, but which have in reality
4340 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4341 behavior. Possible fix for some cases of bug 1346.
4342 - Directory mirrors were fetching relay descriptors only from v2
4343 directory authorities, rather than v3 authorities like they should.
4344 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4345 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4348 - Finally get rid of the deprecated and now harmful notion of "clique
4349 mode", where directory authorities maintain TLS connections to
4353 - In the util/threads test, no longer free the test_mutex before all
4354 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4355 - The master thread could starve the worker threads quite badly on
4356 certain systems, causing them to run only partially in the allowed
4357 window. This resulted in test failures. Now the master thread sleeps
4358 occasionally for a few microseconds while the two worker-threads
4359 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4362 Changes in version 0.2.2.13-alpha - 2010-04-24
4363 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4364 problems we've been seeing on relays, especially relays with their
4365 DirPort open. If your relay has been crashing, or you turned it off
4366 because it used too many resources, give this release a try.
4369 - Teach relays to defend themselves from connection overload. Relays
4370 now close idle circuits early if it looks like they were intended
4371 for directory fetches. Relays are also more aggressive about closing
4372 TLS connections that have no circuits on them. Such circuits are
4373 unlikely to be re-used, and tens of thousands of them were piling
4374 up at the fast relays, causing the relays to run out of sockets
4375 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4376 their directory fetches over TLS).
4379 - Finally get rid of the deprecated and now harmful notion of "clique
4380 mode", where directory authorities maintain TLS connections to
4382 - Directory authorities now do an immediate reachability check as soon
4383 as they hear about a new relay. This change should slightly reduce
4384 the time between setting up a relay and getting listed as running
4385 in the consensus. It should also improve the time between setting
4386 up a bridge and seeing use by bridge users.
4387 - Directory authorities no longer launch a TLS connection to every
4388 relay as they startup. Now that we have 2k+ descriptors cached,
4389 the resulting network hiccup is becoming a burden. Besides,
4390 authorities already avoid voting about Running for the first half
4391 hour of their uptime.
4394 Changes in version 0.2.2.12-alpha - 2010-04-20
4395 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4396 handle and vote on descriptors. It was causing relays to drop out of
4400 - Many relays have been falling out of the consensus lately because
4401 not enough authorities know about their descriptor for them to get
4402 a majority of votes. When we deprecated the v2 directory protocol,
4403 we got rid of the only way that v3 authorities can hear from each
4404 other about other descriptors. Now authorities examine every v3
4405 vote for new descriptors, and fetch them from that authority. Bugfix
4407 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4408 and a warning in or.h related to bandwidth_weight_rule_t that
4409 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4411 - Fix a segfault on relays when DirReqStatistics is enabled
4412 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4416 - Demote a confusing TLS warning that relay operators might get when
4417 someone tries to talk to their OrPort. It is neither the operator's
4418 fault nor can they do anything about it. Fixes bug 1364; bugfix
4422 Changes in version 0.2.2.11-alpha - 2010-04-15
4423 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4424 libraries that was causing some relays to drop out of the consensus.
4427 - Directory mirrors were fetching relay descriptors only from v2
4428 directory authorities, rather than v3 authorities like they should.
4429 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4430 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4431 - Fix a parsing error that made every possible value of
4432 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
4433 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
4434 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
4435 about the option without breaking older ones.
4436 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4437 that claim to be earlier than 0.9.8m, but which have in reality
4438 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4439 behavior. Possible fix for some cases of bug 1346.
4442 - Experiment with a more aggressive approach to preventing clients
4443 from making one-hop exit streams. Exit relays who want to try it
4444 out can set "RefuseUnknownExits 1" in their torrc, and then look
4445 for "Attempt by %s to open a stream" log messages. Let us know
4447 - Add support for statically linking zlib by specifying
4448 --enable-static-zlib, to go with our support for statically linking
4449 openssl and libevent. Resolves bug 1358.
4452 - Fix a segfault that happens whenever a Tor client that is using
4453 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
4455 - When we cleaned up the contrib/tor-exit-notice.html file, we left
4456 out the first line. Fixes bug 1295.
4457 - When building the manpage from a tarball, we required asciidoc, but
4458 the asciidoc -> roff/html conversion was already done for the
4459 tarball. Make 'make' complain only when we need asciidoc (either
4460 because we're compiling directly from git, or because we altered
4461 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
4462 - When none of the directory authorities vote on any params, Tor
4463 segfaulted when trying to make the consensus from the votes. We
4464 didn't trigger the bug in practice, because authorities do include
4465 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
4468 - In the util/threads test, no longer free the test_mutex before all
4469 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4470 - The master thread could starve the worker threads quite badly on
4471 certain systems, causing them to run only partially in the allowed
4472 window. This resulted in test failures. Now the master thread sleeps
4473 occasionally for a few microseconds while the two worker-threads
4474 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4477 Changes in version 0.2.2.10-alpha - 2010-03-07
4478 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
4479 could prevent relays from guessing their IP address correctly. It also
4480 starts the groundwork for another client-side performance boost, since
4481 currently we're not making efficient use of relays that have both the
4482 Guard flag and the Exit flag.
4485 - Fix a regression from our patch for bug 1244 that caused relays
4486 to guess their IP address incorrectly if they didn't set Address
4487 in their torrc and/or their address fails to resolve. Bugfix on
4488 0.2.2.9-alpha; fixes bug 1269.
4490 o Major features (performance):
4491 - Directory authorities now compute consensus weightings that instruct
4492 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4493 and no flag. Clients that use these weightings will distribute
4494 network load more evenly across these different relay types. The
4495 weightings are in the consensus so we can change them globally in
4496 the future. Extra thanks to "outofwords" for finding some nasty
4497 security bugs in the first implementation of this feature.
4499 o Minor features (performance):
4500 - Always perform router selections using weighted relay bandwidth,
4501 even if we don't need a high capacity circuit at the time. Non-fast
4502 circuits now only differ from fast ones in that they can use relays
4503 not marked with the Fast flag. This "feature" could turn out to
4504 be a horrible bug; we should investigate more before it goes into
4508 - Allow disabling building of the manpages. Skipping the manpage
4509 speeds up the build considerably.
4511 o Minor bugfixes (on 0.2.2.x):
4512 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4513 Bugfix on 0.2.2.9-alpha.
4514 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4515 config option. Bugfix on 0.2.2.7-alpha.
4516 - Ship the asciidoc-helper file in the tarball, so that people can
4517 build from source if they want to, and touching the .1.txt files
4518 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4520 o Minor bugfixes (on 0.2.1.x or earlier):
4521 - Fix a dereference-then-NULL-check sequence when publishing
4522 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4524 - Fix another dereference-then-NULL-check sequence. Bugfix on
4525 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4526 - Make sure we treat potentially not NUL-terminated strings correctly.
4527 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4529 o Code simplifications and refactoring:
4530 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4531 compliant. Based on a patch from Christian Kujau.
4532 - Don't use sed in asciidoc-helper anymore.
4533 - Make the build process fail if asciidoc cannot be found and
4534 building with asciidoc isn't disabled.
4537 Changes in version 0.2.2.9-alpha - 2010-02-22
4538 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4539 location of a directory authority, and cleans up a bunch of small bugs.
4541 o Directory authority changes:
4542 - Change IP address for dannenberg (v3 directory authority), and
4543 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4544 service directory authority) from the list.
4547 - Make Tor work again on the latest OS X: when deciding whether to
4548 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4549 version at run-time, not compile time. We need to do this because
4550 Apple doesn't update its dev-tools headers when it updates its
4551 libraries in a security patch.
4552 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4553 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4554 a memory leak when requesting a hidden service descriptor we've
4555 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4557 - Authorities could be tricked into giving out the Exit flag to relays
4558 that didn't allow exiting to any ports. This bug could screw
4559 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4560 1238. Bug discovered by Martin Kowalczyk.
4561 - When freeing a session key, zero it out completely. We only zeroed
4562 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4563 patched by ekir. Fixes bug 1254.
4566 - Fix static compilation by listing the openssl libraries in the right
4567 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4568 - Resume handling .exit hostnames in a special way: originally we
4569 stripped the .exit part and used the requested exit relay. In
4570 0.2.2.1-alpha we stopped treating them in any special way, meaning
4571 if you use a .exit address then Tor will pass it on to the exit
4572 relay. Now we reject the .exit stream outright, since that behavior
4573 might be more expected by the user. Found and diagnosed by Scott
4574 Bennett and Downie on or-talk.
4575 - Don't spam the controller with events when we have no file
4576 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4577 for log messages was already solved from bug 748.)
4578 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4580 - Make the DNSPort option work with libevent 2.x. Don't alter the
4581 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4582 - Emit a GUARD DROPPED controller event for a case we missed.
4583 - Make more fields in the controller protocol case-insensitive, since
4584 control-spec.txt said they were.
4585 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4586 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4587 - Fix a spec conformance issue: the network-status-version token
4588 must be the first token in a v3 consensus or vote. Discovered by
4589 parakeep. Bugfix on 0.2.0.3-alpha.
4591 o Code simplifications and refactoring:
4592 - Generate our manpage and HTML documentation using Asciidoc. This
4593 change should make it easier to maintain the documentation, and
4595 - Remove the --enable-iphone option. According to reports from Marco
4596 Bonetti, Tor builds fine without any special tweaking on recent
4597 iPhone SDK versions.
4598 - Removed some unnecessary files from the source distribution. The
4599 AUTHORS file has now been merged into the people page on the
4600 website. The roadmaps and design doc can now be found in the
4601 projects directory in svn.
4602 - Enabled various circuit build timeout constants to be controlled
4603 by consensus parameters. Also set better defaults for these
4604 parameters based on experimentation on broadband and simulated
4608 - The 'EXTENDCIRCUIT' control port command can now be used with
4609 a circ id of 0 and no path. This feature will cause Tor to build
4610 a new 'fast' general purpose circuit using its own path selection
4612 - Added a BUILDTIMEOUT_SET controller event to describe changes
4613 to the circuit build timeout.
4614 - Future-proof the controller protocol a bit by ignoring keyword
4615 arguments we do not recognize.
4616 - Expand homedirs passed to tor-checkkey. This should silence a
4617 coverity complaint about passing a user-supplied string into
4618 open() without checking it.
4621 Changes in version 0.2.1.25 - 2010-03-16
4622 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4623 prevent relays from guessing their IP address correctly. It also fixes
4624 several minor potential security bugs.
4627 - Fix a regression from our patch for bug 1244 that caused relays
4628 to guess their IP address incorrectly if they didn't set Address
4629 in their torrc and/or their address fails to resolve. Bugfix on
4630 0.2.1.23; fixes bug 1269.
4631 - When freeing a session key, zero it out completely. We only zeroed
4632 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4633 patched by ekir. Fixes bug 1254.
4636 - Fix a dereference-then-NULL-check sequence when publishing
4637 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4639 - Fix another dereference-then-NULL-check sequence. Bugfix on
4640 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4641 - Make sure we treat potentially not NUL-terminated strings correctly.
4642 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4646 Changes in version 0.2.1.24 - 2010-02-21
4647 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4651 - Work correctly out-of-the-box with even more vendor-patched versions
4652 of OpenSSL. In particular, make it so Debian and OS X don't need
4653 customized patches to run/build.
4656 Changes in version 0.2.1.23 - 2010-02-13
4657 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4658 again on the latest OS X, and updates the location of a directory
4661 o Major bugfixes (performance):
4662 - We were selecting our guards uniformly at random, and then weighting
4663 which of our guards we'd use uniformly at random. This imbalance
4664 meant that Tor clients were severely limited on throughput (and
4665 probably latency too) by the first hop in their circuit. Now we
4666 select guards weighted by currently advertised bandwidth. We also
4667 automatically discard guards picked using the old algorithm. Fixes
4668 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4671 - Make Tor work again on the latest OS X: when deciding whether to
4672 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4673 version at run-time, not compile time. We need to do this because
4674 Apple doesn't update its dev-tools headers when it updates its
4675 libraries in a security patch.
4676 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4677 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4678 a memory leak when requesting a hidden service descriptor we've
4679 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4682 o Directory authority changes:
4683 - Change IP address for dannenberg (v3 directory authority), and
4684 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4685 service directory authority) from the list.
4688 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4689 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4692 - Avoid a mad rush at the beginning of each month when each client
4693 rotates half of its guards. Instead we spread the rotation out
4694 throughout the month, but we still avoid leaving a precise timestamp
4695 in the state file about when we first picked the guard. Improves
4696 over the behavior introduced in 0.1.2.17.
4699 Changes in version 0.2.2.8-alpha - 2010-01-26
4700 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4701 causing bridge relays to disappear. If you're running a bridge,
4705 - Fix a memory corruption bug on bridges that occured during the
4706 inclusion of stats data in extra-info descriptors. Also fix the
4707 interface for geoip_get_bridge_stats* to prevent similar bugs in
4708 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4709 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4712 - Ignore OutboundBindAddress when connecting to localhost.
4713 Connections to localhost need to come _from_ localhost, or else
4714 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4718 Changes in version 0.2.2.7-alpha - 2010-01-19
4719 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4720 as laying the groundwork for further relay-side performance fixes. It
4721 also starts cleaning up client behavior with respect to the EntryNodes,
4722 ExitNodes, and StrictNodes config options.
4724 This release also rotates two directory authority keys, due to a
4725 security breach of some of the Torproject servers.
4727 o Directory authority changes:
4728 - Rotate keys (both v3 identity and relay identity) for moria1
4731 o Major features (performance):
4732 - We were selecting our guards uniformly at random, and then weighting
4733 which of our guards we'd use uniformly at random. This imbalance
4734 meant that Tor clients were severely limited on throughput (and
4735 probably latency too) by the first hop in their circuit. Now we
4736 select guards weighted by currently advertised bandwidth. We also
4737 automatically discard guards picked using the old algorithm. Fixes
4738 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4739 - When choosing which cells to relay first, relays can now favor
4740 circuits that have been quiet recently, to provide lower latency
4741 for low-volume circuits. By default, relays enable or disable this
4742 feature based on a setting in the consensus. You can override
4743 this default by using the new "CircuitPriorityHalflife" config
4744 option. Design and code by Ian Goldberg, Can Tang, and Chris
4746 - Add separate per-conn write limiting to go with the per-conn read
4747 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4748 but never per-conn write limits.
4749 - New consensus params "bwconnrate" and "bwconnburst" to let us
4750 rate-limit client connections as they enter the network. It's
4751 controlled in the consensus so we can turn it on and off for
4752 experiments. It's starting out off. Based on proposal 163.
4754 o Major features (relay selection options):
4755 - Switch to a StrictNodes config option, rather than the previous
4756 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
4757 "StrictExcludeNodes" option.
4758 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4759 change during a config reload, mark and discard all our origin
4760 circuits. This fix should address edge cases where we change the
4761 config options and but then choose a circuit that we created before
4763 - If EntryNodes or ExitNodes are set, be more willing to use an
4764 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
4766 - Make EntryNodes config option much more aggressive even when
4767 StrictNodes is not set. Before it would prepend your requested
4768 entrynodes to your list of guard nodes, but feel free to use others
4769 after that. Now it chooses only from your EntryNodes if any of
4770 those are available, and only falls back to others if a) they're
4771 all down and b) StrictNodes is not set.
4772 - Now we refresh your entry guards from EntryNodes at each consensus
4773 fetch -- rather than just at startup and then they slowly rot as
4774 the network changes.
4777 - Stop bridge directory authorities from answering dbg-stability.txt
4778 directory queries, which would let people fetch a list of all
4779 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4782 - Log a notice when we get a new control connection. Now it's easier
4783 for security-conscious users to recognize when a local application
4784 is knocking on their controller door. Suggested by bug 1196.
4785 - New config option "CircuitStreamTimeout" to override our internal
4786 timeout schedule for how many seconds until we detach a stream from
4787 a circuit and try a new circuit. If your network is particularly
4788 slow, you might want to set this to a number like 60.
4789 - New controller command "getinfo config-text". It returns the
4790 contents that Tor would write if you send it a SAVECONF command,
4791 so the controller can write the file to disk itself.
4792 - New options for SafeLogging to allow scrubbing only log messages
4793 generated while acting as a relay.
4794 - Ship the bridges spec file in the tarball too.
4795 - Avoid a mad rush at the beginning of each month when each client
4796 rotates half of its guards. Instead we spread the rotation out
4797 throughout the month, but we still avoid leaving a precise timestamp
4798 in the state file about when we first picked the guard. Improves
4799 over the behavior introduced in 0.1.2.17.
4801 o Minor bugfixes (compiling):
4802 - Fix compilation on OS X 10.3, which has a stub mlockall() but
4803 hides it. Bugfix on 0.2.2.6-alpha.
4804 - Fix compilation on Solaris by removing support for the
4805 DisableAllSwap config option. Solaris doesn't have an rlimit for
4806 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
4809 o Minor bugfixes (crashes):
4810 - Do not segfault when writing buffer stats when we haven't observed
4811 a single circuit to report about. Found by Fabian Lanze. Bugfix on
4813 - If we're in the pathological case where there's no exit bandwidth
4814 but there is non-exit bandwidth, or no guard bandwidth but there
4815 is non-guard bandwidth, don't crash during path selection. Bugfix
4817 - Fix an impossible-to-actually-trigger buffer overflow in relay
4818 descriptor generation. Bugfix on 0.1.0.15.
4820 o Minor bugfixes (privacy):
4821 - Fix an instance where a Tor directory mirror might accidentally
4822 log the IP address of a misbehaving Tor client. Bugfix on
4824 - Don't list Windows capabilities in relay descriptors. We never made
4825 use of them, and maybe it's a bad idea to publish them. Bugfix
4828 o Minor bugfixes (other):
4829 - Resolve an edge case in path weighting that could make us misweight
4830 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4831 - Fix statistics on client numbers by country as seen by bridges that
4832 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
4833 intervals instead of variable 12-to-48-hour intervals.
4834 - After we free an internal connection structure, overwrite it
4835 with a different memory value than we use for overwriting a freed
4836 internal circuit structure. Should help with debugging. Suggested
4838 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
4842 - Remove the HSAuthorityRecordStats option that version 0 hidden
4843 service authorities could have used to track statistics of overall
4844 hidden service usage.
4847 Changes in version 0.2.1.22 - 2010-01-19
4848 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4849 authorities -- it would tell you its whole history of bridge descriptors
4850 if you make the right directory request. This stable update also
4851 rotates two of the seven v3 directory authority keys and locations.
4853 o Directory authority changes:
4854 - Rotate keys (both v3 identity and relay identity) for moria1
4858 - Stop bridge directory authorities from answering dbg-stability.txt
4859 directory queries, which would let people fetch a list of all
4860 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4863 Changes in version 0.2.1.21 - 2009-12-21
4864 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4865 library. If you use Tor on Linux / Unix and you're getting SSL
4866 renegotiation errors, upgrading should help. We also recommend an
4867 upgrade if you're an exit relay.
4870 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4871 handshake from working unless we explicitly tell OpenSSL that we
4872 are using SSL renegotiation safely. We are, of course, but OpenSSL
4873 0.9.8l won't work unless we say we are.
4874 - Avoid crashing if the client is trying to upload many bytes and the
4875 circuit gets torn down at the same time, or if the flip side
4876 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4879 - Do not refuse to learn about authority certs and v2 networkstatus
4880 documents that are older than the latest consensus. This bug might
4881 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4882 Spotted and fixed by xmux.
4883 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4884 trigger platform-specific option misparsing case found by Coverity
4886 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4887 trigger assert. Fixes bug 1173.
4890 Changes in version 0.2.2.6-alpha - 2009-11-19
4891 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
4892 support for the new lower-footprint "microdescriptor" directory design,
4893 future-proofing our consensus format against new hash functions or
4894 other changes, and an Android port. It also makes Tor compatible with
4895 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
4898 - Directory authorities can now create, vote on, and serve multiple
4899 parallel formats of directory data as part of their voting process.
4900 Partially implements Proposal 162: "Publish the consensus in
4902 - Directory authorities can now agree on and publish small summaries
4903 of router information that clients can use in place of regular
4904 server descriptors. This transition will eventually allow clients
4905 to use far less bandwidth for downloading information about the
4906 network. Begins the implementation of Proposal 158: "Clients
4907 download consensus + microdescriptors".
4908 - The directory voting system is now extensible to use multiple hash
4909 algorithms for signatures and resource selection. Newer formats
4910 are signed with SHA256, with a possibility for moving to a better
4911 hash algorithm in the future.
4912 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4913 current and future memory pages via mlockall(). On supported
4914 platforms (modern Linux and probably BSD but not Windows or OS X),
4915 this should effectively disable any and all attempts to page out
4916 memory. This option requires that you start your Tor as root --
4917 if you use DisableAllSwap, please consider using the User option
4918 to properly reduce the privileges of your Tor.
4919 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4920 to help Tor build correctly for Android phones.
4923 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4924 handshake from working unless we explicitly tell OpenSSL that we
4925 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
4926 won't work unless we say we are.
4929 - Fix a crash bug when trying to initialize the evdns module in
4930 Libevent 2. Bugfix on 0.2.1.16-rc.
4931 - Stop logging at severity 'warn' when some other Tor client tries
4932 to establish a circuit with us using weak DH keys. It's a protocol
4933 violation, but that doesn't mean ordinary users need to hear about
4934 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4935 - Do not refuse to learn about authority certs and v2 networkstatus
4936 documents that are older than the latest consensus. This bug might
4937 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4938 Spotted and fixed by xmux.
4939 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4940 - If all authorities restart at once right before a consensus vote,
4941 nobody will vote about "Running", and clients will get a consensus
4942 with no usable relays. Instead, authorities refuse to build a
4943 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4944 - If your relay can't keep up with the number of incoming create
4945 cells, it would log one warning per failure into your logs. Limit
4946 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4947 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4948 on 0.2.0.3-alpha; fixes bug 1113.
4949 - Fix a memory leak on directory authorities during voting that was
4950 introduced in 0.2.2.1-alpha. Found via valgrind.
4953 Changes in version 0.2.1.20 - 2009-10-15
4954 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4955 services at once, prepares for more performance improvements, and
4956 fixes a bunch of smaller bugs.
4958 The Windows and OS X bundles also include a more recent Vidalia,
4959 and switch from Privoxy to Polipo.
4961 The OS X installers are now drag and drop. It's best to un-install
4962 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4963 you want to upgrade, you'll need to update the paths for Tor and Polipo
4964 in the Vidalia Settings window.
4967 - Send circuit or stream sendme cells when our window has decreased
4968 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4969 by Karsten when testing the "reduce circuit window" performance
4970 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4971 before the release of Tor 0.0.0. This is the new winner of the
4973 - Fix a remotely triggerable memory leak when a consensus document
4974 contains more than one signature from the same voter. Bugfix on
4976 - Avoid segfault in rare cases when finishing an introduction circuit
4977 as a client and finding out that we don't have an introduction key
4978 for it. Fixes bug 1073. Reported by Aaron Swartz.
4981 - Tor now reads the "circwindow" parameter out of the consensus,
4982 and uses that value for its circuit package window rather than the
4983 default of 1000 cells. Begins the implementation of proposal 168.
4985 o New directory authorities:
4986 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4988 - Move moria1 and tonga to alternate IP addresses.
4991 - Fix a signed/unsigned compile warning in 0.2.1.19.
4992 - Fix possible segmentation fault on directory authorities. Bugfix on
4994 - Fix an extremely rare infinite recursion bug that could occur if
4995 we tried to log a message after shutting down the log subsystem.
4996 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4997 - Fix an obscure bug where hidden services on 64-bit big-endian
4998 systems might mis-read the timestamp in v3 introduce cells, and
4999 refuse to connect back to the client. Discovered by "rotor".
5000 Bugfix on 0.2.1.6-alpha.
5001 - We were triggering a CLOCK_SKEW controller status event whenever
5002 we connect via the v2 connection protocol to any relay that has
5003 a wrong clock. Instead, we should only inform the controller when
5004 it's a trusted authority that claims our clock is wrong. Bugfix
5005 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5006 - We were telling the controller about CHECKING_REACHABILITY and
5007 REACHABILITY_FAILED status events whenever we launch a testing
5008 circuit or notice that one has failed. Instead, only tell the
5009 controller when we want to inform the user of overall success or
5010 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5012 - Don't warn when we're using a circuit that ends with a node
5013 excluded in ExcludeExitNodes, but the circuit is not used to access
5014 the outside world. This should help fix bug 1090. Bugfix on
5016 - Work around a small memory leak in some versions of OpenSSL that
5017 stopped the memory used by the hostname TLS extension from being
5021 - Add a "getinfo status/accepted-server-descriptor" controller
5022 command, which is the recommended way for controllers to learn
5023 whether our server descriptor has been successfully received by at
5024 least on directory authority. Un-recommend good-server-descriptor
5025 getinfo and status events until we have a better design for them.
5028 Changes in version 0.2.2.5-alpha - 2009-10-11
5029 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5032 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5034 o Directory authorities:
5035 - Temporarily (just for this release) move dizum to an alternate
5039 Changes in version 0.2.2.4-alpha - 2009-10-10
5040 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5041 introduces a new unit test framework, shifts directry authority
5042 addresses around to reduce the impact from recent blocking events,
5043 and fixes a few smaller bugs.
5046 - Fix several more asserts in the circuit_build_times code, for
5047 example one that causes Tor to fail to start once we have
5048 accumulated 5000 build times in the state file. Bugfixes on
5049 0.2.2.2-alpha; fixes bug 1108.
5051 o New directory authorities:
5052 - Move moria1 and Tonga to alternate IP addresses.
5055 - Log SSL state transitions at debug level during handshake, and
5056 include SSL states in error messages. This may help debug future
5057 SSL handshake issues.
5058 - Add a new "Handshake" log domain for activities that happen
5059 during the TLS handshake.
5060 - Revert to the "June 3 2009" ip-to-country file. The September one
5061 seems to have removed most US IP addresses.
5062 - Directory authorities now reject Tor relays with versions less than
5063 0.1.2.14. This step cuts out four relays from the current network,
5064 none of which are very big.
5067 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5069 - Fix two memory leaks in the error case of
5070 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5071 - Don't count one-hop circuits when we're estimating how long it
5072 takes circuits to build on average. Otherwise we'll set our circuit
5073 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5074 - Directory authorities no longer change their opinion of, or vote on,
5075 whether a router is Running, unless they have themselves been
5076 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5079 o Code simplifications and refactoring:
5080 - Revise our unit tests to use the "tinytest" framework, so we
5081 can run tests in their own processes, have smarter setup/teardown
5082 code, and so on. The unit test code has moved to its own
5083 subdirectory, and has been split into multiple modules.
5086 Changes in version 0.2.2.3-alpha - 2009-09-23
5087 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5090 - Fix an overzealous assert in our new circuit build timeout code.
5091 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5094 - If the networkstatus consensus tells us that we should use a
5095 negative circuit package window, ignore it. Otherwise we'll
5096 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5099 Changes in version 0.2.2.2-alpha - 2009-09-21
5100 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5101 clients: Tor tracks the average time it takes to build a circuit, and
5102 avoids using circuits that take too long to build. For fast connections,
5103 this feature can cut your expected latency in half. For slow or flaky
5104 connections, it could ruin your Tor experience. Let us know if it does!
5107 - Tor now tracks how long it takes to build client-side circuits
5108 over time, and adapts its timeout to local network performance.
5109 Since a circuit that takes a long time to build will also provide
5110 bad performance, we get significant latency improvements by
5111 discarding the slowest 20% of circuits. Specifically, Tor creates
5112 circuits more aggressively than usual until it has enough data
5113 points for a good timeout estimate. Implements proposal 151.
5114 We are especially looking for reports (good and bad) from users with
5115 both EDGE and broadband connections that can move from broadband
5116 to EDGE and find out if the build-time data in the .tor/state gets
5117 reset without loss of Tor usability. You should also see a notice
5118 log message telling you that Tor has reset its timeout.
5119 - Directory authorities can now vote on arbitary integer values as
5120 part of the consensus process. This is designed to help set
5121 network-wide parameters. Implements proposal 167.
5122 - Tor now reads the "circwindow" parameter out of the consensus,
5123 and uses that value for its circuit package window rather than the
5124 default of 1000 cells. Begins the implementation of proposal 168.
5127 - Fix a remotely triggerable memory leak when a consensus document
5128 contains more than one signature from the same voter. Bugfix on
5132 - Fix an extremely rare infinite recursion bug that could occur if
5133 we tried to log a message after shutting down the log subsystem.
5134 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5135 - Fix parsing for memory or time units given without a space between
5136 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5137 - A networkstatus vote must contain exactly one signature. Spec
5138 conformance issue. Bugfix on 0.2.0.3-alpha.
5139 - Fix an obscure bug where hidden services on 64-bit big-endian
5140 systems might mis-read the timestamp in v3 introduce cells, and
5141 refuse to connect back to the client. Discovered by "rotor".
5142 Bugfix on 0.2.1.6-alpha.
5143 - We were triggering a CLOCK_SKEW controller status event whenever
5144 we connect via the v2 connection protocol to any relay that has
5145 a wrong clock. Instead, we should only inform the controller when
5146 it's a trusted authority that claims our clock is wrong. Bugfix
5147 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5148 - We were telling the controller about CHECKING_REACHABILITY and
5149 REACHABILITY_FAILED status events whenever we launch a testing
5150 circuit or notice that one has failed. Instead, only tell the
5151 controller when we want to inform the user of overall success or
5152 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5154 - Don't warn when we're using a circuit that ends with a node
5155 excluded in ExcludeExitNodes, but the circuit is not used to access
5156 the outside world. This should help fix bug 1090, but more problems
5157 remain. Bugfix on 0.2.1.6-alpha.
5158 - Work around a small memory leak in some versions of OpenSSL that
5159 stopped the memory used by the hostname TLS extension from being
5161 - Make our 'torify' script more portable; if we have only one of
5162 'torsocks' or 'tsocks' installed, don't complain to the user;
5163 and explain our warning about tsocks better.
5166 - Add a "getinfo status/accepted-server-descriptor" controller
5167 command, which is the recommended way for controllers to learn
5168 whether our server descriptor has been successfully received by at
5169 least on directory authority. Un-recommend good-server-descriptor
5170 getinfo and status events until we have a better design for them.
5171 - Update to the "September 4 2009" ip-to-country file.
5174 Changes in version 0.2.2.1-alpha - 2009-08-26
5175 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5176 Tor clients to bootstrap on networks where only port 80 is reachable,
5177 makes it more straightforward to support hardware crypto accelerators,
5178 and starts the groundwork for gathering stats safely at relays.
5181 - Start the process of disabling ".exit" address notation, since it
5182 can be used for a variety of esoteric application-level attacks
5183 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5186 o New directory authorities:
5187 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5191 - New AccelName and AccelDir options add support for dynamic OpenSSL
5192 hardware crypto acceleration engines.
5193 - Tor now supports tunneling all of its outgoing connections over
5194 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5195 configuration options. Code by Christopher Davis.
5198 - Send circuit or stream sendme cells when our window has decreased
5199 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5200 by Karsten when testing the "reduce circuit window" performance
5201 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5202 before the release of Tor 0.0.0. This is the new winner of the
5205 o New options for gathering stats safely:
5206 - Directory mirrors that set "DirReqStatistics 1" write statistics
5207 about directory requests to disk every 24 hours. As compared to the
5208 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5209 1) stats are written to disk exactly every 24 hours; 2) estimated
5210 shares of v2 and v3 requests are determined as mean values, not at
5211 the end of a measurement period; 3) unresolved requests are listed
5212 with country code '??'; 4) directories also measure download times.
5213 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5214 number of exit streams and transferred bytes per port to disk every
5216 - Relays that set "CellStatistics 1" write statistics on how long
5217 cells spend in their circuit queues to disk every 24 hours.
5218 - Entry nodes that set "EntryStatistics 1" write statistics on the
5219 rough number and origins of connecting clients to disk every 24
5221 - Relays that write any of the above statistics to disk and set
5222 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5223 their extra-info documents.
5226 - New --digests command-line switch to output the digests of the
5227 source files Tor was built with.
5228 - The "torify" script now uses torsocks where available.
5229 - The memarea code now uses a sentinel value at the end of each area
5230 to make sure nothing writes beyond the end of an area. This might
5231 help debug some conceivable causes of bug 930.
5232 - Time and memory units in the configuration file can now be set to
5233 fractional units. For example, "2.5 GB" is now a valid value for
5235 - Certain Tor clients (such as those behind check.torproject.org) may
5236 want to fetch the consensus in an extra early manner. To enable this
5237 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5238 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5239 as only certain clients who must have this information sooner should
5241 - Instead of adding the svn revision to the Tor version string, report
5242 the git commit (when we're building from a git checkout).
5245 - If any of the v3 certs we download are unparseable, we should
5246 actually notice the failure so we don't retry indefinitely. Bugfix
5247 on 0.2.0.x; reported by "rotator".
5248 - If the cached cert file is unparseable, warn but don't exit.
5249 - Fix possible segmentation fault on directory authorities. Bugfix on
5251 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5252 Might help diagnosing bug 1051.
5254 o Deprecated and removed features:
5255 - The controller no longer accepts the old obsolete "addr-mappings/"
5256 or "unregistered-servers-" GETINFO values.
5257 - Hidden services no longer publish version 0 descriptors, and clients
5258 do not request or use version 0 descriptors. However, the old hidden
5259 service authorities still accept and serve version 0 descriptors
5260 when contacted by older hidden services/clients.
5261 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5262 always on; using them is necessary for correct forward-compatible
5264 - Remove support for .noconnect style addresses. Nobody was using
5265 them, and they provided another avenue for detecting Tor users
5266 via application-level web tricks.
5268 o Packaging changes:
5269 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5270 installer bundles. See
5271 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5272 for details of what's new in Vidalia 0.2.3.
5273 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5274 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5275 configuration file, rather than the old Privoxy.
5276 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5277 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5278 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5279 better compatibility with OS X 10.6, aka Snow Leopard.
5280 - OS X Vidalia Bundle: The multi-package installer is now replaced
5281 by a simple drag and drop to the /Applications folder. This change
5282 occurred with the upgrade to Vidalia 0.2.3.
5285 Changes in version 0.2.1.19 - 2009-07-28
5286 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5287 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5290 - Make accessing hidden services on 0.2.1.x work right again.
5291 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5292 part of patch provided by "optimist".
5295 - When a relay/bridge is writing out its identity key fingerprint to
5296 the "fingerprint" file and to its logs, write it without spaces. Now
5297 it will look like the fingerprints in our bridges documentation,
5298 and confuse fewer users.
5301 - Relays no longer publish a new server descriptor if they change
5302 their MaxAdvertisedBandwidth config option but it doesn't end up
5303 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5304 fixes bug 1026. Patch from Sebastian.
5305 - Avoid leaking memory every time we get a create cell but we have
5306 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5307 fixes bug 1034. Reported by BarkerJr.
5310 Changes in version 0.2.1.18 - 2009-07-24
5311 Tor 0.2.1.18 lays the foundations for performance improvements,
5312 adds status events to help users diagnose bootstrap problems, adds
5313 optional authentication/authorization for hidden services, fixes a
5314 variety of potential anonymity problems, and includes a huge pile of
5315 other features and bug fixes.
5318 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5321 Changes in version 0.2.1.17-rc - 2009-07-07
5322 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5323 candidate for the 0.2.1.x series. It lays the groundwork for further
5324 client performance improvements, and also fixes a big bug with directory
5325 authorities that were causing them to assign Guard and Stable flags
5328 The Windows bundles also finally include the geoip database that we
5329 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5330 should actually install Torbutton rather than giving you a cryptic
5331 failure message (oops).
5334 - Clients now use the bandwidth values in the consensus, rather than
5335 the bandwidth values in each relay descriptor. This approach opens
5336 the door to more accurate bandwidth estimates once the directory
5337 authorities start doing active measurements. Implements more of
5341 - When Tor clients restart after 1-5 days, they discard all their
5342 cached descriptors as too old, but they still use the cached
5343 consensus document. This approach is good for robustness, but
5344 bad for performance: since they don't know any bandwidths, they
5345 end up choosing at random rather than weighting their choice by
5346 speed. Fixed by the above feature of putting bandwidths in the
5347 consensus. Bugfix on 0.2.0.x.
5348 - Directory authorities were neglecting to mark relays down in their
5349 internal histories if the relays fall off the routerlist without
5350 ever being found unreachable. So there were relays in the histories
5351 that haven't been seen for eight months, and are listed as being
5352 up for eight months. This wreaked havoc on the "median wfu"
5353 and "median mtbf" calculations, in turn making Guard and Stable
5354 flags very wrong, hurting network performance. Fixes bugs 696 and
5355 969. Bugfix on 0.2.0.6-alpha.
5358 - Serve the DirPortFrontPage page even when we have been approaching
5359 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5360 - The control port would close the connection before flushing long
5361 replies, such as the network consensus, if a QUIT command was issued
5362 before the reply had completed. Now, the control port flushes all
5363 pending replies before closing the connection. Also fixed a spurious
5364 warning when a QUIT command is issued after a malformed or rejected
5365 AUTHENTICATE command, but before the connection was closed. Patch
5366 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5367 - When we can't find an intro key for a v2 hidden service descriptor,
5368 fall back to the v0 hidden service descriptor and log a bug message.
5369 Workaround for bug 1024.
5370 - Fix a log message that did not respect the SafeLogging option.
5374 - If we're a relay and we change our IP address, be more verbose
5375 about the reason that made us change. Should help track down
5376 further bugs for relays on dynamic IP addresses.
5379 Changes in version 0.2.0.35 - 2009-06-24
5381 - Avoid crashing in the presence of certain malformed descriptors.
5382 Found by lark, and by automated fuzzing.
5383 - Fix an edge case where a malicious exit relay could convince a
5384 controller that the client's DNS question resolves to an internal IP
5385 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5388 - Finally fix the bug where dynamic-IP relays disappear when their
5389 IP address changes: directory mirrors were mistakenly telling
5390 them their old address if they asked via begin_dir, so they
5391 never got an accurate answer about their new address, so they
5392 just vanished after a day. For belt-and-suspenders, relays that
5393 don't set Address in their config now avoid using begin_dir for
5394 all direct connections. Should fix bugs 827, 883, and 900.
5395 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5396 that would occur on some exit nodes when DNS failures and timeouts
5397 occurred in certain patterns. Fix for bug 957.
5400 - When starting with a cache over a few days old, do not leak
5401 memory for the obsolete router descriptors in it. Bugfix on
5402 0.2.0.33; fixes bug 672.
5403 - Hidden service clients didn't use a cached service descriptor that
5404 was older than 15 minutes, but wouldn't fetch a new one either,
5405 because there was already one in the cache. Now, fetch a v2
5406 descriptor unless the same descriptor was added to the cache within
5407 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5410 Changes in version 0.2.1.16-rc - 2009-06-20
5411 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5412 a bunch of minor bugs.
5415 - Fix an edge case where a malicious exit relay could convince a
5416 controller that the client's DNS question resolves to an internal IP
5417 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5419 o Major performance improvements (on 0.2.0.x):
5420 - Disable and refactor some debugging checks that forced a linear scan
5421 over the whole server-side DNS cache. These accounted for over 50%
5422 of CPU time on a relatively busy exit node's gprof profile. Found
5424 - Disable some debugging checks that appeared in exit node profile
5428 - Update to the "June 3 2009" ip-to-country file.
5429 - Do not have tor-resolve automatically refuse all .onion addresses;
5430 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5432 o Minor bugfixes (on 0.2.0.x):
5433 - Log correct error messages for DNS-related network errors on
5435 - Fix a race condition that could cause crashes or memory corruption
5436 when running as a server with a controller listening for log
5438 - Avoid crashing when we have a policy specified in a DirPolicy or
5439 SocksPolicy or ReachableAddresses option with ports set on it,
5440 and we re-load the policy. May fix bug 996.
5441 - Hidden service clients didn't use a cached service descriptor that
5442 was older than 15 minutes, but wouldn't fetch a new one either,
5443 because there was already one in the cache. Now, fetch a v2
5444 descriptor unless the same descriptor was added to the cache within
5445 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5447 o Minor bugfixes (on 0.2.1.x):
5448 - Don't warn users about low port and hibernation mix when they
5449 provide a *ListenAddress directive to fix that. Bugfix on
5451 - When switching back and forth between bridge mode, do not start
5452 gathering GeoIP data until two hours have passed.
5453 - Do not complain that the user has requested an excluded node as
5454 an exit when the node is not really an exit. This could happen
5455 because the circuit was for testing, or an introduction point.
5459 Changes in version 0.2.1.15-rc - 2009-05-25
5460 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
5461 series. It fixes a major bug on fast exit relays, as well as a variety
5464 o Major bugfixes (on 0.2.0.x):
5465 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5466 that would occur on some exit nodes when DNS failures and timeouts
5467 occurred in certain patterns. Fix for bug 957.
5469 o Minor bugfixes (on 0.2.0.x):
5470 - Actually return -1 in the error case for read_bandwidth_usage().
5471 Harmless bug, since we currently don't care about the return value
5472 anywhere. Bugfix on 0.2.0.9-alpha.
5473 - Provide a more useful log message if bug 977 (related to buffer
5474 freelists) ever reappears, and do not crash right away.
5475 - Fix an assertion failure on 64-bit platforms when we allocated
5476 memory right up to the end of a memarea, then realigned the memory
5477 one step beyond the end. Fixes a possible cause of bug 930.
5478 - Protect the count of open sockets with a mutex, so we can't
5479 corrupt it when two threads are closing or opening sockets at once.
5480 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5481 - Don't allow a bridge to publish its router descriptor to a
5482 non-bridge directory authority. Fixes part of bug 932.
5483 - When we change to or from being a bridge, reset our counts of
5484 client usage by country. Fixes bug 932.
5485 - Fix a bug that made stream bandwidth get misreported to the
5487 - Stop using malloc_usable_size() to use more area than we had
5488 actually allocated: it was safe, but made valgrind really unhappy.
5489 - Fix a memory leak when v3 directory authorities load their keys
5490 and cert from disk. Bugfix on 0.2.0.1-alpha.
5492 o Minor bugfixes (on 0.2.1.x):
5493 - Fix use of freed memory when deciding to mark a non-addable
5494 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5497 Changes in version 0.2.1.14-rc - 2009-04-12
5498 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5499 series. It begins fixing some major performance problems, and also
5500 finally addresses the bug that was causing relays on dynamic IP
5501 addresses to fall out of the directory.
5504 - Clients replace entry guards that were chosen more than a few months
5505 ago. This change should significantly improve client performance,
5506 especially once more people upgrade, since relays that have been
5507 a guard for a long time are currently overloaded.
5509 o Major bugfixes (on 0.2.0):
5510 - Finally fix the bug where dynamic-IP relays disappear when their
5511 IP address changes: directory mirrors were mistakenly telling
5512 them their old address if they asked via begin_dir, so they
5513 never got an accurate answer about their new address, so they
5514 just vanished after a day. For belt-and-suspenders, relays that
5515 don't set Address in their config now avoid using begin_dir for
5516 all direct connections. Should fix bugs 827, 883, and 900.
5517 - Relays were falling out of the networkstatus consensus for
5518 part of a day if they changed their local config but the
5519 authorities discarded their new descriptor as "not sufficiently
5520 different". Now directory authorities accept a descriptor as changed
5521 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5523 - Avoid crashing in the presence of certain malformed descriptors.
5524 Found by lark, and by automated fuzzing.
5527 - When generating circuit events with verbose nicknames for
5528 controllers, try harder to look up nicknames for routers on a
5529 circuit. (Previously, we would look in the router descriptors we had
5530 for nicknames, but not in the consensus.) Partial fix for bug 941.
5531 - If the bridge config line doesn't specify a port, assume 443.
5532 This makes bridge lines a bit smaller and easier for users to
5534 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5535 bytes (aka 20KB/s), to match our documentation. Also update
5536 directory authorities so they always assign the Fast flag to relays
5537 with 20KB/s of capacity. Now people running relays won't suddenly
5538 find themselves not seeing any use, if the network gets faster
5540 - Update to the "April 3 2009" ip-to-country file.
5543 - Avoid trying to print raw memory to the logs when we decide to
5544 give up on downloading a given relay descriptor. Bugfix on
5546 - In tor-resolve, when the Tor client to use is specified by
5547 <hostname>:<port>, actually use the specified port rather than
5548 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5549 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5550 - When starting with a cache over a few days old, do not leak
5551 memory for the obsolete router descriptors in it. Bugfix on
5553 - Avoid double-free on list of successfully uploaded hidden
5554 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5555 - Change memarea_strndup() implementation to work even when
5556 duplicating a string at the end of a page. This bug was
5557 harmless for now, but could have meant crashes later. Fix by
5558 lark. Bugfix on 0.2.1.1-alpha.
5559 - Limit uploaded directory documents to be 16M rather than 500K.
5560 The directory authorities were refusing v3 consensus votes from
5561 other authorities, since the votes are now 504K. Fixes bug 959;
5562 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5563 - Directory authorities should never send a 503 "busy" response to
5564 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5568 Changes in version 0.2.1.13-alpha - 2009-03-09
5569 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5570 cleanups. We're finally getting close to a release candidate.
5573 - Correctly update the list of which countries we exclude as
5574 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5575 lark. Bugfix on 0.2.1.6-alpha.
5577 o Minor bugfixes (on 0.2.0.x and earlier):
5578 - Automatically detect MacOSX versions earlier than 10.4.0, and
5579 disable kqueue from inside Tor when running with these versions.
5580 We previously did this from the startup script, but that was no
5581 help to people who didn't use the startup script. Resolves bug 863.
5582 - When we had picked an exit node for a connection, but marked it as
5583 "optional", and it turned out we had no onion key for the exit,
5584 stop wanting that exit and try again. This situation may not
5585 be possible now, but will probably become feasible with proposal
5586 158. Spotted by rovv. Fixes another case of bug 752.
5587 - Clients no longer cache certificates for authorities they do not
5588 recognize. Bugfix on 0.2.0.9-alpha.
5589 - When we can't transmit a DNS request due to a network error, retry
5590 it after a while, and eventually transmit a failing response to
5591 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5592 - If the controller claimed responsibility for a stream, but that
5593 stream never finished making its connection, it would live
5594 forever in circuit_wait state. Now we close it after SocksTimeout
5595 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5596 - Drop begin cells to a hidden service if they come from the middle
5597 of a circuit. Patch from lark.
5598 - When we erroneously receive two EXTEND cells for the same circuit
5599 ID on the same connection, drop the second. Patch from lark.
5600 - Fix a crash that occurs on exit nodes when a nameserver request
5601 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5602 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5604 - Do not assume that a stack-allocated character array will be
5605 64-bit aligned on platforms that demand that uint64_t access is
5606 aligned. Possible fix for bug 604.
5607 - Parse dates and IPv4 addresses in a locale- and libc-independent
5608 manner, to avoid platform-dependent behavior on malformed input.
5609 - Build correctly when configured to build outside the main source
5610 path. Patch from Michael Gold.
5611 - We were already rejecting relay begin cells with destination port
5612 of 0. Now also reject extend cells with destination port or address
5613 of 0. Suggested by lark.
5615 o Minor bugfixes (on 0.2.1.x):
5616 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5617 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5618 - If we're an exit node, scrub the IP address to which we are exiting
5619 in the logs. Bugfix on 0.2.1.8-alpha.
5622 - On Linux, use the prctl call to re-enable core dumps when the user
5624 - New controller event NEWCONSENSUS that lists the networkstatus
5625 lines for every recommended relay. Now controllers like Torflow
5626 can keep up-to-date on which relays they should be using.
5627 - Update to the "February 26 2009" ip-to-country file.
5630 Changes in version 0.2.0.34 - 2009-02-08
5631 Tor 0.2.0.34 features several more security-related fixes. You should
5632 upgrade, especially if you run an exit relay (remote crash) or a
5633 directory authority (remote infinite loop), or you're on an older
5634 (pre-XP) or not-recently-patched Windows (remote exploit).
5636 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5637 have many known flaws, and nobody should be using them. You should
5638 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5639 stop using those packages and upgrade anyway.
5642 - Fix an infinite-loop bug on handling corrupt votes under certain
5643 circumstances. Bugfix on 0.2.0.8-alpha.
5644 - Fix a temporary DoS vulnerability that could be performed by
5645 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5646 - Avoid a potential crash on exit nodes when processing malformed
5647 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5648 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5649 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5652 - Fix compilation on systems where time_t is a 64-bit integer.
5653 Patch from Matthias Drochner.
5654 - Don't consider expiring already-closed client connections. Fixes
5655 bug 893. Bugfix on 0.0.2pre20.
5658 Changes in version 0.2.1.12-alpha - 2009-02-08
5659 Tor 0.2.1.12-alpha features several more security-related fixes. You
5660 should upgrade, especially if you run an exit relay (remote crash) or
5661 a directory authority (remote infinite loop), or you're on an older
5662 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5663 includes a big pile of minor bugfixes and cleanups.
5666 - Fix an infinite-loop bug on handling corrupt votes under certain
5667 circumstances. Bugfix on 0.2.0.8-alpha.
5668 - Fix a temporary DoS vulnerability that could be performed by
5669 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5670 - Avoid a potential crash on exit nodes when processing malformed
5671 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5674 - Let controllers actually ask for the "clients_seen" event for
5675 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5676 reported by Matt Edman.
5677 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5679 - Fix a bug in address parsing that was preventing bridges or hidden
5680 service targets from being at IPv6 addresses.
5681 - Solve a bug that kept hardware crypto acceleration from getting
5682 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5684 - Remove a bash-ism from configure.in to build properly on non-Linux
5685 platforms. Bugfix on 0.2.1.1-alpha.
5686 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5687 headers. Bugfix on 0.2.0.10-alpha.
5688 - Don't consider expiring already-closed client connections. Fixes
5689 bug 893. Bugfix on 0.0.2pre20.
5690 - Fix another interesting corner-case of bug 891 spotted by rovv:
5691 Previously, if two hosts had different amounts of clock drift, and
5692 one of them created a new connection with just the wrong timing,
5693 the other might decide to deprecate the new connection erroneously.
5694 Bugfix on 0.1.1.13-alpha.
5695 - Resolve a very rare crash bug that could occur when the user forced
5696 a nameserver reconfiguration during the middle of a nameserver
5697 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5698 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5699 Bugfix on 0.2.1.7-alpha.
5700 - If we're using bridges and our network goes away, be more willing
5701 to forgive our bridges and try again when we get an application
5702 request. Bugfix on 0.2.0.x.
5705 - Support platforms where time_t is 64 bits long. (Congratulations,
5706 NetBSD!) Patch from Matthias Drochner.
5707 - Add a 'getinfo status/clients-seen' controller command, in case
5708 controllers want to hear clients_seen events but connect late.
5711 - Disable GCC's strict alias optimization by default, to avoid the
5712 likelihood of its introducing subtle bugs whenever our code violates
5713 the letter of C99's alias rules.
5716 Changes in version 0.2.0.33 - 2009-01-21
5717 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5718 useful to users. It also finally fixes a bug where a relay or client
5719 that's been off for many days would take a long time to bootstrap.
5721 This update also fixes an important security-related bug reported by
5722 Ilja van Sprundel. You should upgrade. (We'll send out more details
5723 about the bug once people have had some time to upgrade.)
5726 - Fix a heap-corruption bug that may be remotely triggerable on
5727 some platforms. Reported by Ilja van Sprundel.
5730 - When a stream at an exit relay is in state "resolving" or
5731 "connecting" and it receives an "end" relay cell, the exit relay
5732 would silently ignore the end cell and not close the stream. If
5733 the client never closes the circuit, then the exit relay never
5734 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5736 - When sending CREATED cells back for a given circuit, use a 64-bit
5737 connection ID to find the right connection, rather than an addr:port
5738 combination. Now that we can have multiple OR connections between
5739 the same ORs, it is no longer possible to use addr:port to uniquely
5740 identify a connection.
5741 - Bridge relays that had DirPort set to 0 would stop fetching
5742 descriptors shortly after startup, and then briefly resume
5743 after a new bandwidth test and/or after publishing a new bridge
5744 descriptor. Bridge users that try to bootstrap from them would
5745 get a recent networkstatus but would get descriptors from up to
5746 18 hours earlier, meaning most of the descriptors were obsolete
5747 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5748 - Prevent bridge relays from serving their 'extrainfo' document
5749 to anybody who asks, now that extrainfo docs include potentially
5750 sensitive aggregated client geoip summaries. Bugfix on
5752 - If the cached networkstatus consensus is more than five days old,
5753 discard it rather than trying to use it. In theory it could be
5754 useful because it lists alternate directory mirrors, but in practice
5755 it just means we spend many minutes trying directory mirrors that
5756 are long gone from the network. Also discard router descriptors as
5757 we load them if they are more than five days old, since the onion
5758 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5761 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5762 could make gcc generate non-functional binary search code. Bugfix
5764 - Build correctly on platforms without socklen_t.
5765 - Compile without warnings on solaris.
5766 - Avoid potential crash on internal error during signature collection.
5767 Fixes bug 864. Patch from rovv.
5768 - Correct handling of possible malformed authority signing key
5769 certificates with internal signature types. Fixes bug 880.
5770 Bugfix on 0.2.0.3-alpha.
5771 - Fix a hard-to-trigger resource leak when logging credential status.
5773 - When we can't initialize DNS because the network is down, do not
5774 automatically stop Tor from starting. Instead, we retry failed
5775 dns_init() every 10 minutes, and change the exit policy to reject
5776 *:* until one succeeds. Fixes bug 691.
5777 - Use 64 bits instead of 32 bits for connection identifiers used with
5778 the controller protocol, to greatly reduce risk of identifier reuse.
5779 - When we're choosing an exit node for a circuit, and we have
5780 no pending streams, choose a good general exit rather than one that
5781 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5782 - Fix another case of assuming, when a specific exit is requested,
5783 that we know more than the user about what hosts it allows.
5784 Fixes one case of bug 752. Patch from rovv.
5785 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5786 seconds. Warn the user if lower values are given in the
5787 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5788 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5789 user if lower values are given in the configuration. Bugfix on
5790 0.1.1.17-rc. Patch by Sebastian.
5791 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5792 the cache because we already had a v0 descriptor with the same ID.
5793 Bugfix on 0.2.0.18-alpha.
5794 - Fix a race condition when freeing keys shared between main thread
5795 and CPU workers that could result in a memory leak. Bugfix on
5796 0.1.0.1-rc. Fixes bug 889.
5797 - Send a valid END cell back when a client tries to connect to a
5798 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5799 840. Patch from rovv.
5800 - Check which hops rendezvous stream cells are associated with to
5801 prevent possible guess-the-streamid injection attacks from
5802 intermediate hops. Fixes another case of bug 446. Based on patch
5804 - If a broken client asks a non-exit router to connect somewhere,
5805 do not even do the DNS lookup before rejecting the connection.
5806 Fixes another case of bug 619. Patch from rovv.
5807 - When a relay gets a create cell it can't decrypt (e.g. because it's
5808 using the wrong onion key), we were dropping it and letting the
5809 client time out. Now actually answer with a destroy cell. Fixes
5810 bug 904. Bugfix on 0.0.2pre8.
5812 o Minor bugfixes (hidden services):
5813 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5814 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5817 - Report the case where all signatures in a detached set are rejected
5818 differently than the case where there is an error handling the
5820 - When we realize that another process has modified our cached
5821 descriptors, print out a more useful error message rather than
5822 triggering an assertion. Fixes bug 885. Patch from Karsten.
5823 - Implement the 0x20 hack to better resist DNS poisoning: set the
5824 case on outgoing DNS requests randomly, and reject responses that do
5825 not match the case correctly. This logic can be disabled with the
5826 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5827 of servers that do not reliably preserve case in replies. See
5828 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5830 - Check DNS replies for more matching fields to better resist DNS
5832 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5833 compress cells, which are basically all encrypted, compressed, or
5837 Changes in version 0.2.1.11-alpha - 2009-01-20
5838 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
5839 week it will take a long time to bootstrap again" bug. It also fixes
5840 an important security-related bug reported by Ilja van Sprundel. You
5841 should upgrade. (We'll send out more details about the bug once people
5842 have had some time to upgrade.)
5845 - Fix a heap-corruption bug that may be remotely triggerable on
5846 some platforms. Reported by Ilja van Sprundel.
5849 - Discard router descriptors as we load them if they are more than
5850 five days old. Otherwise if Tor is off for a long time and then
5851 starts with cached descriptors, it will try to use the onion
5852 keys in those obsolete descriptors when building circuits. Bugfix
5853 on 0.2.0.x. Fixes bug 887.
5856 - Try to make sure that the version of Libevent we're running with
5857 is binary-compatible with the one we built with. May address bug
5859 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
5860 for bug 905. Bugfix on 0.2.1.7-alpha.
5861 - Add a new --enable-local-appdata configuration switch to change
5862 the default location of the datadir on win32 from APPDATA to
5863 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5864 entirely. Patch from coderman.
5867 - Make outbound DNS packets respect the OutboundBindAddress setting.
5868 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5869 - When our circuit fails at the first hop (e.g. we get a destroy
5870 cell back), avoid using that OR connection anymore, and also
5871 tell all the one-hop directory requests waiting for it that they
5872 should fail. Bugfix on 0.2.1.3-alpha.
5873 - In the torify(1) manpage, mention that tsocks will leak your
5877 Changes in version 0.2.1.10-alpha - 2009-01-06
5878 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
5879 would make the bridge relay not so useful if it had DirPort set to 0,
5880 and one that could let an attacker learn a little bit of information
5881 about the bridge's users), and a bug that would cause your Tor relay
5882 to ignore a circuit create request it can't decrypt (rather than reply
5883 with an error). It also fixes a wide variety of other bugs.
5886 - If the cached networkstatus consensus is more than five days old,
5887 discard it rather than trying to use it. In theory it could
5888 be useful because it lists alternate directory mirrors, but in
5889 practice it just means we spend many minutes trying directory
5890 mirrors that are long gone from the network. Helps bug 887 a bit;
5892 - Bridge relays that had DirPort set to 0 would stop fetching
5893 descriptors shortly after startup, and then briefly resume
5894 after a new bandwidth test and/or after publishing a new bridge
5895 descriptor. Bridge users that try to bootstrap from them would
5896 get a recent networkstatus but would get descriptors from up to
5897 18 hours earlier, meaning most of the descriptors were obsolete
5898 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5899 - Prevent bridge relays from serving their 'extrainfo' document
5900 to anybody who asks, now that extrainfo docs include potentially
5901 sensitive aggregated client geoip summaries. Bugfix on
5905 - New controller event "clients_seen" to report a geoip-based summary
5906 of which countries we've seen clients from recently. Now controllers
5907 like Vidalia can show bridge operators that they're actually making
5909 - Build correctly against versions of OpenSSL 0.9.8 or later built
5910 without support for deprecated functions.
5911 - Update to the "December 19 2008" ip-to-country file.
5913 o Minor bugfixes (on 0.2.0.x):
5914 - Authorities now vote for the Stable flag for any router whose
5915 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5916 - Do not remove routers as too old if we do not have any consensus
5917 document. Bugfix on 0.2.0.7-alpha.
5918 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5919 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5920 - When an exit relay resolves a stream address to a local IP address,
5921 do not just keep retrying that same exit relay over and
5922 over. Instead, just close the stream. Addresses bug 872. Bugfix
5923 on 0.2.0.32. Patch from rovv.
5924 - If a hidden service sends us an END cell, do not consider
5925 retrying the connection; just close it. Patch from rovv.
5926 - When we made bridge authorities stop serving bridge descriptors over
5927 unencrypted links, we also broke DirPort reachability testing for
5928 bridges. So bridges with a non-zero DirPort were printing spurious
5929 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5930 - When a relay gets a create cell it can't decrypt (e.g. because it's
5931 using the wrong onion key), we were dropping it and letting the
5932 client time out. Now actually answer with a destroy cell. Fixes
5933 bug 904. Bugfix on 0.0.2pre8.
5934 - Squeeze 2-5% out of client performance (according to oprofile) by
5935 improving the implementation of some policy-manipulation functions.
5937 o Minor bugfixes (on 0.2.1.x):
5938 - Make get_interface_address() function work properly again; stop
5939 guessing the wrong parts of our address as our address.
5940 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
5941 send on that circuit. Otherwise we might violate the proposal-110
5942 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
5944 - When we're sending non-EXTEND cells to the first hop in a circuit,
5945 for example to use an encrypted directory connection, we don't need
5946 to use RELAY_EARLY cells: the first hop knows what kind of cell
5947 it is, and nobody else can even see the cell type. Conserving
5948 RELAY_EARLY cells makes it easier to cannibalize circuits like
5950 - Stop logging nameserver addresses in reverse order.
5951 - If we are retrying a directory download slowly over and over, do
5952 not automatically give up after the 254th failure. Bugfix on
5954 - Resume reporting accurate "stream end" reasons to the local control
5955 port. They were lost in the changes for Proposal 148. Bugfix on
5958 o Deprecated and removed features:
5959 - The old "tor --version --version" command, which would print out
5960 the subversion "Id" of most of the source files, is now removed. It
5961 turned out to be less useful than we'd expected, and harder to
5964 o Code simplifications and refactoring:
5965 - Change our header file guard macros to be less likely to conflict
5966 with system headers. Adam Langley noticed that we were conflicting
5967 with log.h on Android.
5968 - Tool-assisted documentation cleanup. Nearly every function or
5969 static variable in Tor should have its own documentation now.
5972 Changes in version 0.2.1.9-alpha - 2008-12-25
5973 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
5975 o New directory authorities:
5976 - gabelmoo (the authority run by Karsten Loesing) now has a new
5980 - Never use a connection with a mismatched address to extend a
5981 circuit, unless that connection is canonical. A canonical
5982 connection is one whose address is authenticated by the router's
5983 identity key, either in a NETINFO cell or in a router descriptor.
5984 - Avoid a possible memory corruption bug when receiving hidden service
5985 descriptors. Bugfix on 0.2.1.6-alpha.
5988 - Fix a logic error that would automatically reject all but the first
5989 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
5990 part of bug 813/868. Bug spotted by coderman.
5991 - When a stream at an exit relay is in state "resolving" or
5992 "connecting" and it receives an "end" relay cell, the exit relay
5993 would silently ignore the end cell and not close the stream. If
5994 the client never closes the circuit, then the exit relay never
5995 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
5997 - When we can't initialize DNS because the network is down, do not
5998 automatically stop Tor from starting. Instead, retry failed
5999 dns_init() every 10 minutes, and change the exit policy to reject
6000 *:* until one succeeds. Fixes bug 691.
6003 - Give a better error message when an overzealous init script says
6004 "sudo -u username tor --user username". Makes Bug 882 easier for
6006 - When a directory authority gives us a new guess for our IP address,
6007 log which authority we used. Hopefully this will help us debug
6008 the recent complaints about bad IP address guesses.
6009 - Detect svn revision properly when we're using git-svn.
6010 - Try not to open more than one descriptor-downloading connection
6011 to an authority at once. This should reduce load on directory
6012 authorities. Fixes bug 366.
6013 - Add cross-certification to newly generated certificates, so that
6014 a signing key is enough information to look up a certificate.
6015 Partial implementation of proposal 157.
6016 - Start serving certificates by <identity digest, signing key digest>
6017 pairs. Partial implementation of proposal 157.
6018 - Clients now never report any stream end reason except 'MISC'.
6019 Implements proposal 148.
6020 - On platforms with a maximum syslog string length, truncate syslog
6021 messages to that length ourselves, rather than relying on the
6022 system to do it for us.
6023 - Optimize out calls to time(NULL) that occur for every IO operation,
6024 or for every cell. On systems where time() is a slow syscall,
6025 this fix will be slightly helpful.
6026 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6027 - When we download a descriptor that we then immediately (as
6028 a directory authority) reject, do not retry downloading it right
6029 away. Should save some bandwidth on authorities. Fix for bug
6030 888. Patch by Sebastian Hahn.
6031 - When a download gets us zero good descriptors, do not notify
6032 Tor that new directory information has arrived.
6033 - Avoid some nasty corner cases in the logic for marking connections
6034 as too old or obsolete or noncanonical for circuits. Partial
6037 o Minor features (controller):
6038 - New CONSENSUS_ARRIVED event to note when a new consensus has
6039 been fetched and validated.
6040 - When we realize that another process has modified our cached
6041 descriptors file, print out a more useful error message rather
6042 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6043 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6044 controllers to prevent SIGHUP from reloading the
6045 configuration. Fixes bug 856.
6048 - Resume using the correct "REASON=" stream when telling the
6049 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6050 - When a canonical connection appears later in our internal list
6051 than a noncanonical one for a given OR ID, always use the
6052 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6054 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6055 seconds. Warn the user if lower values are given in the
6056 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6057 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6058 user if lower values are given in the configuration. Bugfix on
6059 0.1.1.17-rc. Patch by Sebastian.
6060 - Fix a race condition when freeing keys shared between main thread
6061 and CPU workers that could result in a memory leak. Bugfix on
6062 0.1.0.1-rc. Fixes bug 889.
6064 o Minor bugfixes (hidden services):
6065 - Do not throw away existing introduction points on SIGHUP (bugfix on
6066 0.0.6pre1); also, do not stall hidden services because we're
6067 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6068 by John Brooks. Patch by Karsten. Fixes bug 874.
6069 - Fix a memory leak when we decline to add a v2 rendezvous
6070 descriptor to the cache because we already had a v0 descriptor
6071 with the same ID. Bugfix on 0.2.0.18-alpha.
6073 o Deprecated and removed features:
6074 - RedirectExits has been removed. It was deprecated since
6076 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6077 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6078 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6080 o Code simplifications and refactoring:
6081 - Rename the confusing or_is_obsolete field to the more appropriate
6082 is_bad_for_new_circs, and move it to or_connection_t where it
6084 - Move edge-only flags from connection_t to edge_connection_t: not
6085 only is this better coding, but on machines of plausible alignment,
6086 it should save 4-8 bytes per connection_t. "Every little bit helps."
6087 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6088 for consistency; keep old option working for backward compatibility.
6089 - Simplify the code for finding connections to use for a circuit.
6092 Changes in version 0.2.1.8-alpha - 2008-12-08
6093 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6094 builds better on unusual platforms like Solaris and old OS X, and
6095 fixes a variety of other issues.
6098 - New DirPortFrontPage option that takes an html file and publishes
6099 it as "/" on the DirPort. Now relay operators can provide a
6100 disclaimer without needing to set up a separate webserver. There's
6101 a sample disclaimer in contrib/tor-exit-notice.html.
6104 - When the client is choosing entry guards, now it selects at most
6105 one guard from a given relay family. Otherwise we could end up with
6106 all of our entry points into the network run by the same operator.
6107 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6110 - Fix a DOS opportunity during the voting signature collection process
6111 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6112 - Fix a possible segfault when establishing an exit connection. Bugfix
6116 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6118 - Made Tor a little less aggressive about deleting expired
6119 certificates. Partial fix for bug 854.
6120 - Stop doing unaligned memory access that generated bus errors on
6121 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6122 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6123 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6124 - Make USR2 log-level switch take effect immediately. Bugfix on
6126 - If one win32 nameserver fails to get added, continue adding the
6127 rest, and don't automatically fail.
6128 - Use fcntl() for locking when flock() is not available. Should fix
6129 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6130 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6131 could make gcc generate non-functional binary search code. Bugfix
6133 - Build correctly on platforms without socklen_t.
6134 - Avoid potential crash on internal error during signature collection.
6135 Fixes bug 864. Patch from rovv.
6136 - Do not use C's stdio library for writing to log files. This will
6137 improve logging performance by a minute amount, and will stop
6138 leaking fds when our disk is full. Fixes bug 861.
6139 - Stop erroneous use of O_APPEND in cases where we did not in fact
6140 want to re-seek to the end of a file before every last write().
6141 - Correct handling of possible malformed authority signing key
6142 certificates with internal signature types. Fixes bug 880. Bugfix
6144 - Fix a hard-to-trigger resource leak when logging credential status.
6148 - Directory mirrors no longer fetch the v1 directory or
6149 running-routers files. They are obsolete, and nobody asks for them
6150 anymore. This is the first step to making v1 authorities obsolete.
6152 o Minor features (controller):
6153 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6157 Changes in version 0.2.0.32 - 2008-11-20
6158 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6159 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6160 a smaller security flaw that might allow an attacker to access local
6161 services, further improves hidden service performance, and fixes a
6162 variety of other issues.
6165 - The "User" and "Group" config options did not clear the
6166 supplementary group entries for the Tor process. The "User" option
6167 is now more robust, and we now set the groups to the specified
6168 user's primary group. The "Group" option is now ignored. For more
6169 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6170 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6171 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6172 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6173 consistently obeyed: if an exit relay refuses a stream because its
6174 exit policy doesn't allow it, we would remember what IP address
6175 the relay said the destination address resolves to, even if it's
6176 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6179 - Fix a DOS opportunity during the voting signature collection process
6180 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6182 o Major bugfixes (hidden services):
6183 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6184 we were failing the whole hidden service request when the v0
6185 descriptor fetch fails, even if the v2 fetch is still pending and
6186 might succeed. Similarly, if the last v2 fetch fails, we were
6187 failing the whole hidden service request even if a v0 fetch is
6188 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6189 - When extending a circuit to a hidden service directory to upload a
6190 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6191 requests failed, because the router descriptor has not been
6192 downloaded yet. In these cases, do not attempt to upload the
6193 rendezvous descriptor, but wait until the router descriptor is
6194 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6195 descriptor from a hidden service directory for which the router
6196 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6200 - Fix several infrequent memory leaks spotted by Coverity.
6201 - When testing for libevent functions, set the LDFLAGS variable
6202 correctly. Found by Riastradh.
6203 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6204 bootstrapping with tunneled directory connections. Bugfix on
6205 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6206 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6207 and we know that server B rejects most-but-not all connections to
6208 port 80, we would previously reject the connection. Now, we assume
6209 the user knows what they were asking for. Fixes bug 752. Bugfix
6210 on 0.0.9rc5. Diagnosed by BarkerJr.
6211 - If we overrun our per-second write limits a little, count this as
6212 having used up our write allocation for the second, and choke
6213 outgoing directory writes. Previously, we had only counted this when
6214 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6215 Bugfix on 0.2.0.x (??).
6216 - Remove the old v2 directory authority 'lefkada' from the default
6217 list. It has been gone for many months.
6218 - Stop doing unaligned memory access that generated bus errors on
6219 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6220 - Make USR2 log-level switch take effect immediately. Bugfix on
6223 o Minor bugfixes (controller):
6224 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6225 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6228 Changes in version 0.2.1.7-alpha - 2008-11-08
6229 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6230 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6231 a smaller security flaw that might allow an attacker to access local
6232 services, adds better defense against DNS poisoning attacks on exit
6233 relays, further improves hidden service performance, and fixes a
6234 variety of other issues.
6237 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6238 consistently obeyed: if an exit relay refuses a stream because its
6239 exit policy doesn't allow it, we would remember what IP address
6240 the relay said the destination address resolves to, even if it's
6241 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6242 - The "User" and "Group" config options did not clear the
6243 supplementary group entries for the Tor process. The "User" option
6244 is now more robust, and we now set the groups to the specified
6245 user's primary group. The "Group" option is now ignored. For more
6246 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6247 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6248 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6249 - Do not use or believe expired v3 authority certificates. Patch
6250 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6253 - Now NodeFamily and MyFamily config options allow spaces in
6254 identity fingerprints, so it's easier to paste them in.
6255 Suggested by Lucky Green.
6256 - Implement the 0x20 hack to better resist DNS poisoning: set the
6257 case on outgoing DNS requests randomly, and reject responses that do
6258 not match the case correctly. This logic can be disabled with the
6259 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6260 of servers that do not reliably preserve case in replies. See
6261 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6263 - Preserve case in replies to DNSPort requests in order to support
6264 the 0x20 hack for resisting DNS poisoning attacks.
6266 o Hidden service performance improvements:
6267 - When the client launches an introduction circuit, retry with a
6268 new circuit after 30 seconds rather than 60 seconds.
6269 - Launch a second client-side introduction circuit in parallel
6270 after a delay of 15 seconds (based on work by Christian Wilms).
6271 - Hidden services start out building five intro circuits rather
6272 than three, and when the first three finish they publish a service
6273 descriptor using those. Now we publish our service descriptor much
6274 faster after restart.
6277 - Minor fix in the warning messages when you're having problems
6278 bootstrapping; also, be more forgiving of bootstrap problems when
6279 we're still making incremental progress on a given bootstrap phase.
6280 - When we're choosing an exit node for a circuit, and we have
6281 no pending streams, choose a good general exit rather than one that
6282 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6283 - Send a valid END cell back when a client tries to connect to a
6284 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6285 840. Patch from rovv.
6286 - If a broken client asks a non-exit router to connect somewhere,
6287 do not even do the DNS lookup before rejecting the connection.
6288 Fixes another case of bug 619. Patch from rovv.
6289 - Fix another case of assuming, when a specific exit is requested,
6290 that we know more than the user about what hosts it allows.
6291 Fixes another case of bug 752. Patch from rovv.
6292 - Check which hops rendezvous stream cells are associated with to
6293 prevent possible guess-the-streamid injection attacks from
6294 intermediate hops. Fixes another case of bug 446. Based on patch
6296 - Avoid using a negative right-shift when comparing 32-bit
6297 addresses. Possible fix for bug 845 and bug 811.
6298 - Make the assert_circuit_ok() function work correctly on circuits that
6299 have already been marked for close.
6300 - Fix read-off-the-end-of-string error in unit tests when decoding
6301 introduction points.
6302 - Fix uninitialized size field for memory area allocation: may improve
6303 memory performance during directory parsing.
6304 - Treat duplicate certificate fetches as failures, so that we do
6305 not try to re-fetch an expired certificate over and over and over.
6306 - Do not say we're fetching a certificate when we'll in fact skip it
6307 because of a pending download.
6310 Changes in version 0.2.1.6-alpha - 2008-09-30
6311 Tor 0.2.1.6-alpha further improves performance and robustness of
6312 hidden services, starts work on supporting per-country relay selection,
6313 and fixes a variety of smaller issues.
6316 - Implement proposal 121: make it possible to build hidden services
6317 that only certain clients are allowed to connect to. This is
6318 enforced at several points, so that unauthorized clients are unable
6319 to send INTRODUCE cells to the service, or even (depending on the
6320 type of authentication) to learn introduction points. This feature
6321 raises the bar for certain kinds of active attacks against hidden
6322 services. Code by Karsten Loesing.
6323 - Relays now store and serve v2 hidden service descriptors by default,
6324 i.e., the new default value for HidServDirectoryV2 is 1. This is
6325 the last step in proposal 114, which aims to make hidden service
6326 lookups more reliable.
6327 - Start work to allow node restrictions to include country codes. The
6328 syntax to exclude nodes in a country with country code XX is
6329 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6330 refinement to decide what config options should take priority if
6331 you ask to both use a particular node and exclude it.
6332 - Allow ExitNodes list to include IP ranges and country codes, just
6333 like the Exclude*Nodes lists. Patch from Robert Hogan.
6336 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6337 Tor to fail to start if you had it configured to use a bridge
6338 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6339 - When extending a circuit to a hidden service directory to upload a
6340 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6341 requests failed, because the router descriptor had not been
6342 downloaded yet. In these cases, we now wait until the router
6343 descriptor is downloaded, and then retry. Likewise, clients
6344 now skip over a hidden service directory if they don't yet have
6345 its router descriptor, rather than futilely requesting it and
6346 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6348 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6349 we were failing the whole hidden service request when the v0
6350 descriptor fetch fails, even if the v2 fetch is still pending and
6351 might succeed. Similarly, if the last v2 fetch fails, we were
6352 failing the whole hidden service request even if a v0 fetch is
6353 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6354 - DNS replies need to have names matching their requests, but
6355 these names should be in the questions section, not necessarily
6356 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6359 - Update to the "September 1 2008" ip-to-country file.
6360 - Allow ports 465 and 587 in the default exit policy again. We had
6361 rejected them in 0.1.0.15, because back in 2005 they were commonly
6362 misconfigured and ended up as spam targets. We hear they are better
6363 locked down these days.
6364 - Use a lockfile to make sure that two Tor processes are not
6365 simultaneously running with the same datadir.
6366 - Serve the latest v3 networkstatus consensus via the control
6367 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6368 - Better logging about stability/reliability calculations on directory
6370 - Drop the requirement to have an open dir port for storing and
6371 serving v2 hidden service descriptors.
6372 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6373 help debug WFU and MTBF calculations.
6374 - Implement most of Proposal 152: allow specialized servers to permit
6375 single-hop circuits, and clients to use those servers to build
6376 single-hop circuits when using a specialized controller. Patch
6377 from Josh Albrecht. Resolves feature request 768.
6378 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6379 people find host:port too confusing.
6380 - Make TrackHostExit mappings expire a while after their last use, not
6381 after their creation. Patch from Robert Hogan.
6382 - Provide circuit purposes along with circuit events to the controller.
6385 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6387 - Fixed some memory leaks -- some quite frequent, some almost
6388 impossible to trigger -- based on results from Coverity.
6389 - When testing for libevent functions, set the LDFLAGS variable
6390 correctly. Found by Riastradh.
6391 - Fix an assertion bug in parsing policy-related options; possible fix
6393 - Catch and report a few more bootstrapping failure cases when Tor
6394 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6395 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6396 bootstrapping with tunneled directory connections. Bugfix on
6397 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6398 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6399 and we know that server B rejects most-but-not all connections to
6400 port 80, we would previously reject the connection. Now, we assume
6401 the user knows what they were asking for. Fixes bug 752. Bugfix
6402 on 0.0.9rc5. Diagnosed by BarkerJr.
6403 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6404 service directories if they have no advertised dir port. Bugfix
6406 - If we overrun our per-second write limits a little, count this as
6407 having used up our write allocation for the second, and choke
6408 outgoing directory writes. Previously, we had only counted this when
6409 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6410 Bugfix on 0.2.0.x (??).
6411 - Avoid a "0 divided by 0" calculation when calculating router uptime
6412 at directory authorities. Bugfix on 0.2.0.8-alpha.
6413 - Make DNS resolved controller events into "CLOSED", not
6414 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6416 - Fix a bug where an unreachable relay would establish enough
6417 reachability testing circuits to do a bandwidth test -- if
6418 we already have a connection to the middle hop of the testing
6419 circuit, then it could establish the last hop by using the existing
6420 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6421 circuits no longer use entry guards in 0.2.1.3-alpha.
6422 - If we have correct permissions on $datadir, we complain to stdout
6423 and fail to start. But dangerous permissions on
6424 $datadir/cached-status/ would cause us to open a log and complain
6425 there. Now complain to stdout and fail to start in both cases. Fixes
6426 bug 820, reported by seeess.
6427 - Remove the old v2 directory authority 'lefkada' from the default
6428 list. It has been gone for many months.
6430 o Code simplifications and refactoring:
6431 - Revise the connection_new functions so that a more typesafe variant
6432 exists. This will work better with Coverity, and let us find any
6433 actual mistakes we're making here.
6434 - Refactor unit testing logic so that dmalloc can be used sensibly
6435 with unit tests to check for memory leaks.
6436 - Move all hidden-service related fields from connection and circuit
6437 structure to substructures: this way they won't eat so much memory.
6440 Changes in version 0.2.0.31 - 2008-09-03
6441 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6442 a big bug we're seeing where in rare cases traffic from one Tor stream
6443 gets mixed into another stream, and fixes a variety of smaller issues.
6446 - Make sure that two circuits can never exist on the same connection
6447 with the same circuit ID, even if one is marked for close. This
6448 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6449 - Relays now reject risky extend cells: if the extend cell includes
6450 a digest of all zeroes, or asks to extend back to the relay that
6451 sent the extend cell, tear down the circuit. Ideas suggested
6453 - If not enough of our entry guards are available so we add a new
6454 one, we might use the new one even if it overlapped with the
6455 current circuit's exit relay (or its family). Anonymity bugfix
6456 pointed out by rovv.
6459 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6460 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6461 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6462 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6463 - Pick size of default geoip filename string correctly on windows.
6464 Fixes bug 806. Bugfix on 0.2.0.30.
6465 - Make the autoconf script accept the obsolete --with-ssl-dir
6466 option as an alias for the actually-working --with-openssl-dir
6467 option. Fix the help documentation to recommend --with-openssl-dir.
6468 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6469 - When using the TransPort option on OpenBSD, and using the User
6470 option to change UID and drop privileges, make sure to open
6471 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6472 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6473 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6474 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6475 on the client side when connecting to a hidden service. Bugfix
6476 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6477 - When closing an application-side connection because its circuit is
6478 getting torn down, generate the stream event correctly. Bugfix on
6479 0.1.2.x. Anonymous patch.
6482 Changes in version 0.2.1.5-alpha - 2008-08-31
6483 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
6484 in a lot of the infrastructure for adding authorization to hidden
6485 services, lays the groundwork for having clients read their load
6486 balancing information out of the networkstatus consensus rather than
6487 the individual router descriptors, addresses two potential anonymity
6488 issues, and fixes a variety of smaller issues.
6491 - Convert many internal address representations to optionally hold
6493 - Generate and accept IPv6 addresses in many protocol elements.
6494 - Make resolver code handle nameservers located at ipv6 addresses.
6495 - Begin implementation of proposal 121 ("Client authorization for
6496 hidden services"): configure hidden services with client
6497 authorization, publish descriptors for them, and configure
6498 authorization data for hidden services at clients. The next
6499 step is to actually access hidden services that perform client
6501 - More progress toward proposal 141: Network status consensus
6502 documents and votes now contain bandwidth information for each
6503 router and a summary of that router's exit policy. Eventually this
6504 will be used by clients so that they do not have to download every
6505 known descriptor before building circuits.
6507 o Major bugfixes (on 0.2.0.x and before):
6508 - When sending CREATED cells back for a given circuit, use a 64-bit
6509 connection ID to find the right connection, rather than an addr:port
6510 combination. Now that we can have multiple OR connections between
6511 the same ORs, it is no longer possible to use addr:port to uniquely
6512 identify a connection.
6513 - Relays now reject risky extend cells: if the extend cell includes
6514 a digest of all zeroes, or asks to extend back to the relay that
6515 sent the extend cell, tear down the circuit. Ideas suggested
6517 - If not enough of our entry guards are available so we add a new
6518 one, we might use the new one even if it overlapped with the
6519 current circuit's exit relay (or its family). Anonymity bugfix
6520 pointed out by rovv.
6523 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6524 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6525 - When using the TransPort option on OpenBSD, and using the User
6526 option to change UID and drop privileges, make sure to open /dev/pf
6527 before dropping privileges. Fixes bug 782. Patch from Christopher
6528 Davis. Bugfix on 0.1.2.1-alpha.
6529 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6530 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6531 - Add a missing safe_str() call for a debug log message.
6532 - Use 64 bits instead of 32 bits for connection identifiers used with
6533 the controller protocol, to greatly reduce risk of identifier reuse.
6534 - Make the autoconf script accept the obsolete --with-ssl-dir
6535 option as an alias for the actually-working --with-openssl-dir
6536 option. Fix the help documentation to recommend --with-openssl-dir.
6537 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6540 - Rate-limit too-many-sockets messages: when they happen, they happen
6541 a lot. Resolves bug 748.
6542 - Resist DNS poisoning a little better by making sure that names in
6543 answer sections match.
6544 - Print the SOCKS5 error message string as well as the error code
6545 when a tor-resolve request fails. Patch from Jacob.
6548 Changes in version 0.2.1.4-alpha - 2008-08-04
6549 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6552 - The address part of exit policies was not correctly written
6553 to router descriptors. This generated router descriptors that failed
6554 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6556 - Tor triggered a false assert when extending a circuit to a relay
6557 but we already have a connection open to that relay. Noticed by
6558 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6561 - Fix a hidden service logging bug: in some edge cases, the router
6562 descriptor of a previously picked introduction point becomes
6563 obsolete and we need to give up on it rather than continually
6564 complaining that it has become obsolete. Observed by xiando. Bugfix
6568 - Take out the TestVia config option, since it was a workaround for
6569 a bug that was fixed in Tor 0.1.1.21.
6572 Changes in version 0.2.1.3-alpha - 2008-08-03
6573 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6574 infinite-length circuit attacks (see proposal 110); fixes a bug that
6575 might cause exit relays to corrupt streams they send back; allows
6576 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6577 ExcludeExitNodes config options; and fixes a big pile of bugs.
6579 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6580 - Send a bootstrap problem "warn" event on the first problem if the
6581 reason is NO_ROUTE (that is, our network is down).
6584 - Implement most of proposal 110: The first K cells to be sent
6585 along a circuit are marked as special "early" cells; only K "early"
6586 cells will be allowed. Once this code is universal, we can block
6587 certain kinds of DOS attack by requiring that EXTEND commands must
6588 be sent using an "early" cell.
6591 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6592 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6593 on the client side when connecting to a hidden service. Bugfix
6594 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6595 - Ensure that two circuits can never exist on the same connection
6596 with the same circuit ID, even if one is marked for close. This
6597 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6600 - When relays do their initial bandwidth measurement, don't limit
6601 to just our entry guards for the test circuits. Otherwise we tend
6602 to have multiple test circuits going through a single entry guard,
6603 which makes our bandwidth test less accurate. Fixes part of bug 654;
6604 patch contributed by Josh Albrecht.
6605 - Add an ExcludeExitNodes option so users can list a set of nodes
6606 that should be be excluded from the exit node position, but
6607 allowed elsewhere. Implements proposal 151.
6608 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6609 ExcludeNodes and ExcludeExitNodes lists.
6610 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6611 be more efficient. Formerly it was quadratic in the number of
6612 servers; now it should be linear. Fixes bug 509.
6613 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6614 and n_conn_id_digest fields into a separate structure that's
6615 only needed when the circuit has not yet attached to an n_conn.
6618 - Change the contrib/tor.logrotate script so it makes the new
6619 logs as "_tor:_tor" rather than the default, which is generally
6620 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6621 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6622 warnings (occasionally), but it can also cause the compiler to
6623 eliminate error-checking code. Suggested by Peter Gutmann.
6624 - When a hidden service is giving up on an introduction point candidate
6625 that was not included in the last published rendezvous descriptor,
6626 don't reschedule publication of the next descriptor. Fixes bug 763.
6628 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6629 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6630 and nobody claims to be using them. Fixes bug 754. Bugfix on
6631 0.1.0.1-rc. Patch from Christian Wilms.
6632 - Fix a small alignment and memory-wasting bug on buffer chunks.
6635 o Minor bugfixes (controller):
6636 - When closing an application-side connection because its circuit
6637 is getting torn down, generate the stream event correctly.
6638 Bugfix on 0.1.2.x. Anonymous patch.
6641 - Remove all backward-compatibility code to support relays running
6642 versions of Tor so old that they no longer work at all on the
6646 Changes in version 0.2.0.30 - 2008-07-15
6648 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6649 warnings (occasionally), but it can also cause the compiler to
6650 eliminate error-checking code. Suggested by Peter Gutmann.
6653 Changes in version 0.2.0.29-rc - 2008-07-08
6654 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6655 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6658 - If you have more than one bridge but don't know their keys,
6659 you would only launch a request for the descriptor of the first one
6660 on your list. (Tor considered launching requests for the others, but
6661 found that it already had a connection on the way for $0000...0000
6662 so it didn't open another.) Bugfix on 0.2.0.x.
6663 - If you have more than one bridge but don't know their keys, and the
6664 connection to one of the bridges failed, you would cancel all
6665 pending bridge connections. (After all, they all have the same
6666 digest.) Bugfix on 0.2.0.x.
6667 - When a hidden service was trying to establish an introduction point,
6668 and Tor had built circuits preemptively for such purposes, we
6669 were ignoring all the preemptive circuits and launching a new one
6670 instead. Bugfix on 0.2.0.14-alpha.
6671 - When a hidden service was trying to establish an introduction point,
6672 and Tor *did* manage to reuse one of the preemptively built
6673 circuits, it didn't correctly remember which one it used,
6674 so it asked for another one soon after, until there were no
6675 more preemptive circuits, at which point it launched one from
6676 scratch. Bugfix on 0.0.9.x.
6677 - Make directory servers include the X-Your-Address-Is: http header in
6678 their responses even for begin_dir conns. Now clients who only
6679 ever use begin_dir connections still have a way to learn their IP
6680 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6683 - Fix a macro/CPP interaction that was confusing some compilers:
6684 some GCCs don't like #if/#endif pairs inside macro arguments.
6686 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6687 Fixes bug 704; fix from Steven Murdoch.
6688 - When opening /dev/null in finish_daemonize(), do not pass the
6689 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6690 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6691 - Correctly detect transparent proxy support on Linux hosts that
6692 require in.h to be included before netfilter_ipv4.h. Patch
6694 - Disallow session resumption attempts during the renegotiation
6695 stage of the v2 handshake protocol. Clients should never be trying
6696 session resumption at this point, but apparently some did, in
6697 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6698 found by Geoff Goodell.
6701 Changes in version 0.2.1.2-alpha - 2008-06-20
6702 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6703 make it easier to set up your own private Tor network; fixes several
6704 big bugs with using more than one bridge relay; fixes a big bug with
6705 offering hidden services quickly after Tor starts; and uses a better
6706 API for reporting potential bootstrapping problems to the controller.
6709 - New TestingTorNetwork config option to allow adjustment of
6710 previously constant values that, while reasonable, could slow
6711 bootstrapping. Implements proposal 135. Patch from Karsten.
6714 - If you have more than one bridge but don't know their digests,
6715 you would only learn a request for the descriptor of the first one
6716 on your list. (Tor considered launching requests for the others, but
6717 found that it already had a connection on the way for $0000...0000
6718 so it didn't open another.) Bugfix on 0.2.0.x.
6719 - If you have more than one bridge but don't know their digests,
6720 and the connection to one of the bridges failed, you would cancel
6721 all pending bridge connections. (After all, they all have the
6722 same digest.) Bugfix on 0.2.0.x.
6723 - When establishing a hidden service, introduction points that
6724 originate from cannibalized circuits are completely ignored and not
6725 included in rendezvous service descriptors. This might be another
6726 reason for delay in making a hidden service available. Bugfix
6727 from long ago (0.0.9.x?)
6730 - Allow OpenSSL to use dynamic locks if it wants.
6731 - When building a consensus, do not include routers that are down.
6732 This will cut down 30% to 40% on consensus size. Implements
6734 - In directory authorities' approved-routers files, allow
6735 fingerprints with or without space.
6736 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6737 controller can query our current bootstrap state in case it attaches
6738 partway through and wants to catch up.
6739 - Send an initial "Starting" bootstrap status event, so we have a
6740 state to start out in.
6743 - Asking for a conditional consensus at .../consensus/<fingerprints>
6744 would crash a dirserver if it did not already have a
6745 consensus. Bugfix on 0.2.1.1-alpha.
6746 - Clean up some macro/CPP interactions: some GCC versions don't like
6747 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
6750 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
6751 - Directory authorities shouldn't complain about bootstrapping
6752 problems just because they do a lot of reachability testing and
6753 some of the connection attempts fail.
6754 - Start sending "count" and "recommendation" key/value pairs in
6755 bootstrap problem status events, so the controller can hear about
6756 problems even before Tor decides they're worth reporting for sure.
6757 - If you're using bridges, generate "bootstrap problem" warnings
6758 as soon as you run out of working bridges, rather than waiting
6759 for ten failures -- which will never happen if you have less than
6761 - If we close our OR connection because there's been a circuit
6762 pending on it for too long, we were telling our bootstrap status
6763 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
6766 Changes in version 0.2.1.1-alpha - 2008-06-13
6767 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
6768 were making the Tor process bloat especially on Linux; makes our TLS
6769 handshake blend in better; sends "bootstrap phase" status events to
6770 the controller, so it can keep the user informed of progress (and
6771 problems) fetching directory information and establishing circuits;
6772 and adds a variety of smaller features.
6775 - More work on making our TLS handshake blend in: modify the list
6776 of ciphers advertised by OpenSSL in client mode to even more
6777 closely resemble a common web browser. We cheat a little so that
6778 we can advertise ciphers that the locally installed OpenSSL doesn't
6780 - Start sending "bootstrap phase" status events to the controller,
6781 so it can keep the user informed of progress fetching directory
6782 information and establishing circuits. Also inform the controller
6783 if we think we're stuck at a particular bootstrap phase. Implements
6785 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6786 cross-platform entropy collection again. We used to use it, then
6787 stopped using it because of a bug that could crash systems that
6788 called RAND_poll when they had a lot of fds open. It looks like the
6789 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6790 at startup, and to call RAND_poll() when we reseed later only if
6791 we have a non-buggy OpenSSL version.
6794 - When we choose to abandon a new entry guard because we think our
6795 older ones might be better, close any circuits pending on that
6796 new entry guard connection. This fix should make us recover much
6797 faster when our network is down and then comes back. Bugfix on
6798 0.1.2.8-beta; found by lodger.
6800 o Memory fixes and improvements:
6801 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6802 to avoid unused RAM in buffer chunks and memory pools.
6803 - Speed up parsing and cut down on memory fragmentation by using
6804 stack-style allocations for parsing directory objects. Previously,
6805 this accounted for over 40% of allocations from within Tor's code
6806 on a typical directory cache.
6807 - Use a Bloom filter rather than a digest-based set to track which
6808 descriptors we need to keep around when we're cleaning out old
6809 router descriptors. This speeds up the computation significantly,
6810 and may reduce fragmentation.
6811 - Reduce the default smartlist size from 32 to 16; it turns out that
6812 most smartlists hold around 8-12 elements tops.
6813 - Make dumpstats() log the fullness and size of openssl-internal
6815 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6816 patch to their OpenSSL, turn it on to save memory on servers. This
6817 patch will (with any luck) get included in a mainline distribution
6819 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6820 compress cells, which are basically all encrypted, compressed,
6824 - Stop reloading the router list from disk for no reason when we
6825 run out of reachable directory mirrors. Once upon a time reloading
6826 it would set the 'is_running' flag back to 1 for them. It hasn't
6827 done that for a long time.
6828 - In very rare situations new hidden service descriptors were
6829 published earlier than 30 seconds after the last change to the
6830 service. (We currently think that a hidden service descriptor
6831 that's been stable for 30 seconds is worth publishing.)
6834 - Allow separate log levels to be configured for different logging
6835 domains. For example, this allows one to log all notices, warnings,
6836 or errors, plus all memory management messages of level debug or
6837 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
6838 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
6839 and stop using a warning that had become unfixably verbose under
6841 - New --hush command-line option similar to --quiet. While --quiet
6842 disables all logging to the console on startup, --hush limits the
6843 output to messages of warning and error severity.
6844 - Servers support a new URL scheme for consensus downloads that
6845 allows the client to specify which authorities are trusted.
6846 The server then only sends the consensus if the client will trust
6847 it. Otherwise a 404 error is sent back. Clients use this
6848 new scheme when the server supports it (meaning it's running
6849 0.2.1.1-alpha or later). Implements proposal 134.
6850 - New configure/torrc options (--enable-geoip-stats,
6851 DirRecordUsageByCountry) to record how many IPs we've served
6852 directory info to in each country code, how many status documents
6853 total we've sent to each country code, and what share of the total
6854 directory requests we should expect to see.
6855 - Use the TLS1 hostname extension to more closely resemble browser
6857 - Lots of new unit tests.
6858 - Add a macro to implement the common pattern of iterating through
6859 two parallel lists in lockstep.
6862 Changes in version 0.2.0.28-rc - 2008-06-13
6863 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
6864 performance bug, and fixes a bunch of smaller bugs.
6867 - Fix a bug where, when we were choosing the 'end stream reason' to
6868 put in our relay end cell that we send to the exit relay, Tor
6869 clients on Windows were sometimes sending the wrong 'reason'. The
6870 anonymity problem is that exit relays may be able to guess whether
6871 the client is running Windows, thus helping partition the anonymity
6872 set. Down the road we should stop sending reasons to exit relays,
6873 or otherwise prevent future versions of this bug.
6876 - While setting up a hidden service, some valid introduction circuits
6877 were overlooked and abandoned. This might be the reason for
6878 the long delay in making a hidden service available. Bugfix on
6882 - Update to the "June 9 2008" ip-to-country file.
6883 - Run 'make test' as part of 'make dist', so we stop releasing so
6884 many development snapshots that fail their unit tests.
6887 - When we're checking if we have enough dir info for each relay
6888 to begin establishing circuits, make sure that we actually have
6889 the descriptor listed in the consensus, not just any descriptor.
6891 - Bridge relays no longer print "xx=0" in their extrainfo document
6892 for every single country code in the geoip db. Bugfix on
6894 - Only warn when we fail to load the geoip file if we were planning to
6895 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
6896 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6897 Tor won't realize it should publish a new relay descriptor. Fixes
6898 bug 688, reported by mfr. Bugfix on 0.1.2.x.
6899 - When we haven't had any application requests lately, don't bother
6900 logging that we have expired a bunch of descriptors. Bugfix
6902 - Make relay cells written on a connection count as non-padding when
6903 tracking how long a connection has been in use. Bugfix on
6904 0.2.0.1-alpha. Spotted by lodger.
6905 - Fix unit tests in 0.2.0.27-rc.
6906 - Fix compile on Windows.
6909 Changes in version 0.2.0.27-rc - 2008-06-03
6910 Tor 0.2.0.27-rc adds a few features we left out of the earlier
6911 release candidates. In particular, we now include an IP-to-country
6912 GeoIP database, so controllers can easily look up what country a
6913 given relay is in, and so bridge relays can give us some sanitized
6914 summaries about which countries are making use of bridges. (See proposal
6915 126-geoip-fetching.txt for details.)
6918 - Include an IP-to-country GeoIP file in the tarball, so bridge
6919 relays can report sanitized summaries of the usage they're seeing.
6922 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
6923 Robert Hogan. Fixes the first part of bug 681.
6924 - Make bridge authorities never serve extrainfo docs.
6925 - Add support to detect Libevent versions in the 1.4.x series
6927 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
6928 - Include a new contrib/tor-exit-notice.html file that exit relay
6929 operators can put on their website to help reduce abuse queries.
6932 - When tunneling an encrypted directory connection, and its first
6933 circuit fails, do not leave it unattached and ask the controller
6934 to deal. Fixes the second part of bug 681.
6935 - Make bridge authorities correctly expire old extrainfo documents
6939 Changes in version 0.2.0.26-rc - 2008-05-13
6940 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
6941 in Debian's OpenSSL packages. All users running any 0.2.0.x version
6942 should upgrade, whether they're running Debian or not.
6944 o Major security fixes:
6945 - Use new V3 directory authority keys on the tor26, gabelmoo, and
6946 moria1 V3 directory authorities. The old keys were generated with
6947 a vulnerable version of Debian's OpenSSL package, and must be
6948 considered compromised. Other authorities' keys were not generated
6949 with an affected version of OpenSSL.
6952 - List authority signatures as "unrecognized" based on DirServer
6953 lines, not on cert cache. Bugfix on 0.2.0.x.
6956 - Add a new V3AuthUseLegacyKey option to make it easier for
6957 authorities to change their identity keys if they have to.
6960 Changes in version 0.2.0.25-rc - 2008-04-23
6961 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
6964 - Remember to initialize threading before initializing logging.
6965 Otherwise, many BSD-family implementations will crash hard on
6966 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
6969 - Authorities correctly free policies on bad servers on
6970 exit. Fixes bug 672. Bugfix on 0.2.0.x.
6973 Changes in version 0.2.0.24-rc - 2008-04-22
6974 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
6975 v3 directory authority, makes relays with dynamic IP addresses and no
6976 DirPort notice more quickly when their IP address changes, fixes a few
6977 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
6979 o New directory authorities:
6980 - Take lefkada out of the list of v3 directory authorities, since
6981 it has been down for months.
6982 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
6986 - Detect address changes more quickly on non-directory mirror
6987 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
6989 o Minor features (security):
6990 - Reject requests for reverse-dns lookup of names that are in
6991 a private address space. Patch from lodger.
6992 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
6995 o Minor bugfixes (crashes):
6996 - Avoid a rare assert that can trigger when Tor doesn't have much
6997 directory information yet and it tries to fetch a v2 hidden
6998 service descriptor. Fixes bug 651, reported by nwf.
6999 - Initialize log mutex before initializing dmalloc. Otherwise,
7000 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7001 - Use recursive pthread mutexes in order to avoid deadlock when
7002 logging debug-level messages to a controller. Bug spotted by nwf,
7003 bugfix on 0.2.0.16-alpha.
7005 o Minor bugfixes (resource management):
7006 - Keep address policies from leaking memory: start their refcount
7007 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7008 - Free authority certificates on exit, so they don't look like memory
7009 leaks. Bugfix on 0.2.0.19-alpha.
7010 - Free static hashtables for policy maps and for TLS connections on
7011 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7012 - Avoid allocating extra space when computing consensuses on 64-bit
7013 platforms. Bug spotted by aakova.
7015 o Minor bugfixes (misc):
7016 - Do not read the configuration file when we've only been told to
7017 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7018 based on patch from Sebastian Hahn.
7019 - Exit relays that are used as a client can now reach themselves
7020 using the .exit notation, rather than just launching an infinite
7021 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7022 - When attempting to open a logfile fails, tell us why.
7023 - Fix a dumb bug that was preventing us from knowing that we should
7024 preemptively build circuits to handle expected directory requests.
7025 Fixes bug 660. Bugfix on 0.1.2.x.
7026 - Warn less verbosely about clock skew from netinfo cells from
7027 untrusted sources. Fixes bug 663.
7028 - Make controller stream events for DNS requests more consistent,
7029 by adding "new stream" events for DNS requests, and removing
7030 spurious "stream closed" events" for cached reverse resolves.
7031 Patch from mwenge. Fixes bug 646.
7032 - Correctly notify one-hop connections when a circuit build has
7033 failed. Possible fix for bug 669. Found by lodger.
7036 Changes in version 0.2.0.23-rc - 2008-03-24
7037 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7038 makes bootstrapping faster if the first directory mirror you contact
7039 is down. The bundles also include the new Vidalia 0.1.2 release.
7042 - When a tunneled directory request is made to a directory server
7043 that's down, notice after 30 seconds rather than 120 seconds. Also,
7044 fail any begindir streams that are pending on it, so they can
7045 retry elsewhere. This was causing multi-minute delays on bootstrap.
7048 Changes in version 0.2.0.22-rc - 2008-03-18
7049 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7050 enables encrypted directory connections by default for non-relays, fixes
7051 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7052 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7055 - Enable encrypted directory connections by default for non-relays,
7056 so censor tools that block Tor directory connections based on their
7057 plaintext patterns will no longer work. This means Tor works in
7058 certain censored countries by default again.
7061 - Make sure servers always request certificates from clients during
7062 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7063 - Do not enter a CPU-eating loop when a connection is closed in
7064 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7065 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7066 - Fix assertion failure that could occur when a blocked circuit
7067 became unblocked, and it had pending client DNS requests. Bugfix
7068 on 0.2.0.1-alpha. Fixes bug 632.
7070 o Minor bugfixes (on 0.1.2.x):
7071 - Generate "STATUS_SERVER" events rather than misspelled
7072 "STATUS_SEVER" events. Caught by mwenge.
7073 - When counting the number of bytes written on a TLS connection,
7074 look at the BIO actually used for writing to the network, not
7075 at the BIO used (sometimes) to buffer data for the network.
7076 Looking at different BIOs could result in write counts on the
7077 order of ULONG_MAX. Fixes bug 614.
7078 - On Windows, correctly detect errors when listing the contents of
7079 a directory. Fix from lodger.
7081 o Minor bugfixes (on 0.2.0.x):
7082 - Downgrade "sslv3 alert handshake failure" message to INFO.
7083 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7084 left BandwidthRate and BandwidthBurst at the default, we would be
7085 silently limited by those defaults. Now raise them to match the
7086 RelayBandwidth* values.
7087 - Fix the SVK version detection logic to work correctly on a branch.
7088 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7089 CPUs. Fixes bug 625.
7090 - Logging functions now check that the passed severity is sane.
7091 - Use proper log levels in the testsuite call of
7092 get_interface_address6().
7093 - When using a nonstandard malloc, do not use the platform values for
7094 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7095 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7097 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7098 - Avoid double-marked-for-close warning when certain kinds of invalid
7099 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7100 for bug 617. Bugfix on 0.2.0.1-alpha.
7101 - Make sure that the "NULL-means-reject *:*" convention is followed by
7102 all the policy manipulation functions, avoiding some possible crash
7103 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7104 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7105 actually works, and doesn't warn about every single reverse lookup.
7106 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7109 - Only log guard node status when guard node status has changed.
7110 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7111 make "INFO" 75% less verbose.
7114 Changes in version 0.2.0.21-rc - 2008-03-02
7115 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7116 makes Tor work well with Vidalia again, fixes a rare assert bug,
7117 and fixes a pair of more minor bugs. The bundles also include Vidalia
7118 0.1.0 and Torbutton 1.1.16.
7121 - The control port should declare that it requires password auth
7122 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7123 bugfix on 0.2.0.20-rc. Fixes bug 615.
7124 - Downgrade assert in connection_buckets_decrement() to a log message.
7125 This may help us solve bug 614, and in any case will make its
7126 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7127 - We were sometimes miscounting the number of bytes read from the
7128 network, causing our rate limiting to not be followed exactly.
7129 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7132 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7133 OpenSSL versions should have been working fine. Diagnosis and patch
7134 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7135 Bugfix on 0.2.0.20-rc.
7138 Changes in version 0.2.0.20-rc - 2008-02-24
7139 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7140 makes more progress towards normalizing Tor's TLS handshake, makes
7141 hidden services work better again, helps relays bootstrap if they don't
7142 know their IP address, adds optional support for linking in openbsd's
7143 allocator or tcmalloc, allows really fast relays to scale past 15000
7144 sockets, and fixes a bunch of minor bugs reported by Veracode.
7147 - Enable the revised TLS handshake based on the one designed by
7148 Steven Murdoch in proposal 124, as revised in proposal 130. It
7149 includes version negotiation for OR connections as described in
7150 proposal 105. The new handshake is meant to be harder for censors
7151 to fingerprint, and it adds the ability to detect certain kinds of
7152 man-in-the-middle traffic analysis attacks. The version negotiation
7153 feature will allow us to improve Tor's link protocol more safely
7155 - Choose which bridge to use proportional to its advertised bandwidth,
7156 rather than uniformly at random. This should speed up Tor for
7157 bridge users. Also do this for people who set StrictEntryNodes.
7158 - When a TrackHostExits-chosen exit fails too many times in a row,
7159 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7162 - Resolved problems with (re-)fetching hidden service descriptors.
7163 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7165 - If we only ever used Tor for hidden service lookups or posts, we
7166 would stop building circuits and start refusing connections after
7167 24 hours, since we falsely believed that Tor was dormant. Reported
7168 by nwf; bugfix on 0.1.2.x.
7169 - Servers that don't know their own IP address should go to the
7170 authorities for their first directory fetch, even if their DirPort
7171 is off or if they don't know they're reachable yet. This will help
7172 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7173 - When counting the number of open sockets, count not only the number
7174 of sockets we have received from the socket() call, but also
7175 the number we've gotten from accept() and socketpair(). This bug
7176 made us fail to count all sockets that we were using for incoming
7177 connections. Bugfix on 0.2.0.x.
7178 - Fix code used to find strings within buffers, when those strings
7179 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7180 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7181 - Add a new __HashedControlSessionPassword option for controllers
7182 to use for one-off session password hashes that shouldn't get
7183 saved to disk by SAVECONF --- Vidalia users were accumulating a
7184 pile of HashedControlPassword lines in their torrc files, one for
7185 each time they had restarted Tor and then clicked Save. Make Tor
7186 automatically convert "HashedControlPassword" to this new option but
7187 only when it's given on the command line. Partial fix for bug 586.
7189 o Minor features (performance):
7190 - Tune parameters for cell pool allocation to minimize amount of
7192 - Add OpenBSD malloc code from phk as an optional malloc
7193 replacement on Linux: some glibc libraries do very poorly
7194 with Tor's memory allocation patterns. Pass
7195 --enable-openbsd-malloc to get the replacement malloc code.
7196 - Add a --with-tcmalloc option to the configure script to link
7197 against tcmalloc (if present). Does not yet search for
7198 non-system include paths.
7199 - Stop imposing an arbitrary maximum on the number of file descriptors
7200 used for busy servers. Bug reported by Olaf Selke; patch from
7203 o Minor features (other):
7204 - When SafeLogging is disabled, log addresses along with all TLS
7206 - When building with --enable-gcc-warnings, check for whether Apple's
7207 warning "-Wshorten-64-to-32" is available.
7208 - Add a --passphrase-fd argument to the tor-gencert command for
7211 o Minor bugfixes (memory leaks and code problems):
7212 - We were leaking a file descriptor if Tor started with a zero-length
7213 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7214 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7216 - We were comparing the raw BridgePassword entry with a base64'ed
7217 version of it, when handling a "/tor/networkstatus-bridges"
7218 directory request. Now compare correctly. Noticed by Veracode.
7219 - Recover from bad tracked-since value in MTBF-history file.
7221 - Alter the code that tries to recover from unhandled write
7222 errors, to not try to flush onto a socket that's given us
7223 unhandled errors. Bugfix on 0.1.2.x.
7224 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7225 tup. Bugfix on 0.2.0.3-alpha.
7227 o Minor bugfixes (other):
7228 - If we have an extra-info document for our server, always make
7229 it available on the control port, even if we haven't gotten
7230 a copy of it from an authority yet. Patch from mwenge.
7231 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7232 - Directory mirrors no longer include a guess at the client's IP
7233 address if the connection appears to be coming from the same /24
7234 network; it was producing too many wrong guesses.
7235 - Make the new hidden service code respect the SafeLogging setting.
7236 Bugfix on 0.2.0.x. Patch from Karsten.
7237 - When starting as an authority, do not overwrite all certificates
7238 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7239 - If we're trying to flush the last bytes on a connection (for
7240 example, when answering a directory request), reset the
7241 time-to-give-up timeout every time we manage to write something
7242 on the socket. Bugfix on 0.1.2.x.
7243 - Change the behavior of "getinfo status/good-server-descriptor"
7244 so it doesn't return failure when any authority disappears.
7245 - Even though the man page said that "TrackHostExits ." should
7246 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7247 - Report TLS "zero return" case as a "clean close" and "IO error"
7248 as a "close". Stop calling closes "unexpected closes": existing
7249 Tors don't use SSL_close(), so having a connection close without
7250 the TLS shutdown handshake is hardly unexpected.
7251 - Send NAMESERVER_STATUS messages for a single failed nameserver
7254 o Code simplifications and refactoring:
7255 - Remove the tor_strpartition function: its logic was confused,
7256 and it was only used for one thing that could be implemented far
7260 Changes in version 0.2.0.19-alpha - 2008-02-09
7261 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7262 handshake, makes path selection for relays more secure and IP address
7263 guessing more robust, and generally fixes a lot of bugs in preparation
7264 for calling the 0.2.0 branch stable.
7267 - Do not include recognizeable strings in the commonname part of
7268 Tor's x509 certificates.
7271 - If we're a relay, avoid picking ourselves as an introduction point,
7272 a rendezvous point, or as the final hop for internal circuits. Bug
7273 reported by taranis and lodger. Bugfix on 0.1.2.x.
7274 - Patch from "Andrew S. Lists" to catch when we contact a directory
7275 mirror at IP address X and he says we look like we're coming from
7276 IP address X. Bugfix on 0.1.2.x.
7278 o Minor features (security):
7279 - Be more paranoid about overwriting sensitive memory on free(),
7280 as a defensive programming tactic to ensure forward secrecy.
7282 o Minor features (directory authority):
7283 - Actually validate the options passed to AuthDirReject,
7284 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7285 - Reject router descriptors with out-of-range bandwidthcapacity or
7286 bandwidthburst values.
7288 o Minor features (controller):
7289 - Reject controller commands over 1MB in length. This keeps rogue
7290 processes from running us out of memory.
7292 o Minor features (misc):
7293 - Give more descriptive well-formedness errors for out-of-range
7294 hidden service descriptor/protocol versions.
7295 - Make memory debugging information describe more about history
7296 of cell allocation, so we can help reduce our memory use.
7298 o Deprecated features (controller):
7299 - The status/version/num-versioning and status/version/num-concurring
7300 GETINFO options are no longer useful in the v3 directory protocol:
7301 treat them as deprecated, and warn when they're used.
7304 - When our consensus networkstatus has been expired for a while, stop
7305 being willing to build circuits using it. Fixes bug 401. Bugfix
7307 - Directory caches now fetch certificates from all authorities
7308 listed in a networkstatus consensus, even when they do not
7309 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7310 - When connecting to a bridge without specifying its key, insert
7311 the connection into the identity-to-connection map as soon as
7312 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7313 - Detect versions of OS X where malloc_good_size() is present in the
7314 library but never actually declared. Resolves bug 587. Bugfix
7316 - Stop incorrectly truncating zlib responses to directory authority
7317 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7318 - Stop recommending that every server operator send mail to tor-ops.
7319 Resolves bug 597. Bugfix on 0.1.2.x.
7320 - Don't trigger an assert if we start a directory authority with a
7321 private IP address (like 127.0.0.1).
7322 - Avoid possible failures when generating a directory with routers
7323 with over-long versions strings, or too many flags set. Bugfix
7325 - If an attempt to launch a DNS resolve request over the control
7326 port fails because we have overrun the limit on the number of
7327 connections, tell the controller that the request has failed.
7328 - Avoid using too little bandwidth when our clock skips a few
7329 seconds. Bugfix on 0.1.2.x.
7330 - Fix shell error when warning about missing packages in configure
7331 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7332 - Do not become confused when receiving a spurious VERSIONS-like
7333 cell from a confused v1 client. Bugfix on 0.2.0.x.
7334 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7335 introduction points for a hidden service have failed. Patch from
7336 Karsten Loesing. Bugfix on 0.2.0.x.
7338 o Code simplifications and refactoring:
7339 - Remove some needless generality from cpuworker code, for improved
7341 - Stop overloading the circuit_t.onionskin field for both "onionskin
7342 from a CREATE cell that we are waiting for a cpuworker to be
7343 assigned" and "onionskin from an EXTEND cell that we are going to
7344 send to an OR as soon as we are connected". Might help with bug 600.
7345 - Add an in-place version of aes_crypt() so that we can avoid doing a
7346 needless memcpy() call on each cell payload.
7349 Changes in version 0.2.0.18-alpha - 2008-01-25
7350 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7351 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7352 that can warn or reject connections to ports generally associated with
7353 vulnerable-plaintext protocols.
7355 o New directory authorities:
7356 - Set up dannenberg (run by CCC) as the sixth v3 directory
7360 - Fix a major memory leak when attempting to use the v2 TLS
7361 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7362 - We accidentally enabled the under-development v2 TLS handshake
7363 code, which was causing log entries like "TLS error while
7364 renegotiating handshake". Disable it again. Resolves bug 590.
7365 - We were computing the wrong Content-Length: header for directory
7366 responses that need to be compressed on the fly, causing clients
7367 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7371 - Avoid going directly to the directory authorities even if you're a
7372 relay, if you haven't found yourself reachable yet or if you've
7373 decided not to advertise your dirport yet. Addresses bug 556.
7374 - If we've gone 12 hours since our last bandwidth check, and we
7375 estimate we have less than 50KB bandwidth capacity but we could
7376 handle more, do another bandwidth test.
7377 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7378 Tor can warn and/or refuse connections to ports commonly used with
7379 vulnerable-plaintext protocols. Currently we warn on ports 23,
7380 109, 110, and 143, but we don't reject any.
7383 - When we setconf ClientOnly to 1, close any current OR and Dir
7384 listeners. Reported by mwenge.
7385 - When we get a consensus that's been signed by more people than
7386 we expect, don't log about it; it's not a big deal. Reported
7390 - Don't answer "/tor/networkstatus-bridges" directory requests if
7391 the request isn't encrypted.
7392 - Make "ClientOnly 1" config option disable directory ports too.
7393 - Patches from Karsten Loesing to make v2 hidden services more
7394 robust: work even when there aren't enough HSDir relays available;
7395 retry when a v2 rend desc fetch fails; but don't retry if we
7396 already have a usable v0 rend desc.
7399 Changes in version 0.2.0.17-alpha - 2008-01-17
7400 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7403 - Make the tor-gencert man page get included correctly in the tarball.
7406 Changes in version 0.2.0.16-alpha - 2008-01-17
7407 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7408 Loesing, and generally cleans up a lot of features and minor bugs.
7410 o New directory authorities:
7411 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7414 o Major performance improvements:
7415 - Switch our old ring buffer implementation for one more like that
7416 used by free Unix kernels. The wasted space in a buffer with 1mb
7417 of data will now be more like 8k than 1mb. The new implementation
7418 also avoids realloc();realloc(); patterns that can contribute to
7419 memory fragmentation.
7422 - Configuration files now accept C-style strings as values. This
7423 helps encode characters not allowed in the current configuration
7424 file format, such as newline or #. Addresses bug 557.
7425 - Although we fixed bug 539 (where servers would send HTTP status 503
7426 responses _and_ send a body too), there are still servers out
7427 there that haven't upgraded. Therefore, make clients parse such
7428 bodies when they receive them.
7429 - When we're not serving v2 directory information, there is no reason
7430 to actually keep any around. Remove the obsolete files and directory
7431 on startup if they are very old and we aren't going to serve them.
7433 o Minor performance improvements:
7434 - Reference-count and share copies of address policy entries; only 5%
7435 of them were actually distinct.
7436 - Never walk through the list of logs if we know that no log is
7437 interested in a given message.
7440 - When an authority has not signed a consensus, do not try to
7441 download a nonexistent "certificate with key 00000000". Bugfix
7442 on 0.2.0.x. Fixes bug 569.
7443 - Fix a rare assert error when we're closing one of our threads:
7444 use a mutex to protect the list of logs, so we never write to the
7445 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
7446 bug 575, which is kind of the revenge of bug 222.
7447 - Patch from Karsten Loesing to complain less at both the client
7448 and the relay when a relay used to have the HSDir flag but doesn't
7449 anymore, and we try to upload a hidden service descriptor.
7450 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
7452 - Do not try to download missing certificates until we have tried
7453 to check our fallback consensus. Fixes bug 583.
7454 - Make bridges round reported GeoIP stats info up to the nearest
7455 estimate, not down. Now we can distinguish between "0 people from
7456 this country" and "1 person from this country".
7457 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
7458 - Avoid possible segfault if key generation fails in
7459 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
7460 - Avoid segfault in the case where a badly behaved v2 versioning
7461 directory sends a signed networkstatus with missing client-versions.
7463 - Avoid segfaults on certain complex invocations of
7464 router_get_by_hexdigest(). Bugfix on 0.1.2.
7465 - Correct bad index on array access in parse_http_time(). Bugfix
7467 - Fix possible bug in vote generation when server versions are present
7468 but client versions are not.
7469 - Fix rare bug on REDIRECTSTREAM control command when called with no
7470 port set: it could erroneously report an error when none had
7472 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
7473 compressing large objects and find ourselves with more than 4k
7474 left over. Bugfix on 0.2.0.
7475 - Fix a small memory leak when setting up a hidden service.
7476 - Fix a few memory leaks that could in theory happen under bizarre
7478 - Fix an assert if we post a general-purpose descriptor via the
7479 control port but that descriptor isn't mentioned in our current
7480 network consensus. Bug reported by Jon McLachlan; bugfix on
7483 o Minor features (controller):
7484 - Get NS events working again. Patch from tup.
7485 - The GETCONF command now escapes and quotes configuration values
7486 that don't otherwise fit into the torrc file.
7487 - The SETCONF command now handles quoted values correctly.
7489 o Minor features (directory authorities):
7490 - New configuration options to override default maximum number of
7491 servers allowed on a single IP address. This is important for
7492 running a test network on a single host.
7493 - Actually implement the -s option to tor-gencert.
7494 - Add a manual page for tor-gencert.
7496 o Minor features (bridges):
7497 - Bridge authorities no longer serve bridge descriptors over
7498 unencrypted connections.
7500 o Minor features (other):
7501 - Add hidden services and DNSPorts to the list of things that make
7502 Tor accept that it has running ports. Change starting Tor with no
7503 ports from a fatal error to a warning; we might change it back if
7504 this turns out to confuse anybody. Fixes bug 579.
7507 Changes in version 0.1.2.19 - 2008-01-17
7508 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7509 exit policy a little bit more conservative so it's safer to run an
7510 exit relay on a home system, and fixes a variety of smaller issues.
7513 - Exit policies now reject connections that are addressed to a
7514 relay's public (external) IP address too, unless
7515 ExitPolicyRejectPrivate is turned off. We do this because too
7516 many relays are running nearby to services that trust them based
7520 - When the clock jumps forward a lot, do not allow the bandwidth
7521 buckets to become negative. Fixes bug 544.
7522 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7523 on every successful resolve. Reported by Mike Perry.
7524 - Purge old entries from the "rephist" database and the hidden
7525 service descriptor database even when DirPort is zero.
7526 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7527 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7528 crashing or mis-answering these requests.
7529 - When we decide to send a 503 response to a request for servers, do
7530 not then also send the server descriptors: this defeats the whole
7531 purpose. Fixes bug 539.
7534 - Changing the ExitPolicyRejectPrivate setting should cause us to
7535 rebuild our server descriptor.
7536 - Fix handling of hex nicknames when answering controller requests for
7537 networkstatus by name, or when deciding whether to warn about
7538 unknown routers in a config option. (Patch from mwenge.)
7539 - Fix a couple of hard-to-trigger autoconf problems that could result
7540 in really weird results on platforms whose sys/types.h files define
7541 nonstandard integer types.
7542 - Don't try to create the datadir when running --verify-config or
7543 --hash-password. Resolves bug 540.
7544 - If we were having problems getting a particular descriptor from the
7545 directory caches, and then we learned about a new descriptor for
7546 that router, we weren't resetting our failure count. Reported
7548 - Although we fixed bug 539 (where servers would send HTTP status 503
7549 responses _and_ send a body too), there are still servers out there
7550 that haven't upgraded. Therefore, make clients parse such bodies
7551 when they receive them.
7552 - Run correctly on systems where rlim_t is larger than unsigned long.
7553 This includes some 64-bit systems.
7554 - Run correctly on platforms (like some versions of OS X 10.5) where
7555 the real limit for number of open files is OPEN_FILES, not rlim_max
7556 from getrlimit(RLIMIT_NOFILES).
7557 - Avoid a spurious free on base64 failure.
7558 - Avoid segfaults on certain complex invocations of
7559 router_get_by_hexdigest().
7560 - Fix rare bug on REDIRECTSTREAM control command when called with no
7561 port set: it could erroneously report an error when none had
7565 Changes in version 0.2.0.15-alpha - 2007-12-25
7566 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7567 features added in 0.2.0.13-alpha.
7570 - Fix several remotely triggerable asserts based on DirPort requests
7571 for a v2 or v3 networkstatus object before we were prepared. This
7572 was particularly bad for 0.2.0.13 and later bridge relays, who
7573 would never have a v2 networkstatus and would thus always crash
7574 when used. Bugfixes on 0.2.0.x.
7575 - Estimate the v3 networkstatus size more accurately, rather than
7576 estimating it at zero bytes and giving it artificially high priority
7577 compared to other directory requests. Bugfix on 0.2.0.x.
7580 - Fix configure.in logic for cross-compilation.
7581 - When we load a bridge descriptor from the cache, and it was
7582 previously unreachable, mark it as retriable so we won't just
7583 ignore it. Also, try fetching a new copy immediately. Bugfixes
7585 - The bridge GeoIP stats were counting other relays, for example
7586 self-reachability and authority-reachability tests.
7589 - Support compilation to target iPhone; patch from cjacker huang.
7590 To build for iPhone, pass the --enable-iphone option to configure.
7593 Changes in version 0.2.0.14-alpha - 2007-12-23
7595 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7596 without a datadirectory from a previous Tor install. Reported
7598 - Fix a crash when we fetch a descriptor that turns out to be
7599 unexpected (it used to be in our networkstatus when we started
7600 fetching it, but it isn't in our current networkstatus), and we
7601 aren't using bridges. Bugfix on 0.2.0.x.
7602 - Fix a crash when accessing hidden services: it would work the first
7603 time you use a given introduction point for your service, but
7604 on subsequent requests we'd be using garbage memory. Fixed by
7605 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7606 - Fix a crash when we load a bridge descriptor from disk but we don't
7607 currently have a Bridge line for it in our torrc. Bugfix on
7611 - If bridge authorities set BridgePassword, they will serve a
7612 snapshot of known bridge routerstatuses from their DirPort to
7613 anybody who knows that password. Unset by default.
7616 - Make the unit tests build again.
7617 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7618 - Make PublishServerDescriptor default to 1, so the default doesn't
7619 have to change as we invent new directory protocol versions.
7620 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7621 be included unless sys/time.h is already included. Fixes
7622 bug 553. Bugfix on 0.2.0.x.
7623 - If we receive a general-purpose descriptor and then receive an
7624 identical bridge-purpose descriptor soon after, don't discard
7625 the next one as a duplicate.
7628 - If BridgeRelay is set to 1, then the default for
7629 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7630 - If the user sets RelayBandwidthRate but doesn't set
7631 RelayBandwidthBurst, then make them equal rather than erroring out.
7634 Changes in version 0.2.0.13-alpha - 2007-12-21
7635 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7636 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7639 o New directory authorities:
7640 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7644 - Only update guard status (usable / not usable) once we have
7645 enough directory information. This was causing us to always pick
7646 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7647 causing us to discard all our guards on startup if we hadn't been
7648 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7649 - Purge old entries from the "rephist" database and the hidden
7650 service descriptor databases even when DirPort is zero. Bugfix
7652 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7653 after opening a circuit -- even a relayed circuit. Bugfix on
7655 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7656 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7657 crashing or mis-answering these types of requests.
7658 - Relays were publishing their server descriptor to v1 and v2
7659 directory authorities, but they didn't try publishing to v3-only
7660 authorities. Fix this; and also stop publishing to v1 authorities.
7662 - When we were reading router descriptors from cache, we were ignoring
7663 the annotations -- so for example we were reading in bridge-purpose
7664 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7665 - When we decided to send a 503 response to a request for servers, we
7666 were then also sending the server descriptors: this defeats the
7667 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7670 - Bridge relays now behave like clients with respect to time
7671 intervals for downloading new consensus documents -- otherwise they
7672 stand out. Bridge users now wait until the end of the interval,
7673 so their bridge relay will be sure to have a new consensus document.
7674 - Three new config options (AlternateDirAuthority,
7675 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7676 user selectively replace the default directory authorities by type,
7677 rather than the all-or-nothing replacement that DirServer offers.
7678 - Tor can now be configured to read a GeoIP file from disk in one
7679 of two formats. This can be used by controllers to map IP addresses
7680 to countries. Eventually, it may support exit-by-country.
7681 - When possible, bridge relays remember which countries users
7682 are coming from, and report aggregate information in their
7683 extra-info documents, so that the bridge authorities can learn
7684 where Tor is blocked.
7685 - Bridge directory authorities now do reachability testing on the
7686 bridges they know. They provide router status summaries to the
7687 controller via "getinfo ns/purpose/bridge", and also dump summaries
7688 to a file periodically.
7689 - Stop fetching directory info so aggressively if your DirPort is
7690 on but your ORPort is off; stop fetching v2 dir info entirely.
7691 You can override these choices with the new FetchDirInfoEarly
7695 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7696 consensus documents when there are too many relays at a single
7697 IP address. Now clear it in v2 network status documents too, and
7698 also clear it in routerinfo_t when the relay is no longer listed
7699 in the relevant networkstatus document.
7700 - Don't crash if we get an unexpected value for the
7701 PublishServerDescriptor config option. Reported by Matt Edman;
7702 bugfix on 0.2.0.9-alpha.
7703 - Our new v2 hidden service descriptor format allows descriptors
7704 that have no introduction points. But Tor crashed when we tried
7705 to build a descriptor with no intro points (and it would have
7706 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7708 - Fix building with dmalloc 5.5.2 with glibc.
7709 - Reject uploaded descriptors and extrainfo documents if they're
7710 huge. Otherwise we'll cache them all over the network and it'll
7711 clog everything up. Reported by Aljosha Judmayer.
7712 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7713 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7714 - When the DANGEROUS_VERSION controller status event told us we're
7715 running an obsolete version, it used the string "OLD" to describe
7716 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7717 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7718 - If we can't expand our list of entry guards (e.g. because we're
7719 using bridges or we have StrictEntryNodes set), don't mark relays
7720 down when they fail a directory request. Otherwise we're too quick
7721 to mark all our entry points down. Bugfix on 0.1.2.x.
7722 - Fix handling of hex nicknames when answering controller requests for
7723 networkstatus by name, or when deciding whether to warn about unknown
7724 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
7725 - Fix a couple of hard-to-trigger autoconf problems that could result
7726 in really weird results on platforms whose sys/types.h files define
7727 nonstandard integer types. Bugfix on 0.1.2.x.
7728 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
7729 - Don't crash on name lookup when we have no current consensus. Fixes
7730 bug 538; bugfix on 0.2.0.x.
7731 - Only Tors that want to mirror the v2 directory info should
7732 create the "cached-status" directory in their datadir. (All Tors
7733 used to create it.) Bugfix on 0.2.0.9-alpha.
7734 - Directory authorities should only automatically download Extra Info
7735 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
7738 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7739 consumers. (We already do this on HUP.)
7740 - Authorities and caches fetch the v2 networkstatus documents
7741 less often, now that v3 is encouraged.
7742 - Add a new config option BridgeRelay that specifies you want to
7743 be a bridge relay. Right now the only difference is that it makes
7744 you answer begin_dir requests, and it makes you cache dir info,
7745 even if your DirPort isn't on.
7746 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7747 ask about source, timestamp of arrival, purpose, etc. We need
7748 something like this to help Vidalia not do GeoIP lookups on bridge
7750 - Allow multiple HashedControlPassword config lines, to support
7751 multiple controller passwords.
7752 - Authorities now decide whether they're authoritative for a given
7753 router based on the router's purpose.
7754 - New config options AuthDirBadDir and AuthDirListBadDirs for
7755 authorities to mark certain relays as "bad directories" in the
7756 networkstatus documents. Also supports the "!baddir" directive in
7757 the approved-routers file.
7760 Changes in version 0.2.0.12-alpha - 2007-11-16
7761 This twelfth development snapshot fixes some more build problems as
7762 well as a few minor bugs.
7765 - Make it build on OpenBSD again. Patch from tup.
7766 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
7767 package-building for Red Hat, OS X, etc.
7769 o Minor bugfixes (on 0.1.2.x):
7770 - Changing the ExitPolicyRejectPrivate setting should cause us to
7771 rebuild our server descriptor.
7773 o Minor bugfixes (on 0.2.0.x):
7774 - When we're lacking a consensus, don't try to perform rendezvous
7775 operations. Reported by Karsten Loesing.
7776 - Fix a small memory leak whenever we decide against using a
7777 newly picked entry guard. Reported by Mike Perry.
7778 - When authorities detected more than two relays running on the same
7779 IP address, they were clearing all the status flags but forgetting
7780 to clear the "hsdir" flag. So clients were being told that a
7781 given relay was the right choice for a v2 hsdir lookup, yet they
7782 never had its descriptor because it was marked as 'not running'
7784 - If we're trying to fetch a bridge descriptor and there's no way
7785 the bridge authority could help us (for example, we don't know
7786 a digest, or there is no bridge authority), don't be so eager to
7787 fall back to asking the bridge authority.
7788 - If we're using bridges or have strictentrynodes set, and our
7789 chosen exit is in the same family as all our bridges/entry guards,
7790 then be flexible about families.
7793 - When we negotiate a v2 link-layer connection (not yet implemented),
7794 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7795 negotiated a v1 connection for their next step. Initial code for
7799 Changes in version 0.2.0.11-alpha - 2007-11-12
7800 This eleventh development snapshot fixes some build problems with
7801 the previous snapshot. It also includes a more secure-by-default exit
7802 policy for relays, fixes an enormous memory leak for exit relays, and
7803 fixes another bug where servers were falling out of the directory list.
7806 - Exit policies now reject connections that are addressed to a
7807 relay's public (external) IP address too, unless
7808 ExitPolicyRejectPrivate is turned off. We do this because too
7809 many relays are running nearby to services that trust them based
7810 on network address. Bugfix on 0.1.2.x.
7813 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7814 on every successful resolve. Reported by Mike Perry; bugfix
7816 - On authorities, never downgrade to old router descriptors simply
7817 because they're listed in the consensus. This created a catch-22
7818 where we wouldn't list a new descriptor because there was an
7819 old one in the consensus, and we couldn't get the new one in the
7820 consensus because we wouldn't list it. Possible fix for bug 548.
7821 Also, this might cause bug 543 to appear on authorities; if so,
7822 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
7824 o Packaging fixes on 0.2.0.10-alpha:
7825 - We were including instructions about what to do with the
7826 src/config/fallback-consensus file, but we weren't actually
7827 including it in the tarball. Disable all of that for now.
7830 - Allow people to say PreferTunnelledDirConns rather than
7831 PreferTunneledDirConns, for those alternate-spellers out there.
7834 - Don't reevaluate all the information from our consensus document
7835 just because we've downloaded a v2 networkstatus that we intend
7836 to cache. Fixes bug 545; bugfix on 0.2.0.x.
7839 Changes in version 0.2.0.10-alpha - 2007-11-10
7840 This tenth development snapshot adds a third v3 directory authority
7841 run by Mike Perry, adds most of Karsten Loesing's new hidden service
7842 descriptor format, fixes a bad crash bug and new bridge bugs introduced
7843 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
7844 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
7845 addresses many more minor issues.
7847 o New directory authorities:
7848 - Set up ides (run by Mike Perry) as the third v3 directory authority.
7851 - Allow tunnelled directory connections to ask for an encrypted
7852 "begin_dir" connection or an anonymized "uses a full Tor circuit"
7853 connection independently. Now we can make anonymized begin_dir
7854 connections for (e.g.) more secure hidden service posting and
7856 - More progress on proposal 114: code from Karsten Loesing to
7857 implement new hidden service descriptor format.
7858 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
7859 accommodate the growing number of servers that use the default
7860 and are reaching it.
7861 - Directory authorities use a new formula for selecting which nodes
7862 to advertise as Guards: they must be in the top 7/8 in terms of
7863 how long we have known about them, and above the median of those
7864 nodes in terms of weighted fractional uptime.
7865 - Make "not enough dir info yet" warnings describe *why* Tor feels
7866 it doesn't have enough directory info yet.
7869 - Stop servers from crashing if they set a Family option (or
7870 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
7872 - Make bridge users work again -- the move to v3 directories in
7873 0.2.0.9-alpha had introduced a number of bugs that made bridges
7874 no longer work for clients.
7875 - When the clock jumps forward a lot, do not allow the bandwidth
7876 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
7878 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
7879 - When the consensus lists a router descriptor that we previously were
7880 mirroring, but that we considered non-canonical, reload the
7881 descriptor as canonical. This fixes bug 543 where Tor servers
7882 would start complaining after a few days that they don't have
7883 enough directory information to build a circuit.
7884 - Consider replacing the current consensus when certificates arrive
7885 that make the pending consensus valid. Previously, we were only
7886 considering replacement when the new certs _didn't_ help.
7887 - Fix an assert error on startup if we didn't already have the
7888 consensus and certs cached in our datadirectory: we were caching
7889 the consensus in consensus_waiting_for_certs but then free'ing it
7891 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
7892 Request) if we need more v3 certs but we've already got pending
7893 requests for all of them.
7894 - Correctly back off from failing certificate downloads. Fixes
7896 - Authorities don't vote on the Running flag if they have been running
7897 for less than 30 minutes themselves. Fixes bug 547, where a newly
7898 started authority would vote that everyone was down.
7901 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7902 it, it had no AES, and it hasn't seen any security patches since
7906 - Clients now hold circuitless TLS connections open for 1.5 times
7907 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
7908 rebuild a new circuit over them within that timeframe. Previously,
7909 they held them open only for KeepalivePeriod (5 minutes).
7910 - Use "If-Modified-Since" to avoid retrieving consensus
7911 networkstatuses that we already have.
7912 - When we have no consensus, check FallbackNetworkstatusFile (defaults
7913 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
7914 we start knowing some directory caches.
7915 - When we receive a consensus from the future, warn about skew.
7916 - Improve skew reporting: try to give the user a better log message
7917 about how skewed they are, and how much this matters.
7918 - When we have a certificate for an authority, believe that
7919 certificate's claims about the authority's IP address.
7920 - New --quiet command-line option to suppress the default console log.
7921 Good in combination with --hash-password.
7922 - Authorities send back an X-Descriptor-Not-New header in response to
7923 an accepted-but-discarded descriptor upload. Partially implements
7925 - Make the log message for "tls error. breaking." more useful.
7926 - Better log messages about certificate downloads, to attempt to
7927 track down the second incarnation of bug 546.
7929 o Minor features (bridges):
7930 - If bridge users set UpdateBridgesFromAuthority, but the digest
7931 they ask for is a 404 from the bridge authority, they now fall
7932 back to trying the bridge directly.
7933 - Bridges now use begin_dir to publish their server descriptor to
7934 the bridge authority, even when they haven't set TunnelDirConns.
7936 o Minor features (controller):
7937 - When reporting clock skew, and we know that the clock is _at least
7938 as skewed_ as some value, but we don't know the actual value,
7939 report the value as a "minimum skew."
7942 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7943 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7947 - Refuse to start if both ORPort and UseBridges are set. Bugfix
7948 on 0.2.0.x, suggested by Matt Edman.
7949 - Don't stop fetching descriptors when FetchUselessDescriptors is
7950 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
7951 reported by tup and ioerror.
7952 - Better log message on vote from unknown authority.
7953 - Don't log "Launching 0 request for 0 router" message.
7955 o Minor bugfixes (memory leaks):
7956 - Stop leaking memory every time we parse a v3 certificate. Bugfix
7958 - Stop leaking memory every time we load a v3 certificate. Bugfix
7959 on 0.2.0.1-alpha. Fixes bug 536.
7960 - Stop leaking a cached networkstatus on exit. Bugfix on
7962 - Stop leaking voter information every time we free a consensus.
7963 Bugfix on 0.2.0.3-alpha.
7964 - Stop leaking signed data every time we check a voter signature.
7965 Bugfix on 0.2.0.3-alpha.
7966 - Stop leaking a signature every time we fail to parse a consensus or
7967 a vote. Bugfix on 0.2.0.3-alpha.
7968 - Stop leaking v2_download_status_map on shutdown. Bugfix on
7970 - Stop leaking conn->nickname every time we make a connection to a
7971 Tor relay without knowing its expected identity digest (e.g. when
7972 using bridges). Bugfix on 0.2.0.3-alpha.
7974 - Minor bugfixes (portability):
7975 - Run correctly on platforms where rlim_t is larger than unsigned
7976 long, and/or where the real limit for number of open files is
7977 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
7978 particular, these may be needed for OS X 10.5.
7981 Changes in version 0.1.2.18 - 2007-10-28
7982 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7983 hidden service introduction that were causing huge delays, and a big
7984 bug that was causing some servers to disappear from the network status
7985 lists for a few hours each day.
7987 o Major bugfixes (crashes):
7988 - If a connection is shut down abruptly because of something that
7989 happened inside connection_flushed_some(), do not call
7990 connection_finished_flushing(). Should fix bug 451:
7991 "connection_stop_writing: Assertion conn->write_event failed"
7992 Bugfix on 0.1.2.7-alpha.
7993 - Fix possible segfaults in functions called from
7994 rend_process_relay_cell().
7996 o Major bugfixes (hidden services):
7997 - Hidden services were choosing introduction points uniquely by
7998 hexdigest, but when constructing the hidden service descriptor
7999 they merely wrote the (potentially ambiguous) nickname.
8000 - Clients now use the v2 intro format for hidden service
8001 connections: they specify their chosen rendezvous point by identity
8002 digest rather than by (potentially ambiguous) nickname. These
8003 changes could speed up hidden service connections dramatically.
8005 o Major bugfixes (other):
8006 - Stop publishing a new server descriptor just because we get a
8007 HUP signal. This led (in a roundabout way) to some servers getting
8008 dropped from the networkstatus lists for a few hours each day.
8009 - When looking for a circuit to cannibalize, consider family as well
8010 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8011 circuit cannibalization).
8012 - When a router wasn't listed in a new networkstatus, we were leaving
8013 the flags for that router alone -- meaning it remained Named,
8014 Running, etc -- even though absence from the networkstatus means
8015 that it shouldn't be considered to exist at all anymore. Now we
8016 clear all the flags for routers that fall out of the networkstatus
8017 consensus. Fixes bug 529.
8020 - Don't try to access (or alter) the state file when running
8021 --list-fingerprint or --verify-config or --hash-password. Resolves
8023 - When generating information telling us how to extend to a given
8024 router, do not try to include the nickname if it is
8025 absent. Resolves bug 467.
8026 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8027 a way to trigger this remotely.)
8028 - When sending a status event to the controller telling it that an
8029 OR address is reachable, set the port correctly. (Previously we
8030 were reporting the dir port.)
8031 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8032 command. Bugfix on 0.1.2.17.
8033 - When loading bandwidth history, do not believe any information in
8034 the future. Fixes bug 434.
8035 - When loading entry guard information, do not believe any information
8037 - When we have our clock set far in the future and generate an
8038 onion key, then re-set our clock to be correct, we should not stop
8039 the onion key from getting rotated.
8040 - On some platforms, accept() can return a broken address. Detect
8041 this more quietly, and deal accordingly. Fixes bug 483.
8042 - It's not actually an error to find a non-pending entry in the DNS
8043 cache when canceling a pending resolve. Don't log unless stuff
8044 is fishy. Resolves bug 463.
8045 - Don't reset trusted dir server list when we set a configuration
8046 option. Patch from Robert Hogan.
8047 - Don't try to create the datadir when running --verify-config or
8048 --hash-password. Resolves bug 540.
8051 Changes in version 0.2.0.9-alpha - 2007-10-24
8052 This ninth development snapshot switches clients to the new v3 directory
8053 system; allows servers to be listed in the network status even when they
8054 have the same nickname as a registered server; and fixes many other
8055 bugs including a big one that was causing some servers to disappear
8056 from the network status lists for a few hours each day.
8058 o Major features (directory system):
8059 - Clients now download v3 consensus networkstatus documents instead
8060 of v2 networkstatus documents. Clients and caches now base their
8061 opinions about routers on these consensus documents. Clients only
8062 download router descriptors listed in the consensus.
8063 - Authorities now list servers who have the same nickname as
8064 a different named server, but list them with a new flag,
8065 "Unnamed". Now we can list servers that happen to pick the same
8066 nickname as a server that registered two years ago and then
8067 disappeared. Partially implements proposal 122.
8068 - If the consensus lists a router as "Unnamed", the name is assigned
8069 to a different router: do not identify the router by that name.
8070 Partially implements proposal 122.
8071 - Authorities can now come to a consensus on which method to use to
8072 compute the consensus. This gives us forward compatibility.
8075 - Stop publishing a new server descriptor just because we HUP or
8076 when we find our DirPort to be reachable but won't actually publish
8077 it. New descriptors without any real changes are dropped by the
8078 authorities, and can screw up our "publish every 18 hours" schedule.
8080 - When a router wasn't listed in a new networkstatus, we were leaving
8081 the flags for that router alone -- meaning it remained Named,
8082 Running, etc -- even though absence from the networkstatus means
8083 that it shouldn't be considered to exist at all anymore. Now we
8084 clear all the flags for routers that fall out of the networkstatus
8085 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8086 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8087 extrainfo documents and then discard them immediately for not
8088 matching the latest router. Bugfix on 0.2.0.1-alpha.
8090 o Minor features (v3 directory protocol):
8091 - Allow tor-gencert to generate a new certificate without replacing
8093 - Allow certificates to include an address.
8094 - When we change our directory-cache settings, reschedule all voting
8095 and download operations.
8096 - Reattempt certificate downloads immediately on failure, as long as
8097 we haven't failed a threshold number of times yet.
8098 - Delay retrying consensus downloads while we're downloading
8099 certificates to verify the one we just got. Also, count getting a
8100 consensus that we already have (or one that isn't valid) as a failure,
8101 and count failing to get the certificates after 20 minutes as a
8103 - Build circuits and download descriptors even if our consensus is a
8104 little expired. (This feature will go away once authorities are
8107 o Minor features (router descriptor cache):
8108 - If we find a cached-routers file that's been sitting around for more
8109 than 28 days unmodified, then most likely it's a leftover from
8110 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8112 - When we (as a cache) download a descriptor because it was listed
8113 in a consensus, remember when the consensus was supposed to expire,
8114 and don't expire the descriptor until then.
8116 o Minor features (performance):
8117 - Call routerlist_remove_old_routers() much less often. This should
8118 speed startup, especially on directory caches.
8119 - Don't try to launch new descriptor downloads quite so often when we
8120 already have enough directory information to build circuits.
8121 - Base64 decoding was actually showing up on our profile when parsing
8122 the initial descriptor file; switch to an in-process all-at-once
8123 implementation that's about 3.5x times faster than calling out to
8126 o Minor features (compilation):
8127 - Detect non-ASCII platforms (if any still exist) and refuse to
8128 build there: some of our code assumes that 'A' is 65 and so on.
8130 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8131 - Make the "next period" votes into "current period" votes immediately
8132 after publishing the consensus; avoid a heisenbug that made them
8133 stick around indefinitely.
8134 - When we discard a vote as a duplicate, do not report this as
8136 - Treat missing v3 keys or certificates as an error when running as a
8137 v3 directory authority.
8138 - When we're configured to be a v3 authority, but we're only listed
8139 as a non-v3 authority in our DirServer line for ourself, correct
8141 - If an authority doesn't have a qualified hostname, just put
8142 its address in the vote. This fixes the problem where we referred to
8143 "moria on moria:9031."
8144 - Distinguish between detached signatures for the wrong period, and
8145 detached signatures for a divergent vote.
8146 - Fix a small memory leak when computing a consensus.
8147 - When there's no concensus, we were forming a vote every 30
8148 minutes, but writing the "valid-after" line in our vote based
8149 on our configured V3AuthVotingInterval: so unless the intervals
8150 matched up, we immediately rejected our own vote because it didn't
8151 start at the voting interval that caused us to construct a vote.
8153 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8154 - Delete unverified-consensus when the real consensus is set.
8155 - Consider retrying a consensus networkstatus fetch immediately
8156 after one fails: don't wait 60 seconds to notice.
8157 - When fetching a consensus as a cache, wait until a newer consensus
8158 should exist before trying to replace the current one.
8159 - Use a more forgiving schedule for retrying failed consensus
8160 downloads than for other types.
8162 o Minor bugfixes (other directory issues):
8163 - Correct the implementation of "download votes by digest." Bugfix on
8165 - Authorities no longer send back "400 you're unreachable please fix
8166 it" errors to Tor servers that aren't online all the time. We're
8167 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8169 o Minor bugfixes (controller):
8170 - Don't reset trusted dir server list when we set a configuration
8171 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8172 - Respond to INT and TERM SIGNAL commands before we execute the
8173 signal, in case the signal shuts us down. We had a patch in
8174 0.1.2.1-alpha that tried to do this by queueing the response on
8175 the connection's buffer before shutting down, but that really
8176 isn't the same thing at all. Bug located by Matt Edman.
8178 o Minor bugfixes (misc):
8179 - Correctly check for bad options to the "PublishServerDescriptor"
8180 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8181 - Stop leaking memory on failing case of base32_decode, and make
8182 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8183 - Don't try to download extrainfo documents when we're trying to
8184 fetch enough directory info to build a circuit: having enough
8185 info should get priority. Bugfix on 0.2.0.x.
8186 - Don't complain that "your server has not managed to confirm that its
8187 ports are reachable" if we haven't been able to build any circuits
8188 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8190 - Detect the reason for failing to mmap a descriptor file we just
8191 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8194 o Code simplifications and refactoring:
8195 - Remove support for the old bw_accounting file: we've been storing
8196 bandwidth accounting information in the state file since
8197 0.1.2.5-alpha. This may result in bandwidth accounting errors
8198 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8199 downgrade to 0.1.1.x or earlier.
8200 - New convenience code to locate a file within the DataDirectory.
8201 - Move non-authority functionality out of dirvote.c.
8202 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8203 so that they all take the same named flags.
8206 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8207 Unix users an easy way to script their Tor process (e.g. by
8208 adjusting bandwidth based on the time of the day).
8211 Changes in version 0.2.0.8-alpha - 2007-10-12
8212 This eighth development snapshot fixes a crash bug that's been bothering
8213 us since February 2007, lets bridge authorities store a list of bridge
8214 descriptors they've seen, gets v3 directory voting closer to working,
8215 starts caching v3 directory consensus documents on directory mirrors,
8216 and fixes a variety of smaller issues including some minor memory leaks.
8218 o Major features (router descriptor cache):
8219 - Store routers in a file called cached-descriptors instead of in
8220 cached-routers. Initialize cached-descriptors from cached-routers
8221 if the old format is around. The new format allows us to store
8222 annotations along with descriptors.
8223 - Use annotations to record the time we received each descriptor, its
8224 source, and its purpose.
8225 - Disable the SETROUTERPURPOSE controller command: it is now
8227 - Controllers should now specify cache=no or cache=yes when using
8228 the +POSTDESCRIPTOR command.
8229 - Bridge authorities now write bridge descriptors to disk, meaning
8230 we can export them to other programs and begin distributing them
8233 o Major features (directory authorities):
8234 - When a v3 authority is missing votes or signatures, it now tries
8236 - Directory authorities track weighted fractional uptime as well as
8237 weighted mean-time-between failures. WFU is suitable for deciding
8238 whether a node is "usually up", while MTBF is suitable for deciding
8239 whether a node is "likely to stay up." We need both, because
8240 "usually up" is a good requirement for guards, while "likely to
8241 stay up" is a good requirement for long-lived connections.
8243 o Major features (v3 directory system):
8244 - Caches now download v3 network status documents as needed,
8245 and download the descriptors listed in them.
8246 - All hosts now attempt to download and keep fresh v3 authority
8247 certificates, and re-attempt after failures.
8248 - More internal-consistency checks for vote parsing.
8250 o Major bugfixes (crashes):
8251 - If a connection is shut down abruptly because of something that
8252 happened inside connection_flushed_some(), do not call
8253 connection_finished_flushing(). Should fix bug 451. Bugfix on
8256 o Major bugfixes (performance):
8257 - Fix really bad O(n^2) performance when parsing a long list of
8258 routers: Instead of searching the entire list for an "extra-info "
8259 string which usually wasn't there, once for every routerinfo
8260 we read, just scan lines forward until we find one we like.
8262 - When we add data to a write buffer in response to the data on that
8263 write buffer getting low because of a flush, do not consider the
8264 newly added data as a candidate for immediate flushing, but rather
8265 make it wait until the next round of writing. Otherwise, we flush
8266 and refill recursively, and a single greedy TLS connection can
8267 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8269 o Minor features (v3 authority system):
8270 - Add more ways for tools to download the votes that lead to the
8272 - Send a 503 when low on bandwidth and a vote, consensus, or
8273 certificate is requested.
8274 - If-modified-since is now implemented properly for all kinds of
8275 certificate requests.
8277 o Minor bugfixes (network statuses):
8278 - Tweak the implementation of proposal 109 slightly: allow at most
8279 two Tor servers on the same IP address, except if it's the location
8280 of a directory authority, in which case allow five. Bugfix on
8283 o Minor bugfixes (controller):
8284 - When sending a status event to the controller telling it that an
8285 OR address is reachable, set the port correctly. (Previously we
8286 were reporting the dir port.) Bugfix on 0.1.2.x.
8288 o Minor bugfixes (v3 directory system):
8289 - Fix logic to look up a cert by its signing key digest. Bugfix on
8291 - Only change the reply to a vote to "OK" if it's not already
8292 set. This gets rid of annoying "400 OK" log messages, which may
8293 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8294 - When we get a valid consensus, recompute the voting schedule.
8295 - Base the valid-after time of a vote on the consensus voting
8296 schedule, not on our preferred schedule.
8297 - Make the return values and messages from signature uploads and
8298 downloads more sensible.
8299 - Fix a memory leak when serving votes and consensus documents, and
8300 another when serving certificates.
8302 o Minor bugfixes (performance):
8303 - Use a slightly simpler string hashing algorithm (copying Python's
8304 instead of Java's) and optimize our digest hashing algorithm to take
8305 advantage of 64-bit platforms and to remove some possibly-costly
8307 - Fix a minor memory leak whenever we parse guards from our state
8308 file. Bugfix on 0.2.0.7-alpha.
8309 - Fix a minor memory leak whenever we write out a file. Bugfix on
8311 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8312 command. Bugfix on 0.2.0.5-alpha.
8314 o Minor bugfixes (portability):
8315 - On some platforms, accept() can return a broken address. Detect
8316 this more quietly, and deal accordingly. Fixes bug 483.
8317 - Stop calling tor_strlower() on uninitialized memory in some cases.
8318 Bugfix in 0.2.0.7-alpha.
8320 o Minor bugfixes (usability):
8321 - Treat some 403 responses from directory servers as INFO rather than
8322 WARN-severity events.
8323 - It's not actually an error to find a non-pending entry in the DNS
8324 cache when canceling a pending resolve. Don't log unless stuff is
8325 fishy. Resolves bug 463.
8327 o Minor bugfixes (anonymity):
8328 - Never report that we've used more bandwidth than we're willing to
8329 relay: it leaks how much non-relay traffic we're using. Resolves
8331 - When looking for a circuit to cannibalize, consider family as well
8332 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8333 circuit cannibalization).
8335 o Code simplifications and refactoring:
8336 - Make a bunch of functions static. Remove some dead code.
8337 - Pull out about a third of the really big routerlist.c; put it in a
8338 new module, networkstatus.c.
8339 - Merge the extra fields in local_routerstatus_t back into
8340 routerstatus_t: we used to need one routerstatus_t for each
8341 authority's opinion, plus a local_routerstatus_t for the locally
8342 computed consensus opinion. To save space, we put the locally
8343 modified fields into local_routerstatus_t, and only the common
8344 stuff into routerstatus_t. But once v3 directories are in use,
8345 clients and caches will no longer need to hold authority opinions;
8346 thus, the rationale for keeping the types separate is now gone.
8347 - Make the code used to reschedule and reattempt downloads more
8349 - Turn all 'Are we a directory server/mirror?' logic into a call to
8351 - Remove the code to generate the oldest (v1) directory format.
8352 The code has been disabled since 0.2.0.5-alpha.
8355 Changes in version 0.2.0.7-alpha - 2007-09-21
8356 This seventh development snapshot makes bridges work again, makes bridge
8357 authorities work for the first time, fixes two huge performance flaws
8358 in hidden services, and fixes a variety of minor issues.
8360 o New directory authorities:
8361 - Set up moria1 and tor26 as the first v3 directory authorities. See
8362 doc/spec/dir-spec.txt for details on the new directory design.
8364 o Major bugfixes (crashes):
8365 - Fix possible segfaults in functions called from
8366 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8368 o Major bugfixes (bridges):
8369 - Fix a bug that made servers send a "404 Not found" in response to
8370 attempts to fetch their server descriptor. This caused Tor servers
8371 to take many minutes to establish reachability for their DirPort,
8372 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8373 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8374 users configure that and specify a bridge with an identity
8375 fingerprint, now they will lookup the bridge descriptor at the
8376 default bridge authority via a one-hop tunnel, but once circuits
8377 are established they will switch to a three-hop tunnel for later
8378 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8380 o Major bugfixes (hidden services):
8381 - Hidden services were choosing introduction points uniquely by
8382 hexdigest, but when constructing the hidden service descriptor
8383 they merely wrote the (potentially ambiguous) nickname.
8384 - Clients now use the v2 intro format for hidden service
8385 connections: they specify their chosen rendezvous point by identity
8386 digest rather than by (potentially ambiguous) nickname. Both
8387 are bugfixes on 0.1.2.x, and they could speed up hidden service
8388 connections dramatically. Thanks to Karsten Loesing.
8390 o Minor features (security):
8391 - As a client, do not believe any server that tells us that an
8392 address maps to an internal address space.
8393 - Make it possible to enable HashedControlPassword and
8394 CookieAuthentication at the same time.
8396 o Minor features (guard nodes):
8397 - Tag every guard node in our state file with the version that
8398 we believe added it, or with our own version if we add it. This way,
8399 if a user temporarily runs an old version of Tor and then switches
8400 back to a new one, she doesn't automatically lose her guards.
8402 o Minor features (speed):
8403 - When implementing AES counter mode, update only the portions of the
8404 counter buffer that need to change, and don't keep separate
8405 network-order and host-order counters when they are the same (i.e.,
8406 on big-endian hosts.)
8408 o Minor features (controller):
8409 - Accept LF instead of CRLF on controller, since some software has a
8410 hard time generating real Internet newlines.
8411 - Add GETINFO values for the server status events
8412 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8416 - Routers no longer include bandwidth-history lines in their
8417 descriptors; this information is already available in extra-info
8418 documents, and including it in router descriptors took up 60%
8419 (!) of compressed router descriptor downloads. Completes
8420 implementation of proposal 104.
8421 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8422 and TorControl.py, as they use the old v0 controller protocol,
8423 and are obsoleted by TorFlow anyway.
8424 - Drop support for v1 rendezvous descriptors, since we never used
8425 them anyway, and the code has probably rotted by now. Based on
8426 patch from Karsten Loesing.
8427 - On OSX, stop warning the user that kqueue support in libevent is
8428 "experimental", since it seems to have worked fine for ages.
8431 - When generating information telling us how to extend to a given
8432 router, do not try to include the nickname if it is absent. Fixes
8433 bug 467. Bugfix on 0.2.0.3-alpha.
8434 - Fix a user-triggerable (but not remotely-triggerable) segfault
8435 in expand_filename(). Bugfix on 0.1.2.x.
8436 - Fix a memory leak when freeing incomplete requests from DNSPort.
8437 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
8438 - Don't try to access (or alter) the state file when running
8439 --list-fingerprint or --verify-config or --hash-password. (Resolves
8440 bug 499.) Bugfix on 0.1.2.x.
8441 - Servers used to decline to publish their DirPort if their
8442 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
8443 were below a threshold. Now they only look at BandwidthRate and
8444 RelayBandwidthRate. Bugfix on 0.1.2.x.
8445 - Remove an optimization in the AES counter-mode code that assumed
8446 that the counter never exceeded 2^68. When the counter can be set
8447 arbitrarily as an IV (as it is by Karsten's new hidden services
8448 code), this assumption no longer holds. Bugfix on 0.1.2.x.
8449 - Resume listing "AUTHORITY" flag for authorities in network status.
8450 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
8452 o Code simplifications and refactoring:
8453 - Revamp file-writing logic so we don't need to have the entire
8454 contents of a file in memory at once before we write to disk. Tor,
8456 - Turn "descriptor store" into a full-fledged type.
8457 - Move all NT services code into a separate source file.
8458 - Unify all code that computes medians, percentile elements, etc.
8459 - Get rid of a needless malloc when parsing address policies.
8462 Changes in version 0.1.2.17 - 2007-08-30
8463 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8464 X bundles. Vidalia 0.0.14 makes authentication required for the
8465 ControlPort in the default configuration, which addresses important
8466 security risks. Everybody who uses Vidalia (or another controller)
8469 In addition, this Tor update fixes major load balancing problems with
8470 path selection, which should speed things up a lot once many people
8473 o Major bugfixes (security):
8474 - We removed support for the old (v0) control protocol. It has been
8475 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8476 become more of a headache than it's worth.
8478 o Major bugfixes (load balancing):
8479 - When choosing nodes for non-guard positions, weight guards
8480 proportionally less, since they already have enough load. Patch
8482 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8483 will allow fast Tor servers to get more attention.
8484 - When we're upgrading from an old Tor version, forget our current
8485 guards and pick new ones according to the new weightings. These
8486 three load balancing patches could raise effective network capacity
8487 by a factor of four. Thanks to Mike Perry for measurements.
8489 o Major bugfixes (stream expiration):
8490 - Expire not-yet-successful application streams in all cases if
8491 they've been around longer than SocksTimeout. Right now there are
8492 some cases where the stream will live forever, demanding a new
8493 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8495 o Minor features (controller):
8496 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8497 is valid before any authentication has been received. It tells
8498 a controller what kind of authentication is expected, and what
8499 protocol is spoken. Implements proposal 119.
8501 o Minor bugfixes (performance):
8502 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8503 greatly speeding up loading cached-routers from disk on startup.
8504 - Disable sentinel-based debugging for buffer code: we squashed all
8505 the bugs that this was supposed to detect a long time ago, and now
8506 its only effect is to change our buffer sizes from nice powers of
8507 two (which platform mallocs tend to like) to values slightly over
8508 powers of two (which make some platform mallocs sad).
8510 o Minor bugfixes (misc):
8511 - If exit bandwidth ever exceeds one third of total bandwidth, then
8512 use the correct formula to weight exit nodes when choosing paths.
8513 Based on patch from Mike Perry.
8514 - Choose perfectly fairly among routers when choosing by bandwidth and
8515 weighting by fraction of bandwidth provided by exits. Previously, we
8516 would choose with only approximate fairness, and correct ourselves
8517 if we ran off the end of the list.
8518 - If we require CookieAuthentication but we fail to write the
8519 cookie file, we would warn but not exit, and end up in a state
8520 where no controller could authenticate. Now we exit.
8521 - If we require CookieAuthentication, stop generating a new cookie
8522 every time we change any piece of our config.
8523 - Refuse to start with certain directory authority keys, and
8524 encourage people using them to stop.
8525 - Terminate multi-line control events properly. Original patch
8527 - Fix a minor memory leak when we fail to find enough suitable
8528 servers to choose a circuit.
8529 - Stop leaking part of the descriptor when we run into a particularly
8530 unparseable piece of it.
8533 Changes in version 0.2.0.6-alpha - 2007-08-26
8534 This sixth development snapshot features a new Vidalia version in the
8535 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8536 the ControlPort in the default configuration, which addresses important
8539 In addition, this snapshot fixes major load balancing problems
8540 with path selection, which should speed things up a lot once many
8541 people have upgraded. The directory authorities also use a new
8542 mean-time-between-failure approach to tracking which servers are stable,
8543 rather than just looking at the most recent uptime.
8545 o New directory authorities:
8546 - Set up Tonga as the default bridge directory authority.
8549 - Directory authorities now track servers by weighted
8550 mean-times-between-failures. When we have 4 or more days of data,
8551 use measured MTBF rather than declared uptime to decide whether
8552 to call a router Stable. Implements proposal 108.
8554 o Major bugfixes (load balancing):
8555 - When choosing nodes for non-guard positions, weight guards
8556 proportionally less, since they already have enough load. Patch
8558 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8559 will allow fast Tor servers to get more attention.
8560 - When we're upgrading from an old Tor version, forget our current
8561 guards and pick new ones according to the new weightings. These
8562 three load balancing patches could raise effective network capacity
8563 by a factor of four. Thanks to Mike Perry for measurements.
8565 o Major bugfixes (descriptor parsing):
8566 - Handle unexpected whitespace better in malformed descriptors. Bug
8567 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8570 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8571 GETINFO for Torstat to use until it can switch to using extrainfos.
8572 - Optionally (if built with -DEXPORTMALLINFO) export the output
8573 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8577 - Do not intermix bridge routers with controller-added
8578 routers. (Bugfix on 0.2.0.x)
8579 - Do not fail with an assert when accept() returns an unexpected
8580 address family. Addresses but does not wholly fix bug 483. (Bugfix
8582 - Let directory authorities startup even when they can't generate
8583 a descriptor immediately, e.g. because they don't know their
8585 - Stop putting the authentication cookie in a file called "0"
8586 in your working directory if you don't specify anything for the
8587 new CookieAuthFile option. Reported by Matt Edman.
8588 - Make it possible to read the PROTOCOLINFO response in a way that
8589 conforms to our control-spec. Reported by Matt Edman.
8590 - Fix a minor memory leak when we fail to find enough suitable
8591 servers to choose a circuit. Bugfix on 0.1.2.x.
8592 - Stop leaking part of the descriptor when we run into a particularly
8593 unparseable piece of it. Bugfix on 0.1.2.x.
8594 - Unmap the extrainfo cache file on exit.
8597 Changes in version 0.2.0.5-alpha - 2007-08-19
8598 This fifth development snapshot fixes compilation on Windows again;
8599 fixes an obnoxious client-side bug that slowed things down and put
8600 extra load on the network; gets us closer to using the v3 directory
8601 voting scheme; makes it easier for Tor controllers to use cookie-based
8602 authentication; and fixes a variety of other bugs.
8605 - Version 1 directories are no longer generated in full. Instead,
8606 authorities generate and serve "stub" v1 directories that list
8607 no servers. This will stop Tor versions 0.1.0.x and earlier from
8608 working, but (for security reasons) nobody should be running those
8611 o Major bugfixes (compilation, 0.2.0.x):
8612 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8613 - Try to fix MSVC compilation: build correctly on platforms that do
8614 not define s6_addr16 or s6_addr32.
8615 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8618 o Major bugfixes (stream expiration):
8619 - Expire not-yet-successful application streams in all cases if
8620 they've been around longer than SocksTimeout. Right now there are
8621 some cases where the stream will live forever, demanding a new
8622 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8625 o Minor features (directory servers):
8626 - When somebody requests a list of statuses or servers, and we have
8627 none of those, return a 404 rather than an empty 200.
8629 o Minor features (directory voting):
8630 - Store v3 consensus status consensuses on disk, and reload them
8633 o Minor features (security):
8634 - Warn about unsafe ControlPort configurations.
8635 - Refuse to start with certain directory authority keys, and
8636 encourage people using them to stop.
8638 o Minor features (controller):
8639 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8640 is valid before any authentication has been received. It tells
8641 a controller what kind of authentication is expected, and what
8642 protocol is spoken. Implements proposal 119.
8643 - New config option CookieAuthFile to choose a new location for the
8644 cookie authentication file, and config option
8645 CookieAuthFileGroupReadable to make it group-readable.
8647 o Minor features (unit testing):
8648 - Add command-line arguments to unit-test executable so that we can
8649 invoke any chosen test from the command line rather than having
8650 to run the whole test suite at once; and so that we can turn on
8651 logging for the unit tests.
8653 o Minor bugfixes (on 0.1.2.x):
8654 - If we require CookieAuthentication but we fail to write the
8655 cookie file, we would warn but not exit, and end up in a state
8656 where no controller could authenticate. Now we exit.
8657 - If we require CookieAuthentication, stop generating a new cookie
8658 every time we change any piece of our config.
8659 - When loading bandwidth history, do not believe any information in
8660 the future. Fixes bug 434.
8661 - When loading entry guard information, do not believe any information
8663 - When we have our clock set far in the future and generate an
8664 onion key, then re-set our clock to be correct, we should not stop
8665 the onion key from getting rotated.
8666 - Clean up torrc sample config file.
8667 - Do not automatically run configure from autogen.sh. This
8668 non-standard behavior tended to annoy people who have built other
8671 o Minor bugfixes (on 0.2.0.x):
8672 - Fix a bug with AutomapHostsOnResolve that would always cause
8673 the second request to fail. Bug reported by Kate. Bugfix on
8675 - Fix a bug in ADDRMAP controller replies that would sometimes
8676 try to print a NULL. Patch from tup.
8677 - Read v3 directory authority keys from the right location.
8678 - Numerous bugfixes to directory voting code.
8681 Changes in version 0.1.2.16 - 2007-08-01
8682 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8683 remote attacker in certain situations to rewrite the user's torrc
8684 configuration file. This can completely compromise anonymity of users
8685 in most configurations, including those running the Vidalia bundles,
8686 TorK, etc. Or worse.
8688 o Major security fixes:
8689 - Close immediately after missing authentication on control port;
8690 do not allow multiple authentication attempts.
8693 Changes in version 0.2.0.4-alpha - 2007-08-01
8694 This fourth development snapshot fixes a critical security vulnerability
8695 for most users, specifically those running Vidalia, TorK, etc. Everybody
8696 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8698 o Major security fixes:
8699 - Close immediately after missing authentication on control port;
8700 do not allow multiple authentication attempts.
8702 o Major bugfixes (compilation):
8703 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8706 o Minor features (performance):
8707 - Be even more aggressive about releasing RAM from small
8708 empty buffers. Thanks to our free-list code, this shouldn't be too
8709 performance-intensive.
8710 - Disable sentinel-based debugging for buffer code: we squashed all
8711 the bugs that this was supposed to detect a long time ago, and
8712 now its only effect is to change our buffer sizes from nice
8713 powers of two (which platform mallocs tend to like) to values
8714 slightly over powers of two (which make some platform mallocs sad).
8715 - Log malloc statistics from mallinfo() on platforms where it
8719 Changes in version 0.2.0.3-alpha - 2007-07-29
8720 This third development snapshot introduces new experimental
8721 blocking-resistance features and a preliminary version of the v3
8722 directory voting design, and includes many other smaller features
8726 - The first pieces of our "bridge" design for blocking-resistance
8727 are implemented. People can run bridge directory authorities;
8728 people can run bridges; and people can configure their Tor clients
8729 with a set of bridges to use as the first hop into the Tor network.
8730 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
8732 - Create listener connections before we setuid to the configured
8733 User and Group. Now non-Windows users can choose port values
8734 under 1024, start Tor as root, and have Tor bind those ports
8735 before it changes to another UID. (Windows users could already
8737 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8738 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8739 on "vserver" accounts. (Patch from coderman.)
8740 - Be even more aggressive about separating local traffic from relayed
8741 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
8743 o Major features (experimental):
8744 - First cut of code for "v3 dir voting": directory authorities will
8745 vote on a common network status document rather than each publishing
8746 their own opinion. This code needs more testing and more corner-case
8747 handling before it's ready for use.
8750 - Directory authorities now call routers Fast if their bandwidth is
8751 at least 100KB/s, and consider their bandwidth adequate to be a
8752 Guard if it is at least 250KB/s, no matter the medians. This fix
8753 complements proposal 107. [Bugfix on 0.1.2.x]
8754 - Directory authorities now never mark more than 3 servers per IP as
8755 Valid and Running. (Implements proposal 109, by Kevin Bauer and
8757 - Minor change to organizationName and commonName generation
8758 procedures in TLS certificates during Tor handshakes, to invalidate
8759 some earlier censorware approaches. This is not a long-term
8760 solution, but applying it will give us a bit of time to look into
8761 the epidemiology of countermeasures as they spread.
8763 o Major bugfixes (directory):
8764 - Rewrite directory tokenization code to never run off the end of
8765 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
8767 o Minor features (controller):
8768 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8769 match requests to applications. (Patch from Robert Hogan.)
8770 - Report address and port correctly on connections to DNSPort. (Patch
8772 - Add a RESOLVE command to launch hostname lookups. (Original patch
8774 - Add GETINFO status/enough-dir-info to let controllers tell whether
8775 Tor has downloaded sufficient directory information. (Patch
8777 - You can now use the ControlSocket option to tell Tor to listen for
8778 controller connections on Unix domain sockets on systems that
8779 support them. (Patch from Peter Palfrader.)
8780 - STREAM NEW events are generated for DNSPort requests and for
8781 tunneled directory connections. (Patch from Robert Hogan.)
8782 - New "GETINFO address-mappings/*" command to get address mappings
8783 with expiry information. "addr-mappings/*" is now deprecated.
8786 o Minor features (misc):
8787 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8789 - The tor-gencert tool for v3 directory authorities now creates all
8790 files as readable to the file creator only, and write-protects
8791 the authority identity key.
8792 - When dumping memory usage, list bytes used in buffer memory
8794 - When running with dmalloc, dump more stats on hup and on exit.
8795 - Directory authorities now fail quickly and (relatively) harmlessly
8796 if they generate a network status document that is somehow
8799 o Traffic load balancing improvements:
8800 - If exit bandwidth ever exceeds one third of total bandwidth, then
8801 use the correct formula to weight exit nodes when choosing paths.
8802 (Based on patch from Mike Perry.)
8803 - Choose perfectly fairly among routers when choosing by bandwidth and
8804 weighting by fraction of bandwidth provided by exits. Previously, we
8805 would choose with only approximate fairness, and correct ourselves
8806 if we ran off the end of the list. [Bugfix on 0.1.2.x]
8808 o Performance improvements:
8809 - Be more aggressive with freeing buffer RAM or putting it on the
8811 - Use Critical Sections rather than Mutexes for synchronizing threads
8812 on win32; Mutexes are heavier-weight, and designed for synchronizing
8815 o Deprecated and removed features:
8816 - RedirectExits is now deprecated.
8817 - Stop allowing address masks that do not correspond to bit prefixes.
8818 We have warned about these for a really long time; now it's time
8819 to reject them. (Patch from croup.)
8821 o Minor bugfixes (directory):
8822 - Fix another crash bug related to extra-info caching. (Bug found by
8823 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
8824 - Directories no longer return a "304 not modified" when they don't
8825 have the networkstatus the client asked for. Also fix a memory
8826 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
8827 - We had accidentally labelled 0.1.2.x directory servers as not
8828 suitable for begin_dir requests, and had labelled no directory
8829 servers as suitable for uploading extra-info documents. [Bugfix
8832 o Minor bugfixes (dns):
8833 - Fix a crash when DNSPort is set more than once. (Patch from Robert
8834 Hogan.) [Bugfix on 0.2.0.2-alpha]
8835 - Add DNSPort connections to the global connection list, so that we
8836 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
8838 - Fix a dangling reference that could lead to a crash when DNSPort is
8839 changed or closed (Patch from Robert Hogan.) [Bugfix on
8842 o Minor bugfixes (controller):
8843 - Provide DNS expiry times in GMT, not in local time. For backward
8844 compatibility, ADDRMAP events only provide GMT expiry in an extended
8845 field. "GETINFO address-mappings" always does the right thing.
8846 - Use CRLF line endings properly in NS events.
8847 - Terminate multi-line control events properly. (Original patch
8848 from tup.) [Bugfix on 0.1.2.x-alpha]
8849 - Do not include spaces in SOURCE_ADDR fields in STREAM
8850 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
8853 Changes in version 0.1.2.15 - 2007-07-17
8854 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
8855 problems, fixes compilation on BSD, and fixes a variety of other
8856 bugs. Everybody should upgrade.
8858 o Major bugfixes (compilation):
8859 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
8861 o Major bugfixes (crashes):
8862 - Try even harder not to dereference the first character after
8863 an mmap(). Reported by lodger.
8864 - Fix a crash bug in directory authorities when we re-number the
8865 routerlist while inserting a new router.
8866 - When the cached-routers file is an even multiple of the page size,
8867 don't run off the end and crash. (Fixes bug 455; based on idea
8869 - Fix eventdns.c behavior on Solaris: It is critical to include
8870 orconfig.h _before_ sys/types.h, so that we can get the expected
8871 definition of _FILE_OFFSET_BITS.
8873 o Major bugfixes (security):
8874 - Fix a possible buffer overrun when using BSD natd support. Bug
8876 - When sending destroy cells from a circuit's origin, don't include
8877 the reason for tearing down the circuit. The spec says we didn't,
8878 and now we actually don't. Reported by lodger.
8879 - Keep streamids from different exits on a circuit separate. This
8880 bug may have allowed other routers on a given circuit to inject
8881 cells into streams. Reported by lodger; fixes bug 446.
8882 - If there's a never-before-connected-to guard node in our list,
8883 never choose any guards past it. This way we don't expand our
8884 guard list unless we need to.
8886 o Minor bugfixes (guard nodes):
8887 - Weight guard selection by bandwidth, so that low-bandwidth nodes
8888 don't get overused as guards.
8890 o Minor bugfixes (directory):
8891 - Correctly count the number of authorities that recommend each
8892 version. Previously, we were under-counting by 1.
8893 - Fix a potential crash bug when we load many server descriptors at
8894 once and some of them make others of them obsolete. Fixes bug 458.
8896 o Minor bugfixes (hidden services):
8897 - Stop tearing down the whole circuit when the user asks for a
8898 connection to a port that the hidden service didn't configure.
8901 o Minor bugfixes (misc):
8902 - On Windows, we were preventing other processes from reading
8903 cached-routers while Tor was running. Reported by janbar.
8904 - Fix a possible (but very unlikely) bug in picking routers by
8905 bandwidth. Add a log message to confirm that it is in fact
8906 unlikely. Patch from lodger.
8907 - Backport a couple of memory leak fixes.
8908 - Backport miscellaneous cosmetic bugfixes.
8911 Changes in version 0.2.0.2-alpha - 2007-06-02
8912 o Major bugfixes on 0.2.0.1-alpha:
8913 - Fix an assertion failure related to servers without extra-info digests.
8914 Resolves bugs 441 and 442.
8916 o Minor features (directory):
8917 - Support "If-Modified-Since" when answering HTTP requests for
8918 directories, running-routers documents, and network-status documents.
8919 (There's no need to support it for router descriptors, since those
8920 are downloaded by descriptor digest.)
8922 o Minor build issues:
8923 - Clear up some MIPSPro compiler warnings.
8924 - When building from a tarball on a machine that happens to have SVK
8925 installed, report the micro-revision as whatever version existed
8926 in the tarball, not as "x".
8929 Changes in version 0.2.0.1-alpha - 2007-06-01
8930 This early development snapshot provides new features for people running
8931 Tor as both a client and a server (check out the new RelayBandwidth
8932 config options); lets Tor run as a DNS proxy; and generally moves us
8933 forward on a lot of fronts.
8935 o Major features, server usability:
8936 - New config options RelayBandwidthRate and RelayBandwidthBurst:
8937 a separate set of token buckets for relayed traffic. Right now
8938 relayed traffic is defined as answers to directory requests, and
8939 OR connections that don't have any local circuits on them.
8941 o Major features, client usability:
8942 - A client-side DNS proxy feature to replace the need for
8943 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
8944 for DNS requests on port 9999, use the Tor network to resolve them
8945 anonymously, and send the reply back like a regular DNS server.
8946 The code still only implements a subset of DNS.
8947 - Make PreferTunneledDirConns and TunnelDirConns work even when
8948 we have no cached directory info. This means Tor clients can now
8949 do all of their connections protected by TLS.
8951 o Major features, performance and efficiency:
8952 - Directory authorities accept and serve "extra info" documents for
8953 routers. These documents contain fields from router descriptors
8954 that aren't usually needed, and that use a lot of excess
8955 bandwidth. Once these fields are removed from router descriptors,
8956 the bandwidth savings should be about 60%. [Partially implements
8958 - Servers upload extra-info documents to any authority that accepts
8959 them. Authorities (and caches that have been configured to download
8960 extra-info documents) download them as needed. [Partially implements
8962 - Change the way that Tor buffers data that it is waiting to write.
8963 Instead of queueing data cells in an enormous ring buffer for each
8964 client->OR or OR->OR connection, we now queue cells on a separate
8965 queue for each circuit. This lets us use less slack memory, and
8966 will eventually let us be smarter about prioritizing different kinds
8968 - Use memory pools to allocate cells with better speed and memory
8969 efficiency, especially on platforms where malloc() is inefficient.
8970 - Stop reading on edge connections when their corresponding circuit
8971 buffers are full; start again as the circuits empty out.
8973 o Major features, other:
8974 - Add an HSAuthorityRecordStats option that hidden service authorities
8975 can use to track statistics of overall hidden service usage without
8976 logging information that would be very useful to an attacker.
8977 - Start work implementing multi-level keys for directory authorities:
8978 Add a standalone tool to generate key certificates. (Proposal 103.)
8981 - Directory authorities now call routers Stable if they have an
8982 uptime of at least 30 days, even if that's not the median uptime
8983 in the network. Implements proposal 107, suggested by Kevin Bauer
8986 o Minor fixes (resource management):
8987 - Count the number of open sockets separately from the number
8988 of active connection_t objects. This will let us avoid underusing
8989 our allocated connection limit.
8990 - We no longer use socket pairs to link an edge connection to an
8991 anonymous directory connection or a DirPort test connection.
8992 Instead, we track the link internally and transfer the data
8993 in-process. This saves two sockets per "linked" connection (at the
8994 client and at the server), and avoids the nasty Windows socketpair()
8996 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
8997 for every single inactive connection_t. Free items from the
8998 4k/16k-buffer free lists when they haven't been used for a while.
9000 o Minor features (build):
9001 - Make autoconf search for libevent, openssl, and zlib consistently.
9002 - Update deprecated macros in configure.in.
9003 - When warning about missing headers, tell the user to let us
9004 know if the compile succeeds anyway, so we can downgrade the
9006 - Include the current subversion revision as part of the version
9007 string: either fetch it directly if we're in an SVN checkout, do
9008 some magic to guess it if we're in an SVK checkout, or use
9009 the last-detected version if we're building from a .tar.gz.
9010 Use this version consistently in log messages.
9012 o Minor features (logging):
9013 - Always prepend "Bug: " to any log message about a bug.
9014 - Put a platform string (e.g. "Linux i686") in the startup log
9015 message, so when people paste just their logs, we know if it's
9016 OpenBSD or Windows or what.
9017 - When logging memory usage, break down memory used in buffers by
9020 o Minor features (directory system):
9021 - New config option V2AuthoritativeDirectory that all directory
9022 authorities should set. This will let future authorities choose
9023 not to serve V2 directory information.
9024 - Directory authorities allow multiple router descriptors and/or extra
9025 info documents to be uploaded in a single go. This will make
9026 implementing proposal 104 simpler.
9028 o Minor features (controller):
9029 - Add a new config option __DisablePredictedCircuits designed for
9030 use by the controller, when we don't want Tor to build any circuits
9032 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9033 so we can exit from the middle of the circuit.
9034 - Implement "getinfo status/circuit-established".
9035 - Implement "getinfo status/version/..." so a controller can tell
9036 whether the current version is recommended, and whether any versions
9037 are good, and how many authorities agree. (Patch from shibz.)
9039 o Minor features (hidden services):
9040 - Allow multiple HiddenServicePort directives with the same virtual
9041 port; when they occur, the user is sent round-robin to one
9042 of the target ports chosen at random. Partially fixes bug 393 by
9043 adding limited ad-hoc round-robining.
9045 o Minor features (other):
9047 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9048 resolve request for hosts matching a given pattern causes Tor to
9049 generate an internal virtual address mapping for that host. This
9050 allows DNSPort to work sensibly with hidden service users. By
9051 default, .exit and .onion addresses are remapped; the list of
9052 patterns can be reconfigured with AutomapHostsSuffixes.
9053 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9054 address. Thanks to the AutomapHostsOnResolve option, this is no
9055 longer a completely silly thing to do.
9056 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9057 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9058 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9059 minus 1 byte: the actual maximum declared bandwidth.
9062 - Removed support for the old binary "version 0" controller protocol.
9063 This has been deprecated since 0.1.1, and warnings have been issued
9064 since 0.1.2. When we encounter a v0 control message, we now send
9065 back an error and close the connection.
9066 - Remove the old "dns worker" server DNS code: it hasn't been default
9067 since 0.1.2.2-alpha, and all the servers seem to be using the new
9070 o Minor bugfixes (portability):
9071 - Even though Windows is equally happy with / and \ as path separators,
9072 try to use \ consistently on Windows and / consistently on Unix: it
9073 makes the log messages nicer.
9074 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9075 - Read resolv.conf files correctly on platforms where read() returns
9076 partial results on small file reads.
9078 o Minor bugfixes (directory):
9079 - Correctly enforce that elements of directory objects do not appear
9080 more often than they are allowed to appear.
9081 - When we are reporting the DirServer line we just parsed, we were
9082 logging the second stanza of the key fingerprint, not the first.
9084 o Minor bugfixes (logging):
9085 - When we hit an EOF on a log (probably because we're shutting down),
9086 don't try to remove the log from the list: just mark it as
9087 unusable. (Bulletproofs against bug 222.)
9089 o Minor bugfixes (other):
9090 - In the exitlist script, only consider the most recently published
9091 server descriptor for each server. Also, when the user requests
9092 a list of servers that _reject_ connections to a given address,
9093 explicitly exclude the IPs that also have servers that accept
9094 connections to that address. (Resolves bug 405.)
9095 - Stop allowing hibernating servers to be "stable" or "fast".
9096 - On Windows, we were preventing other processes from reading
9097 cached-routers while Tor was running. (Reported by janbar)
9098 - Make the NodeFamilies config option work. (Reported by
9099 lodger -- it has never actually worked, even though we added it
9101 - Check return values from pthread_mutex functions.
9102 - Don't save non-general-purpose router descriptors to the disk cache,
9103 because we have no way of remembering what their purpose was when
9105 - Add even more asserts to hunt down bug 417.
9106 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9107 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9108 Add a log message to confirm that it is in fact unlikely.
9110 o Minor bugfixes (controller):
9111 - Make 'getinfo fingerprint' return a 551 error if we're not a
9112 server, so we match what the control spec claims we do. Reported
9114 - Fix a typo in an error message when extendcircuit fails that
9115 caused us to not follow the \r\n-based delimiter protocol. Reported
9118 o Code simplifications and refactoring:
9119 - Stop passing around circuit_t and crypt_path_t pointers that are
9120 implicit in other procedure arguments.
9121 - Drop the old code to choke directory connections when the
9122 corresponding OR connections got full: thanks to the cell queue
9123 feature, OR conns don't get full any more.
9124 - Make dns_resolve() handle attaching connections to circuits
9125 properly, so the caller doesn't have to.
9126 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9127 - Keep the connection array as a dynamic smartlist_t, rather than as
9128 a fixed-sized array. This is important, as the number of connections
9129 is becoming increasingly decoupled from the number of sockets.
9132 Changes in version 0.1.2.14 - 2007-05-25
9133 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9134 change especially affects those who serve or use hidden services),
9135 and fixes several other crash- and security-related bugs.
9137 o Directory authority changes:
9138 - Two directory authorities (moria1 and moria2) just moved to new
9139 IP addresses. This change will particularly affect those who serve
9140 or use hidden services.
9142 o Major bugfixes (crashes):
9143 - If a directory server runs out of space in the connection table
9144 as it's processing a begin_dir request, it will free the exit stream
9145 but leave it attached to the circuit, leading to unpredictable
9146 behavior. (Reported by seeess, fixes bug 425.)
9147 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9148 to corrupt memory under some really unlikely scenarios.
9149 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9150 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9153 o Major bugfixes (security):
9154 - When choosing an entry guard for a circuit, avoid using guards
9155 that are in the same family as the chosen exit -- not just guards
9156 that are exactly the chosen exit. (Reported by lodger.)
9158 o Major bugfixes (resource management):
9159 - If a directory authority is down, skip it when deciding where to get
9160 networkstatus objects or descriptors. Otherwise we keep asking
9161 every 10 seconds forever. Fixes bug 384.
9162 - Count it as a failure if we fetch a valid network-status but we
9163 don't want to keep it. Otherwise we'll keep fetching it and keep
9164 not wanting to keep it. Fixes part of bug 422.
9165 - If all of our dirservers have given us bad or no networkstatuses
9166 lately, then stop hammering them once per minute even when we
9167 think they're failed. Fixes another part of bug 422.
9170 - Actually set the purpose correctly for descriptors inserted with
9172 - When we have k non-v2 authorities in our DirServer config,
9173 we ignored the last k authorities in the list when updating our
9175 - Correctly back-off from requesting router descriptors that we are
9176 having a hard time downloading.
9177 - Read resolv.conf files correctly on platforms where read() returns
9178 partial results on small file reads.
9179 - Don't rebuild the entire router store every time we get 32K of
9180 routers: rebuild it when the journal gets very large, or when
9181 the gaps in the store get very large.
9184 - When routers publish SVN revisions in their router descriptors,
9185 authorities now include those versions correctly in networkstatus
9187 - Warn when using a version of libevent before 1.3b to run a server on
9188 OSX or BSD: these versions interact badly with userspace threads.
9191 Changes in version 0.1.2.13 - 2007-04-24
9192 This release features some major anonymity fixes, such as safer path
9193 selection; better client performance; faster bootstrapping, better
9194 address detection, and better DNS support for servers; write limiting as
9195 well as read limiting to make servers easier to run; and a huge pile of
9196 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9198 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9199 of the Freenode IRC network, remembering his patience and vision for
9200 free speech on the Internet.
9203 - Fix a memory leak when we ask for "all" networkstatuses and we
9204 get one we don't recognize.
9205 - Add more asserts to hunt down bug 417.
9206 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9209 Changes in version 0.1.2.12-rc - 2007-03-16
9211 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9212 directory information requested inside Tor connections (i.e. via
9213 begin_dir cells). It only triggered when the same connection was
9214 serving other data at the same time. Reported by seeess.
9217 - When creating a circuit via the controller, send a 'launched'
9218 event when we're done, so we follow the spec better.
9221 Changes in version 0.1.2.11-rc - 2007-03-15
9222 o Minor bugfixes (controller), reported by daejees:
9223 - Correct the control spec to match how the code actually responds
9224 to 'getinfo addr-mappings/*'.
9225 - The control spec described a GUARDS event, but the code
9226 implemented a GUARD event. Standardize on GUARD, but let people
9230 Changes in version 0.1.2.10-rc - 2007-03-07
9231 o Major bugfixes (Windows):
9232 - Do not load the NT services library functions (which may not exist)
9233 just to detect if we're a service trying to shut down. Now we run
9234 on Win98 and friends again.
9236 o Minor bugfixes (other):
9237 - Clarify a couple of log messages.
9238 - Fix a misleading socks5 error number.
9241 Changes in version 0.1.2.9-rc - 2007-03-02
9242 o Major bugfixes (Windows):
9243 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9244 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9245 int configuration values: the high-order 32 bits would get
9246 truncated. In particular, we were being bitten by the default
9247 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9248 and maybe also bug 397.)
9250 o Minor bugfixes (performance):
9251 - Use OpenSSL's AES implementation on platforms where it's faster.
9252 This could save us as much as 10% CPU usage.
9254 o Minor bugfixes (server):
9255 - Do not rotate onion key immediately after setting it for the first
9258 o Minor bugfixes (directory authorities):
9259 - Stop calling servers that have been hibernating for a long time
9260 "stable". Also, stop letting hibernating or obsolete servers affect
9261 uptime and bandwidth cutoffs.
9262 - Stop listing hibernating servers in the v1 directory.
9264 o Minor bugfixes (hidden services):
9265 - Upload hidden service descriptors slightly less often, to reduce
9266 load on authorities.
9268 o Minor bugfixes (other):
9269 - Fix an assert that could trigger if a controller quickly set then
9270 cleared EntryNodes. Bug found by Udo van den Heuvel.
9271 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9273 - Fix a potential race condition in the rpm installer. Found by
9275 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9276 of 2 as indicating that the server is completely bad; it sometimes
9277 means that the server is just bad for the request in question. (may fix
9278 the last of bug 326.)
9279 - Disable encrypted directory connections when we don't have a server
9280 descriptor for the destination. We'll get this working again in
9284 Changes in version 0.1.2.8-beta - 2007-02-26
9285 o Major bugfixes (crashes):
9286 - Stop crashing when the controller asks us to resetconf more than
9287 one config option at once. (Vidalia 0.0.11 does this.)
9288 - Fix a crash that happened on Win98 when we're given command-line
9289 arguments: don't try to load NT service functions from advapi32.dll
9290 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9292 - Fix a longstanding obscure crash bug that could occur when
9293 we run out of DNS worker processes. (Resolves bug 390.)
9295 o Major bugfixes (hidden services):
9296 - Correctly detect whether hidden service descriptor downloads are
9297 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9299 o Major bugfixes (accounting):
9300 - When we start during an accounting interval before it's time to wake
9301 up, remember to wake up at the correct time. (May fix bug 342.)
9303 o Minor bugfixes (controller):
9304 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9305 clear the corresponding on_circuit variable, and remember later
9306 that we don't need to send a redundant CLOSED event. Resolves part
9308 - Report events where a resolve succeeded or where we got a socks
9309 protocol error correctly, rather than calling both of them
9311 - Change reported stream target addresses to IP consistently when
9312 we finally get the IP from an exit node.
9313 - Send log messages to the controller even if they happen to be very
9316 o Minor bugfixes (other):
9317 - Display correct results when reporting which versions are
9318 recommended, and how recommended they are. (Resolves bug 383.)
9319 - Improve our estimates for directory bandwidth to be less random:
9320 guess that an unrecognized directory will have the average bandwidth
9321 from all known directories, not that it will have the average
9322 bandwidth from those directories earlier than it on the list.
9323 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9324 and hup, stop triggering an assert based on an empty onion_key.
9325 - On platforms with no working mmap() equivalent, don't warn the
9326 user when cached-routers doesn't exist.
9327 - Warn the user when mmap() [or its equivalent] fails for some reason
9328 other than file-not-found.
9329 - Don't warn the user when cached-routers.new doesn't exist: that's
9330 perfectly fine when starting up for the first time.
9331 - When EntryNodes are configured, rebuild the guard list to contain,
9332 in order: the EntryNodes that were guards before; the rest of the
9333 EntryNodes; the nodes that were guards before.
9334 - Mask out all signals in sub-threads; only the libevent signal
9335 handler should be processing them. This should prevent some crashes
9336 on some machines using pthreads. (Patch from coderman.)
9337 - Fix switched arguments on memset in the implementation of
9338 tor_munmap() for systems with no mmap() call.
9339 - When Tor receives a router descriptor that it asked for, but
9340 no longer wants (because it has received fresh networkstatuses
9341 in the meantime), do not warn the user. Cache the descriptor if
9342 we're a cache; drop it if we aren't.
9343 - Make earlier entry guards _really_ get retried when the network
9345 - On a malformed DNS reply, always give an error to the corresponding
9347 - Build with recent libevents on platforms that do not define the
9348 nonstandard types "u_int8_t" and friends.
9350 o Minor features (controller):
9351 - Warn the user when an application uses the obsolete binary v0
9352 control protocol. We're planning to remove support for it during
9353 the next development series, so it's good to give people some
9355 - Add STREAM_BW events to report per-entry-stream bandwidth
9356 use. (Patch from Robert Hogan.)
9357 - Rate-limit SIGNEWNYM signals in response to controllers that
9358 impolitely generate them for every single stream. (Patch from
9359 mwenge; closes bug 394.)
9360 - Make REMAP stream events have a SOURCE (cache or exit), and
9361 make them generated in every case where we get a successful
9362 connected or resolved cell.
9364 o Minor bugfixes (performance):
9365 - Call router_have_min_dir_info half as often. (This is showing up in
9366 some profiles, but not others.)
9367 - When using GCC, make log_debug never get called at all, and its
9368 arguments never get evaluated, when no debug logs are configured.
9369 (This is showing up in some profiles, but not others.)
9372 - Remove some never-implemented options. Mark PathlenCoinWeight as
9374 - Implement proposal 106: Stop requiring clients to have well-formed
9375 certificates; stop checking nicknames in certificates. (Clients
9376 have certificates so that they can look like Tor servers, but in
9377 the future we might want to allow them to look like regular TLS
9378 clients instead. Nicknames in certificates serve no purpose other
9379 than making our protocol easier to recognize on the wire.)
9380 - Revise messages on handshake failure again to be even more clear about
9381 which are incoming connections and which are outgoing.
9382 - Discard any v1 directory info that's over 1 month old (for
9383 directories) or over 1 week old (for running-routers lists).
9384 - Do not warn when individual nodes in the configuration's EntryNodes,
9385 ExitNodes, etc are down: warn only when all possible nodes
9386 are down. (Fixes bug 348.)
9387 - Always remove expired routers and networkstatus docs before checking
9388 whether we have enough information to build circuits. (Fixes
9390 - Put a lower-bound on MaxAdvertisedBandwidth.
9393 Changes in version 0.1.2.7-alpha - 2007-02-06
9394 o Major bugfixes (rate limiting):
9395 - Servers decline directory requests much more aggressively when
9396 they're low on bandwidth. Otherwise they end up queueing more and
9397 more directory responses, which can't be good for latency.
9398 - But never refuse directory requests from local addresses.
9399 - Fix a memory leak when sending a 503 response for a networkstatus
9401 - Be willing to read or write on local connections (e.g. controller
9402 connections) even when the global rate limiting buckets are empty.
9403 - If our system clock jumps back in time, don't publish a negative
9404 uptime in the descriptor. Also, don't let the global rate limiting
9405 buckets go absurdly negative.
9406 - Flush local controller connection buffers periodically as we're
9407 writing to them, so we avoid queueing 4+ megabytes of data before
9410 o Major bugfixes (NT services):
9411 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9412 command-line flag so that admins can override the default by saying
9413 "tor --service install --user "SomeUser"". This will not affect
9414 existing installed services. Also, warn the user that the service
9415 will look for its configuration file in the service user's
9416 %appdata% directory. (We can't do the 'hardwire the user's appdata
9417 directory' trick any more, since we may not have read access to that
9420 o Major bugfixes (other):
9421 - Previously, we would cache up to 16 old networkstatus documents
9422 indefinitely, if they came from nontrusted authorities. Now we
9423 discard them if they are more than 10 days old.
9424 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
9426 - Detect and reject malformed DNS responses containing circular
9428 - If exits are rare enough that we're not marking exits as guards,
9429 ignore exit bandwidth when we're deciding the required bandwidth
9431 - When we're handling a directory connection tunneled over Tor,
9432 don't fill up internal memory buffers with all the data we want
9433 to tunnel; instead, only add it if the OR connection that will
9434 eventually receive it has some room for it. (This can lead to
9435 slowdowns in tunneled dir connections; a better solution will have
9438 o Minor bugfixes (dns):
9439 - Add some defensive programming to eventdns.c in an attempt to catch
9440 possible memory-stomping bugs.
9441 - Detect and reject DNS replies containing IPv4 or IPv6 records with
9442 an incorrect number of bytes. (Previously, we would ignore the
9444 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
9445 in the correct order, and doesn't crash.
9446 - Free memory held in recently-completed DNS lookup attempts on exit.
9447 This was not a memory leak, but may have been hiding memory leaks.
9448 - Handle TTL values correctly on reverse DNS lookups.
9449 - Treat failure to parse resolv.conf as an error.
9451 o Minor bugfixes (other):
9452 - Fix crash with "tor --list-fingerprint" (reported by seeess).
9453 - When computing clock skew from directory HTTP headers, consider what
9454 time it was when we finished asking for the directory, not what
9456 - Expire socks connections if they spend too long waiting for the
9457 handshake to finish. Previously we would let them sit around for
9458 days, if the connecting application didn't close them either.
9459 - And if the socks handshake hasn't started, don't send a
9460 "DNS resolve socks failed" handshake reply; just close it.
9461 - Stop using C functions that OpenBSD's linker doesn't like.
9462 - Don't launch requests for descriptors unless we have networkstatuses
9463 from at least half of the authorities. This delays the first
9464 download slightly under pathological circumstances, but can prevent
9465 us from downloading a bunch of descriptors we don't need.
9466 - Do not log IPs with TLS failures for incoming TLS
9467 connections. (Fixes bug 382.)
9468 - If the user asks to use invalid exit nodes, be willing to use
9470 - Stop using the reserved ac_cv namespace in our configure script.
9471 - Call stat() slightly less often; use fstat() when possible.
9472 - Refactor the way we handle pending circuits when an OR connection
9473 completes or fails, in an attempt to fix a rare crash bug.
9474 - Only rewrite a conn's address based on X-Forwarded-For: headers
9475 if it's a parseable public IP address; and stop adding extra quotes
9476 to the resulting address.
9479 - Weight directory requests by advertised bandwidth. Now we can
9480 let servers enable write limiting but still allow most clients to
9481 succeed at their directory requests. (We still ignore weights when
9482 choosing a directory authority; I hope this is a feature.)
9485 - Create a new file ReleaseNotes which was the old ChangeLog. The
9486 new ChangeLog file now includes the summaries for all development
9488 - Check for addresses with invalid characters at the exit as well
9489 as at the client, and warn less verbosely when they fail. You can
9490 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9491 - Adapt a patch from goodell to let the contrib/exitlist script
9492 take arguments rather than require direct editing.
9493 - Inform the server operator when we decide not to advertise a
9494 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9495 was confusing Zax, so now we're hopefully more helpful.
9496 - Bring us one step closer to being able to establish an encrypted
9497 directory tunnel without knowing a descriptor first. Still not
9498 ready yet. As part of the change, now assume we can use a
9499 create_fast cell if we don't know anything about a router.
9500 - Allow exit nodes to use nameservers running on ports other than 53.
9501 - Servers now cache reverse DNS replies.
9502 - Add an --ignore-missing-torrc command-line option so that we can
9503 get the "use sensible defaults if the configuration file doesn't
9504 exist" behavior even when specifying a torrc location on the command
9507 o Minor features (controller):
9508 - Track reasons for OR connection failure; make these reasons
9509 available via the controller interface. (Patch from Mike Perry.)
9510 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9511 can learn when clients are sending malformed hostnames to Tor.
9512 - Clean up documentation for controller status events.
9513 - Add a REMAP status to stream events to note that a stream's
9514 address has changed because of a cached address or a MapAddress
9518 Changes in version 0.1.2.6-alpha - 2007-01-09
9520 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9521 connection handles more than 4 gigs in either direction, we crash.
9522 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9523 advertised exit node, somebody might try to exit from us when
9524 we're bootstrapping and before we've built our descriptor yet.
9525 Refuse the connection rather than crashing.
9528 - Warn if we (as a server) find that we've resolved an address that we
9529 weren't planning to resolve.
9530 - Warn that using select() on any libevent version before 1.1 will be
9531 unnecessarily slow (even for select()).
9532 - Flush ERR-level controller status events just like we currently
9533 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9534 the controller from learning about current events.
9536 o Minor features (more controller status events):
9537 - Implement EXTERNAL_ADDRESS server status event so controllers can
9538 learn when our address changes.
9539 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9540 can learn when directories reject our descriptor.
9541 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9542 can learn when a client application is speaking a non-socks protocol
9544 - Implement DANGEROUS_SOCKS client status event so controllers
9545 can learn when a client application is leaking DNS addresses.
9546 - Implement BUG general status event so controllers can learn when
9547 Tor is unhappy about its internal invariants.
9548 - Implement CLOCK_SKEW general status event so controllers can learn
9549 when Tor thinks the system clock is set incorrectly.
9550 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9551 server status events so controllers can learn when their descriptors
9552 are accepted by a directory.
9553 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9554 server status events so controllers can learn about Tor's progress in
9555 deciding whether it's reachable from the outside.
9556 - Implement BAD_LIBEVENT general status event so controllers can learn
9557 when we have a version/method combination in libevent that needs to
9559 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9560 and DNS_USELESS server status events so controllers can learn
9561 about changes to DNS server status.
9563 o Minor features (directory):
9564 - Authorities no longer recommend exits as guards if this would shift
9565 too much load to the exit nodes.
9568 Changes in version 0.1.2.5-alpha - 2007-01-06
9570 - Enable write limiting as well as read limiting. Now we sacrifice
9571 capacity if we're pushing out lots of directory traffic, rather
9572 than overrunning the user's intended bandwidth limits.
9573 - Include TLS overhead when counting bandwidth usage; previously, we
9574 would count only the bytes sent over TLS, but not the bytes used
9576 - Support running the Tor service with a torrc not in the same
9577 directory as tor.exe and default to using the torrc located in
9578 the %appdata%\Tor\ of the user who installed the service. Patch
9580 - Servers now check for the case when common DNS requests are going to
9581 wildcarded addresses (i.e. all getting the same answer), and change
9582 their exit policy to reject *:* if it's happening.
9583 - Implement BEGIN_DIR cells, so we can connect to the directory
9584 server via TLS to do encrypted directory requests rather than
9585 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9586 config options if you like.
9588 o Minor features (config and docs):
9589 - Start using the state file to store bandwidth accounting data:
9590 the bw_accounting file is now obsolete. We'll keep generating it
9591 for a while for people who are still using 0.1.2.4-alpha.
9592 - Try to batch changes to the state file so that we do as few
9593 disk writes as possible while still storing important things in
9595 - The state file and the bw_accounting file get saved less often when
9596 the AvoidDiskWrites config option is set.
9597 - Make PIDFile work on Windows (untested).
9598 - Add internal descriptions for a bunch of configuration options:
9599 accessible via controller interface and in comments in saved
9601 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9602 NNTP by default, so this seems like a sensible addition.
9603 - Clients now reject hostnames with invalid characters. This should
9604 avoid some inadvertent info leaks. Add an option
9605 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9606 is running a private network with hosts called @, !, and #.
9607 - Add a maintainer script to tell us which options are missing
9608 documentation: "make check-docs".
9609 - Add a new address-spec.txt document to describe our special-case
9610 addresses: .exit, .onion, and .noconnnect.
9612 o Minor features (DNS):
9613 - Ongoing work on eventdns infrastructure: now it has dns server
9614 and ipv6 support. One day Tor will make use of it.
9615 - Add client-side caching for reverse DNS lookups.
9616 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9617 - When we change nameservers or IP addresses, reset and re-launch
9618 our tests for DNS hijacking.
9620 o Minor features (directory):
9621 - Authorities now specify server versions in networkstatus. This adds
9622 about 2% to the size of compressed networkstatus docs, and allows
9623 clients to tell which servers support BEGIN_DIR and which don't.
9624 The implementation is forward-compatible with a proposed future
9625 protocol version scheme not tied to Tor versions.
9626 - DirServer configuration lines now have an orport= option so
9627 clients can open encrypted tunnels to the authorities without
9628 having downloaded their descriptors yet. Enabled for moria1,
9629 moria2, tor26, and lefkada now in the default configuration.
9630 - Directory servers are more willing to send a 503 "busy" if they
9631 are near their write limit, especially for v1 directory requests.
9632 Now they can use their limited bandwidth for actual Tor traffic.
9633 - Clients track responses with status 503 from dirservers. After a
9634 dirserver has given us a 503, we try not to use it until an hour has
9635 gone by, or until we have no dirservers that haven't given us a 503.
9636 - When we get a 503 from a directory, and we're not a server, we don't
9637 count the failure against the total number of failures allowed
9638 for the thing we're trying to download.
9639 - Report X-Your-Address-Is correctly from tunneled directory
9640 connections; don't report X-Your-Address-Is when it's an internal
9641 address; and never believe reported remote addresses when they're
9643 - Protect against an unlikely DoS attack on directory servers.
9644 - Add a BadDirectory flag to network status docs so that authorities
9645 can (eventually) tell clients about caches they believe to be
9648 o Minor features (controller):
9649 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9650 - Reimplement GETINFO so that info/names stays in sync with the
9652 - Implement "GETINFO fingerprint".
9653 - Implement "SETEVENTS GUARD" so controllers can get updates on
9654 entry guard status as it changes.
9656 o Minor features (clean up obsolete pieces):
9657 - Remove some options that have been deprecated since at least
9658 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9659 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9661 - We no longer look for identity and onion keys in "identity.key" and
9662 "onion.key" -- these were replaced by secret_id_key and
9663 secret_onion_key in 0.0.8pre1.
9664 - We no longer require unrecognized directory entries to be
9667 o Major bugfixes (security):
9668 - Stop sending the HttpProxyAuthenticator string to directory
9669 servers when directory connections are tunnelled through Tor.
9670 - Clients no longer store bandwidth history in the state file.
9671 - Do not log introduction points for hidden services if SafeLogging
9673 - When generating bandwidth history, round down to the nearest
9674 1k. When storing accounting data, round up to the nearest 1k.
9675 - When we're running as a server, remember when we last rotated onion
9676 keys, so that we will rotate keys once they're a week old even if
9677 we never stay up for a week ourselves.
9679 o Major bugfixes (other):
9680 - Fix a longstanding bug in eventdns that prevented the count of
9681 timed-out resolves from ever being reset. This bug caused us to
9682 give up on a nameserver the third time it timed out, and try it
9683 10 seconds later... and to give up on it every time it timed out
9685 - Take out the '5 second' timeout from the connection retry
9686 schedule. Now the first connect attempt will wait a full 10
9687 seconds before switching to a new circuit. Perhaps this will help
9688 a lot. Based on observations from Mike Perry.
9689 - Fix a bug on the Windows implementation of tor_mmap_file() that
9690 would prevent the cached-routers file from ever loading. Reported
9694 - Fix an assert failure when a directory authority sets
9695 AuthDirRejectUnlisted and then receives a descriptor from an
9696 unlisted router. Reported by seeess.
9697 - Avoid a double-free when parsing malformed DirServer lines.
9698 - Fix a bug when a BSD-style PF socket is first used. Patch from
9700 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9701 to resolve an address at a given exit node even when they ask for
9703 - Servers no longer ever list themselves in their "family" line,
9704 even if configured to do so. This makes it easier to configure
9705 family lists conveniently.
9706 - When running as a server, don't fall back to 127.0.0.1 when no
9707 nameservers are configured in /etc/resolv.conf; instead, make the
9708 user fix resolv.conf or specify nameservers explicitly. (Resolves
9710 - Stop accepting certain malformed ports in configured exit policies.
9711 - Don't re-write the fingerprint file every restart, unless it has
9713 - Stop warning when a single nameserver fails: only warn when _all_ of
9714 our nameservers have failed. Also, when we only have one nameserver,
9715 raise the threshold for deciding that the nameserver is dead.
9716 - Directory authorities now only decide that routers are reachable
9717 if their identity keys are as expected.
9718 - When the user uses bad syntax in the Log config line, stop
9719 suggesting other bad syntax as a replacement.
9720 - Correctly detect ipv6 DNS capability on OpenBSD.
9722 o Minor bugfixes (controller):
9723 - Report the circuit number correctly in STREAM CLOSED events. Bug
9724 reported by Mike Perry.
9725 - Do not report bizarre values for results of accounting GETINFOs
9726 when the last second's write or read exceeds the allotted bandwidth.
9727 - Report "unrecognized key" rather than an empty string when the
9728 controller tries to fetch a networkstatus that doesn't exist.
9731 Changes in version 0.1.1.26 - 2006-12-14
9732 o Security bugfixes:
9733 - Stop sending the HttpProxyAuthenticator string to directory
9734 servers when directory connections are tunnelled through Tor.
9735 - Clients no longer store bandwidth history in the state file.
9736 - Do not log introduction points for hidden services if SafeLogging
9740 - Fix an assert failure when a directory authority sets
9741 AuthDirRejectUnlisted and then receives a descriptor from an
9742 unlisted router (reported by seeess).
9745 Changes in version 0.1.2.4-alpha - 2006-12-03
9747 - Add support for using natd; this allows FreeBSDs earlier than
9748 5.1.2 to have ipfw send connections through Tor without using
9749 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9752 - Make all connections to addresses of the form ".noconnect"
9753 immediately get closed. This lets application/controller combos
9754 successfully test whether they're talking to the same Tor by
9755 watching for STREAM events.
9756 - Make cross.sh cross-compilation script work even when autogen.sh
9757 hasn't been run. (Patch from Michael Mohr.)
9758 - Statistics dumped by -USR2 now include a breakdown of public key
9759 operations, for profiling.
9762 - Fix a major leak when directory authorities parse their
9763 approved-routers list, a minor memory leak when we fail to pick
9764 an exit node, and a few rare leaks on errors.
9765 - Handle TransPort connections even when the server sends data before
9766 the client sends data. Previously, the connection would just hang
9767 until the client sent data. (Patch from tup based on patch from
9769 - Avoid assert failure when our cached-routers file is empty on
9773 - Don't log spurious warnings when we see a circuit close reason we
9774 don't recognize; it's probably just from a newer version of Tor.
9775 - Have directory authorities allow larger amounts of drift in uptime
9776 without replacing the server descriptor: previously, a server that
9777 restarted every 30 minutes could have 48 "interesting" descriptors
9779 - Start linking to the Tor specification and Tor reference manual
9780 correctly in the Windows installer.
9781 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9782 Tor/Privoxy we also uninstall Vidalia.
9783 - Resume building on Irix64, and fix a lot of warnings from its
9785 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
9786 when we're running as a client.
9789 Changes in version 0.1.1.25 - 2006-11-04
9791 - When a client asks us to resolve (rather than connect to)
9792 an address, and we have a cached answer, give them the cached
9793 answer. Previously, we would give them no answer at all.
9794 - We were building exactly the wrong circuits when we predict
9795 hidden service requirements, meaning Tor would have to build all
9796 its circuits on demand.
9797 - If none of our live entry guards have a high uptime, but we
9798 require a guard with a high uptime, try adding a new guard before
9799 we give up on the requirement. This patch should make long-lived
9800 connections more stable on average.
9801 - When testing reachability of our DirPort, don't launch new
9802 tests when there's already one in progress -- unreachable
9803 servers were stacking up dozens of testing streams.
9805 o Security bugfixes:
9806 - When the user sends a NEWNYM signal, clear the client-side DNS
9807 cache too. Otherwise we continue to act on previous information.
9810 - Avoid a memory corruption bug when creating a hash table for
9812 - Avoid possibility of controller-triggered crash when misusing
9813 certain commands from a v0 controller on platforms that do not
9814 handle printf("%s",NULL) gracefully.
9815 - Avoid infinite loop on unexpected controller input.
9816 - Don't log spurious warnings when we see a circuit close reason we
9817 don't recognize; it's probably just from a newer version of Tor.
9818 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9819 Tor/Privoxy we also uninstall Vidalia.
9822 Changes in version 0.1.2.3-alpha - 2006-10-29
9824 - Prepare for servers to publish descriptors less often: never
9825 discard a descriptor simply for being too old until either it is
9826 recommended by no authorities, or until we get a better one for
9827 the same router. Make caches consider retaining old recommended
9828 routers for even longer.
9829 - If most authorities set a BadExit flag for a server, clients
9830 don't think of it as a general-purpose exit. Clients only consider
9831 authorities that advertise themselves as listing bad exits.
9832 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9833 headers for content, so that we can work better in the presence of
9834 caching HTTP proxies.
9835 - Allow authorities to list nodes as bad exits by fingerprint or by
9838 o Minor features, controller:
9839 - Add a REASON field to CIRC events; for backward compatibility, this
9840 field is sent only to controllers that have enabled the extended
9841 event format. Also, add additional reason codes to explain why
9842 a given circuit has been destroyed or truncated. (Patches from
9844 - Add a REMOTE_REASON field to extended CIRC events to tell the
9845 controller about why a remote OR told us to close a circuit.
9846 - Stream events also now have REASON and REMOTE_REASON fields,
9847 working much like those for circuit events.
9848 - There's now a GETINFO ns/... field so that controllers can ask Tor
9849 about the current status of a router.
9850 - A new event type "NS" to inform a controller when our opinion of
9851 a router's status has changed.
9852 - Add a GETINFO events/names and GETINFO features/names so controllers
9853 can tell which events and features are supported.
9854 - A new CLEARDNSCACHE signal to allow controllers to clear the
9855 client-side DNS cache without expiring circuits.
9857 o Security bugfixes:
9858 - When the user sends a NEWNYM signal, clear the client-side DNS
9859 cache too. Otherwise we continue to act on previous information.
9862 - Avoid sending junk to controllers or segfaulting when a controller
9863 uses EVENT_NEW_DESC with verbose nicknames.
9864 - Stop triggering asserts if the controller tries to extend hidden
9865 service circuits (reported by mwenge).
9866 - Avoid infinite loop on unexpected controller input.
9867 - When the controller does a "GETINFO network-status", tell it
9868 about even those routers whose descriptors are very old, and use
9869 long nicknames where appropriate.
9870 - Change NT service functions to be loaded on demand. This lets us
9871 build with MinGW without breaking Tor for Windows 98 users.
9872 - Do DirPort reachability tests less often, since a single test
9873 chews through many circuits before giving up.
9874 - In the hidden service example in torrc.sample, stop recommending
9875 esoteric and discouraged hidden service options.
9876 - When stopping an NT service, wait up to 10 sec for it to actually
9877 stop. Patch from Matt Edman; resolves bug 295.
9878 - Fix handling of verbose nicknames with ORCONN controller events:
9879 make them show up exactly when requested, rather than exactly when
9881 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
9882 printing a duplicate "$" in the keys we send (reported by mwenge).
9883 - Correctly set maximum connection limit on Cygwin. (This time
9885 - Try to detect Windows correctly when cross-compiling.
9886 - Detect the size of the routers file correctly even if it is
9887 corrupted (on systems without mmap) or not page-aligned (on systems
9888 with mmap). This bug was harmless.
9889 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
9890 to open a stream fails; now we do in more cases. This should
9891 make clients able to find a good exit faster in some cases, since
9892 unhandleable requests will now get an error rather than timing out.
9893 - Resolve two memory leaks when rebuilding the on-disk router cache
9894 (reported by fookoowa).
9895 - Clean up minor code warnings suggested by the MIPSpro C compiler,
9896 and reported by some Centos users.
9897 - Controller signals now work on non-Unix platforms that don't define
9898 SIGUSR1 and SIGUSR2 the way we expect.
9899 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
9900 values before failing, and always enables eventdns.
9901 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
9902 Try to fix this in configure.in by checking for most functions
9903 before we check for libevent.
9906 Changes in version 0.1.2.2-alpha - 2006-10-07
9908 - Make our async eventdns library on-by-default for Tor servers,
9909 and plan to deprecate the separate dnsworker threads.
9910 - Add server-side support for "reverse" DNS lookups (using PTR
9911 records so clients can determine the canonical hostname for a given
9912 IPv4 address). Only supported by servers using eventdns; servers
9913 now announce in their descriptors whether they support eventdns.
9914 - Specify and implement client-side SOCKS5 interface for reverse DNS
9915 lookups (see doc/socks-extensions.txt).
9916 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
9917 connect to directory servers through Tor. Previously, clients needed
9918 to find Tor exits to make private connections to directory servers.
9919 - Avoid choosing Exit nodes for entry or middle hops when the
9920 total bandwidth available from non-Exit nodes is much higher than
9921 the total bandwidth available from Exit nodes.
9922 - Workaround for name servers (like Earthlink's) that hijack failing
9923 DNS requests and replace the no-such-server answer with a "helpful"
9924 redirect to an advertising-driven search portal. Also work around
9925 DNS hijackers who "helpfully" decline to hijack known-invalid
9926 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
9927 lets you turn it off.
9928 - Send out a burst of long-range padding cells once we've established
9929 that we're reachable. Spread them over 4 circuits, so hopefully
9930 a few will be fast. This exercises our bandwidth and bootstraps
9931 us into the directory more quickly.
9933 o New/improved config options:
9934 - Add new config option "ResolvConf" to let the server operator
9935 choose an alternate resolve.conf file when using eventdns.
9936 - Add an "EnforceDistinctSubnets" option to control our "exclude
9937 servers on the same /16" behavior. It's still on by default; this
9938 is mostly for people who want to operate private test networks with
9939 all the machines on the same subnet.
9940 - If one of our entry guards is on the ExcludeNodes list, or the
9941 directory authorities don't think it's a good guard, treat it as
9942 if it were unlisted: stop using it as a guard, and throw it off
9943 the guards list if it stays that way for a long time.
9944 - Allow directory authorities to be marked separately as authorities
9945 for the v1 directory protocol, the v2 directory protocol, and
9946 as hidden service directories, to make it easier to retire old
9947 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9948 to continue being hidden service authorities too.
9949 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9951 o Minor features, controller:
9952 - Fix CIRC controller events so that controllers can learn the
9953 identity digests of non-Named servers used in circuit paths.
9954 - Let controllers ask for more useful identifiers for servers. Instead
9955 of learning identity digests for un-Named servers and nicknames
9956 for Named servers, the new identifiers include digest, nickname,
9957 and indication of Named status. Off by default; see control-spec.txt
9958 for more information.
9959 - Add a "getinfo address" controller command so it can display Tor's
9960 best guess to the user.
9961 - New controller event to alert the controller when our server
9962 descriptor has changed.
9963 - Give more meaningful errors on controller authentication failure.
9965 o Minor features, other:
9966 - When asked to resolve a hostname, don't use non-exit servers unless
9967 requested to do so. This allows servers with broken DNS to be
9968 useful to the network.
9969 - Divide eventdns log messages into warn and info messages.
9970 - Reserve the nickname "Unnamed" for routers that can't pick
9971 a hostname: any router can call itself Unnamed; directory
9972 authorities will never allocate Unnamed to any particular router;
9973 clients won't believe that any router is the canonical Unnamed.
9974 - Only include function names in log messages for info/debug messages.
9975 For notice/warn/err, the content of the message should be clear on
9976 its own, and printing the function name only confuses users.
9977 - Avoid some false positives during reachability testing: don't try
9978 to test via a server that's on the same /24 as us.
9979 - If we fail to build a circuit to an intended enclave, and it's
9980 not mandatory that we use that enclave, stop wanting it.
9981 - When eventdns is enabled, allow multithreaded builds on NetBSD and
9982 OpenBSD. (We had previously disabled threads on these platforms
9983 because they didn't have working thread-safe resolver functions.)
9985 o Major bugfixes, anonymity/security:
9986 - If a client asked for a server by name, and there's a named server
9987 in our network-status but we don't have its descriptor yet, we
9988 could return an unnamed server instead.
9989 - Fix NetBSD bug that could allow someone to force uninitialized RAM
9990 to be sent to a server's DNS resolver. This only affects NetBSD
9991 and other platforms that do not bounds-check tolower().
9992 - Reject (most) attempts to use Tor circuits with length one. (If
9993 many people start using Tor as a one-hop proxy, exit nodes become
9994 a more attractive target for compromise.)
9995 - Just because your DirPort is open doesn't mean people should be
9996 able to remotely teach you about hidden service descriptors. Now
9997 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9999 o Major bugfixes, other:
10000 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10001 - When a client asks the server to resolve (not connect to)
10002 an address, and it has a cached answer, give them the cached answer.
10003 Previously, the server would give them no answer at all.
10004 - Allow really slow clients to not hang up five minutes into their
10005 directory downloads (suggested by Adam J. Richter).
10006 - We were building exactly the wrong circuits when we anticipated
10007 hidden service requirements, meaning Tor would have to build all
10008 its circuits on demand.
10009 - Avoid crashing when we mmap a router cache file of size 0.
10010 - When testing reachability of our DirPort, don't launch new
10011 tests when there's already one in progress -- unreachable
10012 servers were stacking up dozens of testing streams.
10014 o Minor bugfixes, correctness:
10015 - If we're a directory mirror and we ask for "all" network status
10016 documents, we would discard status documents from authorities
10017 we don't recognize.
10018 - Avoid a memory corruption bug when creating a hash table for
10020 - Avoid controller-triggered crash when misusing certain commands
10021 from a v0 controller on platforms that do not handle
10022 printf("%s",NULL) gracefully.
10023 - Don't crash when a controller sends a third argument to an
10024 "extendcircuit" request.
10025 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10026 response; fix error code when "getinfo dir/status/" fails.
10027 - Avoid crash when telling controller stream-status and a stream
10029 - Patch from Adam Langley to fix assert() in eventdns.c.
10030 - Fix a debug log message in eventdns to say "X resolved to Y"
10031 instead of "X resolved to X".
10032 - Make eventdns give strings for DNS errors, not just error numbers.
10033 - Track unreachable entry guards correctly: don't conflate
10034 'unreachable by us right now' with 'listed as down by the directory
10035 authorities'. With the old code, if a guard was unreachable by
10036 us but listed as running, it would clog our guard list forever.
10037 - Behave correctly in case we ever have a network with more than
10038 2GB/s total advertised capacity.
10039 - Make TrackExitHosts case-insensitive, and fix the behavior of
10040 ".suffix" TrackExitHosts items to avoid matching in the middle of
10042 - Finally fix the openssl warnings from newer gccs that believe that
10043 ignoring a return value is okay, but casting a return value and
10044 then ignoring it is a sign of madness.
10045 - Prevent the contrib/exitlist script from printing the same
10046 result more than once.
10047 - Patch from Steve Hildrey: Generate network status correctly on
10048 non-versioning dirservers.
10049 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10050 via Tor; otherwise you'll think you're the exit node's IP address.
10052 o Minor bugfixes, performance:
10053 - Two small performance improvements on parsing descriptors.
10054 - Major performance improvement on inserting descriptors: change
10055 algorithm from O(n^2) to O(n).
10056 - Make the common memory allocation path faster on machines where
10057 malloc(0) returns a pointer.
10058 - Start remembering X-Your-Address-Is directory hints even if you're
10059 a client, so you can become a server more smoothly.
10060 - Avoid duplicate entries on MyFamily line in server descriptor.
10062 o Packaging, features:
10063 - Remove architecture from OS X builds. The official builds are
10064 now universal binaries.
10065 - The Debian package now uses --verify-config when (re)starting,
10066 to distinguish configuration errors from other errors.
10067 - Update RPMs to require libevent 1.1b.
10069 o Packaging, bugfixes:
10070 - Patches so Tor builds with MinGW on Windows.
10071 - Patches so Tor might run on Cygwin again.
10072 - Resume building on non-gcc compilers and ancient gcc. Resume
10073 building with the -O0 compile flag. Resume building cleanly on
10075 - Run correctly on OS X platforms with case-sensitive filesystems.
10076 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10077 - Add autoconf checks so Tor can build on Solaris x86 again.
10080 - Documented (and renamed) ServerDNSSearchDomains and
10081 ServerDNSResolvConfFile options.
10082 - Be clearer that the *ListenAddress directives can be repeated
10086 Changes in version 0.1.1.24 - 2006-09-29
10088 - Allow really slow clients to not hang up five minutes into their
10089 directory downloads (suggested by Adam J. Richter).
10090 - Fix major performance regression from 0.1.0.x: instead of checking
10091 whether we have enough directory information every time we want to
10092 do something, only check when the directory information has changed.
10093 This should improve client CPU usage by 25-50%.
10094 - Don't crash if, after a server has been running for a while,
10095 it can't resolve its hostname.
10098 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10099 - Don't crash when the controller receives a third argument to an
10100 "extendcircuit" request.
10101 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10102 response; fix error code when "getinfo dir/status/" fails.
10103 - Fix configure.in to not produce broken configure files with
10104 more recent versions of autoconf. Thanks to Clint for his auto*
10106 - Fix security bug on NetBSD that could allow someone to force
10107 uninitialized RAM to be sent to a server's DNS resolver. This
10108 only affects NetBSD and other platforms that do not bounds-check
10110 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10111 methods: these are known to be buggy.
10112 - If we're a directory mirror and we ask for "all" network status
10113 documents, we would discard status documents from authorities
10114 we don't recognize.
10117 Changes in version 0.1.2.1-alpha - 2006-08-27
10119 - Add "eventdns" async dns library from Adam Langley, tweaked to
10120 build on OSX and Windows. Only enabled if you pass the
10121 --enable-eventdns argument to configure.
10122 - Allow servers with no hostname or IP address to learn their
10123 IP address by asking the directory authorities. This code only
10124 kicks in when you would normally have exited with a "no address"
10125 error. Nothing's authenticated, so use with care.
10126 - Rather than waiting a fixed amount of time between retrying
10127 application connections, we wait only 5 seconds for the first,
10128 10 seconds for the second, and 15 seconds for each retry after
10129 that. Hopefully this will improve the expected user experience.
10130 - Patch from Tup to add support for transparent AP connections:
10131 this basically bundles the functionality of trans-proxy-tor
10132 into the Tor mainline. Now hosts with compliant pf/netfilter
10133 implementations can redirect TCP connections straight to Tor
10134 without diverting through SOCKS. Needs docs.
10135 - Busy directory servers save lots of memory by spooling server
10136 descriptors, v1 directories, and v2 networkstatus docs to buffers
10137 as needed rather than en masse. Also mmap the cached-routers
10138 files, so we don't need to keep the whole thing in memory too.
10139 - Automatically avoid picking more than one node from the same
10140 /16 network when constructing a circuit.
10141 - Revise and clean up the torrc.sample that we ship with; add
10142 a section for BandwidthRate and BandwidthBurst.
10145 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10146 split connection_t into edge, or, dir, control, and base structs.
10147 These will save quite a bit of memory on busy servers, and they'll
10148 also help us track down bugs in the code and bugs in the spec.
10149 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10150 or later. Log when we are doing this, so we can diagnose it when
10151 it fails. (Also, recommend libevent 1.1b for kqueue and
10152 win32 methods; deprecate libevent 1.0b harder; make libevent
10153 recommendation system saner.)
10154 - Start being able to build universal binaries on OS X (thanks
10156 - Export the default exit policy via the control port, so controllers
10157 don't need to guess what it is / will be later.
10158 - Add a man page entry for ProtocolWarnings.
10159 - Add TestVia config option to the man page.
10160 - Remove even more protocol-related warnings from Tor server logs,
10161 such as bad TLS handshakes and malformed begin cells.
10162 - Stop fetching descriptors if you're not a dir mirror and you
10163 haven't tried to establish any circuits lately. [This currently
10164 causes some dangerous behavior, because when you start up again
10165 you'll use your ancient server descriptors.]
10166 - New DirPort behavior: if you have your dirport set, you download
10167 descriptors aggressively like a directory mirror, whether or not
10168 your ORPort is set.
10169 - Get rid of the router_retry_connections notion. Now routers
10170 no longer try to rebuild long-term connections to directory
10171 authorities, and directory authorities no longer try to rebuild
10172 long-term connections to all servers. We still don't hang up
10173 connections in these two cases though -- we need to look at it
10174 more carefully to avoid flapping, and we likely need to wait til
10175 0.1.1.x is obsolete.
10176 - Drop compatibility with obsolete Tors that permit create cells
10177 to have the wrong circ_id_type.
10178 - Re-enable per-connection rate limiting. Get rid of the "OP
10179 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10180 separate global buckets that apply depending on what sort of conn
10182 - Start publishing one minute or so after we find our ORPort
10183 to be reachable. This will help reduce the number of descriptors
10184 we have for ourselves floating around, since it's quite likely
10185 other things (e.g. DirPort) will change during that minute too.
10186 - Fork the v1 directory protocol into its own spec document,
10187 and mark dir-spec.txt as the currently correct (v2) spec.
10190 - When we find our DirPort to be reachable, publish a new descriptor
10191 so we'll tell the world (reported by pnx).
10192 - Publish a new descriptor after we hup/reload. This is important
10193 if our config has changed such that we'll want to start advertising
10194 our DirPort now, etc.
10195 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10196 - When we have a state file we cannot parse, tell the user and
10197 move it aside. Now we avoid situations where the user starts
10198 Tor in 1904, Tor writes a state file with that timestamp in it,
10199 the user fixes her clock, and Tor refuses to start.
10200 - Fix configure.in to not produce broken configure files with
10201 more recent versions of autoconf. Thanks to Clint for his auto*
10203 - "tor --verify-config" now exits with -1(255) or 0 depending on
10204 whether the config options are bad or good.
10205 - Resolve bug 321 when using dnsworkers: append a period to every
10206 address we resolve at the exit node, so that we do not accidentally
10207 pick up local addresses, and so that failing searches are retried
10208 in the resolver search domains. (This is already solved for
10209 eventdns.) (This breaks Blossom servers for now.)
10210 - If we are using an exit enclave and we can't connect, e.g. because
10211 its webserver is misconfigured to not listen on localhost, then
10212 back off and try connecting from somewhere else before we fail.
10215 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10216 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10217 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10218 when the IP address is mapped through MapAddress to a hostname.
10219 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10220 useless IPv6 DNS resolves.
10221 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10222 before we execute the signal, in case the signal shuts us down.
10223 - Clean up AllowInvalidNodes man page entry.
10224 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10225 - Add more asserts to track down an assert error on a windows Tor
10226 server with connection_add being called with socket == -1.
10227 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10228 - Fix misleading log messages: an entry guard that is "unlisted",
10229 as well as not known to be "down" (because we've never heard
10230 of it), is not therefore "up".
10231 - Remove code to special-case "-cvs" ending, since it has not
10232 actually mattered since 0.0.9.
10233 - Make our socks5 handling more robust to broken socks clients:
10234 throw out everything waiting on the buffer in between socks
10235 handshake phases, since they can't possibly (so the theory
10236 goes) have predicted what we plan to respond to them.
10239 Changes in version 0.1.1.23 - 2006-07-30
10241 - Fast Tor servers, especially exit nodes, were triggering asserts
10242 due to a bug in handling the list of pending DNS resolves. Some
10243 bugs still remain here; we're hunting them.
10244 - Entry guards could crash clients by sending unexpected input.
10245 - More fixes on reachability testing: if you find yourself reachable,
10246 then don't ever make any client requests (so you stop predicting
10247 circuits), then hup or have your clock jump, then later your IP
10248 changes, you won't think circuits are working, so you won't try to
10249 test reachability, so you won't publish.
10252 - Avoid a crash if the controller does a resetconf firewallports
10253 and then a setconf fascistfirewall=1.
10254 - Avoid an integer underflow when the dir authority decides whether
10255 a router is stable: we might wrongly label it stable, and compute
10256 a slightly wrong median stability, when a descriptor is published
10258 - Fix a place where we might trigger an assert if we can't build our
10259 own server descriptor yet.
10262 Changes in version 0.1.1.22 - 2006-07-05
10264 - Fix a big bug that was causing servers to not find themselves
10265 reachable if they changed IP addresses. Since only 0.1.1.22+
10266 servers can do reachability testing correctly, now we automatically
10267 make sure to test via one of these.
10268 - Fix to allow clients and mirrors to learn directory info from
10269 descriptor downloads that get cut off partway through.
10270 - Directory authorities had a bug in deciding if a newly published
10271 descriptor was novel enough to make everybody want a copy -- a few
10272 servers seem to be publishing new descriptors many times a minute.
10274 - Fix a rare bug that was causing some servers to complain about
10275 "closing wedged cpuworkers" and skip some circuit create requests.
10276 - Make the Exit flag in directory status documents actually work.
10279 Changes in version 0.1.1.21 - 2006-06-10
10280 o Crash and assert fixes from 0.1.1.20:
10281 - Fix a rare crash on Tor servers that have enabled hibernation.
10282 - Fix a seg fault on startup for Tor networks that use only one
10283 directory authority.
10284 - Fix an assert from a race condition that occurs on Tor servers
10285 while exiting, where various threads are trying to log that they're
10286 exiting, and delete the logs, at the same time.
10287 - Make our unit tests pass again on certain obscure platforms.
10290 - Add support for building SUSE RPM packages.
10291 - Speed up initial bootstrapping for clients: if we are making our
10292 first ever connection to any entry guard, then don't mark it down
10294 - When only one Tor server in the network is labelled as a guard,
10295 and we've already picked him, we would cycle endlessly picking him
10296 again, being unhappy about it, etc. Now we specifically exclude
10297 current guards when picking a new guard.
10298 - Servers send create cells more reliably after the TLS connection
10299 is established: we were sometimes forgetting to send half of them
10300 when we had more than one pending.
10301 - If we get a create cell that asks us to extend somewhere, but the
10302 Tor server there doesn't match the expected digest, we now send
10303 a destroy cell back, rather than silently doing nothing.
10304 - Make options->RedirectExit work again.
10305 - Make cookie authentication for the controller work again.
10306 - Stop being picky about unusual characters in the arguments to
10307 mapaddress. It's none of our business.
10308 - Add a new config option "TestVia" that lets you specify preferred
10309 middle hops to use for test circuits. Perhaps this will let me
10310 debug the reachability problems better.
10312 o Log / documentation fixes:
10313 - If we're a server and some peer has a broken TLS certificate, don't
10314 log about it unless ProtocolWarnings is set, i.e., we want to hear
10315 about protocol violations by others.
10316 - Fix spelling of VirtualAddrNetwork in man page.
10317 - Add a better explanation at the top of the autogenerated torrc file
10318 about what happened to our old torrc.
10321 Changes in version 0.1.1.20 - 2006-05-23
10323 - Downgrade a log severity where servers complain that they're
10325 - Avoid a compile warning on FreeBSD.
10326 - Remove string size limit on NEWDESC messages; solve bug 291.
10327 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10328 more thoroughly when we're running on windows.
10331 Changes in version 0.1.1.19-rc - 2006-05-03
10333 - Regenerate our local descriptor if it's dirty and we try to use
10334 it locally (e.g. if it changes during reachability detection).
10335 - If we setconf our ORPort to 0, we continued to listen on the
10336 old ORPort and receive connections.
10337 - Avoid a second warning about machine/limits.h on Debian
10339 - Be willing to add our own routerinfo into the routerlist.
10340 Now authorities will include themselves in their directories
10341 and network-statuses.
10342 - Stop trying to upload rendezvous descriptors to every
10343 directory authority: only try the v1 authorities.
10344 - Servers no longer complain when they think they're not
10345 registered with the directory authorities. There were too many
10347 - Backport dist-rpm changes so rpms can be built without errors.
10350 - Implement an option, VirtualAddrMask, to set which addresses
10351 get handed out in response to mapaddress requests. This works
10352 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10355 Changes in version 0.1.1.18-rc - 2006-04-10
10357 - Work harder to download live network-statuses from all the
10358 directory authorities we know about. Improve the threshold
10359 decision logic so we're more robust to edge cases.
10360 - When fetching rendezvous descriptors, we were willing to ask
10361 v2 authorities too, which would always return 404.
10364 - Stop listing down or invalid nodes in the v1 directory. This will
10365 reduce its bulk by about 1/3, and reduce load on directory
10367 - When deciding whether a router is Fast or Guard-worthy, consider
10368 his advertised BandwidthRate and not just the BandwidthCapacity.
10369 - No longer ship INSTALL and README files -- they are useless now.
10370 - Force rpmbuild to behave and honor target_cpu.
10371 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10372 - Start to include translated versions of the tor-doc-*.html
10373 files, along with the screenshots. Still needs more work.
10374 - Start sending back 512 and 451 errors if mapaddress fails,
10375 rather than not sending anything back at all.
10376 - When we fail to bind or listen on an incoming or outgoing
10377 socket, we should close it before failing. otherwise we just
10378 leak it. (thanks to weasel for finding.)
10379 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10380 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10381 - Make NoPublish (even though deprecated) work again.
10382 - Fix a minor security flaw where a versioning auth dirserver
10383 could list a recommended version many times in a row to make
10384 clients more convinced that it's recommended.
10385 - Fix crash bug if there are two unregistered servers running
10386 with the same nickname, one of them is down, and you ask for
10387 them by nickname in your EntryNodes or ExitNodes. Also, try
10388 to pick the one that's running rather than an arbitrary one.
10389 - Fix an infinite loop we could hit if we go offline for too long.
10390 - Complain when we hit WSAENOBUFS on recv() or write() too.
10391 Perhaps this will help us hunt the bug.
10392 - If you're not a versioning dirserver, don't put the string
10393 "client-versions \nserver-versions \n" in your network-status.
10394 - Lower the minimum required number of file descriptors to 1000,
10395 so we can have some overhead for Valgrind on Linux, where the
10396 default ulimit -n is 1024.
10399 - Add tor.dizum.com as the fifth authoritative directory server.
10400 - Add a new config option FetchUselessDescriptors, off by default,
10401 for when you plan to run "exitlist" on your client and you want
10402 to know about even the non-running descriptors.
10405 Changes in version 0.1.1.17-rc - 2006-03-28
10407 - Clients and servers since 0.1.1.10-alpha have been expiring
10408 connections whenever they are idle for 5 minutes and they *do*
10409 have circuits on them. Oops. With this new version, clients will
10410 discard their previous entry guard choices and avoid choosing
10411 entry guards running these flawed versions.
10412 - Fix memory leak when uncompressing concatenated zlib streams. This
10413 was causing substantial leaks over time on Tor servers.
10414 - The v1 directory was including servers as much as 48 hours old,
10415 because that's how the new routerlist->routers works. Now only
10416 include them if they're 20 hours old or less.
10419 - Resume building on irix64, netbsd 2.0, etc.
10420 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10422 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10423 and it is confusing some users.
10424 - Mirrors stop caching the v1 directory so often.
10425 - Make the max number of old descriptors that a cache will hold
10426 rise with the number of directory authorities, so we can scale.
10427 - Change our win32 uname() hack to be more forgiving about what
10428 win32 versions it thinks it's found.
10431 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
10433 - When the controller's *setconf commands fail, collect an error
10434 message in a string and hand it back to the controller.
10435 - Make the v2 dir's "Fast" flag based on relative capacity, just
10436 like "Stable" is based on median uptime. Name everything in the
10437 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10438 - Log server fingerprint on startup, so new server operators don't
10439 have to go hunting around their filesystem for it.
10440 - Return a robots.txt on our dirport to discourage google indexing.
10441 - Let the controller ask for GETINFO dir/status/foo so it can ask
10442 directly rather than connecting to the dir port. Only works when
10443 dirport is set for now.
10445 o New config options rather than constants in the code:
10446 - SocksTimeout: How long do we let a socks connection wait
10447 unattached before we fail it?
10448 - CircuitBuildTimeout: Cull non-open circuits that were born
10449 at least this many seconds ago.
10450 - CircuitIdleTimeout: Cull open clean circuits that were born
10451 at least this many seconds ago.
10454 Changes in version 0.1.1.16-rc - 2006-03-18
10455 o Bugfixes on 0.1.1.15-rc:
10456 - Fix assert when the controller asks to attachstream a connect-wait
10457 or resolve-wait stream.
10458 - Now do address rewriting when the controller asks us to attach
10459 to a particular circuit too. This will let Blossom specify
10460 "moria2.exit" without having to learn what moria2's IP address is.
10461 - Make the "tor --verify-config" command-line work again, so people
10462 can automatically check if their torrc will parse.
10463 - Authoritative dirservers no longer require an open connection from
10464 a server to consider him "reachable". We need this change because
10465 when we add new auth dirservers, old servers won't know not to
10467 - Let Tor build on Sun CC again.
10468 - Fix an off-by-one buffer size in dirserv.c that magically never
10469 hit our three authorities but broke sjmurdoch's own tor network.
10470 - If we as a directory mirror don't know of any v1 directory
10471 authorities, then don't try to cache any v1 directories.
10472 - Stop warning about unknown servers in our family when they are
10473 given as hex digests.
10474 - Stop complaining as quickly to the server operator that he
10475 hasn't registered his nickname/key binding.
10476 - Various cleanups so we can add new V2 Auth Dirservers.
10477 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10478 reflect the updated flags in our v2 dir protocol.
10479 - Resume allowing non-printable characters for exit streams (both
10480 for connecting and for resolving). Now we tolerate applications
10481 that don't follow the RFCs. But continue to block malformed names
10484 o Bugfixes on 0.1.0.x:
10485 - Fix assert bug in close_logs(): when we close and delete logs,
10486 remove them all from the global "logfiles" list.
10487 - Fix minor integer overflow in calculating when we expect to use up
10488 our bandwidth allocation before hibernating.
10489 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10490 there are multiple SSLs installed with different versions.
10491 - When we try to be a server and Address is not explicitly set and
10492 our hostname resolves to a private IP address, try to use an
10493 interface address if it has a public address. Now Windows machines
10494 that think of themselves as localhost can work by default.
10497 - Let the controller ask for GETINFO dir/server/foo so it can ask
10498 directly rather than connecting to the dir port.
10499 - Let the controller tell us about certain router descriptors
10500 that it doesn't want Tor to use in circuits. Implement
10501 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10502 - New config option SafeSocks to reject all application connections
10503 using unsafe socks protocols. Defaults to off.
10506 Changes in version 0.1.1.15-rc - 2006-03-11
10507 o Bugfixes and cleanups:
10508 - When we're printing strings from the network, don't try to print
10509 non-printable characters. This protects us against shell escape
10510 sequence exploits, and also against attacks to fool humans into
10511 misreading their logs.
10512 - Fix a bug where Tor would fail to establish any connections if you
10513 left it off for 24 hours and then started it: we were happy with
10514 the obsolete network statuses, but they all referred to router
10515 descriptors that were too old to fetch, so we ended up with no
10516 valid router descriptors.
10517 - Fix a seg fault in the controller's "getinfo orconn-status"
10518 command while listing status on incoming handshaking connections.
10519 Introduce a status name "NEW" for these connections.
10520 - If we get a linelist or linelist_s config option from the torrc
10521 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10522 silently resetting it to its default.
10523 - Don't abandon entry guards until they've been down or gone for
10525 - Cleaner and quieter log messages.
10528 - New controller signal NEWNYM that makes new application requests
10529 use clean circuits.
10530 - Add a new circuit purpose 'controller' to let the controller ask
10531 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10532 controller command to let you specify the purpose if you're
10533 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10534 command to let you change a circuit's purpose after it's been
10536 - Accept "private:*" in routerdesc exit policies; not generated yet
10537 because older Tors do not understand it.
10538 - Add BSD-style contributed startup script "rc.subr" from Peter
10542 Changes in version 0.1.1.14-alpha - 2006-02-20
10543 o Bugfixes on 0.1.1.x:
10544 - Don't die if we ask for a stdout or stderr log (even implicitly)
10545 and we're set to RunAsDaemon -- just warn.
10546 - We still had a few bugs in the OR connection rotation code that
10547 caused directory servers to slowly aggregate connections to other
10548 fast Tor servers. This time for sure!
10549 - Make log entries on Win32 include the name of the function again.
10550 - We were treating a pair of exit policies if they were equal even
10551 if one said accept and the other said reject -- causing us to
10552 not always publish a new descriptor since we thought nothing
10554 - Retry pending server downloads as well as pending networkstatus
10555 downloads when we unexpectedly get a socks request.
10556 - We were ignoring the IS_FAST flag in the directory status,
10557 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10559 - If the controller's SAVECONF command fails (e.g. due to file
10560 permissions), let the controller know that it failed.
10563 - If we're trying to be a Tor server and running Windows 95/98/ME
10564 as a server, explain that we'll likely crash.
10565 - When we're a server, a client asks for an old-style directory,
10566 and our write bucket is empty, don't give it to him. This way
10567 small servers can continue to serve the directory *sometimes*,
10568 without getting overloaded.
10569 - Compress exit policies even more -- look for duplicate lines
10571 - Clients now honor the "guard" flag in the router status when
10572 picking entry guards, rather than looking at is_fast or is_stable.
10573 - Retain unrecognized lines in $DATADIR/state file, so that we can
10574 be forward-compatible.
10575 - Generate 18.0.0.0/8 address policy format in descs when we can;
10576 warn when the mask is not reducible to a bit-prefix.
10577 - Let the user set ControlListenAddress in the torrc. This can be
10578 dangerous, but there are some cases (like a secured LAN) where it
10580 - Split ReachableAddresses into ReachableDirAddresses and
10581 ReachableORAddresses, so we can restrict Dir conns to port 80
10582 and OR conns to port 443.
10583 - Now we can target arch and OS in rpm builds (contributed by
10584 Phobos). Also make the resulting dist-rpm filename match the
10586 - New config options to help controllers: FetchServerDescriptors
10587 and FetchHidServDescriptors for whether to fetch server
10588 info and hidserv info or let the controller do it, and
10589 PublishServerDescriptor and PublishHidServDescriptors.
10590 - Also let the controller set the __AllDirActionsPrivate config
10591 option if you want all directory fetches/publishes to happen via
10592 Tor (it assumes your controller bootstraps your circuits).
10595 Changes in version 0.1.0.17 - 2006-02-17
10596 o Crash bugfixes on 0.1.0.x:
10597 - When servers with a non-zero DirPort came out of hibernation,
10598 sometimes they would trigger an assert.
10600 o Other important bugfixes:
10601 - On platforms that don't have getrlimit (like Windows), we were
10602 artificially constraining ourselves to a max of 1024
10603 connections. Now just assume that we can handle as many as 15000
10604 connections. Hopefully this won't cause other problems.
10606 o Backported features:
10607 - When we're a server, a client asks for an old-style directory,
10608 and our write bucket is empty, don't give it to him. This way
10609 small servers can continue to serve the directory *sometimes*,
10610 without getting overloaded.
10611 - Whenever you get a 503 in response to a directory fetch, try
10612 once more. This will become important once servers start sending
10613 503's whenever they feel busy.
10614 - Fetch a new directory every 120 minutes, not every 40 minutes.
10615 Now that we have hundreds of thousands of users running the old
10616 directory algorithm, it's starting to hurt a lot.
10617 - Bump up the period for forcing a hidden service descriptor upload
10618 from 20 minutes to 1 hour.
10621 Changes in version 0.1.1.13-alpha - 2006-02-09
10622 o Crashes in 0.1.1.x:
10623 - When you tried to setconf ORPort via the controller, Tor would
10624 crash. So people using TorCP to become a server were sad.
10625 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10626 servers. The problem appears to be something do with OpenSSL's
10627 random number generation, or how we call it, or something. Let me
10628 know if the crashes continue.
10629 - Turn crypto hardware acceleration off by default, until we find
10630 somebody smart who can test it for us. (It appears to produce
10631 seg faults in at least some cases.)
10632 - Fix a rare assert error when we've tried all intro points for
10633 a hidden service and we try fetching the service descriptor again:
10634 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10637 - Fix a major load balance bug: we were round-robining in 16 KB
10638 chunks, and servers with bandwidthrate of 20 KB, while downloading
10639 a 600 KB directory, would starve their other connections. Now we
10640 try to be a bit more fair.
10641 - Dir authorities and mirrors were never expiring the newest
10642 descriptor for each server, causing memory and directory bloat.
10643 - Fix memory-bloating and connection-bloating bug on servers: We
10644 were never closing any connection that had ever had a circuit on
10645 it, because we were checking conn->n_circuits == 0, yet we had a
10646 bug that let it go negative.
10647 - Make Tor work using squid as your http proxy again -- squid
10648 returns an error if you ask for a URL that's too long, and it uses
10649 a really generic error message. Plus, many people are behind a
10650 transparent squid so they don't even realize it.
10651 - On platforms that don't have getrlimit (like Windows), we were
10652 artificially constraining ourselves to a max of 1024
10653 connections. Now just assume that we can handle as many as 15000
10654 connections. Hopefully this won't cause other problems.
10655 - Add a new config option ExitPolicyRejectPrivate which defaults to
10656 1. This means all exit policies will begin with rejecting private
10657 addresses, unless the server operator explicitly turns it off.
10660 - Clients no longer download descriptors for non-running
10662 - Before we add new directory authorities, we should make it
10663 clear that only v1 authorities should receive/publish hidden
10664 service descriptors.
10667 - As soon as we've fetched some more directory info, immediately
10668 try to download more server descriptors. This way we don't have
10669 a 10 second pause during initial bootstrapping.
10670 - Remove even more loud log messages that the server operator can't
10672 - When we're running an obsolete or un-recommended version, make
10673 the log message more clear about what the problem is and what
10674 versions *are* still recommended.
10675 - Provide a more useful warn message when our onion queue gets full:
10676 the CPU is too slow or the exit policy is too liberal.
10677 - Don't warn when we receive a 503 from a dirserver/cache -- this
10678 will pave the way for them being able to refuse if they're busy.
10679 - When we fail to bind a listener, try to provide a more useful
10680 log message: e.g., "Is Tor already running?"
10681 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10682 Goldberg can prove things about our handshake protocol more
10684 - MaxConn has been obsolete for a while now. Document the ConnLimit
10685 config option, which is a *minimum* number of file descriptors
10686 that must be available else Tor refuses to start.
10687 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10688 if you log to syslog and want something other than LOG_DAEMON.
10689 - Make dirservers generate a separate "guard" flag to mean,
10690 "would make a good entry guard". Make clients parse it and vote
10691 on it. Not used by clients yet.
10692 - Implement --with-libevent-dir option to ./configure. Also, improve
10693 search techniques to find libevent, and use those for openssl too.
10694 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10695 - Only start testing reachability once we've established a
10696 circuit. This will make startup on dirservers less noisy.
10697 - Don't try to upload hidden service descriptors until we have
10698 established a circuit.
10699 - Fix the controller's "attachstream 0" command to treat conn like
10700 it just connected, doing address remapping, handling .exit and
10701 .onion idioms, and so on. Now we're more uniform in making sure
10702 that the controller hears about new and closing connections.
10705 Changes in version 0.1.1.12-alpha - 2006-01-11
10706 o Bugfixes on 0.1.1.x:
10707 - The fix to close duplicate server connections was closing all
10708 Tor client connections if they didn't establish a circuit
10709 quickly enough. Oops.
10710 - Fix minor memory issue (double-free) that happened on exit.
10712 o Bugfixes on 0.1.0.x:
10713 - Tor didn't warn when it failed to open a log file.
10716 Changes in version 0.1.1.11-alpha - 2006-01-10
10717 o Crashes in 0.1.1.x:
10718 - Include all the assert/crash fixes from 0.1.0.16.
10719 - If you start Tor and then quit very quickly, there were some
10720 races that tried to free things that weren't allocated yet.
10721 - Fix a rare memory stomp if you're running hidden services.
10722 - Fix segfault when specifying DirServer in config without nickname.
10723 - Fix a seg fault when you finish connecting to a server but at
10724 that moment you dump his server descriptor.
10725 - Extendcircuit and Attachstream controller commands would
10726 assert/crash if you don't give them enough arguments.
10727 - Fix an assert error when we're out of space in the connection_list
10728 and we try to post a hidden service descriptor (reported by weasel).
10729 - If you specify a relative torrc path and you set RunAsDaemon in
10730 your torrc, then it chdir()'s to the new directory. If you HUP,
10731 it tries to load the new torrc location, fails, and exits.
10732 The fix: no longer allow a relative path to torrc using -f.
10735 - Implement "entry guards": automatically choose a handful of entry
10736 nodes and stick with them for all circuits. Only pick new guards
10737 when the ones you have are unsuitable, and if the old guards
10738 become suitable again, switch back. This will increase security
10739 dramatically against certain end-point attacks. The EntryNodes
10740 config option now provides some hints about which entry guards you
10741 want to use most; and StrictEntryNodes means to only use those.
10742 - New directory logic: download by descriptor digest, not by
10743 fingerprint. Caches try to download all listed digests from
10744 authorities; clients try to download "best" digests from caches.
10745 This avoids partitioning and isolating attacks better.
10746 - Make the "stable" router flag in network-status be the median of
10747 the uptimes of running valid servers, and make clients pay
10748 attention to the network-status flags. Thus the cutoff adapts
10749 to the stability of the network as a whole, making IRC, IM, etc
10750 connections more reliable.
10753 - Tor servers with dynamic IP addresses were needing to wait 18
10754 hours before they could start doing reachability testing using
10755 the new IP address and ports. This is because they were using
10756 the internal descriptor to learn what to test, yet they were only
10757 rebuilding the descriptor once they decided they were reachable.
10758 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
10759 to download certain server descriptors, throw them away, and then
10760 fetch them again after 30 minutes. Now mirrors throw away these
10761 server descriptors so clients can't get them.
10762 - We were leaving duplicate connections to other ORs open for a week,
10763 rather than closing them once we detect a duplicate. This only
10764 really affected authdirservers, but it affected them a lot.
10765 - Spread the authdirservers' reachability testing over the entire
10766 testing interval, so we don't try to do 500 TLS's at once every
10770 - If the network is down, and we try to connect to a conn because
10771 we have a circuit in mind, and we timeout (30 seconds) because the
10772 network never answers, we were expiring the circuit, but we weren't
10773 obsoleting the connection or telling the entry_guards functions.
10774 - Some Tor servers process billions of cells per day. These statistics
10775 need to be uint64_t's.
10776 - Check for integer overflows in more places, when adding elements
10777 to smartlists. This could possibly prevent a buffer overflow
10778 on malicious huge inputs. I don't see any, but I haven't looked
10780 - ReachableAddresses kept growing new "reject *:*" lines on every
10782 - When you "setconf log" via the controller, it should remove all
10783 logs. We were automatically adding back in a "log notice stdout".
10784 - Newly bootstrapped Tor networks couldn't establish hidden service
10785 circuits until they had nodes with high uptime. Be more tolerant.
10786 - We were marking servers down when they could not answer every piece
10787 of the directory request we sent them. This was far too harsh.
10788 - Fix the torify (tsocks) config file to not use Tor for localhost
10790 - Directory authorities now go to the proper authority when asking for
10791 a networkstatus, even when they want a compressed one.
10792 - Fix a harmless bug that was causing Tor servers to log
10793 "Got an end because of misc error, but we're not an AP. Closing."
10794 - Authorities were treating their own descriptor changes as cosmetic,
10795 meaning the descriptor available in the network-status and the
10796 descriptor that clients downloaded were different.
10797 - The OS X installer was adding a symlink for tor_resolve but
10798 the binary was called tor-resolve (reported by Thomas Hardly).
10799 - Workaround a problem with some http proxies where they refuse GET
10800 requests that specify "Content-Length: 0" (reported by Adrian).
10801 - Fix wrong log message when you add a "HiddenServiceNodes" config
10802 line without any HiddenServiceDir line (reported by Chris Thomas).
10805 - Write the TorVersion into the state file so we have a prayer of
10806 keeping forward and backward compatibility.
10807 - Revive the FascistFirewall config option rather than eliminating it:
10808 now it's a synonym for ReachableAddresses *:80,*:443.
10809 - Clients choose directory servers from the network status lists,
10810 not from their internal list of router descriptors. Now they can
10811 go to caches directly rather than needing to go to authorities
10813 - Directory authorities ignore router descriptors that have only
10814 cosmetic differences: do this for 0.1.0.x servers now too.
10815 - Add a new flag to network-status indicating whether the server
10816 can answer v2 directory requests too.
10817 - Authdirs now stop whining so loudly about bad descriptors that
10818 they fetch from other dirservers. So when there's a log complaint,
10819 it's for sure from a freshly uploaded descriptor.
10820 - Reduce memory requirements in our structs by changing the order
10822 - There used to be two ways to specify your listening ports in a
10823 server descriptor: on the "router" line and with a separate "ports"
10824 line. Remove support for the "ports" line.
10825 - New config option "AuthDirRejectUnlisted" for auth dirservers as
10826 a panic button: if we get flooded with unusable servers we can
10827 revert to only listing servers in the approved-routers file.
10828 - Auth dir servers can now mark a fingerprint as "!reject" or
10829 "!invalid" in the approved-routers file (as its nickname), to
10830 refuse descriptors outright or include them but marked as invalid.
10831 - Servers store bandwidth history across restarts/crashes.
10832 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10833 get a better idea of why their circuits failed. Not used yet.
10834 - Directory mirrors now cache up to 16 unrecognized network-status
10835 docs. Now we can add new authdirservers and they'll be cached too.
10836 - When picking a random directory, prefer non-authorities if any
10838 - New controller option "getinfo desc/all-recent" to fetch the
10839 latest server descriptor for every router that Tor knows about.
10842 Changes in version 0.1.0.16 - 2006-01-02
10843 o Crash bugfixes on 0.1.0.x:
10844 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10845 corrupting the heap, losing FDs, or crashing when we need to resize
10846 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10847 - It turns out sparc64 platforms crash on unaligned memory access
10848 too -- so detect and avoid this.
10849 - Handle truncated compressed data correctly (by detecting it and
10851 - Fix possible-but-unlikely free(NULL) in control.c.
10852 - When we were closing connections, there was a rare case that
10853 stomped on memory, triggering seg faults and asserts.
10854 - Avoid potential infinite recursion when building a descriptor. (We
10855 don't know that it ever happened, but better to fix it anyway.)
10856 - We were neglecting to unlink marked circuits from soon-to-close OR
10857 connections, which caused some rare scribbling on freed memory.
10858 - Fix a memory stomping race bug when closing the joining point of two
10859 rendezvous circuits.
10860 - Fix an assert in time parsing found by Steven Murdoch.
10862 o Other bugfixes on 0.1.0.x:
10863 - When we're doing reachability testing, provide more useful log
10864 messages so the operator knows what to expect.
10865 - Do not check whether DirPort is reachable when we are suppressing
10866 advertising it because of hibernation.
10867 - When building with -static or on Solaris, we sometimes needed -ldl.
10868 - When we're deciding whether a stream has enough circuits around
10869 that can handle it, count the freshly dirty ones and not the ones
10870 that are so dirty they won't be able to handle it.
10871 - When we're expiring old circuits, we had a logic error that caused
10872 us to close new rendezvous circuits rather than old ones.
10873 - Give a more helpful log message when you try to change ORPort via
10874 the controller: you should upgrade Tor if you want that to work.
10875 - We were failing to parse Tor versions that start with "Tor ".
10876 - Tolerate faulty streams better: when a stream fails for reason
10877 exitpolicy, stop assuming that the router is lying about his exit
10878 policy. When a stream fails for reason misc, allow it to retry just
10879 as if it was resolvefailed. When a stream has failed three times,
10880 reset its failure count so we can try again and get all three tries.
10883 Changes in version 0.1.1.10-alpha - 2005-12-11
10884 o Correctness bugfixes on 0.1.0.x:
10885 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10886 corrupting the heap, losing FDs, or crashing when we need to resize
10887 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10888 - Stop doing the complex voodoo overkill checking for insecure
10889 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
10890 - When we were closing connections, there was a rare case that
10891 stomped on memory, triggering seg faults and asserts.
10892 - We were neglecting to unlink marked circuits from soon-to-close OR
10893 connections, which caused some rare scribbling on freed memory.
10894 - When we're deciding whether a stream has enough circuits around
10895 that can handle it, count the freshly dirty ones and not the ones
10896 that are so dirty they won't be able to handle it.
10897 - Recover better from TCP connections to Tor servers that are
10898 broken but don't tell you (it happens!); and rotate TLS
10899 connections once a week.
10900 - When we're expiring old circuits, we had a logic error that caused
10901 us to close new rendezvous circuits rather than old ones.
10902 - Fix a scary-looking but apparently harmless bug where circuits
10903 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
10904 servers, and never switch to state CIRCUIT_STATE_OPEN.
10905 - When building with -static or on Solaris, we sometimes needed to
10907 - Give a useful message when people run Tor as the wrong user,
10908 rather than telling them to start chowning random directories.
10909 - We were failing to inform the controller about new .onion streams.
10911 o Security bugfixes on 0.1.0.x:
10912 - Refuse server descriptors if the fingerprint line doesn't match
10913 the included identity key. Tor doesn't care, but other apps (and
10914 humans) might actually be trusting the fingerprint line.
10915 - We used to kill the circuit when we receive a relay command we
10916 don't recognize. Now we just drop it.
10917 - Start obeying our firewall options more rigorously:
10918 . If we can't get to a dirserver directly, try going via Tor.
10919 . Don't ever try to connect (as a client) to a place our
10920 firewall options forbid.
10921 . If we specify a proxy and also firewall options, obey the
10922 firewall options even when we're using the proxy: some proxies
10923 can only proxy to certain destinations.
10924 - Fix a bug found by Lasse Overlier: when we were making internal
10925 circuits (intended to be cannibalized later for rendezvous and
10926 introduction circuits), we were picking them so that they had
10927 useful exit nodes. There was no need for this, and it actually
10928 aids some statistical attacks.
10929 - Start treating internal circuits and exit circuits separately.
10930 It's important to keep them separate because internal circuits
10931 have their last hops picked like middle hops, rather than like
10932 exit hops. So exiting on them will break the user's expectations.
10934 o Bugfixes on 0.1.1.x:
10935 - Take out the mis-feature where we tried to detect IP address
10936 flapping for people with DynDNS, and chose not to upload a new
10937 server descriptor sometimes.
10938 - Try to be compatible with OpenSSL 0.9.6 again.
10939 - Log fix: when the controller is logging about .onion addresses,
10940 sometimes it didn't include the ".onion" part of the address.
10941 - Don't try to modify options->DirServers internally -- if the
10942 user didn't specify any, just add the default ones directly to
10943 the trusted dirserver list. This fixes a bug where people running
10944 controllers would use SETCONF on some totally unrelated config
10945 option, and Tor would start yelling at them about changing their
10947 - Let the controller's redirectstream command specify a port, in
10948 case the controller wants to change that too.
10949 - When we requested a pile of server descriptors, we sometimes
10950 accidentally launched a duplicate request for the first one.
10951 - Bugfix for trackhostexits: write down the fingerprint of the
10952 chosen exit, not its nickname, because the chosen exit might not
10954 - When parsing foo.exit, if foo is unknown, and we are leaving
10955 circuits unattached, set the chosen_exit field and leave the
10956 address empty. This matters because controllers got confused
10958 - Directory authorities no longer try to download server
10959 descriptors that they know they will reject.
10961 o Features and updates:
10962 - Replace balanced trees with hash tables: this should make stuff
10963 significantly faster.
10964 - Resume using the AES counter-mode implementation that we ship,
10965 rather than OpenSSL's. Ours is significantly faster.
10966 - Many other CPU and memory improvements.
10967 - Add a new config option FastFirstHopPK (on by default) so clients
10968 do a trivial crypto handshake for their first hop, since TLS has
10969 already taken care of confidentiality and authentication.
10970 - Add a new config option TestSocks so people can see if their
10971 applications are using socks4, socks4a, socks5-with-ip, or
10972 socks5-with-hostname. This way they don't have to keep mucking
10973 with tcpdump and wondering if something got cached somewhere.
10974 - Warn when listening on a public address for socks. I suspect a
10975 lot of people are setting themselves up as open socks proxies,
10976 and they have no idea that jerks on the Internet are using them,
10977 since they simply proxy the traffic into the Tor network.
10978 - Add "private:*" as an alias in configuration for policies. Now
10979 you can simplify your exit policy rather than needing to list
10980 every single internal or nonroutable network space.
10981 - Add a new controller event type that allows controllers to get
10982 all server descriptors that were uploaded to a router in its role
10983 as authoritative dirserver.
10984 - Start shipping socks-extensions.txt, tor-doc-unix.html,
10985 tor-doc-server.html, and stylesheet.css in the tarball.
10986 - Stop shipping tor-doc.html in the tarball.
10989 Changes in version 0.1.1.9-alpha - 2005-11-15
10990 o Usability improvements:
10991 - Start calling it FooListenAddress rather than FooBindAddress,
10992 since few of our users know what it means to bind an address
10994 - Reduce clutter in server logs. We're going to try to make
10995 them actually usable now. New config option ProtocolWarnings that
10996 lets you hear about how _other Tors_ are breaking the protocol. Off
10998 - Divide log messages into logging domains. Once we put some sort
10999 of interface on this, it will let people looking at more verbose
11000 log levels specify the topics they want to hear more about.
11001 - Make directory servers return better http 404 error messages
11002 instead of a generic "Servers unavailable".
11003 - Check for even more Windows version flags when writing the platform
11004 string in server descriptors, and note any we don't recognize.
11005 - Clean up more of the OpenSSL memory when exiting, so we can detect
11006 memory leaks better.
11007 - Make directory authorities be non-versioning, non-naming by
11008 default. Now we can add new directory servers without requiring
11009 their operators to pay close attention.
11010 - When logging via syslog, include the pid whenever we provide
11011 a log entry. Suggested by Todd Fries.
11013 o Performance improvements:
11014 - Directory servers now silently throw away new descriptors that
11015 haven't changed much if the timestamps are similar. We do this to
11016 tolerate older Tor servers that upload a new descriptor every 15
11017 minutes. (It seemed like a good idea at the time.)
11018 - Inline bottleneck smartlist functions; use fast versions by default.
11019 - Add a "Map from digest to void*" abstraction digestmap_t so we
11020 can do less hex encoding/decoding. Use it in router_get_by_digest()
11021 to resolve a performance bottleneck.
11022 - Allow tor_gzip_uncompress to extract as much as possible from
11023 truncated compressed data. Try to extract as many
11024 descriptors as possible from truncated http responses (when
11025 DIR_PURPOSE_FETCH_ROUTERDESC).
11026 - Make circ->onionskin a pointer, not a static array. moria2 was using
11027 125000 circuit_t's after it had been up for a few weeks, which
11028 translates to 20+ megs of wasted space.
11029 - The private half of our EDH handshake keys are now chosen out
11030 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11032 o Security improvements:
11033 - Start making directory caches retain old routerinfos, so soon
11034 clients can start asking by digest of descriptor rather than by
11035 fingerprint of server.
11036 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11037 to use egd (if present), openbsd weirdness (if present), vms/os2
11038 weirdness (if we ever port there), and more in the future.
11040 o Bugfixes on 0.1.0.x:
11041 - Do round-robin writes of at most 16 kB per write. This might be
11042 more fair on loaded Tor servers, and it might resolve our Windows
11043 crash bug. It might also slow things down.
11044 - Our TLS handshakes were generating a single public/private
11045 keypair for the TLS context, rather than making a new one for
11046 each new connections. Oops. (But we were still rotating them
11047 periodically, so it's not so bad.)
11048 - When we were cannibalizing a circuit with a particular exit
11049 node in mind, we weren't checking to see if that exit node was
11050 already present earlier in the circuit. Oops.
11051 - When a Tor server's IP changes (e.g. from a dyndns address),
11052 upload a new descriptor so clients will learn too.
11053 - Really busy servers were keeping enough circuits open on stable
11054 connections that they were wrapping around the circuit_id
11055 space. (It's only two bytes.) This exposed a bug where we would
11056 feel free to reuse a circuit_id even if it still exists but has
11057 been marked for close. Try to fix this bug. Some bug remains.
11058 - If we would close a stream early (e.g. it asks for a .exit that
11059 we know would refuse it) but the LeaveStreamsUnattached config
11060 option is set by the controller, then don't close it.
11062 o Bugfixes on 0.1.1.8-alpha:
11063 - Fix a big pile of memory leaks, some of them serious.
11064 - Do not try to download a routerdesc if we would immediately reject
11066 - Resume inserting a newline between all router descriptors when
11067 generating (old style) signed directories, since our spec says
11069 - When providing content-type application/octet-stream for
11070 server descriptors using .z, we were leaving out the
11071 content-encoding header. Oops. (Everything tolerated this just
11072 fine, but that doesn't mean we need to be part of the problem.)
11073 - Fix a potential seg fault in getconf and getinfo using version 1
11074 of the controller protocol.
11075 - Avoid crash: do not check whether DirPort is reachable when we
11076 are suppressing it because of hibernation.
11077 - Make --hash-password not crash on exit.
11080 Changes in version 0.1.1.8-alpha - 2005-10-07
11081 o New features (major):
11082 - Clients don't download or use the directory anymore. Now they
11083 download and use network-statuses from the trusted dirservers,
11084 and fetch individual server descriptors as needed from mirrors.
11085 See dir-spec.txt for all the gory details.
11086 - Be more conservative about whether to advertise our DirPort.
11087 The main change is to not advertise if we're running at capacity
11088 and either a) we could hibernate or b) our capacity is low and
11089 we're using a default DirPort.
11090 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11092 o New features (minor):
11093 - Try to be smart about when to retry network-status and
11094 server-descriptor fetches. Still needs some tuning.
11095 - Stop parsing, storing, or using running-routers output (but
11096 mirrors still cache and serve it).
11097 - Consider a threshold of versioning dirservers (dirservers who have
11098 an opinion about which Tor versions are still recommended) before
11099 deciding whether to warn the user that he's obsolete.
11100 - Dirservers can now reject/invalidate by key and IP, with the
11101 config options "AuthDirInvalid" and "AuthDirReject". This is
11102 useful since currently we automatically list servers as running
11103 and usable even if we know they're jerks.
11104 - Provide dire warnings to any users who set DirServer; move it out
11105 of torrc.sample and into torrc.complete.
11106 - Add MyFamily to torrc.sample in the server section.
11107 - Add nicknames to the DirServer line, so we can refer to them
11108 without requiring all our users to memorize their IP addresses.
11109 - When we get an EOF or a timeout on a directory connection, note
11110 how many bytes of serverdesc we are dropping. This will help
11111 us determine whether it is smart to parse incomplete serverdesc
11113 - Add a new function to "change pseudonyms" -- that is, to stop
11114 using any currently-dirty circuits for new streams, so we don't
11115 link new actions to old actions. Currently it's only called on
11116 HUP (or SIGNAL RELOAD).
11117 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11118 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11119 OpenSSL. Also, reseed our entropy every hour, not just at
11120 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11122 o Fixes on 0.1.1.7-alpha:
11123 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11124 version 0, so don't let version 0 controllers ask for it.
11125 - If you requested something with too many newlines via the
11126 v1 controller protocol, you could crash tor.
11127 - Fix a number of memory leaks, including some pretty serious ones.
11128 - Re-enable DirPort testing again, so Tor servers will be willing
11129 to advertise their DirPort if it's reachable.
11130 - On TLS handshake, only check the other router's nickname against
11131 its expected nickname if is_named is set.
11133 o Fixes forward-ported from 0.1.0.15:
11134 - Don't crash when we don't have any spare file descriptors and we
11135 try to spawn a dns or cpu worker.
11136 - Make the numbers in read-history and write-history into uint64s,
11137 so they don't overflow and publish negatives in the descriptor.
11139 o Fixes on 0.1.0.x:
11140 - For the OS X package's modified privoxy config file, comment
11141 out the "logfile" line so we don't log everything passed
11143 - We were whining about using socks4 or socks5-with-local-lookup
11144 even when it's an IP in the "virtual" range we designed exactly
11146 - We were leaking some memory every time the client changes IPs.
11147 - Never call free() on tor_malloc()d memory. This will help us
11148 use dmalloc to detect memory leaks.
11149 - Check for named servers when looking them up by nickname;
11150 warn when we'recalling a non-named server by its nickname;
11151 don't warn twice about the same name.
11152 - Try to list MyFamily elements by key, not by nickname, and warn
11153 if we've not heard of the server.
11154 - Make windows platform detection (uname equivalent) smarter.
11155 - It turns out sparc64 doesn't like unaligned access either.
11158 Changes in version 0.1.0.15 - 2005-09-23
11159 o Bugfixes on 0.1.0.x:
11160 - Reject ports 465 and 587 (spam targets) in default exit policy.
11161 - Don't crash when we don't have any spare file descriptors and we
11162 try to spawn a dns or cpu worker.
11163 - Get rid of IgnoreVersion undocumented config option, and make us
11164 only warn, never exit, when we're running an obsolete version.
11165 - Don't try to print a null string when your server finds itself to
11166 be unreachable and the Address config option is empty.
11167 - Make the numbers in read-history and write-history into uint64s,
11168 so they don't overflow and publish negatives in the descriptor.
11169 - Fix a minor memory leak in smartlist_string_remove().
11170 - We were only allowing ourselves to upload a server descriptor at
11171 most every 20 minutes, even if it changed earlier than that.
11172 - Clean up log entries that pointed to old URLs.
11175 Changes in version 0.1.1.7-alpha - 2005-09-14
11176 o Fixes on 0.1.1.6-alpha:
11177 - Exit servers were crashing when people asked them to make a
11178 connection to an address not in their exit policy.
11179 - Looking up a non-existent stream for a v1 control connection would
11181 - Fix a seg fault if we ask a dirserver for a descriptor by
11182 fingerprint but he doesn't know about him.
11183 - SETCONF was appending items to linelists, not clearing them.
11184 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11185 out and refuse the setconf if it would fail.
11186 - Downgrade the dirserver log messages when whining about
11190 - Add Peter Palfrader's check-tor script to tor/contrib/
11191 It lets you easily check whether a given server (referenced by
11192 nickname) is reachable by you.
11193 - Numerous changes to move towards client-side v2 directories. Not
11196 o Fixes on 0.1.0.x:
11197 - If the user gave tor an odd number of command-line arguments,
11198 we were silently ignoring the last one. Now we complain and fail.
11199 [This wins the oldest-bug prize -- this bug has been present since
11200 November 2002, as released in Tor 0.0.0.]
11201 - Do not use unaligned memory access on alpha, mips, or mipsel.
11202 It *works*, but is very slow, so we treat them as if it doesn't.
11203 - Retry directory requests if we fail to get an answer we like
11204 from a given dirserver (we were retrying before, but only if
11205 we fail to connect).
11206 - When writing the RecommendedVersions line, sort them first.
11207 - When the client asked for a rendezvous port that the hidden
11208 service didn't want to provide, we were sending an IP address
11209 back along with the end cell. Fortunately, it was zero. But stop
11211 - Correct "your server is reachable" log entries to indicate that
11212 it was self-testing that told us so.
11215 Changes in version 0.1.1.6-alpha - 2005-09-09
11216 o Fixes on 0.1.1.5-alpha:
11217 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11218 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11219 - Fix bug with tor_memmem finding a match at the end of the string.
11220 - Make unit tests run without segfaulting.
11221 - Resolve some solaris x86 compile warnings.
11222 - Handle duplicate lines in approved-routers files without warning.
11223 - Fix bug where as soon as a server refused any requests due to his
11224 exit policy (e.g. when we ask for localhost and he tells us that's
11225 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11226 exit policy using him for any exits.
11227 - Only do openssl hardware accelerator stuff if openssl version is
11230 o New controller features/fixes:
11231 - Add a "RESETCONF" command so you can set config options like
11232 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11233 a config option in the torrc with no value, then it clears it
11234 entirely (rather than setting it to its default).
11235 - Add a "GETINFO config-file" to tell us where torrc is.
11236 - Avoid sending blank lines when GETINFO replies should be empty.
11237 - Add a QUIT command for the controller (for using it manually).
11238 - Fix a bug in SAVECONF that was adding default dirservers and
11239 other redundant entries to the torrc file.
11241 o Start on the new directory design:
11242 - Generate, publish, cache, serve new network-status format.
11243 - Publish individual descriptors (by fingerprint, by "all", and by
11245 - Publish client and server recommended versions separately.
11246 - Allow tor_gzip_uncompress() to handle multiple concatenated
11247 compressed strings. Serve compressed groups of router
11248 descriptors. The compression logic here could be more
11250 - Distinguish v1 authorities (all currently trusted directories)
11251 from v2 authorities (all trusted directories).
11252 - Change DirServers config line to note which dirs are v1 authorities.
11253 - Add configuration option "V1AuthoritativeDirectory 1" which
11254 moria1, moria2, and tor26 should set.
11255 - Remove option when getting directory cache to see whether they
11256 support running-routers; they all do now. Replace it with one
11257 to see whether caches support v2 stuff.
11260 - Dirservers now do their own external reachability testing of each
11261 Tor server, and only list them as running if they've been found to
11262 be reachable. We also send back warnings to the server's logs if
11263 it uploads a descriptor that we already believe is unreachable.
11264 - Implement exit enclaves: if we know an IP address for the
11265 destination, and there's a running Tor server at that address
11266 which allows exit to the destination, then extend the circuit to
11267 that exit first. This provides end-to-end encryption and end-to-end
11268 authentication. Also, if the user wants a .exit address or enclave,
11269 use 4 hops rather than 3, and cannibalize a general circ for it
11271 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11272 controller. Also, rotate dns and cpu workers if the controller
11273 changes options that will affect them; and initialize the dns
11274 worker cache tree whether or not we start out as a server.
11275 - Only upload a new server descriptor when options change, 18
11276 hours have passed, uptime is reset, or bandwidth changes a lot.
11277 - Check [X-]Forwarded-For headers in HTTP requests when generating
11278 log messages. This lets people run dirservers (and caches) behind
11279 Apache but still know which IP addresses are causing warnings.
11281 o Config option changes:
11282 - Replace (Fascist)Firewall* config options with a new
11283 ReachableAddresses option that understands address policies.
11284 For example, "ReachableAddresses *:80,*:443"
11285 - Get rid of IgnoreVersion undocumented config option, and make us
11286 only warn, never exit, when we're running an obsolete version.
11287 - Make MonthlyAccountingStart config option truly obsolete now.
11289 o Fixes on 0.1.0.x:
11290 - Reject ports 465 and 587 in the default exit policy, since
11291 people have started using them for spam too.
11292 - It turns out we couldn't bootstrap a network since we added
11293 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11294 has never gone down. Add an AssumeReachable config option to let
11295 servers and dirservers bootstrap. When we're trying to build a
11296 high-uptime or high-bandwidth circuit but there aren't enough
11297 suitable servers, try being less picky rather than simply failing.
11298 - Our logic to decide if the OR we connected to was the right guy
11299 was brittle and maybe open to a mitm for unverified routers.
11300 - We weren't cannibalizing circuits correctly for
11301 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11302 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11303 build those from scratch. This should make hidden services faster.
11304 - Predict required circuits better, with an eye toward making hidden
11305 services faster on the service end.
11306 - Retry streams if the exit node sends back a 'misc' failure. This
11307 should result in fewer random failures. Also, after failing
11308 from resolve failed or misc, reset the num failures, so we give
11309 it a fair shake next time we try.
11310 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11311 - Reduce severity on logs about dns worker spawning and culling.
11312 - When we're shutting down and we do something like try to post a
11313 server descriptor or rendezvous descriptor, don't complain that
11314 we seem to be unreachable. Of course we are, we're shutting down.
11315 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11316 We don't use them yet, but maybe one day our DNS resolver will be
11317 able to discover them.
11318 - Make ContactInfo mandatory for authoritative directory servers.
11319 - Require server descriptors to list IPv4 addresses -- hostnames
11320 are no longer allowed. This also fixes some potential security
11321 problems with people providing hostnames as their address and then
11322 preferentially resolving them to partition users.
11323 - Change log line for unreachability to explicitly suggest /etc/hosts
11324 as the culprit. Also make it clearer what IP address and ports we're
11325 testing for reachability.
11326 - Put quotes around user-supplied strings when logging so users are
11327 more likely to realize if they add bad characters (like quotes)
11329 - Let auth dir servers start without specifying an Address config
11331 - Make unit tests (and other invocations that aren't the real Tor)
11332 run without launching listeners, creating subdirectories, and so on.
11335 Changes in version 0.1.1.5-alpha - 2005-08-08
11336 o Bugfixes included in 0.1.0.14.
11338 o Bugfixes on 0.1.0.x:
11339 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11340 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11341 it would silently using ignore the 6668.
11344 Changes in version 0.1.0.14 - 2005-08-08
11345 o Bugfixes on 0.1.0.x:
11346 - Fix the other half of the bug with crypto handshakes
11348 - Fix an assert trigger if you send a 'signal term' via the
11349 controller when it's listening for 'event info' messages.
11352 Changes in version 0.1.1.4-alpha - 2005-08-04
11353 o Bugfixes included in 0.1.0.13.
11356 - Improve tor_gettimeofday() granularity on windows.
11357 - Make clients regenerate their keys when their IP address changes.
11358 - Implement some more GETINFO goodness: expose helper nodes, config
11359 options, getinfo keys.
11362 Changes in version 0.1.0.13 - 2005-08-04
11363 o Bugfixes on 0.1.0.x:
11364 - Fix a critical bug in the security of our crypto handshakes.
11365 - Fix a size_t underflow in smartlist_join_strings2() that made
11366 it do bad things when you hand it an empty smartlist.
11367 - Fix Windows installer to ship Tor license (thanks to Aphex for
11368 pointing out this oversight) and put a link to the doc directory
11370 - Explicitly set no-unaligned-access for sparc: it turns out the
11371 new gcc's let you compile broken code, but that doesn't make it
11375 Changes in version 0.1.1.3-alpha - 2005-07-23
11376 o Bugfixes on 0.1.1.2-alpha:
11377 - Fix a bug in handling the controller's "post descriptor"
11379 - Fix several bugs in handling the controller's "extend circuit"
11381 - Fix a bug in handling the controller's "stream status" event.
11382 - Fix an assert failure if we have a controller listening for
11383 circuit events and we go offline.
11384 - Re-allow hidden service descriptors to publish 0 intro points.
11385 - Fix a crash when generating your hidden service descriptor if
11386 you don't have enough intro points already.
11388 o New features on 0.1.1.2-alpha:
11389 - New controller function "getinfo accounting", to ask how
11390 many bytes we've used in this time period.
11391 - Experimental support for helper nodes: a lot of the risk from
11392 a small static adversary comes because users pick new random
11393 nodes every time they rebuild a circuit. Now users will try to
11394 stick to the same small set of entry nodes if they can. Not
11395 enabled by default yet.
11397 o Bugfixes on 0.1.0.12:
11398 - If you're an auth dir server, always publish your dirport,
11399 even if you haven't yet found yourself to be reachable.
11400 - Fix a size_t underflow in smartlist_join_strings2() that made
11401 it do bad things when you hand it an empty smartlist.
11404 Changes in version 0.1.0.12 - 2005-07-18
11405 o New directory servers:
11406 - tor26 has changed IP address.
11408 o Bugfixes on 0.1.0.x:
11409 - Fix a possible double-free in tor_gzip_uncompress().
11410 - When --disable-threads is set, do not search for or link against
11411 pthreads libraries.
11412 - Don't trigger an assert if an authoritative directory server
11413 claims its dirport is 0.
11414 - Fix bug with removing Tor as an NT service: some people were
11415 getting "The service did not return an error." Thanks to Matt
11419 Changes in version 0.1.1.2-alpha - 2005-07-15
11420 o New directory servers:
11421 - tor26 has changed IP address.
11423 o Bugfixes on 0.1.0.x, crashes/leaks:
11424 - Port the servers-not-obeying-their-exit-policies fix from
11426 - Fix an fd leak in start_daemon().
11427 - On Windows, you can't always reopen a port right after you've
11428 closed it. So change retry_listeners() to only close and re-open
11429 ports that have changed.
11430 - Fix a possible double-free in tor_gzip_uncompress().
11432 o Bugfixes on 0.1.0.x, usability:
11433 - When tor_socketpair() fails in Windows, give a reasonable
11434 Windows-style errno back.
11435 - Let people type "tor --install" as well as "tor -install" when
11437 want to make it an NT service.
11438 - NT service patch from Matt Edman to improve error messages.
11439 - When the controller asks for a config option with an abbreviated
11440 name, give the full name in our response.
11441 - Correct the man page entry on TrackHostExitsExpire.
11442 - Looks like we were never delivering deflated (i.e. compressed)
11443 running-routers lists, even when asked. Oops.
11444 - When --disable-threads is set, do not search for or link against
11445 pthreads libraries.
11447 o Bugfixes on 0.1.1.x:
11448 - Fix a seg fault with autodetecting which controller version is
11452 - New hidden service descriptor format: put a version in it, and
11453 let people specify introduction/rendezvous points that aren't
11454 in "the directory" (which is subjective anyway).
11455 - Allow the DEBUG controller event to work again. Mark certain log
11456 entries as "don't tell this to controllers", so we avoid cycles.
11459 Changes in version 0.1.0.11 - 2005-06-30
11460 o Bugfixes on 0.1.0.x:
11461 - Fix major security bug: servers were disregarding their
11462 exit policies if clients behaved unexpectedly.
11463 - Make OS X init script check for missing argument, so we don't
11464 confuse users who invoke it incorrectly.
11465 - Fix a seg fault in "tor --hash-password foo".
11466 - The MAPADDRESS control command was broken.
11469 Changes in version 0.1.1.1-alpha - 2005-06-29
11471 - Make OS X init script check for missing argument, so we don't
11472 confuse users who invoke it incorrectly.
11473 - Fix a seg fault in "tor --hash-password foo".
11474 - Fix a possible way to DoS dirservers.
11475 - When we complain that your exit policy implicitly allows local or
11476 private address spaces, name them explicitly so operators can
11478 - Make the log message less scary when all the dirservers are
11479 temporarily unreachable.
11480 - We were printing the number of idle dns workers incorrectly when
11484 - Revised controller protocol (version 1) that uses ascii rather
11485 than binary. Add supporting libraries in python and java so you
11486 can use the controller from your applications without caring how
11487 our protocol works.
11488 - Spiffy new support for crypto hardware accelerators. Can somebody
11492 Changes in version 0.0.9.10 - 2005-06-16
11493 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11494 - Refuse relay cells that claim to have a length larger than the
11495 maximum allowed. This prevents a potential attack that could read
11496 arbitrary memory (e.g. keys) from an exit server's process
11500 Changes in version 0.1.0.10 - 2005-06-14
11501 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11502 libevent before 1.1a.
11505 Changes in version 0.1.0.9-rc - 2005-06-09
11507 - Reset buf->highwater every time buf_shrink() is called, not just on
11508 a successful shrink. This was causing significant memory bloat.
11509 - Fix buffer overflow when checking hashed passwords.
11510 - Security fix: if seeding the RNG on Win32 fails, quit.
11511 - Allow seeding the RNG on Win32 even when you're not running as
11513 - Disable threading on Solaris too. Something is wonky with it,
11514 cpuworkers, and reentrant libs.
11515 - Reenable the part of the code that tries to flush as soon as an
11516 OR outbuf has a full TLS record available. Perhaps this will make
11517 OR outbufs not grow as huge except in rare cases, thus saving lots
11518 of CPU time plus memory.
11519 - Reject malformed .onion addresses rather then passing them on as
11520 normal web requests.
11521 - Adapt patch from Adam Langley: fix possible memory leak in
11522 tor_lookup_hostname().
11523 - Initialize libevent later in the startup process, so the logs are
11524 already established by the time we start logging libevent warns.
11525 - Use correct errno on win32 if libevent fails.
11526 - Check and warn about known-bad/slow libevent versions.
11527 - Pay more attention to the ClientOnly config option.
11528 - Have torctl.in/tor.sh.in check for location of su binary (needed
11530 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11531 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11532 HttpProxyAuthenticator
11533 - Stop warning about sigpipes in the logs. We're going to
11534 pretend that getting these occassionally is normal and fine.
11535 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11537 installer screens; and don't put stuff into StartupItems unless
11538 the user asks you to.
11539 - Require servers that use the default dirservers to have public IP
11540 addresses. We have too many servers that are configured with private
11541 IPs and their admins never notice the log entries complaining that
11542 their descriptors are being rejected.
11543 - Add OSX uninstall instructions. An actual uninstall script will
11547 Changes in version 0.1.0.8-rc - 2005-05-23
11549 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11550 panics. Disable kqueue on all OS X Tors.
11551 - Fix RPM: remove duplicate line accidentally added to the rpm
11553 - Disable threads on openbsd too, since its gethostaddr is not
11555 - Tolerate libevent 0.8 since it still works, even though it's
11557 - Enable building on Red Hat 9.0 again.
11558 - Allow the middle hop of the testing circuit to be running any
11559 version, now that most of them have the bugfix to let them connect
11560 to unknown servers. This will allow reachability testing to work
11561 even when 0.0.9.7-0.0.9.9 become obsolete.
11562 - Handle relay cells with rh.length too large. This prevents
11563 a potential attack that could read arbitrary memory (maybe even
11564 keys) from the exit server's process.
11565 - We screwed up the dirport reachability testing when we don't yet
11566 have a cached version of the directory. Hopefully now fixed.
11567 - Clean up router_load_single_router() (used by the controller),
11568 so it doesn't seg fault on error.
11569 - Fix a minor memory leak when somebody establishes an introduction
11570 point at your Tor server.
11571 - If a socks connection ends because read fails, don't warn that
11572 you're not sending a socks reply back.
11575 - Add HttpProxyAuthenticator config option too, that works like
11576 the HttpsProxyAuthenticator config option.
11577 - Encode hashed controller passwords in hex instead of base64,
11578 to make it easier to write controllers.
11581 Changes in version 0.1.0.7-rc - 2005-05-17
11583 - Fix a bug in the OS X package installer that prevented it from
11584 installing on Tiger.
11585 - Fix a script bug in the OS X package installer that made it
11586 complain during installation.
11587 - Find libevent even if it's hiding in /usr/local/ and your
11588 CFLAGS and LDFLAGS don't tell you to look there.
11589 - Be able to link with libevent as a shared library (the default
11590 after 1.0d), even if it's hiding in /usr/local/lib and even
11591 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11592 assuming you're running gcc. Otherwise fail and give a useful
11594 - Fix a bug in the RPM packager: set home directory for _tor to
11595 something more reasonable when first installing.
11596 - Free a minor amount of memory that is still reachable on exit.
11599 Changes in version 0.1.0.6-rc - 2005-05-14
11601 - Implement --disable-threads configure option. Disable threads on
11602 netbsd by default, because it appears to have no reentrant resolver
11604 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11605 release (1.1) detects and disables kqueue if it's broken.
11606 - Append default exit policy before checking for implicit internal
11607 addresses. Now we don't log a bunch of complaints on startup
11608 when using the default exit policy.
11609 - Some people were putting "Address " in their torrc, and they had
11610 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11611 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11612 LOCALSTATEDIR/tor instead.
11613 - Fix fragmented-message bug in TorControl.py.
11614 - Resolve a minor bug which would prevent unreachable dirports
11615 from getting suppressed in the published descriptor.
11616 - When the controller gave us a new descriptor, we weren't resolving
11617 it immediately, so Tor would think its address was 0.0.0.0 until
11618 we fetched a new directory.
11619 - Fix an uppercase/lowercase case error in suppressing a bogus
11620 libevent warning on some Linuxes.
11623 - Begin scrubbing sensitive strings from logs by default. Turn off
11624 the config option SafeLogging if you need to do debugging.
11625 - Switch to a new buffer management algorithm, which tries to avoid
11626 reallocing and copying quite as much. In first tests it looks like
11627 it uses *more* memory on average, but less cpu.
11628 - First cut at support for "create-fast" cells. Clients can use
11629 these when extending to their first hop, since the TLS already
11630 provides forward secrecy and authentication. Not enabled on
11632 - When dirservers refuse a router descriptor, we now log its
11633 contactinfo, platform, and the poster's IP address.
11634 - Call tor_free_all instead of connections_free_all after forking, to
11635 save memory on systems that need to fork.
11636 - Whine at you if you're a server and you don't set your contactinfo.
11637 - Implement --verify-config command-line option to check if your torrc
11638 is valid without actually launching Tor.
11639 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11640 rather than just rejecting it.
11643 Changes in version 0.1.0.5-rc - 2005-04-27
11645 - Stop trying to print a null pointer if an OR conn fails because
11646 we didn't like its cert.
11648 - Switch our internal buffers implementation to use a ring buffer,
11649 to hopefully improve performance for fast servers a lot.
11650 - Add HttpsProxyAuthenticator support (basic auth only), based
11651 on patch from Adam Langley.
11652 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11653 the fast servers that have been joining lately.
11654 - Give hidden service accesses extra time on the first attempt,
11655 since 60 seconds is often only barely enough. This might improve
11657 - Improve performance for dirservers: stop re-parsing the whole
11658 directory every time you regenerate it.
11659 - Add more debugging info to help us find the weird dns freebsd
11660 pthreads bug; cleaner debug messages to help track future issues.
11663 Changes in version 0.0.9.9 - 2005-04-23
11664 o Bugfixes on 0.0.9.x:
11665 - If unofficial Tor clients connect and send weird TLS certs, our
11666 Tor server triggers an assert. This release contains a minimal
11667 backport from the broader fix that we put into 0.1.0.4-rc.
11670 Changes in version 0.1.0.4-rc - 2005-04-23
11672 - If unofficial Tor clients connect and send weird TLS certs, our
11673 Tor server triggers an assert. Stop asserting, and start handling
11674 TLS errors better in other situations too.
11675 - When the controller asks us to tell it about all the debug-level
11676 logs, it turns out we were generating debug-level logs while
11677 telling it about them, which turns into a bad loop. Now keep
11678 track of whether you're sending a debug log to the controller,
11679 and don't log when you are.
11680 - Fix the "postdescriptor" feature of the controller interface: on
11681 non-complete success, only say "done" once.
11683 - Clients are now willing to load balance over up to 2mB, not 1mB,
11684 of advertised bandwidth capacity.
11685 - Add a NoPublish config option, so you can be a server (e.g. for
11686 testing running Tor servers in other Tor networks) without
11687 publishing your descriptor to the primary dirservers.
11690 Changes in version 0.1.0.3-rc - 2005-04-08
11691 o Improvements on 0.1.0.2-rc:
11692 - Client now retries when streams end early for 'hibernating' or
11693 'resource limit' reasons, rather than failing them.
11694 - More automated handling for dirserver operators:
11695 - Automatically approve nodes running 0.1.0.2-rc or later,
11696 now that the the reachability detection stuff is working.
11697 - Now we allow two unverified servers with the same nickname
11698 but different keys. But if a nickname is verified, only that
11699 nickname+key are allowed.
11700 - If you're an authdirserver connecting to an address:port,
11701 and it's not the OR you were expecting, forget about that
11702 descriptor. If he *was* the one you were expecting, then forget
11703 about all other descriptors for that address:port.
11704 - Allow servers to publish descriptors from 12 hours in the future.
11705 Corollary: only whine about clock skew from the dirserver if
11706 he's a trusted dirserver (since now even verified servers could
11707 have quite wrong clocks).
11708 - Adjust maximum skew and age for rendezvous descriptors: let skew
11709 be 48 hours rather than 90 minutes.
11710 - Efficiency improvements:
11711 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11712 it much faster to look up a circuit for each relay cell.
11713 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11714 since they're eating our cpu on exit nodes.
11715 - Stop wasting time doing a case insensitive comparison for every
11716 dns name every time we do any lookup. Canonicalize the names to
11717 lowercase and be done with it.
11718 - Start sending 'truncated' cells back rather than destroy cells,
11719 if the circuit closes in front of you. This means we won't have
11720 to abandon partially built circuits.
11721 - Only warn once per nickname from add_nickname_list_to_smartlist
11722 per failure, so an entrynode or exitnode choice that's down won't
11724 - Put a note in the torrc about abuse potential with the default
11726 - Revise control spec and implementation to allow all log messages to
11727 be sent to controller with their severities intact (suggested by
11728 Matt Edman). Update TorControl to handle new log event types.
11729 - Provide better explanation messages when controller's POSTDESCRIPTOR
11731 - Stop putting nodename in the Platform string in server descriptors.
11732 It doesn't actually help, and it is confusing/upsetting some people.
11734 o Bugfixes on 0.1.0.2-rc:
11735 - We were printing the host mask wrong in exit policies in server
11736 descriptors. This isn't a critical bug though, since we were still
11737 obeying the exit policy internally.
11738 - Fix Tor when compiled with libevent but without pthreads: move
11739 connection_unregister() from _connection_free() to
11741 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
11742 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
11743 when we look through the connection array, we'll find any of the
11744 cpu/dnsworkers. This is no good.
11746 o Bugfixes on 0.0.9.8:
11747 - Fix possible bug on threading platforms (e.g. win32) which was
11748 leaking a file descriptor whenever a cpuworker or dnsworker died.
11749 - When using preferred entry or exit nodes, ignore whether the
11750 circuit wants uptime or capacity. They asked for the nodes, they
11752 - chdir() to your datadirectory at the *end* of the daemonize process,
11753 not the beginning. This was a problem because the first time you
11754 run tor, if your datadir isn't there, and you have runasdaemon set
11755 to 1, it will try to chdir to it before it tries to create it. Oops.
11756 - Handle changed router status correctly when dirserver reloads
11757 fingerprint file. We used to be dropping all unverified descriptors
11758 right then. The bug was hidden because we would immediately
11759 fetch a directory from another dirserver, which would include the
11760 descriptors we just dropped.
11761 - When we're connecting to an OR and he's got a different nickname/key
11762 than we were expecting, only complain loudly if we're an OP or a
11763 dirserver. Complaining loudly to the OR admins just confuses them.
11764 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11765 artificially capped at 500kB.
11768 Changes in version 0.0.9.8 - 2005-04-07
11769 o Bugfixes on 0.0.9.x:
11770 - We have a bug that I haven't found yet. Sometimes, very rarely,
11771 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11772 thinks of itself as idle. This meant that no new circuits ever got
11773 established. Here's a workaround to kill any cpuworker that's been
11774 busy for more than 100 seconds.
11777 Changes in version 0.1.0.2-rc - 2005-04-01
11778 o Bugfixes on 0.1.0.1-rc:
11779 - Fixes on reachability detection:
11780 - Don't check for reachability while hibernating.
11781 - If ORPort is reachable but DirPort isn't, still publish the
11782 descriptor, but zero out DirPort until it's found reachable.
11783 - When building testing circs for ORPort testing, use only
11784 high-bandwidth nodes, so fewer circuits fail.
11785 - Complain about unreachable ORPort separately from unreachable
11786 DirPort, so the user knows what's going on.
11787 - Make sure we only conclude ORPort reachability if we didn't
11788 initiate the conn. Otherwise we could falsely conclude that
11789 we're reachable just because we connected to the guy earlier
11790 and he used that same pipe to extend to us.
11791 - Authdirservers shouldn't do ORPort reachability detection,
11792 since they're in clique mode, so it will be rare to find a
11793 server not already connected to them.
11794 - When building testing circuits, always pick middle hops running
11795 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
11796 bug. (This is a kludge; it will go away when 0.0.9.x becomes
11798 - When we decide we're reachable, actually publish our descriptor
11800 - Fix bug in redirectstream in the controller.
11801 - Fix the state descriptor strings so logs don't claim edge streams
11802 are in a different state than they actually are.
11803 - Use recent libevent features when possible (this only really affects
11804 win32 and osx right now, because the new libevent with these
11805 features hasn't been released yet). Add code to suppress spurious
11807 - Prevent possible segfault in connection_close_unattached_ap().
11808 - Fix newlines on torrc in win32.
11809 - Improve error msgs when tor-resolve fails.
11811 o Improvements on 0.0.9.x:
11812 - New experimental script tor/contrib/ExerciseServer.py (needs more
11813 work) that uses the controller interface to build circuits and
11814 fetch pages over them. This will help us bootstrap servers that
11815 have lots of capacity but haven't noticed it yet.
11816 - New experimental script tor/contrib/PathDemo.py (needs more work)
11817 that uses the controller interface to let you choose whole paths
11819 "<hostname>.<path,separated by dots>.<length of path>.path"
11820 - When we've connected to an OR and handshaked but didn't like
11821 the result, we were closing the conn without sending destroy
11822 cells back for pending circuits. Now send those destroys.
11825 Changes in version 0.0.9.7 - 2005-04-01
11826 o Bugfixes on 0.0.9.x:
11827 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11828 - Compare identity to identity, not to nickname, when extending to
11829 a router not already in the directory. This was preventing us from
11830 extending to unknown routers. Oops.
11831 - Make sure to create OS X Tor user in <500 range, so we aren't
11832 creating actual system users.
11833 - Note where connection-that-hasn't-sent-end was marked, and fix
11834 a few really loud instances of this harmless bug (it's fixed more
11838 Changes in version 0.1.0.1-rc - 2005-03-28
11840 - Add reachability testing. Your Tor server will automatically try
11841 to see if its ORPort and DirPort are reachable from the outside,
11842 and it won't upload its descriptor until it decides they are.
11843 - Handle unavailable hidden services better. Handle slow or busy
11844 hidden services better.
11845 - Add support for CONNECTing through https proxies, with "HttpsProxy"
11847 - New exit policy: accept most low-numbered ports, rather than
11848 rejecting most low-numbered ports.
11849 - More Tor controller support (still experimental). See
11850 http://tor.eff.org/doc/control-spec.txt for all the new features,
11851 including signals to emulate unix signals from any platform;
11852 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
11853 closestream; closecircuit; etc.
11854 - Make nt services work and start on startup on win32 (based on
11855 patch by Matt Edman).
11856 - Add a new AddressMap config directive to rewrite incoming socks
11857 addresses. This lets you, for example, declare an implicit
11858 required exit node for certain sites.
11859 - Add a new TrackHostExits config directive to trigger addressmaps
11860 for certain incoming socks addresses -- for sites that break when
11861 your exit keeps changing (based on patch by Mike Perry).
11862 - Redo the client-side dns cache so it's just an addressmap too.
11863 - Notice when our IP changes, and reset stats/uptime/reachability.
11864 - When an application is using socks5, give him the whole variety of
11865 potential socks5 responses (connect refused, host unreachable, etc),
11866 rather than just "success" or "failure".
11867 - A more sane version numbering system. See
11868 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
11869 - New contributed script "exitlist": a simple python script to
11870 parse directories and find Tor nodes that exit to listed
11872 - New contributed script "privoxy-tor-toggle" to toggle whether
11873 Privoxy uses Tor. Seems to be configured for Debian by default.
11874 - Report HTTP reasons to client when getting a response from directory
11875 servers -- so you can actually know what went wrong.
11876 - New config option MaxAdvertisedBandwidth which lets you advertise
11877 a low bandwidthrate (to not attract as many circuits) while still
11878 allowing a higher bandwidthrate in reality.
11880 o Robustness/stability fixes:
11881 - Make Tor use Niels Provos's libevent instead of its current
11882 poll-but-sometimes-select mess. This will let us use faster async
11883 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
11885 - pthread support now too. This was forced because when we forked,
11886 we ended up wasting a lot of duplicate ram over time. Also switch
11887 to foo_r versions of some library calls to allow reentry and
11889 - Better handling for heterogeneous / unreliable nodes:
11890 - Annotate circuits w/ whether they aim to contain high uptime nodes
11891 and/or high capacity nodes. When building circuits, choose
11893 - This means that every single node in an intro rend circuit,
11894 not just the last one, will have a minimum uptime.
11895 - New config option LongLivedPorts to indicate application streams
11896 that will want high uptime circuits.
11897 - Servers reset uptime when a dir fetch entirely fails. This
11898 hopefully reflects stability of the server's network connectivity.
11899 - If somebody starts his tor server in Jan 2004 and then fixes his
11900 clock, don't make his published uptime be a year.
11901 - Reset published uptime when you wake up from hibernation.
11902 - Introduce a notion of 'internal' circs, which are chosen without
11903 regard to the exit policy of the last hop. Intro and rendezvous
11904 circs must be internal circs, to avoid leaking information. Resolve
11905 and connect streams can use internal circs if they want.
11906 - New circuit pooling algorithm: make sure to have enough circs around
11907 to satisfy any predicted ports, and also make sure to have 2 internal
11908 circs around if we've required internal circs lately (and with high
11909 uptime if we've seen that lately too).
11910 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
11911 which describes how often we retry making new circuits if current
11912 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
11913 how long we're willing to make use of an already-dirty circuit.
11914 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
11915 circ as necessary, if there are any completed ones lying around
11916 when we try to launch one.
11917 - Make hidden services try to establish a rendezvous for 30 seconds,
11918 rather than for n (where n=3) attempts to build a circuit.
11919 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
11920 "ShutdownWaitLength".
11921 - Try to be more zealous about calling connection_edge_end when
11922 things go bad with edge conns in connection.c.
11923 - Revise tor-spec to add more/better stream end reasons.
11924 - Revise all calls to connection_edge_end to avoid sending "misc",
11925 and to take errno into account where possible.
11928 - Fix a race condition that can trigger an assert, when we have a
11929 pending create cell and an OR connection fails right then.
11930 - Fix several double-mark-for-close bugs, e.g. where we were finding
11931 a conn for a cell even if that conn is already marked for close.
11932 - Make sequence of log messages when starting on win32 with no config
11933 file more reasonable.
11934 - When choosing an exit node for a new non-internal circ, don't take
11935 into account whether it'll be useful for any pending x.onion
11936 addresses -- it won't.
11937 - Turn addr_policy_compare from a tristate to a quadstate; this should
11938 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
11939 for google.com" problem.
11940 - Make "platform" string in descriptor more accurate for Win32 servers,
11941 so it's not just "unknown platform".
11942 - Fix an edge case in parsing config options (thanks weasel).
11943 If they say "--" on the commandline, it's not an option.
11944 - Reject odd-looking addresses at the client (e.g. addresses that
11945 contain a colon), rather than having the server drop them because
11947 - tor-resolve requests were ignoring .exit if there was a working circuit
11948 they could use instead.
11949 - REUSEADDR on normal platforms means you can rebind to the port
11950 right after somebody else has let it go. But REUSEADDR on win32
11951 means to let you bind to the port _even when somebody else
11952 already has it bound_! So, don't do that on Win32.
11953 - Change version parsing logic: a version is "obsolete" if it is not
11954 recommended and (1) there is a newer recommended version in the
11955 same series, or (2) there are no recommended versions in the same
11956 series, but there are some recommended versions in a newer series.
11957 A version is "new" if it is newer than any recommended version in
11959 - Stop most cases of hanging up on a socks connection without sending
11963 - Require BandwidthRate to be at least 20kB/s for servers.
11964 - When a dirserver causes you to give a warn, mention which dirserver
11966 - New config option DirAllowPrivateAddresses for authdirservers.
11967 Now by default they refuse router descriptors that have non-IP or
11968 private-IP addresses.
11969 - Stop publishing socksport in the directory, since it's not
11970 actually meant to be public. For compatibility, publish a 0 there
11972 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
11973 smart" value, that is low for servers and high for clients.
11974 - If our clock jumps forward by 100 seconds or more, assume something
11975 has gone wrong with our network and abandon all not-yet-used circs.
11976 - Warn when exit policy implicitly allows local addresses.
11977 - If we get an incredibly skewed timestamp from a dirserver mirror
11978 that isn't a verified OR, don't warn -- it's probably him that's
11980 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
11981 cookies to disk and doesn't log each web request to disk. (Thanks
11982 to Brett Carrington for pointing this out.)
11983 - When a client asks us for a dir mirror and we don't have one,
11984 launch an attempt to get a fresh one.
11985 - If we're hibernating and we get a SIGINT, exit immediately.
11986 - Add --with-dmalloc ./configure option, to track memory leaks.
11987 - And try to free all memory on closing, so we can detect what
11989 - Cache local dns resolves correctly even when they're .exit
11991 - Give a better warning when some other server advertises an
11992 ORPort that is actually an apache running ssl.
11993 - Add "opt hibernating 1" to server descriptor to make it clearer
11994 whether the server is hibernating.
11997 Changes in version 0.0.9.6 - 2005-03-24
11998 o Bugfixes on 0.0.9.x (crashes and asserts):
11999 - Add new end stream reasons to maintainance branch. Fix bug where
12000 reason (8) could trigger an assert. Prevent bug from recurring.
12001 - Apparently win32 stat wants paths to not end with a slash.
12002 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12003 blowing away the circuit that conn->cpath_layer points to, then
12004 checking to see if the circ is well-formed. Backport check to make
12005 sure we dont use the cpath on a closed connection.
12006 - Prevent circuit_resume_edge_reading_helper() from trying to package
12007 inbufs for marked-for-close streams.
12008 - Don't crash on hup if your options->address has become unresolvable.
12009 - Some systems (like OS X) sometimes accept() a connection and tell
12010 you the remote host is 0.0.0.0:0. If this happens, due to some
12011 other mis-features, we get confused; so refuse the conn for now.
12013 o Bugfixes on 0.0.9.x (other):
12014 - Fix harmless but scary "Unrecognized content encoding" warn message.
12015 - Add new stream error reason: TORPROTOCOL reason means "you are not
12016 speaking a version of Tor I understand; say bye-bye to your stream."
12017 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12018 into the future, now that we are more tolerant of skew. This
12019 resolves a bug where a Tor server would refuse to cache a directory
12020 because all the directories it gets are too far in the future;
12021 yet the Tor server never logs any complaints about clock skew.
12022 - Mac packaging magic: make man pages useable, and do not overwrite
12023 existing torrc files.
12024 - Make OS X log happily to /var/log/tor/tor.log
12027 Changes in version 0.0.9.5 - 2005-02-22
12028 o Bugfixes on 0.0.9.x:
12029 - Fix an assert race at exit nodes when resolve requests fail.
12030 - Stop picking unverified dir mirrors--it only leads to misery.
12031 - Patch from Matt Edman to make NT services work better. Service
12032 support is still not compiled into the executable by default.
12033 - Patch from Dmitri Bely so the Tor service runs better under
12034 the win32 SYSTEM account.
12035 - Make tor-resolve actually work (?) on Win32.
12036 - Fix a sign bug when getrlimit claims to have 4+ billion
12037 file descriptors available.
12038 - Stop refusing to start when bandwidthburst == bandwidthrate.
12039 - When create cells have been on the onion queue more than five
12040 seconds, just send back a destroy and take them off the list.
12043 Changes in version 0.0.9.4 - 2005-02-03
12044 o Bugfixes on 0.0.9:
12045 - Fix an assert bug that took down most of our servers: when
12046 a server claims to have 1 GB of bandwidthburst, don't
12048 - Don't crash as badly if we have spawned the max allowed number
12049 of dnsworkers, or we're out of file descriptors.
12050 - Block more file-sharing ports in the default exit policy.
12051 - MaxConn is now automatically set to the hard limit of max
12052 file descriptors we're allowed (ulimit -n), minus a few for
12054 - Give a clearer message when servers need to raise their
12055 ulimit -n when they start running out of file descriptors.
12056 - SGI Compatibility patches from Jan Schaumann.
12057 - Tolerate a corrupt cached directory better.
12058 - When a dirserver hasn't approved your server, list which one.
12059 - Go into soft hibernation after 95% of the bandwidth is used,
12060 not 99%. This is especially important for daily hibernators who
12061 have a small accounting max. Hopefully it will result in fewer
12062 cut connections when the hard hibernation starts.
12063 - Load-balance better when using servers that claim more than
12064 800kB/s of capacity.
12065 - Make NT services work (experimental, only used if compiled in).
12068 Changes in version 0.0.9.3 - 2005-01-21
12069 o Bugfixes on 0.0.9:
12070 - Backport the cpu use fixes from main branch, so busy servers won't
12071 need as much processor time.
12072 - Work better when we go offline and then come back, or when we
12073 run Tor at boot before the network is up. We do this by
12074 optimistically trying to fetch a new directory whenever an
12075 application request comes in and we think we're offline -- the
12076 human is hopefully a good measure of when the network is back.
12077 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12078 long as you keep using them; actually publish hidserv descriptors
12079 shortly after they change, rather than waiting 20-40 minutes.
12080 - Enable Mac startup script by default.
12081 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12082 - When you update AllowUnverifiedNodes or FirewallPorts via the
12083 controller's setconf feature, we were always appending, never
12085 - When you update HiddenServiceDir via setconf, it was screwing up
12086 the order of reading the lines, making it fail.
12087 - Do not rewrite a cached directory back to the cache; otherwise we
12088 will think it is recent and not fetch a newer one on startup.
12089 - Workaround for webservers that lie about Content-Encoding: Tor
12090 now tries to autodetect compressed directories and compression
12091 itself. This lets us Proxypass dir fetches through apache.
12094 Changes in version 0.0.9.2 - 2005-01-04
12095 o Bugfixes on 0.0.9 (crashes and asserts):
12096 - Fix an assert on startup when the disk is full and you're logging
12098 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12099 style address, then we'd crash.
12100 - Fix an assert trigger when the running-routers string we get from
12101 a dirserver is broken.
12102 - Make worker threads start and run on win32. Now win32 servers
12104 - Bandaid (not actually fix, but now it doesn't crash) an assert
12105 where the dns worker dies mysteriously and the main Tor process
12106 doesn't remember anything about the address it was resolving.
12108 o Bugfixes on 0.0.9 (Win32):
12109 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12110 name out of the warning/assert messages.
12111 - Fix a superficial "unhandled error on read" bug on win32.
12112 - The win32 installer no longer requires a click-through for our
12113 license, since our Free Software license grants rights but does not
12115 - Win32: When connecting to a dirserver fails, try another one
12116 immediately. (This was already working for non-win32 Tors.)
12117 - Stop trying to parse $HOME on win32 when hunting for default
12119 - Make tor-resolve.c work on win32 by calling network_init().
12121 o Bugfixes on 0.0.9 (other):
12122 - Make 0.0.9.x build on Solaris again.
12123 - Due to a fencepost error, we were blowing away the \n when reporting
12124 confvalue items in the controller. So asking for multiple config
12125 values at once couldn't work.
12126 - When listing circuits that are pending on an opening OR connection,
12127 if we're an OR we were listing circuits that *end* at us as
12128 being pending on every listener, dns/cpu worker, etc. Stop that.
12129 - Dirservers were failing to create 'running-routers' or 'directory'
12130 strings if we had more than some threshold of routers. Fix them so
12131 they can handle any number of routers.
12132 - Fix a superficial "Duplicate mark for close" bug.
12133 - Stop checking for clock skew for OR connections, even for servers.
12134 - Fix a fencepost error that was chopping off the last letter of any
12135 nickname that is the maximum allowed nickname length.
12136 - Update URLs in log messages so they point to the new website.
12137 - Fix a potential problem in mangling server private keys while
12138 writing to disk (not triggered yet, as far as we know).
12139 - Include the licenses for other free software we include in Tor,
12140 now that we're shipping binary distributions more regularly.
12143 Changes in version 0.0.9.1 - 2004-12-15
12144 o Bugfixes on 0.0.9:
12145 - Make hibernation actually work.
12146 - Make HashedControlPassword config option work.
12147 - When we're reporting event circuit status to a controller,
12148 don't use the stream status code.
12151 Changes in version 0.0.9 - 2004-12-12
12153 - Clean up manpage and torrc.sample file.
12154 - Clean up severities and text of log warnings.
12156 - Make servers trigger an assert when they enter hibernation.
12159 Changes in version 0.0.9rc7 - 2004-12-08
12160 o Bugfixes on 0.0.9rc:
12161 - Fix a stack-trashing crash when an exit node begins hibernating.
12162 - Avoid looking at unallocated memory while considering which
12163 ports we need to build circuits to cover.
12164 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12165 we shouldn't hold-open-until-flush if the eof arrived first.
12166 - Fix a bug with init_cookie_authentication() in the controller.
12167 - When recommending new-format log lines, if the upper bound is
12168 LOG_ERR, leave it implicit.
12170 o Bugfixes on 0.0.8.1:
12171 - Fix a whole slew of memory leaks.
12172 - Fix isspace() and friends so they still make Solaris happy
12173 but also so they don't trigger asserts on win32.
12174 - Fix parse_iso_time on platforms without strptime (eg win32).
12175 - win32: tolerate extra "readable" events better.
12176 - win32: when being multithreaded, leave parent fdarray open.
12177 - Make unit tests work on win32.
12180 Changes in version 0.0.9rc6 - 2004-12-06
12181 o Bugfixes on 0.0.9pre:
12182 - Clean up some more integer underflow opportunities (not exploitable
12184 - While hibernating, hup should not regrow our listeners.
12185 - Send an end to the streams we close when we hibernate, rather
12186 than just chopping them off.
12187 - React to eof immediately on non-open edge connections.
12189 o Bugfixes on 0.0.8.1:
12190 - Calculate timeout for waiting for a connected cell from the time
12191 we sent the begin cell, not from the time the stream started. If
12192 it took a long time to establish the circuit, we would time out
12193 right after sending the begin cell.
12194 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12195 of * as always matching, so we were picking reject *:* nodes as
12196 exit nodes too. Oops.
12199 - New circuit building strategy: keep a list of ports that we've
12200 used in the past 6 hours, and always try to have 2 circuits open
12201 or on the way that will handle each such port. Seed us with port
12202 80 so web users won't complain that Tor is "slow to start up".
12203 - Make kill -USR1 dump more useful stats about circuits.
12204 - When warning about retrying or giving up, print the address, so
12205 the user knows which one it's talking about.
12206 - If you haven't used a clean circuit in an hour, throw it away,
12207 just to be on the safe side. (This means after 6 hours a totally
12208 unused Tor client will have no circuits open.)
12211 Changes in version 0.0.9rc5 - 2004-12-01
12212 o Bugfixes on 0.0.8.1:
12213 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12214 - Let resolve conns retry/expire also, rather than sticking around
12216 - If we are using select, make sure we stay within FD_SETSIZE.
12218 o Bugfixes on 0.0.9pre:
12219 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12220 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12222 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12223 instead. Impose minima and maxima for all *Period options; impose
12224 even tighter maxima for fetching if we are a caching dirserver.
12225 Clip rather than rejecting.
12226 - Fetch cached running-routers from servers that serve it (that is,
12227 authdirservers and servers running 0.0.9rc5-cvs or later.)
12230 - Accept *:706 (silc) in default exit policy.
12231 - Implement new versioning format for post 0.1.
12232 - Support "foo.nickname.exit" addresses, to let Alice request the
12233 address "foo" as viewed by exit node "nickname". Based on a patch
12235 - Make tor --version --version dump the cvs Id of every file.
12238 Changes in version 0.0.9rc4 - 2004-11-28
12239 o Bugfixes on 0.0.8.1:
12240 - Make windows sockets actually non-blocking (oops), and handle
12241 win32 socket errors better.
12243 o Bugfixes on 0.0.9rc1:
12244 - Actually catch the -USR2 signal.
12247 Changes in version 0.0.9rc3 - 2004-11-25
12248 o Bugfixes on 0.0.8.1:
12249 - Flush the log file descriptor after we print "Tor opening log file",
12250 so we don't see those messages days later.
12252 o Bugfixes on 0.0.9rc1:
12253 - Make tor-resolve work again.
12254 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12255 - Fix an assert trigger for clients/servers handling resolves.
12258 Changes in version 0.0.9rc2 - 2004-11-24
12259 o Bugfixes on 0.0.9rc1:
12260 - I broke socks5 support while fixing the eof bug.
12261 - Allow unitless bandwidths and intervals; they default to bytes
12263 - New servers don't start out hibernating; they are active until
12264 they run out of bytes, so they have a better estimate of how
12265 long it takes, and so their operators can know they're working.
12268 Changes in version 0.0.9rc1 - 2004-11-23
12269 o Bugfixes on 0.0.8.1:
12270 - Finally fix a bug that's been plaguing us for a year:
12271 With high load, circuit package window was reaching 0. Whenever
12272 we got a circuit-level sendme, we were reading a lot on each
12273 socket, but only writing out a bit. So we would eventually reach
12274 eof. This would be noticed and acted on even when there were still
12275 bytes sitting in the inbuf.
12276 - When poll() is interrupted, we shouldn't believe the revents values.
12278 o Bugfixes on 0.0.9pre6:
12279 - Fix hibernate bug that caused pre6 to be broken.
12280 - Don't keep rephist info for routers that haven't had activity for
12281 24 hours. (This matters now that clients have keys, since we track
12283 - Never call close_temp_logs while validating log options.
12284 - Fix backslash-escaping on tor.sh.in and torctl.in.
12287 - Implement weekly/monthly/daily accounting: now you specify your
12288 hibernation properties by
12289 AccountingMax N bytes|KB|MB|GB|TB
12290 AccountingStart day|week|month [day] HH:MM
12291 Defaults to "month 1 0:00".
12292 - Let bandwidth and interval config options be specified as 5 bytes,
12293 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12294 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12295 get back to normal.)
12296 - If your requested entry or exit node has advertised bandwidth 0,
12298 - Be more greedy about filling up relay cells -- we try reading again
12299 once we've processed the stuff we read, in case enough has arrived
12300 to fill the last cell completely.
12301 - Apply NT service patch from Osamu Fujino. Still needs more work.
12304 Changes in version 0.0.9pre6 - 2004-11-15
12305 o Bugfixes on 0.0.8.1:
12306 - Fix assert failure on malformed socks4a requests.
12307 - Use identity comparison, not nickname comparison, to choose which
12308 half of circuit-ID-space each side gets to use. This is needed
12309 because sometimes we think of a router as a nickname, and sometimes
12310 as a hex ID, and we can't predict what the other side will do.
12311 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12312 write() call will fail and we handle it there.
12313 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12314 and smartlist_len, which are two major profiling offenders.
12316 o Bugfixes on 0.0.9pre5:
12317 - Fix a bug in read_all that was corrupting config files on windows.
12318 - When we're raising the max number of open file descriptors to
12319 'unlimited', don't log that we just raised it to '-1'.
12320 - Include event code with events, as required by control-spec.txt.
12321 - Don't give a fingerprint when clients do --list-fingerprint:
12322 it's misleading, because it will never be the same again.
12323 - Stop using strlcpy in tor_strndup, since it was slowing us
12325 - Remove warn on startup about missing cached-directory file.
12326 - Make kill -USR1 work again.
12327 - Hibernate if we start tor during the "wait for wakeup-time" phase
12328 of an accounting interval. Log our hibernation plans better.
12329 - Authoritative dirservers now also cache their directory, so they
12330 have it on start-up.
12333 - Fetch running-routers; cache running-routers; compress
12334 running-routers; serve compressed running-routers.z
12335 - Add NSI installer script contributed by J Doe.
12336 - Commit VC6 and VC7 workspace/project files.
12337 - Commit a tor.spec for making RPM files, with help from jbash.
12338 - Add contrib/torctl.in contributed by Glenn Fink.
12339 - Implement the control-spec's SAVECONF command, to write your
12340 configuration to torrc.
12341 - Get cookie authentication for the controller closer to working.
12342 - Include control-spec.txt in the tarball.
12343 - When set_conf changes our server descriptor, upload a new copy.
12344 But don't upload it too often if there are frequent changes.
12345 - Document authentication config in man page, and document signals
12347 - Clean up confusing parts of man page and torrc.sample.
12348 - Make expand_filename handle ~ and ~username.
12349 - Use autoconf to enable largefile support where necessary. Use
12350 ftello where available, since ftell can fail at 2GB.
12351 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12352 log more informatively.
12353 - Give a slightly more useful output for "tor -h".
12354 - Refuse application socks connections to port 0.
12355 - Check clock skew for verified servers, but allow unverified
12356 servers and clients to have any clock skew.
12357 - Break DirFetchPostPeriod into:
12358 - DirFetchPeriod for fetching full directory,
12359 - StatusFetchPeriod for fetching running-routers,
12360 - DirPostPeriod for posting server descriptor,
12361 - RendPostPeriod for posting hidden service descriptors.
12362 - Make sure the hidden service descriptors are at a random offset
12363 from each other, to hinder linkability.
12366 Changes in version 0.0.9pre5 - 2004-11-09
12367 o Bugfixes on 0.0.9pre4:
12368 - Fix a seg fault in unit tests (doesn't affect main program).
12369 - Fix an assert bug where a hidden service provider would fail if
12370 the first hop of his rendezvous circuit was down.
12371 - Hidden service operators now correctly handle version 1 style
12372 INTRODUCE1 cells (nobody generates them still, so not a critical
12374 - If do_hup fails, actually notice.
12375 - Handle more errnos from accept() without closing the listener.
12376 Some OpenBSD machines were closing their listeners because
12377 they ran out of file descriptors.
12378 - Send resolve cells to exit routers that are running a new
12379 enough version of the resolve code to work right.
12380 - Better handling of winsock includes on non-MSV win32 compilers.
12381 - Some people had wrapped their tor client/server in a script
12382 that would restart it whenever it died. This did not play well
12383 with our "shut down if your version is obsolete" code. Now people
12384 don't fetch a new directory if their local cached version is
12386 - Make our autogen.sh work on ksh as well as bash.
12389 - Hibernation: New config option "AccountingMaxKB" lets you
12390 set how many KBytes per month you want to allow your server to
12391 consume. Rather than spreading those bytes out evenly over the
12392 month, we instead hibernate for some of the month and pop up
12393 at a deterministic time, work until the bytes are consumed, then
12394 hibernate again. Config option "MonthlyAccountingStart" lets you
12395 specify which day of the month your billing cycle starts on.
12396 - Control interface: a separate program can now talk to your
12397 client/server over a socket, and get/set config options, receive
12398 notifications of circuits and streams starting/finishing/dying,
12399 bandwidth used, etc. The next step is to get some GUIs working.
12400 Let us know if you want to help out. See doc/control-spec.txt .
12401 - Ship a contrib/tor-control.py as an example script to interact
12402 with the control port.
12403 - "tor --hash-password zzyxz" will output a salted password for
12404 use in authenticating to the control interface.
12405 - New log format in config:
12406 "Log minsev[-maxsev] stdout|stderr|syslog" or
12407 "Log minsev[-maxsev] file /var/foo"
12410 - DirPolicy config option, to let people reject incoming addresses
12411 from their dirserver.
12412 - "tor --list-fingerprint" will list your identity key fingerprint
12414 - Add "pass" target for RedirectExit, to make it easier to break
12415 out of a sequence of RedirectExit rules.
12416 - Clients now generate a TLS cert too, in preparation for having
12417 them act more like real nodes.
12418 - Ship src/win32/ in the tarball, so people can use it to build.
12419 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12421 - New "router-status" line in directory, to better bind each verified
12422 nickname to its identity key.
12423 - Deprecate unofficial config option abbreviations, and abbreviations
12424 not on the command line.
12425 - Add a pure-C tor-resolve implementation.
12426 - Use getrlimit and friends to ensure we can reach MaxConn (currently
12427 1024) file descriptors.
12429 o Code security improvements, inspired by Ilja:
12430 - Replace sprintf with snprintf. (I think they were all safe, but
12432 - Replace strcpy/strncpy with strlcpy in more places.
12433 - Avoid strcat; use snprintf or strlcat instead.
12434 - snprintf wrapper with consistent (though not C99) overflow behavior.
12437 Changes in version 0.0.9pre4 - 2004-10-17
12438 o Bugfixes on 0.0.9pre3:
12439 - If the server doesn't specify an exit policy, use the real default
12440 exit policy, not reject *:*.
12441 - Ignore fascistfirewall when uploading/downloading hidden service
12442 descriptors, since we go through Tor for those; and when using
12443 an HttpProxy, since we assume it can reach them all.
12444 - When looking for an authoritative dirserver, use only the ones
12445 configured at boot. Don't bother looking in the directory.
12446 - The rest of the fix for get_default_conf_file() on older win32.
12447 - Make 'Routerfile' config option obsolete.
12450 - New 'MyFamily nick1,...' config option for a server to
12451 specify other servers that shouldn't be used in the same circuit
12452 with it. Only believed if nick1 also specifies us.
12453 - New 'NodeFamily nick1,nick2,...' config option for a client to
12454 specify nodes that it doesn't want to use in the same circuit.
12455 - New 'Redirectexit pattern address:port' config option for a
12456 server to redirect exit connections, e.g. to a local squid.
12459 Changes in version 0.0.9pre3 - 2004-10-13
12460 o Bugfixes on 0.0.8.1:
12461 - Better torrc example lines for dirbindaddress and orbindaddress.
12462 - Improved bounds checking on parsed ints (e.g. config options and
12463 the ones we find in directories.)
12464 - Better handling of size_t vs int, so we're more robust on 64
12466 - Fix the rest of the bug where a newly started OR would appear
12467 as unverified even after we've added his fingerprint and hupped
12469 - Fix a bug from 0.0.7: when read() failed on a stream, we would
12470 close it without sending back an end. So 'connection refused'
12471 would simply be ignored and the user would get no response.
12473 o Bugfixes on 0.0.9pre2:
12474 - Serving the cached-on-disk directory to people is bad. We now
12475 provide no directory until we've fetched a fresh one.
12476 - Workaround for bug on windows where cached-directories get crlf
12478 - Make get_default_conf_file() work on older windows too.
12479 - If we write a *:* exit policy line in the descriptor, don't write
12480 any more exit policy lines.
12483 - Use only 0.0.9pre1 and later servers for resolve cells.
12484 - Make the dirservers file obsolete.
12485 - Include a dir-signing-key token in directories to tell the
12486 parsing entity which key is being used to sign.
12487 - Remove the built-in bulky default dirservers string.
12488 - New config option "Dirserver %s:%d [fingerprint]", which can be
12489 repeated as many times as needed. If no dirservers specified,
12490 default to moria1,moria2,tor26.
12491 - Make moria2 advertise a dirport of 80, so people behind firewalls
12492 will be able to get a directory.
12493 - Http proxy support
12494 - Dirservers translate requests for http://%s:%d/x to /x
12495 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12496 be routed through this host.
12497 - Clients ask for /tor/x rather than /x for new enough dirservers.
12498 This way we can one day coexist peacefully with apache.
12499 - Clients specify a "Host: %s%d" http header, to be compatible
12500 with more proxies, and so running squid on an exit node can work.
12503 Changes in version 0.0.8.1 - 2004-10-13
12505 - Fix a seg fault that can be triggered remotely for Tor
12506 clients/servers with an open dirport.
12507 - Fix a rare assert trigger, where routerinfos for entries in
12508 our cpath would expire while we're building the path.
12509 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12510 - Fix a rare seg fault for people running hidden services on
12511 intermittent connections.
12512 - Fix a bug in parsing opt keywords with objects.
12513 - Fix a stale pointer assert bug when a stream detaches and
12515 - Fix a string format vulnerability (probably not exploitable)
12516 in reporting stats locally.
12517 - Fix an assert trigger: sometimes launching circuits can fail
12518 immediately, e.g. because too many circuits have failed recently.
12519 - Fix a compile warning on 64 bit platforms.
12522 Changes in version 0.0.9pre2 - 2004-10-03
12524 - Make fetching a cached directory work for 64-bit platforms too.
12525 - Make zlib.h a required header, not an optional header.
12528 Changes in version 0.0.9pre1 - 2004-10-01
12530 - Stop using separate defaults for no-config-file and
12531 empty-config-file. Now you have to explicitly turn off SocksPort,
12532 if you don't want it open.
12533 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12534 - Improve man page to mention more of the 0.0.8 features.
12535 - Fix a rare seg fault for people running hidden services on
12536 intermittent connections.
12537 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12539 - Fix more dns related bugs: send back resolve_failed and end cells
12540 more reliably when the resolve fails, rather than closing the
12541 circuit and then trying to send the cell. Also attach dummy resolve
12542 connections to a circuit *before* calling dns_resolve(), to fix
12543 a bug where cached answers would never be sent in RESOLVED cells.
12544 - When we run out of disk space, or other log writing error, don't
12545 crash. Just stop logging to that log and continue.
12546 - We were starting to daemonize before we opened our logs, so if
12547 there were any problems opening logs, we would complain to stderr,
12548 which wouldn't work, and then mysteriously exit.
12549 - Fix a rare bug where sometimes a verified OR would connect to us
12550 before he'd uploaded his descriptor, which would cause us to
12551 assign conn->nickname as though he's unverified. Now we look through
12552 the fingerprint list to see if he's there.
12553 - Fix a rare assert trigger, where routerinfos for entries in
12554 our cpath would expire while we're building the path.
12557 - Clients can ask dirservers for /dir.z to get a compressed version
12558 of the directory. Only works for servers running 0.0.9, of course.
12559 - Make clients cache directories and use them to seed their router
12560 lists at startup. This means clients have a datadir again.
12561 - Configuration infrastructure support for warning on obsolete
12563 - Respond to content-encoding headers by trying to uncompress as
12565 - Reply with a deflated directory when a client asks for "dir.z".
12566 We could use allow-encodings instead, but allow-encodings isn't
12567 specified in HTTP 1.0.
12568 - Raise the max dns workers from 50 to 100.
12569 - Discourage people from setting their dirfetchpostperiod more often
12570 than once per minute.
12571 - Protect dirservers from overzealous descriptor uploading -- wait
12572 10 seconds after directory gets dirty, before regenerating.
12575 Changes in version 0.0.8 - 2004-08-25
12576 o Port it to SunOS 5.9 / Athena
12579 Changes in version 0.0.8rc2 - 2004-08-20
12580 o Make it compile on cygwin again.
12581 o When picking unverified routers, skip those with low uptime and/or
12582 low bandwidth, depending on what properties you care about.
12585 Changes in version 0.0.8rc1 - 2004-08-18
12586 o Changes from 0.0.7.3:
12588 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12589 don't put it into the client dns cache.
12590 - If a begin failed due to exit policy, but we believe the IP address
12591 should have been allowed, switch that router to exitpolicy reject *:*
12592 until we get our next directory.
12594 - Clients choose nodes proportional to advertised bandwidth.
12595 - Avoid using nodes with low uptime as introduction points.
12596 - Handle servers with dynamic IP addresses: don't replace
12597 options->Address with the resolved one at startup, and
12598 detect our address right before we make a routerinfo each time.
12599 - 'FascistFirewall' option to pick dirservers and ORs on specific
12600 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12601 which ports are open. (Defaults to 80,443)
12602 - Be more aggressive about trying to make circuits when the network
12603 has changed (e.g. when you unsuspend your laptop).
12604 - Check for time skew on http headers; report date in response to
12606 - If the entrynode config line has only one node, don't pick it as
12608 - Add strict{entry|exit}nodes config options. If set to 1, then
12609 we refuse to build circuits that don't include the specified entry
12611 - OutboundBindAddress config option, to bind to a specific
12612 IP address for outgoing connect()s.
12613 - End truncated log entries (e.g. directories) with "[truncated]".
12615 o Patches to 0.0.8preX:
12617 - Patches to compile and run on win32 again (maybe)?
12618 - Fix crash when looking for ~/.torrc with no $HOME set.
12619 - Fix a race bug in the unit tests.
12620 - Handle verified/unverified name collisions better when new
12621 routerinfo's arrive in a directory.
12622 - Sometimes routers were getting entered into the stats before
12623 we'd assigned their identity_digest. Oops.
12624 - Only pick and establish intro points after we've gotten a
12627 - AllowUnverifiedNodes config option to let circuits choose no-name
12628 routers in entry,middle,exit,introduction,rendezvous positions.
12629 Allow middle and rendezvous positions by default.
12630 - Add a man page for tor-resolve.
12633 Changes in version 0.0.7.3 - 2004-08-12
12634 o Stop dnsworkers from triggering an assert failure when you
12635 ask them to resolve the host "".
12638 Changes in version 0.0.8pre3 - 2004-08-09
12639 o Changes from 0.0.7.2:
12640 - Allow multiple ORs with same nickname in routerlist -- now when
12641 people give us one identity key for a nickname, then later
12642 another, we don't constantly complain until the first expires.
12643 - Remember used bandwidth (both in and out), and publish 15-minute
12644 snapshots for the past day into our descriptor.
12645 - You can now fetch $DIRURL/running-routers to get just the
12646 running-routers line, not the whole descriptor list. (But
12647 clients don't use this yet.)
12648 - When people mistakenly use Tor as an http proxy, point them
12649 at the tor-doc.html rather than the INSTALL.
12650 - Remove our mostly unused -- and broken -- hex_encode()
12651 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12652 for pointing out this bug.)
12653 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12654 fewer problems with people using the wrong key.
12655 - Change the default exit policy to reject the default edonkey,
12656 kazaa, gnutella ports.
12657 - Add replace_file() to util.[ch] to handle win32's rename().
12659 o Changes from 0.0.8preX:
12660 - Fix two bugs in saving onion keys to disk when rotating, so
12661 hopefully we'll get fewer people using old onion keys.
12662 - Fix an assert error that was making SocksPolicy not work.
12663 - Be willing to expire routers that have an open dirport -- it's
12664 just the authoritative dirservers we want to not forget.
12665 - Reject tor-resolve requests for .onion addresses early, so we
12666 don't build a whole rendezvous circuit and then fail.
12667 - When you're warning a server that he's unverified, don't cry
12668 wolf unpredictably.
12669 - Fix a race condition: don't try to extend onto a connection
12670 that's still handshaking.
12671 - For servers in clique mode, require the conn to be open before
12672 you'll choose it for your path.
12673 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12674 end relay cell, etc.
12675 - Measure bandwidth capacity over the last 24 hours, not just 12
12676 - Bugfix: authoritative dirservers were making and signing a new
12677 directory for each client, rather than reusing the cached one.
12680 Changes in version 0.0.8pre2 - 2004-08-04
12681 o Changes from 0.0.7.2:
12683 - Check directory signature _before_ you decide whether you're
12684 you're running an obsolete version and should exit.
12685 - Check directory signature _before_ you parse the running-routers
12686 list to decide who's running or verified.
12687 - Bugfixes and features:
12688 - Check return value of fclose while writing to disk, so we don't
12689 end up with broken files when servers run out of disk space.
12690 - Log a warning if the user uses an unsafe socks variant, so people
12691 are more likely to learn about privoxy or socat.
12692 - Dirservers now include RFC1123-style dates in the HTTP headers,
12693 which one day we will use to better detect clock skew.
12695 o Changes from 0.0.8pre1:
12696 - Make it compile without warnings again on win32.
12697 - Log a warning if you're running an unverified server, to let you
12698 know you might want to get it verified.
12699 - Only pick a default nickname if you plan to be a server.
12702 Changes in version 0.0.8pre1 - 2004-07-23
12704 - Made our unit tests compile again on OpenBSD 3.5, and tor
12705 itself compile again on OpenBSD on a sparc64.
12706 - We were neglecting milliseconds when logging on win32, so
12707 everything appeared to happen at the beginning of each second.
12709 o Protocol changes:
12710 - 'Extend' relay cell payloads now include the digest of the
12711 intended next hop's identity key. Now we can verify that we're
12712 extending to the right router, and also extend to routers we
12713 hadn't heard of before.
12716 - Tor nodes can now act as relays (with an advertised ORPort)
12717 without being manually verified by the dirserver operators.
12718 - Uploaded descriptors of unverified routers are now accepted
12719 by the dirservers, and included in the directory.
12720 - Verified routers are listed by nickname in the running-routers
12721 list; unverified routers are listed as "$<fingerprint>".
12722 - We now use hash-of-identity-key in most places rather than
12723 nickname or addr:port, for improved security/flexibility.
12724 - To avoid Sybil attacks, paths still use only verified servers.
12725 But now we have a chance to play around with hybrid approaches.
12726 - Nodes track bandwidth usage to estimate capacity (not used yet).
12727 - ClientOnly option for nodes that never want to become servers.
12728 - Directory caching.
12729 - "AuthoritativeDir 1" option for the official dirservers.
12730 - Now other nodes (clients and servers) will cache the latest
12731 directory they've pulled down.
12732 - They can enable their DirPort to serve it to others.
12733 - Clients will pull down a directory from any node with an open
12734 DirPort, and check the signature/timestamp correctly.
12735 - Authoritative dirservers now fetch directories from other
12736 authdirservers, to stay better synced.
12737 - Running-routers list tells who's down also, along with noting
12738 if they're verified (listed by nickname) or unverified (listed
12740 - Allow dirservers to serve running-router list separately.
12741 This isn't used yet.
12742 - ORs connect-on-demand to other ORs
12743 - If you get an extend cell to an OR you're not connected to,
12744 connect, handshake, and forward the create cell.
12745 - The authoritative dirservers stay connected to everybody,
12746 and everybody stays connected to 0.0.7 servers, but otherwise
12747 clients/servers expire unused connections after 5 minutes.
12748 - When servers get a sigint, they delay 30 seconds (refusing new
12749 connections) then exit. A second sigint causes immediate exit.
12750 - File and name management:
12751 - Look for .torrc if no CONFDIR "torrc" is found.
12752 - If no datadir is defined, then choose, make, and secure ~/.tor
12754 - If torrc not found, exitpolicy reject *:*.
12755 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
12756 - If no nickname is defined, derive default from hostname.
12757 - Rename secret key files, e.g. identity.key -> secret_id_key,
12758 to discourage people from mailing their identity key to tor-ops.
12759 - Refuse to build a circuit before the directory has arrived --
12760 it won't work anyway, since you won't know the right onion keys
12762 - Try other dirservers immediately if the one you try is down. This
12763 should tolerate down dirservers better now.
12764 - Parse tor version numbers so we can do an is-newer-than check
12765 rather than an is-in-the-list check.
12766 - New socks command 'resolve', to let us shim gethostbyname()
12768 - A 'tor_resolve' script to access the socks resolve functionality.
12769 - A new socks-extensions.txt doc file to describe our
12770 interpretation and extensions to the socks protocols.
12771 - Add a ContactInfo option, which gets published in descriptor.
12772 - Publish OR uptime in descriptor (and thus in directory) too.
12773 - Write tor version at the top of each log file
12774 - New docs in the tarball:
12776 - Document that you should proxy your SSL traffic too.
12779 Changes in version 0.0.7.2 - 2004-07-07
12780 o A better fix for the 0.0.0.0 problem, that will hopefully
12781 eliminate the remaining related assertion failures.
12784 Changes in version 0.0.7.1 - 2004-07-04
12785 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
12786 since internally we use 0.0.0.0 to signify "not yet resolved".
12789 Changes in version 0.0.7 - 2004-06-07
12790 o Updated the man page to reflect the new features.
12793 Changes in version 0.0.7rc2 - 2004-06-06
12794 o Changes from 0.0.7rc1:
12795 - Make it build on Win32 again.
12796 o Changes from 0.0.6.2:
12797 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12801 Changes in version 0.0.7rc1 - 2004-06-02
12803 - On sighup, we were adding another log without removing the first
12804 one. So log messages would get duplicated n times for n sighups.
12805 - Several cases of using a connection after we'd freed it. The
12806 problem was that connections that are pending resolve are in both
12807 the pending_resolve tree, and also the circuit's resolving_streams
12808 list. When you want to remove one, you must remove it from both.
12809 - Fix a double-mark-for-close where an end cell arrived for a
12810 resolving stream, and then the resolve failed.
12811 - Check directory signatures based on name of signer, not on whom
12812 we got the directory from. This will let us cache directories more
12815 - Crank up some of our constants to handle more users.
12818 Changes in version 0.0.7pre1 - 2004-06-02
12819 o Fixes for crashes and other obnoxious bugs:
12820 - Fix an epipe bug: sometimes when directory connections failed
12821 to connect, we would give them a chance to flush before closing
12823 - When we detached from a circuit because of resolvefailed, we
12824 would immediately try the same circuit twice more, and then
12825 give up on the resolve thinking we'd tried three different
12827 - Limit the number of intro circuits we'll attempt to build for a
12828 hidden service per 15-minute period.
12829 - Check recommended-software string *early*, before actually parsing
12830 the directory. Thus we can detect an obsolete version and exit,
12831 even if the new directory format doesn't parse.
12832 o Fixes for security bugs:
12833 - Remember which nodes are dirservers when you startup, and if a
12834 random OR enables his dirport, don't automatically assume he's
12835 a trusted dirserver.
12837 - Directory connections were asking the wrong poll socket to
12838 start writing, and not asking themselves to start writing.
12839 - When we detached from a circuit because we sent a begin but
12840 didn't get a connected, we would use it again the first time;
12841 but after that we would correctly switch to a different one.
12842 - Stop warning when the first onion decrypt attempt fails; they
12843 will sometimes legitimately fail now that we rotate keys.
12844 - Override unaligned-access-ok check when $host_cpu is ia64 or
12845 arm. Apparently they allow it but the kernel whines.
12846 - Dirservers try to reconnect periodically too, in case connections
12848 - Fix some memory leaks in directory servers.
12849 - Allow backslash in Win32 filenames.
12850 - Made Tor build complain-free on FreeBSD, hopefully without
12851 breaking other BSD builds. We'll see.
12853 - Doxygen markup on all functions and global variables.
12854 - Make directory functions update routerlist, not replace it. So
12855 now directory disagreements are not so critical a problem.
12856 - Remove the upper limit on number of descriptors in a dirserver's
12857 directory (not that we were anywhere close).
12858 - Allow multiple logfiles at different severity ranges.
12859 - Allow *BindAddress to specify ":port" rather than setting *Port
12860 separately. Allow multiple instances of each BindAddress config
12861 option, so you can bind to multiple interfaces if you want.
12862 - Allow multiple exit policy lines, which are processed in order.
12863 Now we don't need that huge line with all the commas in it.
12864 - Enable accept/reject policies on SOCKS connections, so you can bind
12865 to 0.0.0.0 but still control who can use your OP.
12868 Changes in version 0.0.6.2 - 2004-05-16
12869 o Our integrity-checking digest was checking only the most recent cell,
12870 not the previous cells like we'd thought.
12871 Thanks to Stefan Mark for finding the flaw!
12874 Changes in version 0.0.6.1 - 2004-05-06
12875 o Fix two bugs in our AES counter-mode implementation (this affected
12876 onion-level stream encryption, but not TLS-level). It turns
12877 out we were doing something much more akin to a 16-character
12878 polyalphabetic cipher. Oops.
12879 Thanks to Stefan Mark for finding the flaw!
12880 o Retire moria3 as a directory server, and add tor26 as a directory
12884 Changes in version 0.0.6 - 2004-05-02
12885 [version bump only]
12888 Changes in version 0.0.6rc4 - 2004-05-01
12889 o Update the built-in dirservers list to use the new directory format
12890 o Fix a rare seg fault: if a node offering a hidden service attempts
12891 to build a circuit to Alice's rendezvous point and fails before it
12892 reaches the last hop, it retries with a different circuit, but
12894 o Handle windows socket errors correctly.
12897 Changes in version 0.0.6rc3 - 2004-04-28
12898 o Don't expire non-general excess circuits (if we had enough
12899 circuits open, we were expiring rendezvous circuits -- even
12900 when they had a stream attached. oops.)
12901 o Fetch randomness from /dev/urandom better (not via fopen/fread)
12902 o Better debugging for tls errors
12903 o Some versions of openssl have an SSL_pending function that erroneously
12904 returns bytes when there is a non-application record pending.
12905 o Set Content-Type on the directory and hidserv descriptor.
12906 o Remove IVs from cipher code, since AES-ctr has none.
12907 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
12908 o We were using an array of length zero in a few places.
12909 o win32's gethostbyname can't resolve an IP to an IP.
12910 o win32's close can't close a socket.
12913 Changes in version 0.0.6rc2 - 2004-04-26
12914 o Fix a bug where we were closing tls connections intermittently.
12915 It turns out openssl keeps its errors around -- so if an error
12916 happens, and you don't ask about it, and then another openssl
12917 operation happens and succeeds, and you ask if there was an error,
12918 it tells you about the first error. Fun fun.
12919 o Fix a bug that's been lurking since 27 may 03 (!)
12920 When passing back a destroy cell, we would use the wrong circ id.
12921 'Mostly harmless', but still worth fixing.
12922 o Since we don't support truncateds much, don't bother sending them;
12923 just close the circ.
12924 o check for <machine/limits.h> so we build on NetBSD again (I hope).
12925 o don't crash if a conn that sent a begin has suddenly lost its circuit
12926 (this was quite rare).
12929 Changes in version 0.0.6rc1 - 2004-04-25
12930 o We now rotate link (tls context) keys and onion keys.
12931 o CREATE cells now include oaep padding, so you can tell
12932 if you decrypted them correctly.
12933 o Add bandwidthburst to server descriptor.
12934 o Directories now say which dirserver signed them.
12935 o Use a tor_assert macro that logs failed assertions too.
12938 Changes in version 0.0.6pre5 - 2004-04-18
12939 o changes from 0.0.6pre4:
12940 - make tor build on broken freebsd 5.2 installs
12941 - fix a failed assert when you try an intro point, get a nack, and try
12942 a second one and it works.
12943 - when alice uses a port that the hidden service doesn't accept,
12944 it now sends back an end cell (denied by exit policy). otherwise
12945 alice would just have to wait to time out.
12946 - fix another rare bug: when we had tried all the intro
12947 points for a hidden service, we fetched the descriptor
12948 again, but we left our introcirc thinking it had already
12949 sent an intro, so it kept waiting for a response...
12950 - bugfix: when you sleep your hidden-service laptop, as soon
12951 as it wakes up it tries to upload a service descriptor, but
12952 socketpair fails for some reason (localhost not up yet?).
12953 now we simply give up on that upload, and we'll try again later.
12954 i'd still like to find the bug though.
12955 - if an intro circ waiting for an ack dies before getting one, then
12957 - we were reusing stale service descriptors and refetching usable
12961 Changes in version 0.0.6pre4 - 2004-04-14
12962 o changes from 0.0.6pre3:
12963 - when bob fails to connect to the rendezvous point, and his
12964 circ didn't fail because of the rendezvous point itself, then
12965 he retries a couple of times
12966 - we expire introduction and rendezvous circs more thoroughly
12967 (sometimes they were hanging around forever)
12968 - we expire unattached rendezvous streams that have been around
12969 too long (they were sticking around forever).
12970 - fix a measly fencepost error that was crashing everybody with
12974 Changes in version 0.0.6pre3 - 2004-04-14
12975 o changes from 0.0.6pre2:
12976 - make hup work again
12977 - fix some memory leaks for dirservers
12978 - allow more skew in rendezvous descriptor timestamps, to help
12979 handle people like blanu who don't know what time it is
12980 - normal circs are 3 hops, but some rend/intro circs are 4, if
12981 the initiator doesn't get to choose the last hop
12982 - send acks for introductions, so alice can know whether to try
12984 - bob publishes intro points more correctly
12985 o changes from 0.0.5:
12986 - fix an assert trigger that's been plaguing us since the days
12987 of 0.0.2prexx (thanks weasel!)
12988 - retry stream correctly when we fail to connect because of
12989 exit-policy-reject (should try another) or can't-resolve-address
12990 (also should try another, because dns on random internet servers
12992 - when we hup a dirserver and we've *removed* a server from the
12993 approved-routers list, now we remove that server from the
12994 in-memory directories too
12997 Changes in version 0.0.6pre2 - 2004-04-08
12998 o We fixed our base32 implementation. Now it works on all architectures.
13001 Changes in version 0.0.6pre1 - 2004-04-08
13003 - Hidden services and rendezvous points are implemented. Go to
13004 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13005 hidden services. (This only works via a socks4a proxy such as
13006 Privoxy, and currently it's quite slow.)
13009 Changes in version 0.0.5 - 2004-03-30
13010 [version bump only]
13013 Changes in version 0.0.5rc3 - 2004-03-29
13014 o Install torrc as torrc.sample -- we no longer clobber your
13016 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13017 o Add in a 'notice' log level for things the operator should hear
13018 but that aren't warnings
13021 Changes in version 0.0.5rc2 - 2004-03-29
13022 o Hold socks connection open until reply is flushed (if possible)
13023 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13024 the dns farm to do it.
13025 o Fix c99 aliasing warnings in rephist.c
13026 o Don't include server descriptors that are older than 24 hours in the
13028 o Give socks 'reject' replies their whole 15s to attempt to flush,
13029 rather than seeing the 60s timeout and assuming the flush had failed.
13030 o Clean automake droppings from the cvs repository
13033 Changes in version 0.0.5rc1 - 2004-03-28
13034 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13035 o Only build circuits after we've fetched the directory: clients were
13036 using only the directory servers before they'd fetched a directory.
13037 This also means longer startup time; so it goes.
13038 o Fix an assert trigger where an OP would fail to handshake, and we'd
13039 expect it to have a nickname.
13040 o Work around a tsocks bug: do a socks reject when AP connection dies
13041 early, else tsocks goes into an infinite loop.
13044 Changes in version 0.0.4 - 2004-03-26
13045 o When connecting to a dirserver or OR and the network is down,
13049 Changes in version 0.0.3 - 2004-03-26
13050 o Warn and fail if server chose a nickname with illegal characters
13051 o Port to Solaris and Sparc:
13052 - include missing header fcntl.h
13053 - have autoconf find -lsocket -lnsl automatically
13054 - deal with hardware word alignment
13055 - make uname() work (solaris has a different return convention)
13056 - switch from using signal() to sigaction()
13057 o Preliminary work on reputation system:
13058 - Keep statistics on success/fail of connect attempts; they're published
13059 by kill -USR1 currently.
13060 - Add a RunTesting option to try to learn link state by creating test
13061 circuits, even when SocksPort is off.
13062 - Remove unused open circuits when there are too many.
13065 Changes in version 0.0.2 - 2004-03-19
13066 - Include strlcpy and strlcat for safer string ops
13067 - define INADDR_NONE so we compile (but still not run) on solaris
13070 Changes in version 0.0.2pre27 - 2004-03-14
13072 - Allow internal tor networks (we were rejecting internal IPs,
13073 now we allow them if they're set explicitly).
13074 - And fix a few endian issues.
13077 Changes in version 0.0.2pre26 - 2004-03-14
13079 - If a stream times out after 15s without a connected cell, don't
13080 try that circuit again: try a new one.
13081 - Retry streams at most 4 times. Then give up.
13082 - When a dirserver gets a descriptor from an unknown router, it
13083 logs its fingerprint (so the dirserver operator can choose to
13084 accept it even without mail from the server operator).
13085 - Inform unapproved servers when we reject their descriptors.
13086 - Make tor build on Windows again. It works as a client, who knows
13088 - Clearer instructions in the torrc for how to set up a server.
13089 - Be more efficient about reading fd's when our global token bucket
13090 (used for rate limiting) becomes empty.
13092 - Stop asserting that computers always go forward in time. It's
13094 - When we sent a cell (e.g. destroy) and then marked an OR connection
13095 expired, we might close it before finishing a flush if the other
13096 side isn't reading right then.
13097 - Don't allow dirservers to start if they haven't defined
13098 RecommendedVersions
13099 - We were caching transient dns failures. Oops.
13100 - Prevent servers from publishing an internal IP as their address.
13101 - Address a strcat vulnerability in circuit.c
13104 Changes in version 0.0.2pre25 - 2004-03-04
13106 - Put the OR's IP in its router descriptor, not its fqdn. That way
13107 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13110 - If the user typed in an address that didn't resolve, the server
13114 Changes in version 0.0.2pre24 - 2004-03-03
13116 - Fix an assertion failure in dns.c, where we were trying to dequeue
13117 a pending dns resolve even if it wasn't pending
13118 - Fix a spurious socks5 warning about still trying to write after the
13119 connection is finished.
13120 - Hold certain marked_for_close connections open until they're finished
13121 flushing, rather than losing bytes by closing them too early.
13122 - Correctly report the reason for ending a stream
13123 - Remove some duplicate calls to connection_mark_for_close
13124 - Put switch_id and start_daemon earlier in the boot sequence, so it
13125 will actually try to chdir() to options.DataDirectory
13126 - Make 'make test' exit(1) if a test fails; fix some unit tests
13127 - Make tor fail when you use a config option it doesn't know about,
13128 rather than warn and continue.
13129 - Make --version work
13130 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13133 Changes in version 0.0.2pre23 - 2004-02-29
13135 - Print a statement when the first circ is finished, so the user
13136 knows it's working.
13137 - If a relay cell is unrecognized at the end of the circuit,
13138 send back a destroy. (So attacks to mutate cells are more
13140 - New config option 'excludenodes' to avoid certain nodes for circuits.
13141 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13142 so you can collect coredumps there.
13144 - Fix a bug in tls flushing where sometimes data got wedged and
13145 didn't flush until more data got sent. Hopefully this bug was
13146 a big factor in the random delays we were seeing.
13147 - Make 'connected' cells include the resolved IP, so the client
13148 dns cache actually gets populated.
13149 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13150 - When we time-out on a stream and detach from the circuit, send an
13151 end cell down it first.
13152 - Only warn about an unknown router (in exitnodes, entrynodes,
13153 excludenodes) after we've fetched a directory.
13156 Changes in version 0.0.2pre22 - 2004-02-26
13158 - Servers publish less revealing uname information in descriptors.
13159 - More memory tracking and assertions, to crash more usefully when
13161 - If the default torrc isn't there, just use some default defaults.
13162 Plus provide an internal dirservers file if they don't have one.
13163 - When the user tries to use Tor as an http proxy, give them an http
13164 501 failure explaining that we're a socks proxy.
13165 - Dump a new router.desc on hup, to help confused people who change
13166 their exit policies and then wonder why router.desc doesn't reflect
13168 - Clean up the generic tor.sh init script that we ship with.
13170 - If the exit stream is pending on the resolve, and a destroy arrives,
13171 then the stream wasn't getting removed from the pending list. I
13172 think this was the one causing recent server crashes.
13173 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13174 - When it couldn't resolve any dirservers, it was useless from then on.
13175 Now it reloads the RouterFile (or default dirservers) if it has no
13177 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13178 many users don't even *have* a /usr/local/sbin/.
13181 Changes in version 0.0.2pre21 - 2004-02-18
13183 - There's a ChangeLog file that actually reflects the changelog.
13184 - There's a 'torify' wrapper script, with an accompanying
13185 tor-tsocks.conf, that simplifies the process of using tsocks for
13186 tor. It even has a man page.
13187 - The tor binary gets installed to sbin rather than bin now.
13188 - Retry streams where the connected cell hasn't arrived in 15 seconds
13189 - Clean up exit policy handling -- get the default out of the torrc,
13190 so we can update it without forcing each server operator to fix
13192 - Allow imaps and pop3s in default exit policy
13194 - Prevent picking middleman nodes as the last node in the circuit
13197 Changes in version 0.0.2pre20 - 2004-01-30
13199 - We now have a deb package, and it's in debian unstable. Go to
13200 it, apt-getters. :)
13201 - I've split the TotalBandwidth option into BandwidthRate (how many
13202 bytes per second you want to allow, long-term) and
13203 BandwidthBurst (how many bytes you will allow at once before the cap
13204 kicks in). This better token bucket approach lets you, say, set
13205 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13206 performance while not exceeding your monthly bandwidth quota.
13207 - Push out a tls record's worth of data once you've got it, rather
13208 than waiting until you've read everything waiting to be read. This
13209 may improve performance by pipelining better. We'll see.
13210 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13211 from failed circuits (if they haven't been connected yet) and attach
13213 - Expire old streams that haven't managed to connect. Some day we'll
13214 have them reattach to new circuits instead.
13217 - Fix several memory leaks that were causing servers to become bloated
13219 - Fix a few very rare assert triggers. A few more remain.
13220 - Setuid to User _before_ complaining about running as root.
13223 Changes in version 0.0.2pre19 - 2004-01-07
13225 - Fix deadlock condition in dns farm. We were telling a child to die by
13226 closing the parent's file descriptor to him. But newer children were
13227 inheriting the open file descriptor from the parent, and since they
13228 weren't closing it, the socket never closed, so the child never read
13229 eof, so he never knew to exit. Similarly, dns workers were holding
13230 open other sockets, leading to all sorts of chaos.
13231 - New cleaner daemon() code for forking and backgrounding.
13232 - If you log to a file, it now prints an entry at the top of the
13233 logfile so you know it's working.
13234 - The onionskin challenge length was 30 bytes longer than necessary.
13235 - Started to patch up the spec so it's not quite so out of date.
13238 Changes in version 0.0.2pre18 - 2004-01-02
13240 - Fix endian issues with the 'integrity' field in the relay header.
13241 - Fix a potential bug where connections in state
13242 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13245 Changes in version 0.0.2pre17 - 2003-12-30
13247 - Made --debuglogfile (or any second log file, actually) work.
13248 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13249 adversary could force us into an infinite loop.
13252 - Each onionskin handshake now includes a hash of the computed key,
13253 to prove the server's identity and help perfect forward secrecy.
13254 - Changed cell size from 256 to 512 bytes (working toward compatibility
13256 - Changed cell length to 2 bytes, and moved it to the relay header.
13257 - Implemented end-to-end integrity checking for the payloads of
13259 - Separated streamid from 'recognized' (otherwise circuits will get
13260 messed up when we try to have streams exit from the middle). We
13261 use the integrity-checking to confirm that a cell is addressed to
13263 - Randomize the initial circid and streamid values, so an adversary who
13264 breaks into a node can't learn how many circuits or streams have
13268 Changes in version 0.0.2pre16 - 2003-12-14
13270 - Fixed a bug that made HUP trigger an assert
13271 - Fixed a bug where a circuit that immediately failed wasn't being
13272 counted as a failed circuit in counting retries.
13275 - Now we close the circuit when we get a truncated cell: otherwise we're
13276 open to an anonymity attack where a bad node in the path truncates
13277 the circuit and then we open streams at him.
13278 - Add port ranges to exit policies
13279 - Add a conservative default exit policy
13280 - Warn if you're running tor as root
13281 - on HUP, retry OR connections and close/rebind listeners
13282 - options.EntryNodes: try these nodes first when picking the first node
13283 - options.ExitNodes: if your best choices happen to include any of
13284 your preferred exit nodes, you choose among just those preferred
13286 - options.ExcludedNodes: nodes that are never picked in path building
13289 Changes in version 0.0.2pre15 - 2003-12-03
13290 o Robustness and bugfixes:
13291 - Sometimes clients would cache incorrect DNS resolves, which would
13292 really screw things up.
13293 - An OP that goes offline would slowly leak all its sockets and stop
13295 - A wide variety of bugfixes in exit node selection, exit policy
13296 handling, and processing pending streams when a new circuit is
13298 - Pick nodes for a path only from those the directory says are up
13299 - Choose randomly from all running dirservers, not always the first one
13300 - Increase allowed http header size for directory fetch.
13301 - Stop writing to stderr (if we're daemonized it will be closed).
13302 - Enable -g always, so cores will be more useful to me.
13303 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13306 - Wrote a man page. It lists commonly used options.
13309 - Change default loglevel to warn.
13310 - Make PidFile default to null rather than littering in your CWD.
13311 - OnionRouter config option is now obsolete. Instead it just checks
13313 - Moved to a single unified torrc file for both clients and servers.
13316 Changes in version 0.0.2pre14 - 2003-11-29
13317 o Robustness and bugfixes:
13318 - Force the admin to make the DataDirectory himself
13319 - to get ownership/permissions right
13320 - so clients no longer make a DataDirectory and then never use it
13321 - fix bug where a client who was offline for 45 minutes would never
13322 pull down a directory again
13323 - fix (or at least hide really well) the dns assert bug that was
13324 causing server crashes
13325 - warnings and improved robustness wrt clockskew for certs
13326 - use the native daemon(3) to daemonize, when available
13327 - exit if bind() fails
13328 - exit if neither socksport nor orport is defined
13329 - include our own tor_timegm (Win32 doesn't have its own)
13330 - bugfix for win32 with lots of connections
13331 - fix minor bias in PRNG
13332 - make dirserver more robust to corrupt cached directory
13335 - Wrote the design document (woo)
13337 o Circuit building and exit policies:
13338 - Circuits no longer try to use nodes that the directory has told them
13340 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13341 bitcounts (18.0.0.0/8).
13342 - Make AP connections standby for a circuit if no suitable circuit
13343 exists, rather than failing
13344 - Circuits choose exit node based on addr/port, exit policies, and
13345 which AP connections are standing by
13346 - Bump min pathlen from 2 to 3
13347 - Relay end cells have a payload to describe why the stream ended.
13348 - If the stream failed because of exit policy, try again with a new
13350 - Clients have a dns cache to remember resolved addresses.
13351 - Notice more quickly when we have no working circuits
13354 - APPort is now called SocksPort
13355 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13357 - RecommendedVersions is now a config variable rather than
13358 hardcoded (for dirservers)
13359 - Reloads config on HUP
13360 - Usage info on -h or --help
13361 - If you set User and Group config vars, it'll setu/gid to them.
13364 Changes in version 0.0.2pre13 - 2003-10-19
13365 o General stability:
13366 - SSL_write no longer fails when it returns WANTWRITE and the number
13367 of bytes in the buf has changed by the next SSL_write call.
13368 - Fix segfault fetching directory when network is down
13369 - Fix a variety of minor memory leaks
13370 - Dirservers reload the fingerprints file on HUP, so I don't have
13371 to take down the network when I approve a new router
13372 - Default server config file has explicit Address line to specify fqdn
13375 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13376 - Make listener connections not ever alloc bufs
13378 o Autoconf improvements:
13379 - don't clobber an external CFLAGS in ./configure
13380 - Make install now works
13381 - create var/lib/tor on make install
13382 - autocreate a tor.sh initscript to help distribs
13383 - autocreate the torrc and sample-server-torrc with correct paths
13385 o Log files and Daemonizing now work:
13386 - If --DebugLogFile is specified, log to it at -l debug
13387 - If --LogFile is specified, use it instead of commandline
13388 - If --RunAsDaemon is set, tor forks and backgrounds on startup