1 Changes in version 0.2.3.15-alpha - 2012-04-30
2 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
3 the development branch build on Windows again.
5 o Minor bugfixes (on 0.2.2.x and earlier):
6 - Make sure that there are no unhandled pending TLS errors before
7 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
8 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
9 Bugfix on 0.1.0.5-rc; fixes bug 4528.
10 - Fix an assert that directory authorities could trigger on sighup
11 during some configuration state transitions. We now don't treat
12 it as a fatal error when the new descriptor we just generated in
13 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
14 - After we pick a directory mirror, we would refuse to use it if
15 it's in our ExcludeExitNodes list, resulting in mysterious failures
16 to bootstrap for people who just wanted to avoid exiting from
17 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
18 - When building with --enable-static-tor on OpenBSD, do not
19 erroneously attempt to link -lrt. Fixes bug 5103.
21 o Minor bugfixes (on 0.2.3.x):
22 - When Tor is built with kernel headers from a recent (last few
23 years) Linux kernel, do not fail to run on older (pre-2.6.28
24 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
25 - Fix cross-compilation isssues with mingw. Bugfixes on 0.2.3.6-alpha
27 - Fix compilation with miniupnpc version 1.6; patch from
28 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
29 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
30 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
31 - Fix compilation on platforms without unistd.h, or where environ
32 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
35 - Directory authorities are now a little more lenient at accepting
36 older router descriptors, or newer router descriptors that don't
37 make big changes. This should help ameliorate past and future
38 issues where routers think they have uploaded valid descriptors,
39 but the authorities don't think so. Fix for ticket 2479.
40 - Make the code that clients use to detect an address change be
41 IPv6-aware, so that it won't fill clients' logs with error
42 messages when trying to get the IPv4 address of an IPv6
43 connection. Implements ticket 5537.
46 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
47 authorities needed to use it for a while to keep the network working
48 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
49 that was six months ago. As of now, it should no longer be needed
53 Changes in version 0.2.3.14-alpha - 2012-04-23
54 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
55 candidate. It also dramatically speeds up AES: fast relays should
56 consider switching to the newer OpenSSL library.
58 o Directory authority changes:
59 - Change IP address for ides (v3 directory authority), and rename
63 - Avoid logging uninitialized data when unable to decode a hidden
64 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
65 - Avoid a client-side assertion failure when receiving an INTRODUCE2
66 cell on a general purpose circuit. Fixes bug 5644; bugfix on
68 - If authorities are unable to get a v2 consensus document from other
69 directory authorities, they no longer fall back to fetching
70 them from regular directory caches. Fixes bug 5635; bugfix on
71 0.2.2.26-beta, where routers stopped downloading v2 consensus
73 - When we start a Tor client with a normal consensus already cached,
74 be willing to download a microdescriptor consensus. Fixes bug 4011;
77 o Major features (performance):
78 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
79 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
80 vectorized AES implementations as appropriate. These can be much,
81 much faster than other AES implementations.
83 o Minor bugfixes (0.2.2.x and earlier):
84 - Don't launch more than 10 service-side introduction-point circuits
85 for a hidden service in five minutes. Previously, we would consider
86 launching more introduction-point circuits if at least one second
87 had passed without any introduction-point circuits failing. Fixes
88 bug 4607; bugfix on 0.0.7pre1.
89 - Change the BridgePassword feature (part of the "bridge community"
90 design, which is not yet implemented) to use a time-independent
91 comparison. The old behavior might have allowed an adversary
92 to use timing to guess the BridgePassword value. Fixes bug 5543;
93 bugfix on 0.2.0.14-alpha.
94 - Enforce correct return behavior of tor_vsscanf() when the '%%'
95 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
96 - When sending an HTTP/1.1 proxy request, include a Host header.
97 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
98 - Don't log that we have "decided to publish new relay descriptor"
99 unless we are actually publishing a descriptor. Fixes bug 3942;
100 bugfix on 0.2.2.28-beta.
102 o Minor bugfixes (0.2.3.x):
103 - Fix a bug where a bridge authority crashes (on a failed assert)
104 if it has seen no directory requests when it's time to write
105 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
106 - Fix bug stomping on ORPort option NoListen and ignoring option
107 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
108 - In the testsuite, provide a large enough buffer in the tor_sscanf
109 unit test. Otherwise we'd overrun that buffer and crash during
110 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
112 - Make sure we create the keys directory if it doesn't exist and we're
113 about to store the dynamic Diffie-Hellman parameters. Fixes bug
114 5572; bugfix on 0.2.3.13-alpha.
115 - Fix a small memory leak when trying to decode incorrect base16
116 authenticator during SAFECOOKIE authentication. Found by
117 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
120 - Add more information to a log statement that might help track down
121 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
122 non-IP address" messages (or any Bug messages, for that matter!),
123 please let us know about it.
124 - Relays now understand an IPv6 address when they get one from a
125 directory server. Resolves ticket 4875.
126 - Resolve IPv6 addresses in bridge and entry statistics to country
127 code "??" which means we at least count them. Resolves ticket 5053;
128 improves on 0.2.3.9-alpha.
129 - Update to the April 3 2012 Maxmind GeoLite Country database.
130 - Begin a doc/state-contents.txt file to explain the contents of
131 the Tor state file. Fixes bug 2987.
133 o Default torrc changes:
134 - Stop listing "socksport 9050" in torrc.sample. We open a socks
135 port on 9050 by default anyway, so this should not change anything
137 - Stop mentioning the deprecated *ListenAddress options in
138 torrc.sample. Fixes bug 5438.
139 - Document unit of bandwidth related options in sample torrc.
143 - The "torify" script no longer supports the "tsocks" socksifier
144 tool, since tsocks doesn't support DNS and UDP right for Tor.
145 Everyone should be using torsocks instead. Fixes bugs 3530 and
146 5180. Based on a patch by "ugh".
149 - Change the symmetric cipher interface so that creating and
150 initializing a stream cipher are no longer separate functions.
151 - Remove all internal support for unpadded RSA. We never used it, and
152 it would be a bad idea to start.
155 Changes in version 0.2.3.13-alpha - 2012-03-26
156 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
157 in managed pluggable transports, as well as providing other cleanups
158 that get us closer to a release candidate.
160 o Directory authority changes:
161 - Change IP address for maatuska (v3 directory authority).
164 - Provide controllers with a safer way to implement the cookie
165 authentication mechanism. With the old method, if another locally
166 running program could convince a controller that it was the Tor
167 process, then that program could trick the contoller into telling
168 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
169 authentication method uses a challenge-response approach to prevent
170 this attack. Fixes bug 5185, implements proposal 193.
171 - Never use a bridge or a controller-supplied node as an exit, even
172 if its exit policy allows it. Found by wanoskarnet. Fixes bug
173 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
174 and 0.2.0.3-alpha (for bridge-purpose descriptors).
175 - Only build circuits if we have a sufficient threshold of the total
176 descriptors that are marked in the consensus with the "Exit"
177 flag. This mitigates an attack proposed by wanoskarnet, in which
178 all of a client's bridges collude to restrict the exit nodes that
179 the client knows about. Fixes bug 5343.
181 o Major bugfixes (on Tor 0.2.3.x):
182 - Avoid an assert when managed proxies like obfsproxy are configured,
183 and we receive HUP signals or setconf attempts too rapidly. This
184 situation happens most commonly when Vidalia tries to attach to
185 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
186 bugfix on 0.2.3.6-alpha.
187 - Fix a relay-side pluggable transports bug where managed proxies were
188 unreachable from the Internet, because Tor asked them to bind on
189 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
190 - Stop discarding command-line arguments when TestingTorNetwork
191 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
192 0.2.3.9-alpha, where task 4552 added support for two layers of
194 - Resume allowing the unit tests to run in gdb. This was accidentally
195 made impossible when the DisableDebuggerAttachment option was
196 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
197 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
198 0.2.3.11-alpha. Reported by Anthony G. Basile.
200 o Minor bugfixes (on 0.2.2.x and earlier):
201 - Ensure we don't cannibalize circuits that are longer than three hops
202 already, so we don't end up making circuits with 5 or more
203 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
204 0.1.0.1-rc which introduced cannibalization.
205 - Detect and reject certain misformed escape sequences in
206 configuration values. Previously, these values would cause us
207 to crash if received in a torrc file or over an authenticated
208 control port. Bug found by Esteban Manchado Velázquez, and
209 independently by Robert Connolly from Matta Consulting who further
210 noted that it allows a post-authentication heap overflow. Patch
211 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
212 bugfix on 0.2.0.16-alpha.
213 - Fix a compile warning when using the --enable-openbsd-malloc
214 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
215 - Directory caches no longer refuse to clean out descriptors because
216 of missing v2 networkstatus documents, unless they're configured
217 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
218 0.2.2.26-beta. Patch by Daniel Bryg.
219 - Update to the latest version of the tinytest unit testing framework.
220 This includes a couple of bugfixes that can be relevant for
221 running forked unit tests on Windows, and removes all reserved
224 o Minor bugfixes (on 0.2.3.x):
225 - On a failed pipe() call, don't leak file descriptors. Fixes bug
226 4296; bugfix on 0.2.3.1-alpha.
227 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
228 until after we have received a CERTS cell. Fixes bug 4361; bugfix
229 on 0.2.3.6-alpha. Patch by "frosty".
230 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
231 option, so that the IP stack doesn't decide to use it for IPv4
232 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
233 - Ensure that variables set in Tor's environment cannot override
234 environment variables that Tor passes to a managed
235 pluggable-transport proxy. Previously, Tor would pass every
236 variable in its environment to managed proxies along with the new
237 ones, in such a way that on many operating systems, the inherited
238 environment variables would override those which Tor tried to
239 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
240 bugfix on 0.2.3.9-alpha for Windows.
243 - A wide variety of new unit tests by Esteban Manchado Velázquez.
244 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
245 - Update to the March 6 2012 Maxmind GeoLite Country database.
248 Changes in version 0.2.3.12-alpha - 2012-02-13
249 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
250 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
251 when Tor is configured to use a pluggable transport like obfsproxy.
254 - Fix builds when the path to sed, openssl, or sha1sum contains
255 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
257 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
258 connections. This change should allow busy exit relays to stop
259 running out of available sockets as quickly. Fixes bug 4950;
260 bugfix on 0.2.2.26-beta.
261 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
262 would ask the bridge for microdescriptors, which are only supported
263 in 0.2.3.x, and then fail to bootstrap when it didn't get the
264 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
265 - Properly set up obfsproxy's environment when in managed mode. The
266 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
267 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
268 5076 and 5082; bugfix on 0.2.3.6-alpha.
271 - Use the dead_strip option when building Tor on OS X. This reduces
272 binary size by almost 19% when linking openssl and libevent
273 statically, which we do for Tor Browser Bundle.
274 - Fix broken URLs in the sample torrc file, and tell readers about
275 the OutboundBindAddress, ExitPolicyRejectPrivate, and
276 PublishServerDescriptor options. Addresses bug 4652.
277 - Update to the February 7 2012 Maxmind GeoLite Country database.
280 - Downgrade the "We're missing a certificate" message from notice
281 to info: people kept mistaking it for a real problem, whereas it
282 is seldom the problem even when we are failing to bootstrap. Fixes
283 bug 5067; bugfix on 0.2.0.10-alpha.
284 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
285 managed pluggable transport server proxy's environment.
286 Previously, we would put it there, even though Tor doesn't
287 implement an 'extended server port' yet, and even though Tor
288 almost certainly isn't listening at that address. For now, we set
289 it to an empty string to avoid crashing older obfsproxies. Bugfix
291 - Log the heartbeat message every HeartbeatPeriod seconds, not every
292 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
293 0.2.3.1-alpha. Bug reported by Scott Bennett.
294 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
295 bugfix on 0.2.3.11-alpha.
296 - Update "ClientOnly" man page entry to explain that there isn't
297 really any point to messing with it. Resolves ticket 5005.
298 - Use the correct CVE number for CVE-2011-4576 in our comments and
299 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
302 o Code simplifications and refactoring:
303 - Use the _WIN32 macro throughout our code to detect Windows.
304 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
308 Changes in version 0.2.3.11-alpha - 2012-01-22
309 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
310 the last step of the plan to limit maximum circuit length, includes
311 a wide variety of hidden service performance and correctness fixes,
312 works around an OpenSSL security flaw if your distro is too stubborn
313 to upgrade, and fixes a bunch of smaller issues.
316 - Now that Tor 0.2.0.x is completely deprecated, enable the final
317 part of "Proposal 110: Avoiding infinite length circuits" by
318 refusing all circuit-extend requests that do not use a relay_early
319 cell. This change helps Tor resist a class of denial-of-service
320 attacks by limiting the maximum circuit length.
321 - Adjust the number of introduction points that a hidden service
322 will try to maintain based on how long its introduction points
323 remain in use and how many introductions they handle. Fixes
325 - Try to use system facilities for enumerating local interface
326 addresses, before falling back to our old approach (which was
327 binding a UDP socket, and calling getsockname() on it). That
328 approach was scaring OS X users whose draconian firewall
329 software warned about binding to UDP sockets, regardless of
330 whether packets were sent. Now we try to use getifaddrs(),
331 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
332 system supports. Resolves ticket 1827.
334 o Major security workaround:
335 - When building or running with any version of OpenSSL earlier
336 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
337 versions have a bug (CVE-2011-4576) in which their block cipher
338 padding includes uninitialized data, potentially leaking sensitive
339 information to any peer with whom they make a SSLv3 connection. Tor
340 does not use SSL v3 by default, but a hostile client or server
341 could force an SSLv3 connection in order to gain information that
342 they shouldn't have been able to get. The best solution here is to
343 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
344 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
345 to make sure that the bug can't happen.
348 - Fix the SOCKET_OK test that we use to tell when socket
349 creation fails so that it works on Win64. Fixes part of bug 4533;
350 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
351 - Correct our replacements for the timeradd() and timersub() functions
352 on platforms that lack them (for example, Windows). The timersub()
353 function is used when expiring circuits, while timeradd() is
354 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
355 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
356 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
357 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
358 bug at runtime, not compile time, because some distributions hack
359 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
360 on 0.2.3.9-alpha. Found by Pascal.
362 o Minor features (controller):
363 - Use absolute path names when reporting the torrc filename in the
364 control protocol, so a controller can more easily find the torrc
365 file. Resolves bug 1101.
366 - Extend the control protocol to report flags that control a circuit's
367 path selection in CIRC events and in replies to 'GETINFO
368 circuit-status'. Implements part of ticket 2411.
369 - Extend the control protocol to report the hidden service address
370 and current state of a hidden-service-related circuit in CIRC
371 events and in replies to 'GETINFO circuit-status'. Implements part
373 - When reporting the path to the cookie file to the controller,
374 give an absolute path. Resolves ticket 4881.
375 - Allow controllers to request an event notification whenever a
376 circuit is cannibalized or its purpose is changed. Implements
378 - Include the creation time of a circuit in CIRC and CIRC2
379 control-port events and the list produced by the 'GETINFO
380 circuit-status' control-port command.
382 o Minor features (directory authorities):
383 - Directory authorities now reject versions of Tor older than
384 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
385 inclusive. These versions accounted for only a small fraction of
386 the Tor network, and have numerous known security issues. Resolves
388 - Authority operators can now vote for all relays in a given
389 set of countries to be BadDir/BadExit/Invalid/Rejected.
390 - Provide two consensus parameters (FastFlagMinThreshold and
391 FastFlagMaxThreshold) to control the range of allowable bandwidths
392 for the Fast directory flag. These allow authorities to run
393 experiments on appropriate requirements for being a "Fast" node.
394 The AuthDirFastGuarantee config value still applies.
395 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
396 directory authority option (introduced in Tor 0.2.2.34).
398 o Minor features (other):
399 - Don't disable the DirPort when we cannot exceed our AccountingMax
400 limit during this interval because the effective bandwidthrate is
401 low enough. This is useful in a situation where AccountMax is only
402 used as an additional safeguard or to provide statistics.
403 - Prepend an informative header to generated dynamic_dh_params files.
404 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
405 EntryNodes will have no effect. Resolves issue 2571.
406 - Log more useful messages when we fail to disable debugger
408 - Log which authority we're missing votes from when we go to fetch
409 them from the other auths.
410 - Log (at debug level) whenever a circuit's purpose is changed.
411 - Add missing documentation for the MaxClientCircuitsPending,
412 UseMicrodescriptors, UserspaceIOCPBuffers, and
413 _UseFilteringSSLBufferevents options, all introduced during
415 - Update to the January 3 2012 Maxmind GeoLite Country database.
417 o Minor bugfixes (hidden services):
418 - Don't close hidden service client circuits which have almost
419 finished connecting to their destination when they reach
420 the normal circuit-build timeout. Previously, we would close
421 introduction circuits which are waiting for an acknowledgement
422 from the introduction point, and rendezvous circuits which have
423 been specified in an INTRODUCE1 cell sent to a hidden service,
424 after the normal CBT. Now, we mark them as 'timed out', and launch
425 another rendezvous attempt in parallel. This behavior change can
426 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
427 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
428 - Don't close hidden-service-side rendezvous circuits when they
429 reach the normal circuit-build timeout. This behaviour change can
430 be disabled using the new
431 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
432 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
433 - Make sure we never mark the wrong rendezvous circuit as having
434 had its introduction cell acknowleged by the introduction-point
435 relay. Previously, when we received an INTRODUCE_ACK cell on a
436 client-side hidden-service introduction circuit, we might have
437 marked a rendezvous circuit other than the one we specified in
438 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
439 a warning message and interfered with the hidden service
440 connection-establishment process. Fixes bug 4759; bugfix on
441 0.2.3.3-alpha, when we added the stream-isolation feature which
442 might cause Tor to open multiple rendezvous circuits for the same
444 - Don't trigger an assertion failure when we mark a new client-side
445 hidden-service introduction circuit for close during the process
446 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
449 o Minor bugfixes (log messages):
450 - Correctly spell "connect" in a log message on failure to create a
451 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
453 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
454 Fixes bug 4856; bugfix on Tor 0.0.6.
455 - Fix the log message describing how we work around discovering
456 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
457 4837; bugfix on 0.2.2.9-alpha.
458 - When logging about a disallowed .exit name, do not also call it
459 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
461 o Minor bugfixes (build fixes):
462 - During configure, detect when we're building with clang version
463 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
464 CFLAGS. clang doesn't support them yet.
465 - During configure, search for library containing cos function as
466 libm lives in libcore on some platforms (BeOS/Haiku). Linking
467 against libm was hard-coded before. Fixes the first part of bug
468 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
470 - Detect attempts to build Tor on (as yet hypothetical) versions
471 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
472 fix for bug 4533. Bugfix on 0.2.2.28-beta.
473 - Preprocessor directives should not be put inside the arguments
474 of a macro. This would break compilation with GCC releases prior
475 to version 3.3. We would never recommend such an old GCC version,
476 but it is apparently required for binary compatibility on some
477 platforms (namely, certain builds of Haiku). Fixes the other part
478 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
481 o Minor bugfixes (other):
482 - Older Linux kernels erroneously respond to strange nmap behavior
483 by having accept() return successfully with a zero-length
484 socket. When this happens, just close the connection. Previously,
485 we would try harder to learn the remote address: but there was
486 no such remote address to learn, and our method for trying to
487 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
488 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
489 - Fix null-pointer access that could occur if TLS allocation failed.
490 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
491 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
492 accidentally been reverted.
493 - Fix our implementation of crypto_random_hostname() so it can't
494 overflow on ridiculously large inputs. (No Tor version has ever
495 provided this kind of bad inputs, but let's be correct in depth.)
496 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
497 - Find more places in the code that should have been testing for
498 invalid sockets using the SOCKET_OK macro. Required for a fix
499 for bug 4533. Bugfix on 0.2.2.28-beta.
500 - Fix an assertion failure when, while running with bufferevents, a
501 connection finishes connecting after it is marked for close, but
502 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
503 - test_util_spawn_background_ok() hardcoded the expected value
504 for ENOENT to 2. This isn't portable as error numbers are
505 platform specific, and particularly the hurd has ENOENT at
506 0x40000002. Construct expected string at runtime, using the correct
507 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
508 - Reject attempts to disable DisableDebuggerAttachment while Tor is
509 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
510 - Use an appropriate-width type for sockets in tor-fw-helper on
511 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
514 - When sending or relaying a RELAY_EARLY cell, we used to convert
515 it to a RELAY cell if the connection was using the v1 link
516 protocol. This was a workaround for older versions of Tor, which
517 didn't handle RELAY_EARLY cells properly. Now that all supported
518 versions can handle RELAY_EARLY cells, and now that we're enforcing
519 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
520 remove this workaround. Addresses bug 4786.
522 o Code simplifications and refactoring:
523 - Use OpenSSL's built-in SSL_state_string_long() instead of our
524 own homebrewed ssl_state_to_string() replacement. Patch from
525 Emile Snyder. Fixes bug 4653.
526 - Use macros to indicate OpenSSL versions, so we don't need to worry
527 about accidental hexadecimal bit shifts.
528 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
530 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
531 - Use the smartlist_add_asprintf() alias more consistently.
532 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
533 invalid value, rather than just -1.
534 - Rename a handful of old identifiers, mostly related to crypto
535 structures and crypto functions. By convention, our "create an
536 object" functions are called "type_new()", our "free an object"
537 functions are called "type_free()", and our types indicate that
538 they are types only with a final "_t". But a handful of older
539 types and functions broke these rules, with function names like
540 "type_create" or "subsystem_op_type", or with type names like
544 Changes in version 0.2.3.10-alpha - 2011-12-16
545 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
546 Tor's buffers code. Absolutely everybody should upgrade.
548 The bug relied on an incorrect calculation when making data continuous
549 in one of our IO buffers, if the first chunk of the buffer was
550 misaligned by just the wrong amount. The miscalculation would allow an
551 attacker to overflow a piece of heap-allocated memory. To mount this
552 attack, the attacker would need to either open a SOCKS connection to
553 Tor's SocksPort (usually restricted to localhost), or target a Tor
554 instance configured to make its connections through a SOCKS proxy
555 (which Tor does not do by default).
557 Good security practice requires that all heap-overflow bugs should be
558 presumed to be exploitable until proven otherwise, so we are treating
559 this as a potential code execution attack. Please upgrade immediately!
560 This bug does not affect bufferevents-based builds of Tor. Special
561 thanks to "Vektor" for reporting this issue to us!
563 This release also contains a few minor bugfixes for issues discovered
567 - Fix a heap overflow bug that could occur when trying to pull
568 data into the first chunk of a buffer, when that chunk had
569 already had some data drained from it. Fixes CVE-2011-2778;
570 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
573 - If we can't attach streams to a rendezvous circuit when we
574 finish connecting to a hidden service, clear the rendezvous
575 circuit's stream-isolation state and try to attach streams
576 again. Previously, we cleared rendezvous circuits' isolation
577 state either too early (if they were freshly built) or not at all
578 (if they had been built earlier and were cannibalized). Bugfix on
579 0.2.3.3-alpha; fixes bug 4655.
580 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
581 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
582 - Fix an assertion failure when a relay with accounting enabled
583 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
586 - Update to the December 6 2011 Maxmind GeoLite Country database.
589 Changes in version 0.2.2.35 - 2011-12-16
590 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
591 buffers code. Absolutely everybody should upgrade.
593 The bug relied on an incorrect calculation when making data continuous
594 in one of our IO buffers, if the first chunk of the buffer was
595 misaligned by just the wrong amount. The miscalculation would allow an
596 attacker to overflow a piece of heap-allocated memory. To mount this
597 attack, the attacker would need to either open a SOCKS connection to
598 Tor's SocksPort (usually restricted to localhost), or target a Tor
599 instance configured to make its connections through a SOCKS proxy
600 (which Tor does not do by default).
602 Good security practice requires that all heap-overflow bugs should be
603 presumed to be exploitable until proven otherwise, so we are treating
604 this as a potential code execution attack. Please upgrade immediately!
605 This bug does not affect bufferevents-based builds of Tor. Special
606 thanks to "Vektor" for reporting this issue to us!
608 Tor 0.2.2.35 also fixes several bugs in previous versions, including
609 crash bugs for unusual configurations, and a long-term bug that
610 would prevent Tor from starting on Windows machines with draconian
613 With this release, we remind everyone that 0.2.0.x has reached its
614 formal end-of-life. Those Tor versions have many known flaws, and
615 nobody should be using them. You should upgrade -- ideally to the
616 0.2.2.x series. If you're using a Linux or BSD and its packages are
617 obsolete, stop using those packages and upgrade anyway.
619 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
620 longer receive support after some time in early 2012.
623 - Fix a heap overflow bug that could occur when trying to pull
624 data into the first chunk of a buffer, when that chunk had
625 already had some data drained from it. Fixes CVE-2011-2778;
626 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
627 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
628 that it doesn't attempt to allocate a socketpair. This could cause
629 some problems on Windows systems with overzealous firewalls. Fix for
630 bug 4457; workaround for Libevent versions 2.0.1-alpha through
632 - If we mark an OR connection for close based on a cell we process,
633 don't process any further cells on it. We already avoid further
634 reads on marked-for-close connections, but now we also discard the
635 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
636 which was the first version where we might mark a connection for
637 close based on processing a cell on it.
638 - Correctly sanity-check that we don't underflow on a memory
639 allocation (and then assert) for hidden service introduction
640 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
641 bugfix on 0.2.1.5-alpha.
642 - Fix a memory leak when we check whether a hidden service
643 descriptor has any usable introduction points left. Fixes bug
644 4424. Bugfix on 0.2.2.25-alpha.
645 - Don't crash when we're running as a relay and don't have a GeoIP
646 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
647 we've had in the 0.2.3.x branch already.
648 - When running as a client, do not print a misleading (and plain
649 wrong) log message that we're collecting "directory request"
650 statistics: clients don't collect statistics. Also don't create a
651 useless (because empty) stats file in the stats/ directory. Fixes
652 bug 4353; bugfix on 0.2.2.34.
655 - Detect failure to initialize Libevent. This fix provides better
656 detection for future instances of bug 4457.
657 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
658 function. This was eating up hideously large amounts of time on some
659 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
660 - Resolve an integer overflow bug in smartlist_ensure_capacity().
661 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
663 - Don't warn about unused log_mutex in log.c when building with
664 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
665 0.1.0.6-rc which introduced --disable-threads.
666 - When configuring, starting, or stopping an NT service, stop
667 immediately after the service configuration attempt has succeeded
668 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
669 - When sending a NETINFO cell, include the original address
670 received for the other side, not its canonical address. Found
671 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
672 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
673 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
674 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
675 occurred when a client tried to fetch a descriptor for a bridge
676 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
677 - Backport fixes for a pair of compilation warnings on Windows.
678 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
679 - If we had ever tried to call tor_addr_to_str on an address of
680 unknown type, we would have done a strdup on an uninitialized
681 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
682 Reported by "troll_un".
683 - Correctly detect and handle transient lookup failures from
684 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
685 Reported by "troll_un".
686 - Fix null-pointer access that could occur if TLS allocation failed.
687 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
688 - Use tor_socket_t type for listener argument to accept(). Fixes bug
689 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
692 - Add two new config options for directory authorities:
693 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
694 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
695 that is always sufficient to satisfy the bandwidth requirement for
696 the Guard flag. Now it will be easier for researchers to simulate
697 Tor networks with different values. Resolves ticket 4484.
698 - When Tor ignores a hidden service specified in its configuration,
699 include the hidden service's directory in the warning message.
700 Previously, we would only tell the user that some hidden service
701 was ignored. Bugfix on 0.0.6; fixes bug 4426.
702 - Update to the December 6 2011 Maxmind GeoLite Country database.
705 - Make it easier to automate expert package builds on Windows,
706 by removing an absolute path from makensis.exe command.
709 Changes in version 0.2.3.9-alpha - 2011-12-08
710 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
711 a "DisableNetwork" security feature that bundles can use to avoid
712 touching the network until bridges are configured, moves forward on
713 the pluggable transport design, fixes a flaw in the hidden service
714 design that unnecessarily prevented clients with wrong clocks from
715 reaching hidden services, and fixes a wide variety of other issues.
718 - Clients can now connect to private bridges over IPv6. Bridges
719 still need at least one IPv4 address in order to connect to
720 other relays. Note that we don't yet handle the case where the
721 user has two bridge lines for the same bridge (one IPv4, one
722 IPv6). Implements parts of proposal 186.
723 - New "DisableNetwork" config option to prevent Tor from launching any
724 connections or accepting any connections except on a control port.
725 Bundles and controllers can set this option before letting Tor talk
726 to the rest of the network, for example to prevent any connections
727 to a non-bridge address. Packages like Orbot can also use this
728 option to instruct Tor to save power when the network is off.
729 - Clients and bridges can now be configured to use a separate
730 "transport" proxy. This approach makes the censorship arms race
731 easier by allowing bridges to use protocol obfuscation plugins. It
732 implements the "managed proxy" part of proposal 180 (ticket 3472).
733 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
734 implementation. It makes AES_CTR about 7% faster than our old one
735 (which was about 10% faster than the one OpenSSL used to provide).
736 Resolves ticket 4526.
737 - Add a "tor2web mode" for clients that want to connect to hidden
738 services non-anonymously (and possibly more quickly). As a safety
739 measure to try to keep users from turning this on without knowing
740 what they are doing, tor2web mode must be explicitly enabled at
741 compile time, and a copy of Tor compiled to run in tor2web mode
742 cannot be used as a normal Tor client. Implements feature 2553.
743 - Add experimental support for running on Windows with IOCP and no
744 kernel-space socket buffers. This feature is controlled by a new
745 "UserspaceIOCPBuffers" config option (off by default), which has
746 no effect unless Tor has been built with support for bufferevents,
747 is running on Windows, and has enabled IOCP. This may, in the long
748 run, help solve or mitigate bug 98.
749 - Use a more secure consensus parameter voting algorithm. Now at
750 least three directory authorities or a majority of them must
751 vote on a given parameter before it will be included in the
752 consensus. Implements proposal 178.
755 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
756 They used to check that the timestamp was within 30 minutes
757 of their system clock, so they could cap the size of their
758 replay-detection cache, but that approach unnecessarily refused
759 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
760 the v3 intro-point protocol (the first one which sent a timestamp
761 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
762 - Only use the EVP interface when AES acceleration is enabled,
763 to avoid a 5-7% performance regression. Resolves issue 4525;
764 bugfix on 0.2.3.8-alpha.
766 o Privacy/anonymity features (bridge detection):
767 - Make bridge SSL certificates a bit more stealthy by using random
768 serial numbers, in the same fashion as OpenSSL when generating
769 self-signed certificates. Implements ticket 4584.
770 - Introduce a new config option "DynamicDHGroups", enabled by
771 default, which provides each bridge with a unique prime DH modulus
772 to be used during SSL handshakes. This option attempts to help
773 against censors who might use the Apache DH modulus as a static
774 identifier for bridges. Addresses ticket 4548.
776 o Minor features (new/different config options):
777 - New configuration option "DisableDebuggerAttachment" (on by default)
778 to prevent basic debugging attachment attempts by other processes.
779 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
780 - Allow MapAddress directives to specify matches against super-domains,
781 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
782 Implements issue 933.
783 - Slightly change behavior of "list" options (that is, config
784 options that can appear more than once) when they appear both in
785 torrc and on the command line. Previously, the command-line options
786 would be appended to the ones from torrc. Now, the command-line
787 options override the torrc options entirely. This new behavior
788 allows the user to override list options (like exit policies and
789 ports to listen on) from the command line, rather than simply
790 appending to the list.
791 - You can get the old (appending) command-line behavior for "list"
792 options by prefixing the option name with a "+".
793 - You can remove all the values for a "list" option from the command
794 line without adding any new ones by prefixing the option name
796 - Add experimental support for a "defaults" torrc file to be parsed
797 before the regular torrc. Torrc options override the defaults file's
798 options in the same way that the command line overrides the torrc.
799 The SAVECONF controller command saves only those options which
800 differ between the current configuration and the defaults file. HUP
801 reloads both files. (Note: This is an experimental feature; its
802 behavior will probably be refined in future 0.2.3.x-alpha versions
803 to better meet packagers' needs.) Implements task 4552.
806 - Try to make the introductory warning message that Tor prints on
807 startup more useful for actually finding help and information.
808 Resolves ticket 2474.
809 - Running "make version" now displays the version of Tor that
810 we're about to build. Idea from katmagic; resolves issue 4400.
811 - Expire old or over-used hidden service introduction points.
812 Required by fix for bug 3460.
813 - Move the replay-detection cache for the RSA-encrypted parts of
814 INTRODUCE2 cells to the introduction point data structures.
815 Previously, we would use one replay-detection cache per hidden
816 service. Required by fix for bug 3460.
817 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
818 public key replay-detection cache from 60 minutes to 5 minutes. This
819 replay-detection cache is now used only to detect multiple
820 INTRODUCE2 cells specifying the same rendezvous point, so we can
821 avoid launching multiple simultaneous attempts to connect to it.
823 o Minor bugfixes (on Tor 0.2.2.x and earlier):
824 - Resolve an integer overflow bug in smartlist_ensure_capacity().
825 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
827 - Fix a minor formatting issue in one of tor-gencert's error messages.
829 - Prevent a false positive from the check-spaces script, by disabling
830 the "whitespace between function name and (" check for functions
832 - Fix a log message suggesting that people contact a non-existent
833 email address. Fixes bug 3448.
834 - Fix null-pointer access that could occur if TLS allocation failed.
835 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
836 - Report a real bootstrap problem to the controller on router
837 identity mismatch. Previously we just said "foo", which probably
838 made a lot of sense at the time. Fixes bug 4169; bugfix on
840 - If we had ever tried to call tor_addr_to_str() on an address of
841 unknown type, we would have done a strdup() on an uninitialized
842 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
843 Reported by "troll_un".
844 - Correctly detect and handle transient lookup failures from
845 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
846 Reported by "troll_un".
847 - Use tor_socket_t type for listener argument to accept(). Fixes bug
848 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
849 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
850 bug 4532; found by "troll_un".
852 o Minor bugfixes (on Tor 0.2.3.x):
853 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
855 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
856 circuit for use as a hidden service client's rendezvous point.
857 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
858 with help from wanoskarnet.
859 - Restore behavior of overriding SocksPort, ORPort, and similar
860 options from the command line. Bugfix on 0.2.3.3-alpha.
863 - Properly handle the case where the build-tree is not the same
864 as the source tree when generating src/common/common_sha1.i,
865 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
866 bugfix on 0.2.0.1-alpha.
868 o Code simplifications, cleanups, and refactorings:
869 - Remove the pure attribute from all functions that used it
870 previously. In many cases we assigned it incorrectly, because the
871 functions might assert or call impure functions, and we don't have
872 evidence that keeping the pure attribute is worthwhile. Implements
873 changes suggested in ticket 4421.
874 - Remove some dead code spotted by coverity. Fixes cid 432.
875 Bugfix on 0.2.3.1-alpha, closes bug 4637.
878 Changes in version 0.2.3.8-alpha - 2011-11-22
879 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
880 socketpair-related bug that has been bothering Windows users. It adds
881 support to serve microdescriptors to controllers, so Vidalia's network
882 map can resume listing relays (once Vidalia implements its side),
883 and adds better support for hardware AES acceleration. Finally, it
884 starts the process of adjusting the bandwidth cutoff for getting the
885 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
886 that tiny relays harm performance more than they help network capacity.
889 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
890 that it doesn't attempt to allocate a socketpair. This could cause
891 some problems on Windows systems with overzealous firewalls. Fix for
892 bug 4457; workaround for Libevent versions 2.0.1-alpha through
894 - Correctly sanity-check that we don't underflow on a memory
895 allocation (and then assert) for hidden service introduction
896 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
897 bugfix on 0.2.1.5-alpha.
898 - Remove the artificially low cutoff of 20KB to guarantee the Fast
899 flag. In the past few years the average relay speed has picked
900 up, and while the "top 7/8 of the network get the Fast flag" and
901 "all relays with 20KB or more of capacity get the Fast flag" rules
902 used to have the same result, now the top 7/8 of the network has
903 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
904 - Fix a rare assertion failure when checking whether a v0 hidden
905 service descriptor has any usable introduction points left, and
906 we don't have enough information to build a circuit to the first
907 intro point named in the descriptor. The HS client code in
908 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
909 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
910 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
911 - Make bridge authorities not crash when they are asked for their own
912 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
913 - When running as a client, do not print a misleading (and plain
914 wrong) log message that we're collecting "directory request"
915 statistics: clients don't collect statistics. Also don't create a
916 useless (because empty) stats file in the stats/ directory. Fixes
917 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
920 - Allow Tor controllers like Vidalia to obtain the microdescriptor
921 for a relay by identity digest or nickname. Previously,
922 microdescriptors were only available by their own digests, so a
923 controller would have to ask for and parse the whole microdescriptor
924 consensus in order to look up a single relay's microdesc. Fixes
925 bug 3832; bugfix on 0.2.3.1-alpha.
926 - Use OpenSSL's EVP interface for AES encryption, so that all AES
927 operations can use hardware acceleration (if present). Resolves
930 o Minor bugfixes (on 0.2.2.x and earlier):
931 - Detect failure to initialize Libevent. This fix provides better
932 detection for future instances of bug 4457.
933 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
934 function. This was eating up hideously large amounts of time on some
935 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
936 - Don't warn about unused log_mutex in log.c when building with
937 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
938 0.1.0.6-rc which introduced --disable-threads.
939 - Allow manual 'authenticate' commands to the controller interface
940 from netcat (nc) as well as telnet. We were rejecting them because
941 they didn't come with the expected whitespace at the end of the
942 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
943 - Fix some (not actually triggerable) buffer size checks in usage of
944 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
946 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
947 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
948 - When configuring, starting, or stopping an NT service, stop
949 immediately after the service configuration attempt has succeeded
950 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
951 - When sending a NETINFO cell, include the original address
952 received for the other side, not its canonical address. Found
953 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
954 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
955 can pick them up when the tests aren't disabled. Bugfix on
956 0.2.2.4-alpha which introduced tinytest.
957 - Fix a memory leak when we check whether a hidden service
958 descriptor has any usable introduction points left. Fixes bug
959 4424. Bugfix on 0.2.2.25-alpha.
960 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
961 occurred when a client tried to fetch a descriptor for a bridge
962 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
964 o Minor bugfixes (on 0.2.3.x):
965 - Make util unit tests build correctly with MSVC. Bugfix on
966 0.2.3.3-alpha. Patch by Gisle Vanem.
967 - Successfully detect AUTH_CHALLENGE cells with no recognized
968 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
970 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
971 it should still send a NETINFO cell to allow the connection to
972 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
974 - Log less loudly when we get an invalid authentication certificate
975 from a source other than a directory authority: it's not unusual
976 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
978 - Tolerate servers with more clock skew in their authentication
979 certificates than previously. Fixes bug 4371; bugfix on
981 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
982 on 0.2.3.4-alpha and 0.2.3.6-alpha.
985 - Add two new config options for directory authorities:
986 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
987 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
988 that is always sufficient to satisfy the bandwidth requirement for
989 the Guard flag. Now it will be easier for researchers to simulate
990 Tor networks with different values. Resolves ticket 4484.
991 - When Tor ignores a hidden service specified in its configuration,
992 include the hidden service's directory in the warning message.
993 Previously, we would only tell the user that some hidden service
994 was ignored. Bugfix on 0.0.6; fixes bug 4426.
995 - When we fail to initialize Libevent, retry with IOCP disabled so we
996 don't need to turn on multi-threading support in Libevent, which in
997 turn requires a working socketpair(). This is a workaround for bug
998 4457, which affects Libevent versions from 2.0.1-alpha through
1000 - Detect when we try to build on a platform that doesn't define
1001 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1002 - Update to the November 1 2011 Maxmind GeoLite Country database.
1004 o Packaging changes:
1005 - Make it easier to automate expert package builds on Windows,
1006 by removing an absolute path from makensis.exe command.
1008 o Code simplifications and refactoring:
1009 - Remove some redundant #include directives throughout the code.
1010 Patch from Andrea Gelmini.
1011 - Unconditionally use OpenSSL's AES implementation instead of our
1012 old built-in one. OpenSSL's AES has been better for a while, and
1013 relatively few servers should still be on any version of OpenSSL
1014 that doesn't have good optimized assembly AES.
1015 - Use the name "CERTS" consistently to refer to the new cell type;
1016 we were calling it CERT in some places and CERTS in others.
1019 - Numerous new unit tests for functions in util.c and address.c by
1021 - The long-disabled benchmark tests are now split into their own
1022 ./src/test/bench binary.
1023 - The benchmark tests can now use more accurate timers than
1024 gettimeofday() when such timers are available.
1027 Changes in version 0.2.3.7-alpha - 2011-10-30
1028 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1029 the new v3 handshake. It also resolves yet another bridge address
1033 - If we mark an OR connection for close based on a cell we process,
1034 don't process any further cells on it. We already avoid further
1035 reads on marked-for-close connections, but now we also discard the
1036 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1037 which was the first version where we might mark a connection for
1038 close based on processing a cell on it.
1039 - Fix a double-free bug that would occur when we received an invalid
1040 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1041 bugfix on 0.2.3.6-alpha.
1042 - Bridges no longer include their address in NETINFO cells on outgoing
1043 OR connections, to allow them to blend in better with clients.
1044 Removes another avenue for enumerating bridges. Reported by
1045 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1046 cells were introduced.
1049 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1050 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1053 Changes in version 0.2.3.6-alpha - 2011-10-26
1054 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1055 anonymity vulnerability where an attacker can deanonymize Tor
1056 users. Everybody should upgrade.
1058 This release also features support for a new v3 connection handshake
1059 protocol, and fixes to make hidden service connections more robust.
1062 - Implement a new handshake protocol (v3) for authenticating Tors to
1063 each other over TLS. It should be more resistant to fingerprinting
1064 than previous protocols, and should require less TLS hacking for
1065 future Tor implementations. Implements proposal 176.
1066 - Allow variable-length padding cells to disguise the length of
1067 Tor's TLS records. Implements part of proposal 184.
1069 o Privacy/anonymity fixes (clients):
1070 - Clients and bridges no longer send TLS certificate chains on
1071 outgoing OR connections. Previously, each client or bridge would
1072 use the same cert chain for all outgoing OR connections until
1073 its IP address changes, which allowed any relay that the client
1074 or bridge contacted to determine which entry guards it is using.
1075 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1076 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1077 no longer considers that connection as suitable for satisfying a
1078 circuit EXTEND request. Now relays can protect clients from the
1079 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1080 - Directory authorities no longer assign the Guard flag to relays
1081 that haven't upgraded to the above "refuse EXTEND requests
1082 to client connections" fix. Now directory authorities can
1083 protect clients from the CVE-2011-2768 issue even if neither
1084 the clients nor the relays have upgraded yet. There's a new
1085 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1086 to let us transition smoothly, else tomorrow there would be no
1089 o Major bugfixes (hidden services):
1090 - Improve hidden service robustness: when an attempt to connect to
1091 a hidden service ends, be willing to refetch its hidden service
1092 descriptors from each of the HSDir relays responsible for them
1093 immediately. Previously, we would not consider refetching the
1094 service's descriptors from each HSDir for 15 minutes after the last
1095 fetch, which was inconvenient if the hidden service was not running
1096 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1097 - When one of a hidden service's introduction points appears to be
1098 unreachable, stop trying it. Previously, we would keep trying
1099 to build circuits to the introduction point until we lost the
1100 descriptor, usually because the user gave up and restarted Tor.
1101 Partly fixes bug 3825.
1102 - Don't launch a useless circuit after failing to use one of a
1103 hidden service's introduction points. Previously, we would
1104 launch a new introduction circuit, but not set the hidden service
1105 which that circuit was intended to connect to, so it would never
1106 actually be used. A different piece of code would then create a
1107 new introduction circuit correctly. Bug reported by katmagic and
1108 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1110 o Major bugfixes (other):
1111 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1112 that they initiated. Relays could distinguish incoming bridge
1113 connections from client connections, creating another avenue for
1114 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1115 Found by "frosty_un".
1116 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1117 tor gets started. This prevents a wrong average bandwidth
1118 estimate, which would cause relays to always start a new accounting
1119 interval at the earliest possible moment. Fixes bug 2003; bugfix
1120 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1121 immensely in tracking this bug down.
1122 - Fix a crash bug when changing node restrictions while a DNS lookup
1123 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1126 o Minor bugfixes (on 0.2.2.x and earlier):
1127 - When a hidden service turns an extra service-side introduction
1128 circuit into a general-purpose circuit, free the rend_data and
1129 intro_key fields first, so we won't leak memory if the circuit
1130 is cannibalized for use as another service-side introduction
1131 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1132 - Rephrase the log message emitted if the TestSocks check is
1133 successful. Patch from Fabian Keil; fixes bug 4094.
1134 - Bridges now skip DNS self-tests, to act a little more stealthily.
1135 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1136 bridges. Patch by "warms0x".
1137 - Remove a confusing dollar sign from the example fingerprint in the
1138 man page, and also make the example fingerprint a valid one. Fixes
1139 bug 4309; bugfix on 0.2.1.3-alpha.
1140 - Fix internal bug-checking logic that was supposed to catch
1141 failures in digest generation so that it will fail more robustly
1142 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1143 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1144 - Report any failure in init_keys() calls launched because our
1145 IP address has changed. Spotted by Coverity Scan. Bugfix on
1146 0.1.1.4-alpha; fixes CID 484.
1148 o Minor bugfixes (on 0.2.3.x):
1149 - Fix a bug in configure.in that kept it from building a configure
1150 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1151 bugfix on 0.2.3.1-alpha.
1152 - Don't warn users that they are exposing a client port to the
1153 Internet if they have specified an RFC1918 address. Previously,
1154 we would warn if the user had specified any non-loopback
1155 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1156 - Fix memory leaks in the failing cases of the new SocksPort and
1157 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1158 fixes coverity CIDs 485, 486, and 487.
1161 - When a hidden service's introduction point times out, consider
1162 trying it again during the next attempt to connect to the
1163 HS. Previously, we would not try it again unless a newly fetched
1164 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1165 - The next version of Windows will be called Windows 8, and it has
1166 a major version of 6, minor version of 2. Correctly identify that
1167 version instead of calling it "Very recent version". Resolves
1168 ticket 4153; reported by funkstar.
1169 - The Bridge Authority now writes statistics on how many bridge
1170 descriptors it gave out in total, and how many unique descriptors
1171 it gave out. It also lists how often the most and least commonly
1172 fetched descriptors were given out, as well as the median and
1173 25th/75th percentile. Implements tickets 4200 and 4294.
1174 - Update to the October 4 2011 Maxmind GeoLite Country database.
1176 o Code simplifications and refactoring:
1177 - Remove some old code to remember statistics about which descriptors
1178 we've served as a directory mirror. The feature wasn't used and
1179 is outdated now that microdescriptors are around.
1180 - Rename Tor functions that turn strings into addresses, so that
1181 "parse" indicates that no hostname resolution occurs, and
1182 "lookup" indicates that hostname resolution may occur. This
1183 should help prevent mistakes in the future. Fixes bug 3512.
1186 Changes in version 0.2.2.34 - 2011-10-26
1187 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1188 can deanonymize Tor users. Everybody should upgrade.
1190 The attack relies on four components: 1) Clients reuse their TLS cert
1191 when talking to different relays, so relays can recognize a user by
1192 the identity key in her cert. 2) An attacker who knows the client's
1193 identity key can probe each guard relay to see if that identity key
1194 is connected to that guard relay right now. 3) A variety of active
1195 attacks in the literature (starting from "Low-Cost Traffic Analysis
1196 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1197 discover the guard relays that a Tor user visiting the website is using.
1198 4) Clients typically pick three guards at random, so the set of guards
1199 for a given user could well be a unique fingerprint for her. This
1200 release fixes components #1 and #2, which is enough to block the attack;
1201 the other two remain as open research problems. Special thanks to
1202 "frosty_un" for reporting the issue to us!
1204 Clients should upgrade so they are no longer recognizable by the TLS
1205 certs they present. Relays should upgrade so they no longer allow a
1206 remote attacker to probe them to test whether unpatched clients are
1207 currently connected to them.
1209 This release also fixes several vulnerabilities that allow an attacker
1210 to enumerate bridge relays. Some bridge enumeration attacks still
1211 remain; see for example proposal 188.
1213 o Privacy/anonymity fixes (clients):
1214 - Clients and bridges no longer send TLS certificate chains on
1215 outgoing OR connections. Previously, each client or bridge would
1216 use the same cert chain for all outgoing OR connections until
1217 its IP address changes, which allowed any relay that the client
1218 or bridge contacted to determine which entry guards it is using.
1219 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1220 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1221 no longer considers that connection as suitable for satisfying a
1222 circuit EXTEND request. Now relays can protect clients from the
1223 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1224 - Directory authorities no longer assign the Guard flag to relays
1225 that haven't upgraded to the above "refuse EXTEND requests
1226 to client connections" fix. Now directory authorities can
1227 protect clients from the CVE-2011-2768 issue even if neither
1228 the clients nor the relays have upgraded yet. There's a new
1229 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1230 to let us transition smoothly, else tomorrow there would be no
1233 o Privacy/anonymity fixes (bridge enumeration):
1234 - Bridge relays now do their directory fetches inside Tor TLS
1235 connections, like all the other clients do, rather than connecting
1236 directly to the DirPort like public relays do. Removes another
1237 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1238 - Bridges relays now build circuits for themselves in a more similar
1239 way to how clients build them. Removes another avenue for
1240 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1241 when bridges were introduced.
1242 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1243 that they initiated. Relays could distinguish incoming bridge
1244 connections from client connections, creating another avenue for
1245 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1246 Found by "frosty_un".
1249 - Fix a crash bug when changing node restrictions while a DNS lookup
1250 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1252 - Don't launch a useless circuit after failing to use one of a
1253 hidden service's introduction points. Previously, we would
1254 launch a new introduction circuit, but not set the hidden service
1255 which that circuit was intended to connect to, so it would never
1256 actually be used. A different piece of code would then create a
1257 new introduction circuit correctly. Bug reported by katmagic and
1258 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1261 - Change an integer overflow check in the OpenBSD_Malloc code so
1262 that GCC is less likely to eliminate it as impossible. Patch
1263 from Mansour Moufid. Fixes bug 4059.
1264 - When a hidden service turns an extra service-side introduction
1265 circuit into a general-purpose circuit, free the rend_data and
1266 intro_key fields first, so we won't leak memory if the circuit
1267 is cannibalized for use as another service-side introduction
1268 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1269 - Bridges now skip DNS self-tests, to act a little more stealthily.
1270 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1271 bridges. Patch by "warms0x".
1272 - Fix internal bug-checking logic that was supposed to catch
1273 failures in digest generation so that it will fail more robustly
1274 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1275 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1276 - Report any failure in init_keys() calls launched because our
1277 IP address has changed. Spotted by Coverity Scan. Bugfix on
1278 0.1.1.4-alpha; fixes CID 484.
1280 o Minor bugfixes (log messages and documentation):
1281 - Remove a confusing dollar sign from the example fingerprint in the
1282 man page, and also make the example fingerprint a valid one. Fixes
1283 bug 4309; bugfix on 0.2.1.3-alpha.
1284 - The next version of Windows will be called Windows 8, and it has
1285 a major version of 6, minor version of 2. Correctly identify that
1286 version instead of calling it "Very recent version". Resolves
1287 ticket 4153; reported by funkstar.
1288 - Downgrade log messages about circuit timeout calibration from
1289 "notice" to "info": they don't require or suggest any human
1290 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1291 bugfix on 0.2.2.14-alpha.
1294 - Turn on directory request statistics by default and include them in
1295 extra-info descriptors. Don't break if we have no GeoIP database.
1296 Backported from 0.2.3.1-alpha; implements ticket 3951.
1297 - Update to the October 4 2011 Maxmind GeoLite Country database.
1300 Changes in version 0.2.1.31 - 2011-10-26
1301 Tor 0.2.1.31 backports important security and privacy fixes for
1302 oldstable. This release is intended only for package maintainers and
1303 others who cannot use the 0.2.2 stable series. All others should be
1304 using Tor 0.2.2.x or newer.
1306 o Security fixes (also included in 0.2.2.x):
1307 - Replace all potentially sensitive memory comparison operations
1308 with versions whose runtime does not depend on the data being
1309 compared. This will help resist a class of attacks where an
1310 adversary can use variations in timing information to learn
1311 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1312 implementation by Robert Ransom based partially on code by DJB.)
1313 - Fix an assert in parsing router descriptors containing IPv6
1314 addresses. This one took down the directory authorities when
1315 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1317 o Privacy/anonymity fixes (also included in 0.2.2.x):
1318 - Clients and bridges no longer send TLS certificate chains on
1319 outgoing OR connections. Previously, each client or bridge would
1320 use the same cert chain for all outgoing OR connections until
1321 its IP address changes, which allowed any relay that the client
1322 or bridge contacted to determine which entry guards it is using.
1323 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1324 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1325 no longer considers that connection as suitable for satisfying a
1326 circuit EXTEND request. Now relays can protect clients from the
1327 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1328 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1329 that they initiated. Relays could distinguish incoming bridge
1330 connections from client connections, creating another avenue for
1331 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1332 Found by "frosty_un".
1333 - When receiving a hidden service descriptor, check that it is for
1334 the hidden service we wanted. Previously, Tor would store any
1335 hidden service descriptors that a directory gave it, whether it
1336 wanted them or not. This wouldn't have let an attacker impersonate
1337 a hidden service, but it did let directories pre-seed a client
1338 with descriptors that it didn't want. Bugfix on 0.0.6.
1339 - Avoid linkability based on cached hidden service descriptors: forget
1340 all hidden service descriptors cached as a client when processing a
1341 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1342 - Make the bridge directory authority refuse to answer directory
1343 requests for "all" descriptors. It used to include bridge
1344 descriptors in its answer, which was a major information leak.
1345 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1346 - Don't attach new streams to old rendezvous circuits after SIGNAL
1347 NEWNYM. Previously, we would keep using an existing rendezvous
1348 circuit if it remained open (i.e. if it were kept open by a
1349 long-lived stream, or if a new stream were attached to it before
1350 Tor could notice that it was old and no longer in use). Bugfix on
1351 0.1.1.15-rc; fixes bug 3375.
1353 o Minor bugfixes (also included in 0.2.2.x):
1354 - When we restart our relay, we might get a successful connection
1355 from the outside before we've started our reachability tests,
1356 triggering a warning: "ORPort found reachable, but I have no
1357 routerinfo yet. Failing to inform controller of success." This
1358 bug was harmless unless Tor is running under a controller
1359 like Vidalia, in which case the controller would never get a
1360 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1362 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1363 enabled. Fixes bug 1526.
1364 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1365 anything since 0.2.1.16-rc.
1366 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1367 None of the cases where we did this before were wrong, but by making
1368 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1369 - Fix a rare crash bug that could occur when a client was configured
1370 with a large number of bridges. Fixes bug 2629; bugfix on
1371 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1372 - Correct the warning displayed when a rendezvous descriptor exceeds
1373 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1375 - Fix an uncommon assertion failure when running with DNSPort under
1376 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1377 - When warning about missing zlib development packages during compile,
1378 give the correct package names. Bugfix on 0.2.0.1-alpha.
1379 - Require that introduction point keys and onion keys have public
1380 exponent 65537. Bugfix on 0.2.0.10-alpha.
1381 - Do not crash when our configuration file becomes unreadable, for
1382 example due to a permissions change, between when we start up
1383 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1385 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1387 - Always NUL-terminate the sun_path field of a sockaddr_un before
1388 passing it to the kernel. (Not a security issue: kernels are
1389 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1390 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1391 - Don't stack-allocate the list of supplementary GIDs when we're
1392 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1393 could take up to 256K, which is way too much stack. Found by
1394 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1396 o Minor bugfixes (only in 0.2.1.x):
1397 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
1398 rely on them. Bugfix on 0.2.1.30.
1399 - Use git revisions instead of svn revisions when generating our
1400 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1402 o Minor features (also included in 0.2.2.x):
1403 - Adjust the expiration time on our SSL session certificates to
1404 better match SSL certs seen in the wild. Resolves ticket 4014.
1405 - Allow nameservers with IPv6 address. Resolves bug 2574.
1406 - Update to the October 4 2011 Maxmind GeoLite Country database.
1409 Changes in version 0.2.3.5-alpha - 2011-09-28
1410 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
1411 bridge relays; fixes an assertion error that many users started hitting
1412 today; and adds the ability to refill token buckets more often than
1413 once per second, allowing significant performance improvements.
1416 - Bridge relays now do their directory fetches inside Tor TLS
1417 connections, like all the other clients do, rather than connecting
1418 directly to the DirPort like public relays do. Removes another
1419 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1420 - Bridges relays now build circuits for themselves in a more similar
1421 way to how clients build them. Removes another avenue for
1422 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1423 when bridges were introduced.
1426 - Fix an "Assertion md->held_by_node == 1 failed" error that could
1427 occur when the same microdescriptor was referenced by two node_t
1428 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
1430 o Major features (networking):
1431 - Add a new TokenBucketRefillInterval option to refill token buckets
1432 more frequently than once per second. This should improve network
1433 performance, alleviate queueing problems, and make traffic less
1434 bursty. Implements proposal 183; closes ticket 3630. Design by
1435 Florian Tschorsch and Björn Scheuermann; implementation by
1439 - Change an integer overflow check in the OpenBSD_Malloc code so
1440 that GCC is less likely to eliminate it as impossible. Patch
1441 from Mansour Moufid. Fixes bug 4059.
1443 o Minor bugfixes (usability):
1444 - Downgrade log messages about circuit timeout calibration from
1445 "notice" to "info": they don't require or suggest any human
1446 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1447 bugfix on 0.2.2.14-alpha.
1449 o Minor features (diagnostics):
1450 - When the system call to create a listener socket fails, log the
1451 error message explaining why. This may help diagnose bug 4027.
1454 Changes in version 0.2.3.4-alpha - 2011-09-13
1455 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
1456 tweak to Tor's TLS handshake that makes relays and bridges that run
1457 this new version reachable from Iran again. It also fixes a few new
1458 bugs in 0.2.3.x, and teaches relays to recognize when they're not
1459 listed in the network consensus and republish.
1461 o Major bugfixes (also part of 0.2.2.33):
1462 - Avoid an assertion failure when reloading a configuration with
1463 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1464 3923; bugfix on 0.2.2.25-alpha.
1466 o Minor features (security, also part of 0.2.2.33):
1467 - Check for replays of the public-key encrypted portion of an
1468 INTRODUCE1 cell, in addition to the current check for replays of
1469 the g^x value. This prevents a possible class of active attacks
1470 by an attacker who controls both an introduction point and a
1471 rendezvous point, and who uses the malleability of AES-CTR to
1472 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1473 that these attacks is infeasible (requiring the attacker to send
1474 on the order of zettabytes of altered cells in a short interval),
1475 but we'd rather block them off in case there are any classes of
1476 this attack that we missed. Reported by Willem Pinckaers.
1478 o Minor features (also part of 0.2.2.33):
1479 - Adjust the expiration time on our SSL session certificates to
1480 better match SSL certs seen in the wild. Resolves ticket 4014.
1481 - Change the default required uptime for a relay to be accepted as
1482 a HSDir (hidden service directory) from 24 hours to 25 hours.
1483 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1484 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1485 authorities to abstain from voting on assignment of the HSDir
1486 consensus flag. Related to bug 2649.
1487 - Update to the September 6 2011 Maxmind GeoLite Country database.
1489 o Minor bugfixes (also part of 0.2.2.33):
1490 - Demote the 'replay detected' log message emitted when a hidden
1491 service receives the same Diffie-Hellman public key in two different
1492 INTRODUCE2 cells to info level. A normal Tor client can cause that
1493 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1494 fixes part of bug 2442.
1495 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1496 level. There is nothing that a hidden service's operator can do
1497 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1499 - Clarify a log message specifying the characters permitted in
1500 HiddenServiceAuthorizeClient client names. Previously, the log
1501 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1502 given the impression that every ASCII character between "+" and "_"
1503 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1505 o Build fixes (also part of 0.2.2.33):
1506 - Clean up some code issues that prevented Tor from building on older
1507 BSDs. Fixes bug 3894; reported by "grarpamp".
1508 - Search for a platform-specific version of "ar" when cross-compiling.
1509 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1512 - Fix a bug where the SocksPort option (for example) would get
1513 ignored and replaced by the default if a SocksListenAddress
1514 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
1518 - Relays now try regenerating and uploading their descriptor more
1519 frequently if they are not listed in the consensus, or if the
1520 version of their descriptor listed in the consensus is too
1521 old. This fix should prevent situations where a server declines
1522 to re-publish itself because it has done so too recently, even
1523 though the authorities decided not to list its recent-enough
1524 descriptor. Fix for bug 3327.
1527 - Relays now include a reason for regenerating their descriptors
1528 in an HTTP header when uploading to the authorities. This will
1529 make it easier to debug descriptor-upload issues in the future.
1530 - When starting as root and then changing our UID via the User
1531 control option, and we have a ControlSocket configured, make sure
1532 that the ControlSocket is owned by the same account that Tor will
1533 run under. Implements ticket 3421; fix by Jérémy Bobbio.
1536 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
1537 utility function used in the control-port code). This shouldn't
1538 ever happen unless Tor is completely out of memory, but if it did
1539 happen and Tor somehow recovered from it, Tor could have sent a log
1540 message to a control port in the middle of a reply to a controller
1541 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
1542 - Make 'FetchUselessDescriptors' cause all descriptor types and
1543 all consensus types (including microdescriptors) to get fetched.
1544 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
1547 - Make a new "entry connection" struct as an internal subtype of "edge
1548 connection", to simplify the code and make exit connections smaller.
1551 Changes in version 0.2.2.33 - 2011-09-13
1552 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
1553 TLS handshake that makes relays and bridges that run this new version
1554 reachable from Iran again.
1557 - Avoid an assertion failure when reloading a configuration with
1558 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1559 3923; bugfix on 0.2.2.25-alpha.
1561 o Minor features (security):
1562 - Check for replays of the public-key encrypted portion of an
1563 INTRODUCE1 cell, in addition to the current check for replays of
1564 the g^x value. This prevents a possible class of active attacks
1565 by an attacker who controls both an introduction point and a
1566 rendezvous point, and who uses the malleability of AES-CTR to
1567 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1568 that these attacks are infeasible (requiring the attacker to send
1569 on the order of zettabytes of altered cells in a short interval),
1570 but we'd rather block them off in case there are any classes of
1571 this attack that we missed. Reported by Willem Pinckaers.
1574 - Adjust the expiration time on our SSL session certificates to
1575 better match SSL certs seen in the wild. Resolves ticket 4014.
1576 - Change the default required uptime for a relay to be accepted as
1577 a HSDir (hidden service directory) from 24 hours to 25 hours.
1578 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1579 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1580 authorities to abstain from voting on assignment of the HSDir
1581 consensus flag. Related to bug 2649.
1582 - Update to the September 6 2011 Maxmind GeoLite Country database.
1584 o Minor bugfixes (documentation and log messages):
1585 - Correct the man page to explain that HashedControlPassword and
1586 CookieAuthentication can both be set, in which case either method
1587 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1588 when we decided to allow these config options to both be set. Issue
1590 - Demote the 'replay detected' log message emitted when a hidden
1591 service receives the same Diffie-Hellman public key in two different
1592 INTRODUCE2 cells to info level. A normal Tor client can cause that
1593 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1594 fixes part of bug 2442.
1595 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1596 level. There is nothing that a hidden service's operator can do
1597 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1599 - Clarify a log message specifying the characters permitted in
1600 HiddenServiceAuthorizeClient client names. Previously, the log
1601 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1602 given the impression that every ASCII character between "+" and "_"
1603 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1606 - Provide a substitute implementation of lround() for MSVC, which
1607 apparently lacks it. Patch from Gisle Vanem.
1608 - Clean up some code issues that prevented Tor from building on older
1609 BSDs. Fixes bug 3894; reported by "grarpamp".
1610 - Search for a platform-specific version of "ar" when cross-compiling.
1611 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1614 Changes in version 0.2.3.3-alpha - 2011-09-01
1615 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
1616 security, and provides client-side support for the microdescriptor
1617 and optimistic data features introduced earlier in the 0.2.3.x
1618 series. It also includes numerous critical bugfixes in the (optional)
1619 bufferevent-based networking backend.
1621 o Major features (stream isolation):
1622 - You can now configure Tor so that streams from different
1623 applications are isolated on different circuits, to prevent an
1624 attacker who sees your streams as they leave an exit node from
1625 linking your sessions to one another. To do this, choose some way
1626 to distinguish the applications: have them connect to different
1627 SocksPorts, or have one of them use SOCKS4 while the other uses
1628 SOCKS5, or have them pass different authentication strings to the
1629 SOCKS proxy. Then, use the new SocksPort syntax to configure the
1630 degree of isolation you need. This implements Proposal 171.
1631 - There's a new syntax for specifying multiple client ports (such as
1632 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
1633 multiple *Port entries with full addr:port syntax on each.
1634 The old *ListenAddress format is still supported, but you can't
1635 mix it with the new *Port syntax.
1637 o Major features (other):
1638 - Enable microdescriptor fetching by default for clients. This allows
1639 clients to download a much smaller amount of directory information.
1640 To disable it (and go back to the old-style consensus and
1641 descriptors), set "UseMicrodescriptors 0" in your torrc file.
1642 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
1643 "PortForwarding" config option), now supports Windows.
1644 - When using an exit relay running 0.2.3.x, clients can now
1645 "optimistically" send data before the exit relay reports that
1646 the stream has opened. This saves a round trip when starting
1647 connections where the client speaks first (such as web browsing).
1648 This behavior is controlled by a consensus parameter (currently
1649 disabled). To turn it on or off manually, use the "OptimisticData"
1650 torrc option. Implements proposal 181; code by Ian Goldberg.
1652 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
1653 - When using IOCP on Windows, we need to enable Libevent windows
1655 - The IOCP backend now works even when the user has not specified
1656 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
1657 Fixes part of bug 3752.
1658 - Correctly record the bytes we've read and written when using
1659 bufferevents, so that we can include them in our bandwidth history
1660 and advertised bandwidth. Fixes bug 3803.
1661 - Apply rate-limiting only at the bottom of a chain of filtering
1662 bufferevents. This prevents us from filling up internal read
1663 buffers and violating rate-limits when filtering bufferevents
1664 are enabled. Fixes part of bug 3804.
1665 - Add high-watermarks to the output buffers for filtered
1666 bufferevents. This prevents us from filling up internal write
1667 buffers and wasting CPU cycles when filtering bufferevents are
1668 enabled. Fixes part of bug 3804.
1669 - Correctly notice when data has been written from a bufferevent
1670 without flushing it completely. Fixes bug 3805.
1671 - Fix a bug where server-side tunneled bufferevent-based directory
1672 streams would get closed prematurely. Fixes bug 3814.
1673 - Fix a use-after-free error with per-connection rate-limiting
1674 buckets. Fixes bug 3888.
1676 o Major bugfixes (also part of 0.2.2.31-rc):
1677 - If we're configured to write our ControlPorts to disk, only write
1678 them after switching UID and creating the data directory. This way,
1679 we don't fail when starting up with a nonexistent DataDirectory
1680 and a ControlPortWriteToFile setting based on that directory. Fixes
1681 bug 3747; bugfix on Tor 0.2.2.26-beta.
1684 - Added a new CONF_CHANGED event so that controllers can be notified
1685 of any configuration changes made by other controllers, or by the
1686 user. Implements ticket 1692.
1687 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
1688 leak when using bufferevents, and lets Libevent worry about how to
1689 best copy data out of a buffer.
1690 - Replace files in stats/ rather than appending to them. Now that we
1691 include statistics in extra-info descriptors, it makes no sense to
1692 keep old statistics forever. Implements ticket 2930.
1694 o Minor features (build compatibility):
1695 - Limited, experimental support for building with nmake and MSVC.
1696 - Provide a substitute implementation of lround() for MSVC, which
1697 apparently lacks it. Patch from Gisle Vanem.
1699 o Minor features (also part of 0.2.2.31-rc):
1700 - Update to the August 2 2011 Maxmind GeoLite Country database.
1702 o Minor bugfixes (on 0.2.3.x-alpha):
1703 - Fix a spurious warning when parsing SOCKS requests with
1704 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
1705 - Get rid of a harmless warning that could happen on relays running
1706 with bufferevents. The warning was caused by someone doing an http
1707 request to a relay's orport. Also don't warn for a few related
1708 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
1710 o Minor bugfixes (on 2.2.x and earlier):
1711 - Correct the man page to explain that HashedControlPassword and
1712 CookieAuthentication can both be set, in which case either method
1713 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1714 when we decided to allow these config options to both be set. Issue
1716 - The "--quiet" and "--hush" options now apply not only to Tor's
1717 behavior before logs are configured, but also to Tor's behavior in
1718 the absense of configured logs. Fixes bug 3550; bugfix on
1721 o Minor bugfixes (also part of 0.2.2.31-rc):
1722 - Write several files in text mode, on OSes that distinguish text
1723 mode from binary mode (namely, Windows). These files are:
1724 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1725 that collect those statistics; 'client_keys' and 'hostname' for
1726 hidden services that use authentication; and (in the tor-gencert
1727 utility) newly generated identity and signing keys. Previously,
1728 we wouldn't specify text mode or binary mode, leading to an
1729 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1730 the DirRecordUsageByCountry option which would have triggered
1731 the assertion failure was added), although this assertion failure
1732 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1733 - Selectively disable deprecation warnings on OS X because Lion
1734 started deprecating the shipped copy of openssl. Fixes bug 3643.
1735 - Remove an extra pair of quotation marks around the error
1736 message in control-port STATUS_GENERAL BUG events. Bugfix on
1737 0.1.2.6-alpha; fixes bug 3732.
1738 - When unable to format an address as a string, report its value
1739 as "???" rather than reusing the last formatted address. Bugfix
1742 o Code simplifications and refactoring:
1743 - Rewrite the listener-selection logic so that parsing which ports
1744 we want to listen on is now separate from binding to the ports
1748 - Building Tor with bufferevent support now requires Libevent
1749 2.0.13-stable or later. Previous versions of Libevent had bugs in
1750 SSL-related bufferevents and related issues that would make Tor
1751 work badly with bufferevents. Requiring 2.0.13-stable also allows
1752 Tor with bufferevents to take advantage of Libevent APIs
1753 introduced after 2.0.8-rc.
1756 Changes in version 0.2.2.32 - 2011-08-27
1757 The Tor 0.2.2 release series is dedicated to the memory of Andreas
1758 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
1759 a founder of the PETS community, a leader in our field, a mentor,
1760 and a friend. He left us with these words: "I had the possibility
1761 to contribute to this world that is not as it should be. I hope I
1762 could help in some areas to make the world a better place, and that
1763 I could also encourage other people to be engaged in improving the
1764 world. Please, stay engaged. This world needs you, your love, your
1765 initiative -- now I cannot be part of that anymore."
1767 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
1768 ready. More than two years in the making, this release features improved
1769 client performance and hidden service reliability, better compatibility
1770 for Android, correct behavior for bridges that listen on more than
1771 one address, more extensible and flexible directory object handling,
1772 better reporting of network statistics, improved code security, and
1773 many many other features and bugfixes.
1776 Changes in version 0.2.2.31-rc - 2011-08-17
1777 Tor 0.2.2.31-rc is the second and hopefully final release candidate
1778 for the Tor 0.2.2.x series.
1781 - Remove an extra pair of quotation marks around the error
1782 message in control-port STATUS_GENERAL BUG events. Bugfix on
1783 0.1.2.6-alpha; fixes bug 3732.
1784 - If we're configured to write our ControlPorts to disk, only write
1785 them after switching UID and creating the data directory. This way,
1786 we don't fail when starting up with a nonexistent DataDirectory
1787 and a ControlPortWriteToFile setting based on that directory. Fixes
1788 bug 3747; bugfix on Tor 0.2.2.26-beta.
1791 - Update to the August 2 2011 Maxmind GeoLite Country database.
1794 - Allow GETINFO fingerprint to return a fingerprint even when
1795 we have not yet built a router descriptor. Fixes bug 3577;
1796 bugfix on 0.2.0.1-alpha.
1797 - Write several files in text mode, on OSes that distinguish text
1798 mode from binary mode (namely, Windows). These files are:
1799 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1800 that collect those statistics; 'client_keys' and 'hostname' for
1801 hidden services that use authentication; and (in the tor-gencert
1802 utility) newly generated identity and signing keys. Previously,
1803 we wouldn't specify text mode or binary mode, leading to an
1804 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1805 the DirRecordUsageByCountry option which would have triggered
1806 the assertion failure was added), although this assertion failure
1807 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1808 - Selectively disable deprecation warnings on OS X because Lion
1809 started deprecating the shipped copy of openssl. Fixes bug 3643.
1810 - When unable to format an address as a string, report its value
1811 as "???" rather than reusing the last formatted address. Bugfix
1815 Changes in version 0.2.3.2-alpha - 2011-07-18
1816 Tor 0.2.3.2-alpha introduces two new experimental features:
1817 microdescriptors and pluggable transports. It also continues cleaning
1818 up a variety of recently introduced features.
1821 - Clients can now use microdescriptors instead of regular descriptors
1822 to build circuits. Microdescriptors are authority-generated
1823 summaries of regular descriptors' contents, designed to change
1824 very rarely (see proposal 158 for details). This feature is
1825 designed to save bandwidth, especially for clients on slow internet
1826 connections. It's off by default for now, since nearly no caches
1827 support it, but it will be on-by-default for clients in a future
1828 version. You can use the UseMicrodescriptors option to turn it on.
1829 - Tor clients using bridges can now be configured to use a separate
1830 'transport' proxy for each bridge. This approach helps to resist
1831 censorship by allowing bridges to use protocol obfuscation
1832 plugins. It implements part of proposal 180. Implements ticket 2841.
1833 - While we're trying to bootstrap, record how many TLS connections
1834 fail in each state, and report which states saw the most failures
1835 in response to any bootstrap failures. This feature may speed up
1836 diagnosis of censorship events. Implements ticket 3116.
1838 o Major bugfixes (on 0.2.3.1-alpha):
1839 - When configuring a large set of nodes in EntryNodes (as with
1840 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
1841 random subset to be guards, and choose them in random
1842 order. Fixes bug 2798.
1843 - Tor could crash when remembering a consensus in a non-used consensus
1844 flavor without having a current consensus set. Fixes bug 3361.
1845 - Comparing an unknown address to a microdescriptor's shortened exit
1846 policy would always give a "rejected" result. Fixes bug 3599.
1847 - Using microdescriptors as a client no longer prevents Tor from
1848 uploading and downloading hidden service descriptors. Fixes
1852 - Allow nameservers with IPv6 address. Resolves bug 2574.
1853 - Accept attempts to include a password authenticator in the
1854 handshake, as supported by SOCKS5. This handles SOCKS clients that
1855 don't know how to omit a password when authenticating. Resolves
1857 - When configuring a large set of nodes in EntryNodes, and there are
1858 enough of them listed as Guard so that we don't need to consider
1859 the non-guard entries, prefer the ones listed with the Guard flag.
1860 - Check for and recover from inconsistency in the microdescriptor
1861 cache. This will make it harder for us to accidentally free a
1862 microdescriptor without removing it from the appropriate data
1863 structures. Fixes issue 3135; issue noted by "wanoskarnet".
1864 - Log SSL state transitions at log level DEBUG, log domain
1865 HANDSHAKE. This can be useful for debugging censorship events.
1866 Implements ticket 3264.
1867 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
1868 implements ticket 3439.
1870 o Minor bugfixes (on 0.2.3.1-alpha):
1871 - Do not free all general-purpose regular descriptors just
1872 because microdescriptor use is enabled. Fixes bug 3113.
1873 - Correctly link libevent_openssl when --enable-static-libevent
1874 is passed to configure. Fixes bug 3118.
1875 - Bridges should not complain during their heartbeat log messages that
1876 they are unlisted in the consensus: that's more or less the point
1877 of being a bridge. Fixes bug 3183.
1878 - Report a SIGNAL event to controllers when acting on a delayed
1879 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
1880 event to the controller if we acted on a SIGNAL NEWNYM command
1881 immediately, and otherwise not report a SIGNAL event for the
1882 command at all. Fixes bug 3349.
1883 - Fix a crash when handling the SIGNAL controller command or
1884 reporting ERR-level status events with bufferevents enabled. Found
1885 by Robert Ransom. Fixes bug 3367.
1886 - Always ship the tor-fw-helper manpage in our release tarballs.
1887 Fixes bug 3389. Reported by Stephen Walker.
1888 - Fix a class of double-mark-for-close bugs when bufferevents
1889 are enabled. Fixes bug 3403.
1890 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
1891 - Add SIGNAL to the list returned by the 'GETINFO events/names'
1892 control-port command. Fixes part of bug 3465.
1893 - Prevent using negative indices during unit test runs when read_all()
1894 fails. Spotted by coverity.
1895 - Fix a rare memory leak when checking the nodelist without it being
1896 present. Found by coverity.
1897 - Only try to download a microdescriptor-flavored consensus from
1898 a directory cache that provides them.
1900 o Minor bugfixes (on 0.2.2.x and earlier):
1901 - Assert that hidden-service-related operations are not performed
1902 using single-hop circuits. Previously, Tor would assert that
1903 client-side streams are not attached to single-hop circuits,
1904 but not that other sensitive operations on the client and service
1905 side are not performed using single-hop circuits. Fixes bug 3332;
1907 - Don't publish a new relay descriptor when we reload our onion key,
1908 unless the onion key has actually changed. Fixes bug 3263 and
1909 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
1910 - Allow GETINFO fingerprint to return a fingerprint even when
1911 we have not yet built a router descriptor. Fixes bug 3577;
1912 bugfix on 0.2.0.1-alpha.
1913 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
1914 on 0.2.2.4-alpha; fixes bug 3427.
1916 o Code simplification and refactoring:
1917 - Use tor_sscanf() in place of scanf() in more places through the
1918 code. This makes us a little more locale-independent, and
1919 should help shut up code-analysis tools that can't tell
1920 a safe sscanf string from a dangerous one.
1921 - Use tt_assert(), not tor_assert(), for checking for test failures.
1922 This makes the unit tests more able to go on in the event that
1924 - Split connection_about_to_close() into separate functions for each
1928 - On Windows, we now define the _WIN32_WINNT macros only if they
1929 are not already defined. This lets the person building Tor decide,
1930 if they want, to require a later version of Windows.
1933 Changes in version 0.2.2.30-rc - 2011-07-07
1934 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
1935 series. It fixes a few smaller bugs, but generally appears stable.
1936 Please test it and let us know whether it is!
1939 - Send a SUCCEEDED stream event to the controller when a reverse
1940 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
1941 discovered by katmagic.
1942 - Always NUL-terminate the sun_path field of a sockaddr_un before
1943 passing it to the kernel. (Not a security issue: kernels are
1944 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1945 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1946 - Don't stack-allocate the list of supplementary GIDs when we're
1947 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1948 could take up to 256K, which is way too much stack. Found by
1949 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1950 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
1951 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
1952 fixes part of bug 3465.
1953 - Fix a memory leak when receiving a descriptor for a hidden
1954 service we didn't ask for. Found by Coverity; CID #30. Bugfix
1958 - Update to the July 1 2011 Maxmind GeoLite Country database.
1961 Changes in version 0.2.2.29-beta - 2011-06-20
1962 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
1963 have bridge lines in their torrc but don't want to use them; gets
1964 us closer to having the control socket feature working on Debian;
1965 and fixes a variety of smaller bugs.
1968 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
1969 When we changed the default behavior to "use bridges if any
1970 are listed in the torrc", we surprised users who had bridges
1971 in their torrc files but who didn't actually want to use them.
1972 Partial resolution for bug 3354.
1975 - Don't attach new streams to old rendezvous circuits after SIGNAL
1976 NEWNYM. Previously, we would keep using an existing rendezvous
1977 circuit if it remained open (i.e. if it were kept open by a
1978 long-lived stream, or if a new stream were attached to it before
1979 Tor could notice that it was old and no longer in use). Bugfix on
1980 0.1.1.15-rc; fixes bug 3375.
1983 - Fix a bug when using ControlSocketsGroupWritable with User. The
1984 directory's group would be checked against the current group, not
1985 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
1986 bugfix on 0.2.2.26-beta.
1987 - Make connection_printf_to_buf()'s behaviour sane. Its callers
1988 expect it to emit a CRLF iff the format string ends with CRLF;
1989 it actually emitted a CRLF iff (a) the format string ended with
1990 CRLF or (b) the resulting string was over 1023 characters long or
1991 (c) the format string did not end with CRLF *and* the resulting
1992 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
1993 fixes part of bug 3407.
1994 - Make send_control_event_impl()'s behaviour sane. Its callers
1995 expect it to always emit a CRLF at the end of the string; it
1996 might have emitted extra control characters as well. Bugfix on
1997 0.1.1.9-alpha; fixes another part of bug 3407.
1998 - Make crypto_rand_int() check the value of its input correctly.
1999 Previously, it accepted values up to UINT_MAX, but could return a
2000 negative number if given a value above INT_MAX+1. Found by George
2001 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2002 - Avoid a segfault when reading a malformed circuit build state
2003 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2005 - When asked about a DNS record type we don't support via a
2006 client DNSPort, reply with NOTIMPL rather than an empty
2007 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2008 - Fix a rare memory leak during stats writing. Found by coverity.
2011 - Update to the June 1 2011 Maxmind GeoLite Country database.
2013 o Code simplifications and refactoring:
2014 - Remove some dead code as indicated by coverity.
2015 - Remove a few dead assignments during router parsing. Found by
2017 - Add some forgotten return value checks during unit tests. Found
2019 - Don't use 1-bit wide signed bit fields. Found by coverity.
2022 Changes in version 0.2.2.28-beta - 2011-06-04
2023 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2024 fixed a big bug in whether relays stay in the consensus consistently,
2025 we moved closer to handling bridges and hidden services correctly,
2026 and we started the process of better handling the dreaded "my Vidalia
2027 died, and now my Tor demands a password when I try to reconnect to it"
2031 - Don't decide to make a new descriptor when receiving a HUP signal.
2032 This bug has caused a lot of 0.2.2.x relays to disappear from the
2033 consensus periodically. Fixes the most common case of triggering
2034 bug 1810; bugfix on 0.2.2.7-alpha.
2035 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2036 - Don't try to build descriptors if "ORPort auto" is set and we
2037 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2039 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2040 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2041 - Apply circuit timeouts to opened hidden-service-related circuits
2042 based on the correct start time. Previously, we would apply the
2043 circuit build timeout based on time since the circuit's creation;
2044 it was supposed to be applied based on time since the circuit
2045 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2046 - Use the same circuit timeout for client-side introduction
2047 circuits as for other four-hop circuits, rather than the timeout
2048 for single-hop directory-fetch circuits; the shorter timeout may
2049 have been appropriate with the static circuit build timeout in
2050 0.2.1.x and earlier, but caused many hidden service access attempts
2051 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2052 on 0.2.2.2-alpha; fixes another part of bug 1297.
2053 - In ticket 2511 we fixed a case where you could use an unconfigured
2054 bridge if you had configured it as a bridge the last time you ran
2055 Tor. Now fix another edge case: if you had configured it as a bridge
2056 but then switched to a different bridge via the controller, you
2057 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2061 - Add an __OwningControllerProcess configuration option and a
2062 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2063 that when it exits, Tor will shut down. Implements feature 3049.
2064 - If "UseBridges 1" is set and no bridges are configured, Tor will
2065 now refuse to build any circuits until some bridges are set.
2066 If "UseBridges auto" is set, Tor will use bridges if they are
2067 configured and we are not running as a server, but otherwise will
2068 make circuits as usual. The new default is "auto". Patch by anonym,
2069 so the Tails LiveCD can stop automatically revealing you as a Tor
2073 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2074 - Remove a trailing asterisk from "exit-policy/default" in the
2075 output of the control port command "GETINFO info/names". Bugfix
2077 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2079 - Warn when the user configures two HiddenServiceDir lines that point
2080 to the same directory. Bugfix on 0.0.6 (the version introducing
2081 HiddenServiceDir); fixes bug 3289.
2082 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2083 part of bug 2748; bugfix on 0.2.0.10-alpha.
2084 - Log malformed requests for rendezvous descriptors as protocol
2085 warnings, not warnings. Also, use a more informative log message
2086 in case someone sees it at log level warning without prior
2087 info-level messages. Fixes the other part of bug 2748; bugfix
2089 - Clear the table recording the time of the last request for each
2090 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2091 Previously, we would clear our HS descriptor cache on SIGNAL
2092 NEWNYM, but if we had previously retrieved a descriptor (or tried
2093 to) from every directory responsible for it, we would refuse to
2094 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2096 - Fix a log message that said "bits" while displaying a value in
2097 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2099 - When checking for 1024-bit keys, check for 1024 bits, not 128
2100 bytes. This allows Tor to correctly discard keys of length 1017
2101 through 1023. Bugfix on 0.0.9pre5.
2104 - Relays now log the reason for publishing a new relay descriptor,
2105 so we have a better chance of hunting down instances of bug 1810.
2106 Resolves ticket 3252.
2107 - Revise most log messages that refer to nodes by nickname to
2108 instead use the "$key=nickname at address" format. This should be
2109 more useful, especially since nicknames are less and less likely
2110 to be unique. Resolves ticket 3045.
2111 - Log (at info level) when purging pieces of hidden-service-client
2112 state because of SIGNAL NEWNYM.
2115 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2116 anything since 0.2.1.16-rc.
2119 Changes in version 0.2.2.27-beta - 2011-05-18
2120 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2121 release, and also adds a few more general bugfixes.
2124 - Fix a crash bug when changing bridges in a running Tor process.
2125 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2126 - When the controller configures a new bridge, don't wait 10 to 60
2127 seconds before trying to fetch its descriptor. Bugfix on
2128 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2131 - Require that onion keys have exponent 65537 in microdescriptors too.
2132 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2133 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2134 Changed the limit to 512 characters by removing base64 newlines.
2135 Fixes bug 2752. Fix by Michael Yakubovich.
2136 - When a client starts or stops using bridges, never use a circuit
2137 that was built before the configuration change. This behavior could
2138 put at risk a user who uses bridges to ensure that her traffic
2139 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2143 Changes in version 0.2.2.26-beta - 2011-05-17
2144 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2145 also introduces a new "socksport auto" approach that should make it
2146 easier to run multiple Tors on the same system, and does a lot of
2147 cleanup to get us closer to a release candidate.
2149 o Security/privacy fixes:
2150 - Replace all potentially sensitive memory comparison operations
2151 with versions whose runtime does not depend on the data being
2152 compared. This will help resist a class of attacks where an
2153 adversary can use variations in timing information to learn
2154 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2155 implementation by Robert Ransom based partially on code by DJB.)
2156 - When receiving a hidden service descriptor, check that it is for
2157 the hidden service we wanted. Previously, Tor would store any
2158 hidden service descriptors that a directory gave it, whether it
2159 wanted them or not. This wouldn't have let an attacker impersonate
2160 a hidden service, but it did let directories pre-seed a client
2161 with descriptors that it didn't want. Bugfix on 0.0.6.
2162 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2163 DNS cache entries, and virtual address mappings: that's what
2164 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2167 - The options SocksPort, ControlPort, and so on now all accept a
2168 value "auto" that opens a socket on an OS-selected port. A
2169 new ControlPortWriteToFile option tells Tor to write its
2170 actual control port or ports to a chosen file. If the option
2171 ControlPortFileGroupReadable is set, the file is created as
2172 group-readable. Now users can run two Tor clients on the same
2173 system without needing to manually mess with parameters. Resolves
2174 part of ticket 3076.
2175 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2176 help busy exit nodes avoid running out of useable ports just
2177 because all the ports have been used in the near past. Resolves
2181 - New "GETINFO net/listeners/(type)" controller command to return
2182 a list of addresses and ports that are bound for listeners for a
2183 given connection type. This is useful when the user has configured
2184 "SocksPort auto" and the controller needs to know which port got
2185 chosen. Resolves another part of ticket 3076.
2186 - Add a new ControlSocketsGroupWritable configuration option: when
2187 it is turned on, ControlSockets are group-writeable by the default
2188 group of the current user. Patch by Jérémy Bobbio; implements
2190 - Tor now refuses to create a ControlSocket in a directory that is
2191 world-readable (or group-readable if ControlSocketsGroupWritable
2192 is 0). This is necessary because some operating systems do not
2193 enforce permissions on an AF_UNIX sockets. Permissions on the
2194 directory holding the socket, however, seems to work everywhere.
2195 - Rate-limit a warning about failures to download v2 networkstatus
2196 documents. Resolves part of bug 1352.
2197 - Backport code from 0.2.3.x that allows directory authorities to
2198 clean their microdescriptor caches. Needed to resolve bug 2230.
2199 - When an HTTPS proxy reports "403 Forbidden", we now explain
2200 what it means rather than calling it an unexpected status code.
2201 Closes bug 2503. Patch from Michael Yakubovich.
2202 - Update to the May 1 2011 Maxmind GeoLite Country database.
2205 - Authorities now clean their microdesc cache periodically and when
2206 reading from disk initially, not only when adding new descriptors.
2207 This prevents a bug where we could lose microdescriptors. Bugfix
2208 on 0.2.2.6-alpha. Fixes bug 2230.
2209 - Do not crash when our configuration file becomes unreadable, for
2210 example due to a permissions change, between when we start up
2211 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2213 - Avoid a bug that would keep us from replacing a microdescriptor
2214 cache on Windows. (We would try to replace the file while still
2215 holding it open. That's fine on Unix, but Windows doesn't let us
2216 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2217 - Add missing explanations for the authority-related torrc options
2218 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2219 man page. Resolves issue 2379.
2220 - As an authority, do not upload our own vote or signature set to
2221 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2222 it would get flagged as a duplicate. Resolves bug 3026.
2223 - Accept hidden service descriptors if we think we might be a hidden
2224 service directory, regardless of what our consensus says. This
2225 helps robustness, since clients and hidden services can sometimes
2226 have a more up-to-date view of the network consensus than we do,
2227 and if they think that the directory authorities list us a HSDir,
2228 we might actually be one. Related to bug 2732; bugfix on
2230 - When a controller changes TrackHostExits, remove mappings for
2231 hosts that should no longer have their exits tracked. Bugfix on
2233 - When a controller changes VirtualAddrNetwork, remove any mappings
2234 for hosts that were automapped to the old network. Bugfix on
2236 - When a controller changes one of the AutomapHosts* options, remove
2237 any mappings for hosts that should no longer be automapped. Bugfix
2239 - Do not reset the bridge descriptor download status every time we
2240 re-parse our configuration or get a configuration change. Fixes
2241 bug 3019; bugfix on 0.2.0.3-alpha.
2243 o Minor bugfixes (code cleanup):
2244 - When loading the microdesc journal, remember its current size.
2245 In 0.2.2, this helps prevent the microdesc journal from growing
2246 without limit on authorities (who are the only ones to use it in
2247 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2248 Fix posted by "cypherpunks."
2249 - The microdesc journal is supposed to get rebuilt only if it is
2250 at least _half_ the length of the store, not _twice_ the length
2251 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2252 - Fix a potential null-pointer dereference while computing a
2253 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2255 - Avoid a possible null-pointer dereference when rebuilding the mdesc
2256 cache without actually having any descriptors to cache. Bugfix on
2257 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
2258 - If we fail to compute the identity digest of a v3 legacy keypair,
2259 warn, and don't use a buffer-full of junk instead. Bugfix on
2260 0.2.1.1-alpha; fixes bug 3106.
2261 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2262 where if the function had ever in the future been used to check
2263 for the presence of a too-large number, it would have given an
2264 incorrect result. (Fortunately, we only used it for 16-bit
2265 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2266 - Require that introduction point keys and onion handshake keys
2267 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2271 - Caches no longer download and serve v2 networkstatus documents
2272 unless FetchV2Networkstatus flag is set: these documents haven't
2273 haven't been used by clients or relays since 0.2.0.x. Resolves
2277 Changes in version 0.2.3.1-alpha - 2011-05-05
2278 Tor 0.2.3.1-alpha adds some new experimental features, including support
2279 for an improved network IO backend, IOCP networking on Windows,
2280 microdescriptor caching, "fast-start" support for streams, and automatic
2281 home router configuration. There are also numerous internal improvements
2282 to try to make the code easier for developers to work with.
2284 This is the first alpha release in a new series, so expect there to be
2285 bugs. Users who would rather test out a more stable branch should
2286 stay with 0.2.2.x for now.
2289 - Tor can now optionally build with the "bufferevents" buffered IO
2290 backend provided by Libevent 2. To use this feature, make sure you
2291 have the latest possible version of Libevent, and pass the
2292 --enable-bufferevents flag to configure when building Tor from
2293 source. This feature will make our networking code more flexible,
2294 let us stack layers on each other, and let us use more efficient
2295 zero-copy transports where available.
2296 - As an experimental feature, Tor can use IOCP for networking on Windows.
2297 Once this code is tuned and optimized, it promises much better
2298 performance than the select-based backend we've used in the past. To
2299 try this feature, you must build Tor with Libevent 2, configure Tor
2300 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
2301 your torrc. There are known bugs here: only try this if you can help
2302 debug it as it breaks.
2303 - The EntryNodes option can now include country codes like {de} or IP
2304 addresses or network masks. Previously we had disallowed these options
2305 because we didn't have an efficient way to keep the list up to
2306 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
2307 - Exit nodes now accept and queue data on not-yet-connected streams.
2308 Previously, the client wasn't allowed to send data until the stream was
2309 connected, which slowed down all connections. This change will enable
2310 clients to perform a "fast-start" on streams and send data without
2311 having to wait for a confirmation that the stream has opened. (Patch
2312 from Ian Goldberg; implements the server side of Proposal 174.)
2313 - Tor now has initial support for automatic port mapping on the many
2314 home routers that support NAT-PMP or UPnP. (Not yet supported on
2315 Windows). To build the support code, you'll need to have libnatpnp
2316 library and/or the libminiupnpc library, and you'll need to enable the
2317 feature specifically by passing "--enable-upnp" and/or
2318 "--enable-natpnp" to configure. To turn it on, use the new
2319 PortForwarding option.
2320 - Caches now download, cache, and serve multiple "flavors" of the
2321 consensus, including a flavor that describes microdescriptors.
2322 - Caches now download, cache, and serve microdescriptors -- small
2323 summaries of router descriptors that are authenticated by all of the
2324 directory authorities. Once enough caches are running this code,
2325 clients will be able to save significant amounts of directory bandwidth
2326 by downloading microdescriptors instead of router descriptors.
2329 - Make logging resolution configurable with a new LogTimeGranularity
2330 option, and change the default from 1 millisecond to 1 second.
2331 Implements enhancement 1668.
2332 - We log which torrc file we're using on startup. Implements ticket
2334 - Ordinarily, Tor does not count traffic from private addresses (like
2335 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2336 There is now a new option, CountPrivateBandwidth, to disable this
2337 behavior. Patch from Daniel Cagara.
2338 - New --enable-static-tor configure option for building Tor as
2339 statically as possible. Idea, general hackery and thoughts from
2340 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2342 - If you set the NumCPUs option to 0, Tor will now try to detect how
2343 many CPUs you have. This is the new default behavior.
2344 - Turn on directory request statistics by default and include them in
2345 extra-info descriptors. Don't break if we have no GeoIP database.
2346 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2347 bidirectional use of connections to disk every 24 hours.
2348 - Add a GeoIP file digest to the extra-info descriptor. Implements
2350 - The NodeFamily option -- which let you declare that you want to
2351 consider nodes to be part of a family whether they list themselves
2352 that way or not -- now allows IP address ranges and country codes.
2353 - Add a new 'Heartbeat' log message type to periodically log a message
2354 describing Tor's status at level Notice. This feature is meant for
2355 operators who log at notice, and want to make sure that their Tor
2356 server is still working. Implementation by George Kadianakis.
2358 o Minor bugfixes (on 0.2.2.25-alpha):
2359 - When loading the microdesc journal, remember its current size.
2360 In 0.2.2, this helps prevent the microdesc journal from growing
2361 without limit on authorities (who are the only ones to use it in
2362 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2363 Fix posted by "cypherpunks."
2364 - The microdesc journal is supposed to get rebuilt only if it is
2365 at least _half_ the length of the store, not _twice_ the length
2366 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2367 - If as an authority we fail to compute the identity digest of a v3
2368 legacy keypair, warn, and don't use a buffer-full of junk instead.
2369 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
2370 - Authorities now clean their microdesc cache periodically and when
2371 reading from disk initially, not only when adding new descriptors.
2372 This prevents a bug where we could lose microdescriptors. Bugfix
2375 o Minor features (controller):
2376 - Add a new SIGNAL event to the controller interface so that
2377 controllers can be notified when Tor handles a signal. Resolves
2378 issue 1955. Patch by John Brooks.
2379 - Add a new GETINFO option to get total bytes read and written. Patch
2380 from pipe, revised by atagar. Resolves ticket 2345.
2381 - Implement some GETINFO controller fields to provide information about
2382 the Tor process's pid, euid, username, and resource limits.
2385 - Our build system requires automake 1.6 or later to create the
2386 Makefile.in files. Previously, you could have used 1.4.
2387 This only affects developers and people building Tor from git;
2388 people who build Tor from the source distribution without changing
2389 the Makefile.am files should be fine.
2390 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
2391 so on. This is more robust against some of the failure modes
2392 associated with running the autotools pieces on their own.
2394 o Minor packaging issues:
2395 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
2396 already created. Patch from Andreas Stieger. Fixes bug 2573.
2398 o Code simplifications and refactoring:
2399 - A major revision to our internal node-selecting and listing logic.
2400 Tor already had at least two major ways to look at the question of
2401 "which Tor servers do we know about": a list of router descriptors,
2402 and a list of entries in the current consensus. With
2403 microdescriptors, we're adding a third. Having so many systems
2404 without an abstraction layer over them was hurting the codebase.
2405 Now, we have a new "node_t" abstraction that presents a consistent
2406 interface to a client's view of a Tor node, and holds (nearly) all
2407 of the mutable state formerly in routerinfo_t and routerstatus_t.
2408 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2409 no longer link against Libevent: they never used it, but
2410 our library structure used to force them to link it.
2413 - Remove some old code to work around even older versions of Tor that
2414 used forked processes to handle DNS requests. Such versions of Tor
2415 are no longer in use as servers.
2417 o Documentation fixes:
2418 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2419 - Add missing documentation for the authority-related torrc options
2420 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
2424 Changes in version 0.2.2.25-alpha - 2011-04-29
2425 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
2426 robust, routers no longer overreport their bandwidth, Win7 should crash
2427 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
2428 now prevents hidden service-related activity from being linkable. It
2429 provides more information to Vidalia so you can see if your bridge is
2430 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
2431 StrictNodes configuration options to make them more reliable, more
2432 understandable, and more regularly applied. If you use those options,
2433 please see the revised documentation for them in the manual page.
2436 - Relays were publishing grossly inflated bandwidth values because
2437 they were writing their state files wrong--now they write the
2438 correct value. Also, resume reading bandwidth history from the
2439 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
2440 - Improve hidden service robustness: When we find that we have
2441 extended a hidden service's introduction circuit to a relay not
2442 listed as an introduction point in the HS descriptor we currently
2443 have, retry with an introduction point from the current
2444 descriptor. Previously we would just give up. Fixes bugs 1024 and
2445 1930; bugfix on 0.2.0.10-alpha.
2446 - Clients now stop trying to use an exit node associated with a given
2447 destination by TrackHostExits if they fail to reach that exit node.
2448 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
2449 - Fix crash bug on platforms where gmtime and localtime can return
2450 NULL. Windows 7 users were running into this one. Fixes part of bug
2451 2077. Bugfix on all versions of Tor. Found by boboper.
2453 o Security and stability fixes:
2454 - Don't double-free a parsable, but invalid, microdescriptor, even if
2455 it is followed in the blob we're parsing by an unparsable
2456 microdescriptor. Fixes an issue reported in a comment on bug 2954.
2457 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
2458 - If the Nickname configuration option isn't given, Tor would pick a
2459 nickname based on the local hostname as the nickname for a relay.
2460 Because nicknames are not very important in today's Tor and the
2461 "Unnamed" nickname has been implemented, this is now problematic
2462 behavior: It leaks information about the hostname without being
2463 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
2464 introduced the Unnamed nickname. Reported by tagnaq.
2465 - Fix an uncommon assertion failure when running with DNSPort under
2466 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2467 - Avoid linkability based on cached hidden service descriptors: forget
2468 all hidden service descriptors cached as a client when processing a
2469 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2472 - Export GeoIP information on bridge usage to controllers even if we
2473 have not yet been running for 24 hours. Now Vidalia bridge operators
2474 can get more accurate and immediate feedback about their
2475 contributions to the network.
2477 o Major features and bugfixes (node selection):
2478 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2479 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
2480 options. Previously, we had been ambiguous in describing what
2481 counted as an "exit" node, and what operations exactly "StrictNodes
2482 0" would permit. This created confusion when people saw nodes built
2483 through unexpected circuits, and made it hard to tell real bugs from
2484 surprises. Now the intended behavior is:
2485 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2486 a node that delivers user traffic outside the Tor network.
2487 . "Entry", in the context of EntryNodes, means a node used as the
2488 first hop of a multihop circuit. It doesn't include direct
2489 connections to directory servers.
2490 . "ExcludeNodes" applies to all nodes.
2491 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2492 StrictNodes is set, Tor should avoid all nodes listed in
2493 ExcludeNodes, even when it will make user requests fail. When
2494 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2495 whenever it can, except when it must use an excluded node to
2496 perform self-tests, connect to a hidden service, provide a
2497 hidden service, fulfill a .exit request, upload directory
2498 information, or fetch directory information.
2499 Collectively, the changes to implement the behavior fix bug 1090.
2500 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2501 a node is listed in both, it's treated as excluded.
2502 - ExcludeNodes now applies to directory nodes -- as a preference if
2503 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2504 Don't exclude all the directory authorities and set StrictNodes to 1
2505 unless you really want your Tor to break.
2506 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2507 - ExcludeExitNodes now overrides .exit requests.
2508 - We don't use bridges listed in ExcludeNodes.
2509 - When StrictNodes is 1:
2510 . We now apply ExcludeNodes to hidden service introduction points
2511 and to rendezvous points selected by hidden service users. This
2512 can make your hidden service less reliable: use it with caution!
2513 . If we have used ExcludeNodes on ourself, do not try relay
2514 reachability self-tests.
2515 . If we have excluded all the directory authorities, we will not
2516 even try to upload our descriptor if we're a relay.
2517 . Do not honor .exit requests to an excluded node.
2518 - Remove a misfeature that caused us to ignore the Fast/Stable flags
2519 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
2520 - When the set of permitted nodes changes, we now remove any mappings
2521 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
2523 - We never cannibalize a circuit that had excluded nodes on it, even
2524 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
2525 - Revert a change where we would be laxer about attaching streams to
2526 circuits than when building the circuits. This was meant to prevent
2527 a set of bugs where streams were never attachable, but our improved
2528 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
2529 - Keep track of how many times we launch a new circuit to handle a
2530 given stream. Too many launches could indicate an inconsistency
2531 between our "launch a circuit to handle this stream" logic and our
2532 "attach this stream to one of the available circuits" logic.
2533 - Improve log messages related to excluded nodes.
2536 - Fix a spurious warning when moving from a short month to a long
2537 month on relays with month-based BandwidthAccounting. Bugfix on
2538 0.2.2.17-alpha; fixes bug 3020.
2539 - When a client finds that an origin circuit has run out of 16-bit
2540 stream IDs, we now mark it as unusable for new streams. Previously,
2541 we would try to close the entire circuit. Bugfix on 0.0.6.
2542 - Add a forgotten cast that caused a compile warning on OS X 10.6.
2543 Bugfix on 0.2.2.24-alpha.
2544 - Be more careful about reporting the correct error from a failed
2545 connect() system call. Under some circumstances, it was possible to
2546 look at an incorrect value for errno when sending the end reason.
2547 Bugfix on 0.1.0.1-rc.
2548 - Correctly handle an "impossible" overflow cases in connection byte
2549 counting, where we write or read more than 4GB on an edge connection
2550 in a single second. Bugfix on 0.1.2.8-beta.
2551 - Correct the warning displayed when a rendezvous descriptor exceeds
2552 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2554 - Clients and hidden services now use HSDir-flagged relays for hidden
2555 service descriptor downloads and uploads even if the relays have no
2556 DirPort set and the client has disabled TunnelDirConns. This will
2557 eventually allow us to give the HSDir flag to relays with no
2558 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
2559 - Downgrade "no current certificates known for authority" message from
2560 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
2561 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
2562 2917. Bugfix on 0.1.1.1-alpha.
2563 - Only limit the lengths of single HS descriptors, even when multiple
2564 HS descriptors are published to an HSDir relay in a single POST
2565 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
2566 - Write the current time into the LastWritten line in our state file,
2567 rather than the time from the previous write attempt. Also, stop
2568 trying to use a time of -1 in our log statements. Fixes bug 3039;
2569 bugfix on 0.2.2.14-alpha.
2570 - Be more consistent in our treatment of file system paths. "~" should
2571 get expanded to the user's home directory in the Log config option.
2572 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
2573 feature for the -f and --DataDirectory options.
2576 - Make sure every relay writes a state file at least every 12 hours.
2577 Previously, a relay could go for weeks without writing its state
2578 file, and on a crash could lose its bandwidth history, capacity
2579 estimates, client country statistics, and so on. Addresses bug 3012.
2580 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
2581 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
2582 clients are already deprecated because of security bugs.
2583 - Don't allow v0 hidden service authorities to act as clients.
2584 Required by fix for bug 3000.
2585 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
2586 by fix for bug 3000.
2587 - Ensure that no empty [dirreq-](read|write)-history lines are added
2588 to an extrainfo document. Implements ticket 2497.
2590 o Code simplification and refactoring:
2591 - Remove workaround code to handle directory responses from servers
2592 that had bug 539 (they would send HTTP status 503 responses _and_
2593 send a body too). Since only server versions before
2594 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
2595 keep the workaround in place.
2596 - Remove the old 'fuzzy time' logic. It was supposed to be used for
2597 handling calculations where we have a known amount of clock skew and
2598 an allowed amount of unknown skew. But we only used it in three
2599 places, and we never adjusted the known/unknown skew values. This is
2600 still something we might want to do someday, but if we do, we'll
2601 want to do it differently.
2602 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2603 None of the cases where we did this before were wrong, but by making
2604 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2605 - Use GetTempDir to find the proper temporary directory location on
2606 Windows when generating temporary files for the unit tests. Patch by
2610 Changes in version 0.2.2.24-alpha - 2011-04-08
2611 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
2612 prevented Tor clients from effectively using "multihomed" bridges,
2613 that is, bridges that listen on multiple ports or IP addresses so users
2614 can continue to use some of their addresses even if others get blocked.
2617 - Fix a bug where bridge users who configure the non-canonical
2618 address of a bridge automatically switch to its canonical
2619 address. If a bridge listens at more than one address, it should be
2620 able to advertise those addresses independently and any non-blocked
2621 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
2623 - If you configured Tor to use bridge A, and then quit and
2624 configured Tor to use bridge B instead, it would happily continue
2625 to use bridge A if it's still reachable. While this behavior is
2626 a feature if your goal is connectivity, in some scenarios it's a
2627 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
2628 - Directory authorities now use data collected from their own
2629 uptime observations when choosing whether to assign the HSDir flag
2630 to relays, instead of trusting the uptime value the relay reports in
2631 its descriptor. This change helps prevent an attack where a small
2632 set of nodes with frequently-changing identity keys can blackhole
2633 a hidden service. (Only authorities need upgrade; others will be
2634 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
2637 - When we restart our relay, we might get a successful connection
2638 from the outside before we've started our reachability tests,
2639 triggering a warning: "ORPort found reachable, but I have no
2640 routerinfo yet. Failing to inform controller of success." This
2641 bug was harmless unless Tor is running under a controller
2642 like Vidalia, in which case the controller would never get a
2643 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2645 - Make directory authorities more accurate at recording when
2646 relays that have failed several reachability tests became
2647 unreachable, so we can provide more accuracy at assigning Stable,
2648 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
2649 - Fix an issue that prevented static linking of libevent on
2650 some platforms (notably Linux). Fixes bug 2698; bugfix on
2651 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
2652 the --with-static-libevent configure option).
2653 - We now ask the other side of a stream (the client or the exit)
2654 for more data on that stream when the amount of queued data on
2655 that stream dips low enough. Previously, we wouldn't ask the
2656 other side for more data until either it sent us more data (which
2657 it wasn't supposed to do if it had exhausted its window!) or we
2658 had completely flushed all our queued data. This flow control fix
2659 should improve throughput. Fixes bug 2756; bugfix on the earliest
2660 released versions of Tor (svn commit r152).
2661 - Avoid a double-mark-for-free warning when failing to attach a
2662 transparent proxy connection. (We thought we had fixed this in
2663 0.2.2.23-alpha, but it turns out our fix was checking the wrong
2664 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
2665 bug) and 0.2.2.23-alpha (the incorrect fix).
2666 - When warning about missing zlib development packages during compile,
2667 give the correct package names. Bugfix on 0.2.0.1-alpha.
2670 - Directory authorities now log the source of a rejected POSTed v3
2672 - Make compilation with clang possible when using
2673 --enable-gcc-warnings by removing two warning options that clang
2674 hasn't implemented yet and by fixing a few warnings. Implements
2676 - When expiring circuits, use microsecond timers rather than
2677 one-second timers. This can avoid an unpleasant situation where a
2678 circuit is launched near the end of one second and expired right
2679 near the beginning of the next, and prevent fluctuations in circuit
2681 - Use computed circuit-build timeouts to decide when to launch
2682 parallel introduction circuits for hidden services. (Previously,
2683 we would retry after 15 seconds.)
2684 - Update to the April 1 2011 Maxmind GeoLite Country database.
2687 - Create the /var/run/tor directory on startup on OpenSUSE if it is
2688 not already created. Patch from Andreas Stieger. Fixes bug 2573.
2690 o Documentation changes:
2691 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
2692 - Resolve all doxygen warnings except those for missing documentation.
2694 - Add doxygen documentation for more functions, fields, and types.
2697 Changes in version 0.2.2.23-alpha - 2011-03-08
2698 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
2699 they restart they don't lose their bandwidth capacity estimate. This
2700 release also fixes a diverse set of user-facing bugs, ranging from
2701 relays overrunning their rate limiting to clients falsely warning about
2702 clock skew to bridge descriptor leaks by our bridge directory authority.
2705 - Stop sending a CLOCK_SKEW controller status event whenever
2706 we fetch directory information from a relay that has a wrong clock.
2707 Instead, only inform the controller when it's a trusted authority
2708 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2709 the rest of bug 1074.
2710 - Fix an assert in parsing router descriptors containing IPv6
2711 addresses. This one took down the directory authorities when
2712 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2713 - Make the bridge directory authority refuse to answer directory
2714 requests for "all" descriptors. It used to include bridge
2715 descriptors in its answer, which was a major information leak.
2716 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2717 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2718 Tor would ignore their RelayBandwidthBurst setting,
2719 potentially using more bandwidth than expected. Bugfix on
2720 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2721 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2722 hidserv" in her torrc. The 'hidserv' argument never controlled
2723 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2726 - Relays now save observed peak bandwidth throughput rates to their
2727 state file (along with total usage, which was already saved)
2728 so that they can determine their correct estimated bandwidth on
2729 restart. Resolves bug 1863, where Tor relays would reset their
2730 estimated bandwidth to 0 after restarting.
2731 - Directory authorities now take changes in router IP address and
2732 ORPort into account when determining router stability. Previously,
2733 if a router changed its IP or ORPort, the authorities would not
2734 treat it as having any downtime for the purposes of stability
2735 calculation, whereas clients would experience downtime since the
2736 change could take a while to propagate to them. Resolves issue 1035.
2737 - Enable Address Space Layout Randomization (ASLR) and Data Execution
2738 Prevention (DEP) by default on Windows to make it harder for
2739 attackers to exploit vulnerabilities. Patch from John Brooks.
2741 o Minor bugfixes (on 0.2.1.x and earlier):
2742 - Fix a rare crash bug that could occur when a client was configured
2743 with a large number of bridges. Fixes bug 2629; bugfix on
2744 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2745 - Avoid a double mark-for-free warning when failing to attach a
2746 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
2748 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
2749 found by "cypherpunks". This bug was introduced before the first
2750 Tor release, in svn commit r110.
2751 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
2752 don't mention them in the manpage. Fixes bug 2450; issue
2753 spotted by keb and G-Lo.
2754 - Fix a bug in bandwidth history state parsing that could have been
2755 triggered if a future version of Tor ever changed the timing
2756 granularity at which bandwidth history is measured. Bugfix on
2758 - When a relay decides that its DNS is too broken for it to serve
2759 as an exit server, it advertised itself as a non-exit, but
2760 continued to act as an exit. This could create accidental
2761 partitioning opportunities for users. Instead, if a relay is
2762 going to advertise reject *:* as its exit policy, it should
2763 really act with exit policy "reject *:*". Fixes bug 2366.
2764 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
2765 - In the special case where you configure a public exit relay as your
2766 bridge, Tor would be willing to use that exit relay as the last
2767 hop in your circuit as well. Now we fail that circuit instead.
2768 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
2769 - Fix a bug with our locking implementation on Windows that couldn't
2770 correctly detect when a file was already locked. Fixes bug 2504,
2771 bugfix on 0.2.1.6-alpha.
2772 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
2773 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
2775 - Set target port in get_interface_address6() correctly. Bugfix
2776 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
2777 - Directory authorities are now more robust to hops back in time
2778 when calculating router stability. Previously, if a run of uptime
2779 or downtime appeared to be negative, the calculation could give
2780 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
2782 - Fix an assert that got triggered when using the TestingTorNetwork
2783 configuration option and then issuing a GETINFO config-text control
2784 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
2786 o Minor bugfixes (on 0.2.2.x):
2787 - Clients should not weight BadExit nodes as Exits in their node
2788 selection. Similarly, directory authorities should not count BadExit
2789 bandwidth as Exit bandwidth when computing bandwidth-weights.
2790 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
2791 - Correctly clear our dir_read/dir_write history when there is an
2792 error parsing any bw history value from the state file. Bugfix on
2794 - Resolve a bug in verifying signatures of directory objects
2795 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
2796 Fixes bug 2409. Found by "piebeer".
2797 - Bridge authorities no longer crash on SIGHUP when they try to
2798 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
2802 - Log less aggressively about circuit timeout changes, and improve
2803 some other circuit timeout messages. Resolves bug 2004.
2804 - Log a little more clearly about the times at which we're no longer
2805 accepting new connections. Resolves bug 2181.
2806 - Reject attempts at the client side to open connections to private
2807 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
2808 a randomly chosen exit node. Attempts to do so are always
2809 ill-defined, generally prevented by exit policies, and usually
2810 in error. This will also help to detect loops in transparent
2811 proxy configurations. You can disable this feature by setting
2812 "ClientRejectInternalAddresses 0" in your torrc.
2813 - Always treat failure to allocate an RSA key as an unrecoverable
2815 - Update to the March 1 2011 Maxmind GeoLite Country database.
2817 o Minor features (log subsystem):
2818 - Add documentation for configuring logging at different severities in
2819 different log domains. We've had this feature since 0.2.1.1-alpha,
2820 but for some reason it never made it into the manpage. Fixes
2822 - Make it simpler to specify "All log domains except for A and B".
2823 Previously you needed to say "[*,~A,~B]". Now you can just say
2825 - Add a "LogMessageDomains 1" option to include the domains of log
2826 messages along with the messages. Without this, there's no way
2827 to use log domains without reading the source or doing a lot
2830 o Packaging changes:
2831 - Stop shipping the Tor specs files and development proposal documents
2832 in the tarball. They are now in a separate git repository at
2833 git://git.torproject.org/torspec.git
2836 Changes in version 0.2.1.30 - 2011-02-23
2837 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
2838 change is a slight tweak to Tor's TLS handshake that makes relays
2839 and bridges that run this new version reachable from Iran again.
2840 We don't expect this tweak will win the arms race long-term, but it
2841 buys us time until we roll out a better solution.
2844 - Stop sending a CLOCK_SKEW controller status event whenever
2845 we fetch directory information from a relay that has a wrong clock.
2846 Instead, only inform the controller when it's a trusted authority
2847 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2848 the rest of bug 1074.
2849 - Fix a bounds-checking error that could allow an attacker to
2850 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2852 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2853 Tor would ignore their RelayBandwidthBurst setting,
2854 potentially using more bandwidth than expected. Bugfix on
2855 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2856 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2857 hidserv" in her torrc. The 'hidserv' argument never controlled
2858 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2861 - Adjust our TLS Diffie-Hellman parameters to match those used by
2863 - Update to the February 1 2011 Maxmind GeoLite Country database.
2866 - Check for and reject overly long directory certificates and
2867 directory tokens before they have a chance to hit any assertions.
2868 Bugfix on 0.2.1.28. Found by "doorss".
2869 - Bring the logic that gathers routerinfos and assesses the
2870 acceptability of circuits into line. This prevents a Tor OP from
2871 getting locked in a cycle of choosing its local OR as an exit for a
2872 path (due to a .exit request) and then rejecting the circuit because
2873 its OR is not listed yet. It also prevents Tor clients from using an
2874 OR running in the same instance as an exit (due to a .exit request)
2875 if the OR does not meet the same requirements expected of an OR
2876 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
2878 o Packaging changes:
2879 - Stop shipping the Tor specs files and development proposal documents
2880 in the tarball. They are now in a separate git repository at
2881 git://git.torproject.org/torspec.git
2882 - Do not include Git version tags as though they are SVN tags when
2883 generating a tarball from inside a repository that has switched
2884 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2887 Changes in version 0.2.2.22-alpha - 2011-01-25
2888 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
2889 main other change is a slight tweak to Tor's TLS handshake that makes
2890 relays and bridges that run this new version reachable from Iran again.
2891 We don't expect this tweak will win the arms race long-term, but it
2892 will buy us a bit more time until we roll out a better solution.
2895 - Fix a bounds-checking error that could allow an attacker to
2896 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2898 - Don't assert when changing from bridge to relay or vice versa
2899 via the controller. The assert happened because we didn't properly
2900 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
2901 bug 2433. Reported by bastik.
2904 - Adjust our TLS Diffie-Hellman parameters to match those used by
2906 - Provide a log message stating which geoip file we're parsing
2907 instead of just stating that we're parsing the geoip file.
2908 Implements ticket 2432.
2911 - Check for and reject overly long directory certificates and
2912 directory tokens before they have a chance to hit any assertions.
2913 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
2916 Changes in version 0.2.2.21-alpha - 2011-01-15
2917 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
2918 continues our recent code security audit work. The main fix resolves
2919 a remote heap overflow vulnerability that can allow remote code
2920 execution (CVE-2011-0427). Other fixes address a variety of assert
2921 and crash bugs, most of which we think are hard to exploit remotely.
2923 o Major bugfixes (security), also included in 0.2.1.29:
2924 - Fix a heap overflow bug where an adversary could cause heap
2925 corruption. This bug probably allows remote code execution
2926 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
2928 - Prevent a denial-of-service attack by disallowing any
2929 zlib-compressed data whose compression factor is implausibly
2930 high. Fixes part of bug 2324; reported by "doorss".
2931 - Zero out a few more keys in memory before freeing them. Fixes
2932 bug 2384 and part of bug 2385. These key instances found by
2933 "cypherpunks", based on Andrew Case's report about being able
2934 to find sensitive data in Tor's memory space if you have enough
2935 permissions. Bugfix on 0.0.2pre9.
2937 o Major bugfixes (crashes), also included in 0.2.1.29:
2938 - Prevent calls to Libevent from inside Libevent log handlers.
2939 This had potential to cause a nasty set of crashes, especially
2940 if running Libevent with debug logging enabled, and running
2941 Tor with a controller watching for low-severity log messages.
2942 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
2943 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
2944 underflow errors there too. Fixes the other part of bug 2324.
2945 - Fix a bug where we would assert if we ever had a
2946 cached-descriptors.new file (or another file read directly into
2947 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
2948 on 0.2.1.25. Found by doorss.
2949 - Fix some potential asserts and parsing issues with grossly
2950 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
2953 o Minor bugfixes (other), also included in 0.2.1.29:
2954 - Fix a bug with handling misformed replies to reverse DNS lookup
2955 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
2956 bug reported by doorss.
2957 - Fix compilation on mingw when a pthreads compatibility library
2958 has been installed. (We don't want to use it, so we shouldn't
2959 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
2960 - Fix a bug where we would declare that we had run out of virtual
2961 addresses when the address space was only half-exhausted. Bugfix
2963 - Correctly handle the case where AutomapHostsOnResolve is set but
2964 no virtual addresses are available. Fixes bug 2328; bugfix on
2965 0.1.2.1-alpha. Bug found by doorss.
2966 - Correctly handle wrapping around when we run out of virtual
2967 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
2969 o Minor features, also included in 0.2.1.29:
2970 - Update to the January 1 2011 Maxmind GeoLite Country database.
2971 - Introduce output size checks on all of our decryption functions.
2973 o Build changes, also included in 0.2.1.29:
2974 - Tor does not build packages correctly with Automake 1.6 and earlier;
2975 added a check to Makefile.am to make sure that we're building with
2976 Automake 1.7 or later.
2977 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
2978 because we built it with a too-old version of automake. Thus that
2979 release broke ./configure --enable-openbsd-malloc, which is popular
2980 among really fast exit relays on Linux.
2982 o Major bugfixes, new in 0.2.2.21-alpha:
2983 - Prevent crash/heap corruption when the cbtnummodes consensus
2984 parameter is set to 0 or large values. Fixes bug 2317; bugfix
2987 o Major features, new in 0.2.2.21-alpha:
2988 - Introduce minimum/maximum values that clients will believe
2989 from the consensus. Now we'll have a better chance to avoid crashes
2990 or worse when a consensus param has a weird value.
2992 o Minor features, new in 0.2.2.21-alpha:
2993 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
2994 used on bridges, and it makes bridge scanning somewhat easier.
2995 - If writing the state file to disk fails, wait up to an hour before
2996 retrying again, rather than trying again each second. Fixes bug
2997 2346; bugfix on Tor 0.1.1.3-alpha.
2998 - Make Libevent log messages get delivered to controllers later,
2999 and not from inside the Libevent log handler. This prevents unsafe
3000 reentrant Libevent calls while still letting the log messages
3002 - Detect platforms that brokenly use a signed size_t, and refuse to
3003 build there. Found and analyzed by doorss and rransom.
3004 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3007 o Minor bugfixes, new in 0.2.2.21-alpha:
3008 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3009 than waiting forever for them to finish. Fixes bug 2330; bugfix
3010 on 0.2.0.16-alpha. Found by doorss.
3011 - Add assertions to check for overflow in arguments to
3012 base32_encode() and base32_decode(); fix a signed-unsigned
3013 comparison there too. These bugs are not actually reachable in Tor,
3014 but it's good to prevent future errors too. Found by doorss.
3015 - Correctly detect failures to create DNS requests when using Libevent
3016 versions before v2. (Before Libevent 2, we used our own evdns
3017 implementation. Its return values for Libevent's evdns_resolve_*()
3018 functions are not consistent with those from Libevent.) Fixes bug
3019 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3021 o Documentation, new in 0.2.2.21-alpha:
3022 - Document the default socks host and port (127.0.0.1:9050) for
3026 Changes in version 0.2.1.29 - 2011-01-15
3027 Tor 0.2.1.29 continues our recent code security audit work. The main
3028 fix resolves a remote heap overflow vulnerability that can allow remote
3029 code execution. Other fixes address a variety of assert and crash bugs,
3030 most of which we think are hard to exploit remotely.
3032 o Major bugfixes (security):
3033 - Fix a heap overflow bug where an adversary could cause heap
3034 corruption. This bug probably allows remote code execution
3035 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3037 - Prevent a denial-of-service attack by disallowing any
3038 zlib-compressed data whose compression factor is implausibly
3039 high. Fixes part of bug 2324; reported by "doorss".
3040 - Zero out a few more keys in memory before freeing them. Fixes
3041 bug 2384 and part of bug 2385. These key instances found by
3042 "cypherpunks", based on Andrew Case's report about being able
3043 to find sensitive data in Tor's memory space if you have enough
3044 permissions. Bugfix on 0.0.2pre9.
3046 o Major bugfixes (crashes):
3047 - Prevent calls to Libevent from inside Libevent log handlers.
3048 This had potential to cause a nasty set of crashes, especially
3049 if running Libevent with debug logging enabled, and running
3050 Tor with a controller watching for low-severity log messages.
3051 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3052 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3053 underflow errors there too. Fixes the other part of bug 2324.
3054 - Fix a bug where we would assert if we ever had a
3055 cached-descriptors.new file (or another file read directly into
3056 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3057 on 0.2.1.25. Found by doorss.
3058 - Fix some potential asserts and parsing issues with grossly
3059 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3062 o Minor bugfixes (other):
3063 - Fix a bug with handling misformed replies to reverse DNS lookup
3064 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3065 bug reported by doorss.
3066 - Fix compilation on mingw when a pthreads compatibility library
3067 has been installed. (We don't want to use it, so we shouldn't
3068 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3069 - Fix a bug where we would declare that we had run out of virtual
3070 addresses when the address space was only half-exhausted. Bugfix
3072 - Correctly handle the case where AutomapHostsOnResolve is set but
3073 no virtual addresses are available. Fixes bug 2328; bugfix on
3074 0.1.2.1-alpha. Bug found by doorss.
3075 - Correctly handle wrapping around to when we run out of virtual
3076 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3077 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3078 because we built it with a too-old version of automake. Thus that
3079 release broke ./configure --enable-openbsd-malloc, which is popular
3080 among really fast exit relays on Linux.
3083 - Update to the January 1 2011 Maxmind GeoLite Country database.
3084 - Introduce output size checks on all of our decryption functions.
3087 - Tor does not build packages correctly with Automake 1.6 and earlier;
3088 added a check to Makefile.am to make sure that we're building with
3089 Automake 1.7 or later.
3092 Changes in version 0.2.2.20-alpha - 2010-12-17
3093 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3094 exploitable bugs. We also fix a variety of other significant bugs,
3095 change the IP address for one of our directory authorities, and update
3096 the minimum version that Tor relays must run to join the network.
3099 - Fix a remotely exploitable bug that could be used to crash instances
3100 of Tor remotely by overflowing on the heap. Remote-code execution
3101 hasn't been confirmed, but can't be ruled out. Everyone should
3102 upgrade. Bugfix on the 0.1.1 series and later.
3103 - Fix a bug that could break accounting on 64-bit systems with large
3104 time_t values, making them hibernate for impossibly long intervals.
3105 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3106 - Fix a logic error in directory_fetches_from_authorities() that
3107 would cause all _non_-exits refusing single-hop-like circuits
3108 to fetch from authorities, when we wanted to have _exits_ fetch
3109 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3111 - Fix a stream fairness bug that would cause newer streams on a given
3112 circuit to get preference when reading bytes from the origin or
3113 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3114 introduced before the first Tor release, in svn revision r152.
3116 o Directory authority changes:
3117 - Change IP address and ports for gabelmoo (v3 directory authority).
3120 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3121 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3122 - Fix an off-by-one error in calculating some controller command
3123 argument lengths. Fortunately, this mistake is harmless since
3124 the controller code does redundant NUL termination too. Found by
3125 boboper. Bugfix on 0.1.1.1-alpha.
3126 - Do not dereference NULL if a bridge fails to build its
3127 extra-info descriptor. Found by an anonymous commenter on
3128 Trac. Bugfix on 0.2.2.19-alpha.
3131 - Update to the December 1 2010 Maxmind GeoLite Country database.
3132 - Directory authorities now reject relays running any versions of
3133 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3134 known bugs that keep RELAY_EARLY cells from working on rendezvous
3135 circuits. Followup to fix for bug 2081.
3136 - Directory authorities now reject relays running any version of Tor
3137 older than 0.2.0.26-rc. That version is the earliest that fetches
3138 current directory information correctly. Fixes bug 2156.
3139 - Report only the top 10 ports in exit-port stats in order not to
3140 exceed the maximum extra-info descriptor length of 50 KB. Implements
3144 Changes in version 0.2.1.28 - 2010-12-17
3145 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3146 exploitable bugs. We also took this opportunity to change the IP address
3147 for one of our directory authorities, and to update the geoip database
3151 - Fix a remotely exploitable bug that could be used to crash instances
3152 of Tor remotely by overflowing on the heap. Remote-code execution
3153 hasn't been confirmed, but can't be ruled out. Everyone should
3154 upgrade. Bugfix on the 0.1.1 series and later.
3156 o Directory authority changes:
3157 - Change IP address and ports for gabelmoo (v3 directory authority).
3160 - Update to the December 1 2010 Maxmind GeoLite Country database.
3163 Changes in version 0.2.1.27 - 2010-11-23
3164 Yet another OpenSSL security patch broke its compatibility with Tor:
3165 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3166 also took this opportunity to fix several crash bugs, integrate a new
3167 directory authority, and update the bundled GeoIP database.
3170 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3171 No longer set the tlsext_host_name extension on server SSL objects;
3172 but continue to set it on client SSL objects. Our goal in setting
3173 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3174 bugfix on 0.2.1.1-alpha.
3175 - Do not log messages to the controller while shrinking buffer
3176 freelists. Doing so would sometimes make the controller connection
3177 try to allocate a buffer chunk, which would mess up the internals
3178 of the freelist and cause an assertion failure. Fixes bug 1125;
3179 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3180 - Learn our external IP address when we're a relay or bridge, even if
3181 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3182 where we introduced bridge relays that don't need to publish to
3183 be useful. Fixes bug 2050.
3184 - Do even more to reject (and not just ignore) annotations on
3185 router descriptors received anywhere but from the cache. Previously
3186 we would ignore such annotations at first, but cache them to disk
3187 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3188 - When you're using bridges and your network goes away and your
3189 bridges get marked as down, recover when you attempt a new socks
3190 connection (if the network is back), rather than waiting up to an
3191 hour to try fetching new descriptors for your bridges. Bugfix on
3192 0.2.0.3-alpha; fixes bug 1981.
3195 - Move to the November 2010 Maxmind GeoLite country db (rather
3196 than the June 2009 ip-to-country GeoIP db) for our statistics that
3197 count how many users relays are seeing from each country. Now we'll
3198 have more accurate data, especially for many African countries.
3200 o New directory authorities:
3201 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3205 - Fix an assertion failure that could occur in directory caches or
3206 bridge users when using a very short voting interval on a testing
3207 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3209 - Enforce multiplicity rules when parsing annotations. Bugfix on
3210 0.2.0.8-alpha. Found by piebeer.
3211 - Allow handshaking OR connections to take a full KeepalivePeriod
3212 seconds to handshake. Previously, we would close them after
3213 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3214 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3216 - When building with --enable-gcc-warnings on OpenBSD, disable
3217 warnings in system headers. This makes --enable-gcc-warnings
3218 pass on OpenBSD 4.8.
3221 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3222 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3223 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3224 Servers can start sending this code when enough clients recognize
3225 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3226 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3227 Patch from mingw-san.
3230 - Remove the old debian/ directory from the main Tor distribution.
3231 The official Tor-for-debian git repository lives at the URL
3232 https://git.torproject.org/debian/tor.git
3233 - Stop shipping the old doc/website/ directory in the tarball. We
3234 changed the website format in late 2010, and what we shipped in
3235 0.2.1.26 really wasn't that useful anyway.
3238 Changes in version 0.2.2.19-alpha - 2010-11-22
3239 Yet another OpenSSL security patch broke its compatibility with Tor:
3240 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
3243 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3244 No longer set the tlsext_host_name extension on server SSL objects;
3245 but continue to set it on client SSL objects. Our goal in setting
3246 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3247 bugfix on 0.2.1.1-alpha.
3250 - Try harder not to exceed the maximum length of 50 KB when writing
3251 statistics to extra-info descriptors. This bug was triggered by very
3252 fast relays reporting exit-port, entry, and dirreq statistics.
3253 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
3254 - Publish a router descriptor even if generating an extra-info
3255 descriptor fails. Previously we would not publish a router
3256 descriptor without an extra-info descriptor; this can cause fast
3257 exit relays collecting exit-port statistics to drop from the
3258 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3261 Changes in version 0.2.2.18-alpha - 2010-11-16
3262 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
3263 us lately, makes unpublished bridge relays able to detect their IP
3264 address, and fixes a wide variety of other bugs to get us much closer
3265 to a stable release.
3268 - Do even more to reject (and not just ignore) annotations on
3269 router descriptors received anywhere but from the cache. Previously
3270 we would ignore such annotations at first, but cache them to disk
3271 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3272 - Do not log messages to the controller while shrinking buffer
3273 freelists. Doing so would sometimes make the controller connection
3274 try to allocate a buffer chunk, which would mess up the internals
3275 of the freelist and cause an assertion failure. Fixes bug 1125;
3276 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3277 - Learn our external IP address when we're a relay or bridge, even if
3278 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3279 where we introduced bridge relays that don't need to publish to
3280 be useful. Fixes bug 2050.
3281 - Maintain separate TLS contexts and certificates for incoming and
3282 outgoing connections in bridge relays. Previously we would use the
3283 same TLS contexts and certs for incoming and outgoing connections.
3284 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3285 - Maintain separate identity keys for incoming and outgoing TLS
3286 contexts in bridge relays. Previously we would use the same
3287 identity keys for incoming and outgoing TLS contexts. Bugfix on
3288 0.2.0.3-alpha; addresses the other half of bug 988.
3289 - Avoid an assertion failure when we as an authority receive a
3290 duplicate upload of a router descriptor that we already have,
3291 but which we previously considered an obsolete descriptor.
3292 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
3293 - Avoid a crash bug triggered by looking at a dangling pointer while
3294 setting the network status consensus. Found by Robert Ransom.
3295 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
3296 - Fix a logic error where servers that _didn't_ act as exits would
3297 try to keep their server lists more aggressively up to date than
3298 exits, when it was supposed to be the other way around. Bugfix
3301 o Minor bugfixes (on Tor 0.2.1.x and earlier):
3302 - When we're trying to guess whether we know our IP address as
3303 a relay, we would log various ways that we failed to guess
3304 our address, but never log that we ended up guessing it
3305 successfully. Now add a log line to help confused and anxious
3306 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3307 - Bring the logic that gathers routerinfos and assesses the
3308 acceptability of circuits into line. This prevents a Tor OP from
3309 getting locked in a cycle of choosing its local OR as an exit for a
3310 path (due to a .exit request) and then rejecting the circuit because
3311 its OR is not listed yet. It also prevents Tor clients from using an
3312 OR running in the same instance as an exit (due to a .exit request)
3313 if the OR does not meet the same requirements expected of an OR
3314 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3315 - Correctly describe errors that occur when generating a TLS object.
3316 Previously we would attribute them to a failure while generating a
3317 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3319 - Enforce multiplicity rules when parsing annotations. Bugfix on
3320 0.2.0.8-alpha. Found by piebeer.
3321 - Fix warnings that newer versions of autoconf produced during
3322 ./autogen.sh. These warnings appear to be harmless in our case,
3323 but they were extremely verbose. Fixes bug 2020.
3325 o Minor bugfixes (on Tor 0.2.2.x):
3326 - Enable protection of small arrays whenever we build with gcc
3327 hardening features, not only when also building with warnings
3328 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
3331 - Make hidden services work better in private Tor networks by not
3332 requiring any uptime to join the hidden service descriptor
3333 DHT. Implements ticket 2088.
3334 - Rate-limit the "your application is giving Tor only an IP address"
3335 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3336 - When AllowSingleHopExits is set, print a warning to explain to the
3337 relay operator why most clients are avoiding her relay.
3338 - Update to the November 1 2010 Maxmind GeoLite Country database.
3340 o Code simplifications and refactoring:
3341 - When we fixed bug 1038 we had to put in a restriction not to send
3342 RELAY_EARLY cells on rend circuits. This was necessary as long
3343 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3344 active. Now remove this obsolete check. Resolves bug 2081.
3345 - Some options used different conventions for uppercasing of acronyms
3346 when comparing manpage and source. Fix those in favor of the
3347 manpage, as it makes sense to capitalize acronyms.
3348 - Remove the torrc.complete file. It hasn't been kept up to date
3349 and users will have better luck checking out the manpage.
3350 - Remove the obsolete "NoPublish" option; it has been flagged
3351 as obsolete and has produced a warning since 0.1.1.18-rc.
3352 - Remove everything related to building the expert bundle for OS X.
3353 It has confused many users, doesn't work right on OS X 10.6,
3354 and is hard to get rid of once installed. Resolves bug 1274.
3357 Changes in version 0.2.2.17-alpha - 2010-09-30
3358 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
3359 to use one-hop circuits (which can put the exit relays at higher risk,
3360 plus unbalance the network); fixes a big bug in bandwidth accounting
3361 for relays that want to limit their monthly bandwidth use; fixes a
3362 big pile of bugs in how clients tolerate temporary network failure;
3363 and makes our adaptive circuit build timeout feature (which improves
3364 client performance if your network is fast while not breaking things
3365 if your network is slow) better handle bad networks.
3368 - Exit relays now try harder to block exit attempts from unknown
3369 relays, to make it harder for people to use them as one-hop proxies
3370 a la tortunnel. Controlled by the refuseunknownexits consensus
3371 parameter (currently enabled), or you can override it on your
3372 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
3374 o Major bugfixes (0.2.1.x and earlier):
3375 - Fix a bug in bandwidth accounting that could make us use twice
3376 the intended bandwidth when our interval start changes due to
3377 daylight saving time. Now we tolerate skew in stored vs computed
3378 interval starts: if the start of the period changes by no more than
3379 50% of the period's duration, we remember bytes that we transferred
3380 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3381 - Always search the Windows system directory for system DLLs, and
3382 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
3383 - When you're using bridges and your network goes away and your
3384 bridges get marked as down, recover when you attempt a new socks
3385 connection (if the network is back), rather than waiting up to an
3386 hour to try fetching new descriptors for your bridges. Bugfix on
3387 0.2.0.3-alpha; fixes bug 1981.
3389 o Major bugfixes (on 0.2.2.x):
3390 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
3392 - Fix a segfault that could happen when operating a bridge relay with
3393 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
3394 - The consensus bandwidth-weights (used by clients to choose fast
3395 relays) entered an unexpected edge case in September where
3396 Exits were much scarcer than Guards, resulting in bad weight
3397 recommendations. Now we compute them using new constraints that
3398 should succeed in all cases. Also alter directory authorities to
3399 not include the bandwidth-weights line if they fail to produce
3400 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
3401 - When weighting bridges during path selection, we used to trust
3402 the bandwidths they provided in their descriptor, only capping them
3403 at 10MB/s. This turned out to be problematic for two reasons:
3404 Bridges could claim to handle a lot more traffic then they
3405 actually would, thus making more clients pick them and have a
3406 pretty effective DoS attack. The other issue is that new bridges
3407 that might not have a good estimate for their bw capacity yet
3408 would not get used at all unless no other bridges are available
3409 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
3411 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
3412 - Ignore cannibalized circuits when recording circuit build times.
3413 This should provide for a minor performance improvement for hidden
3414 service users using 0.2.2.14-alpha, and should remove two spurious
3415 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
3416 - Simplify the logic that causes us to decide if the network is
3417 unavailable for purposes of recording circuit build times. If we
3418 receive no cells whatsoever for the entire duration of a circuit's
3419 full measured lifetime, the network is probably down. Also ignore
3420 one-hop directory fetching circuit timeouts when calculating our
3421 circuit build times. These changes should hopefully reduce the
3422 cases where we see ridiculous circuit build timeouts for people
3423 with spotty wireless connections. Fixes part of bug 1772; bugfix
3425 - Prevent the circuit build timeout from becoming larger than
3426 the maximum build time we have ever seen. Also, prevent the time
3427 period for measurement circuits from becoming larger than twice that
3428 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
3431 - When we run out of directory information such that we can't build
3432 circuits, but then get enough that we can build circuits, log when
3433 we actually construct a circuit, so the user has a better chance of
3434 knowing what's going on. Fixes bug 1362.
3435 - Be more generous with how much bandwidth we'd use up (with
3436 accounting enabled) before entering "soft hibernation". Previously,
3437 we'd refuse new connections and circuits once we'd used up 95% of
3438 our allotment. Now, we use up 95% of our allotment, AND make sure
3439 that we have no more than 500MB (or 3 hours of expected traffic,
3440 whichever is lower) remaining before we enter soft hibernation.
3441 - If we've configured EntryNodes and our network goes away and/or all
3442 our entrynodes get marked down, optimistically retry them all when
3443 a new socks application request appears. Fixes bug 1882.
3444 - Add some more defensive programming for architectures that can't
3445 handle unaligned integer accesses. We don't know of any actual bugs
3446 right now, but that's the best time to fix them. Fixes bug 1943.
3447 - Support line continuations in the torrc config file. If a line
3448 ends with a single backslash character, the newline is ignored, and
3449 the configuration value is treated as continuing on the next line.
3452 o Minor bugfixes (on 0.2.1.x and earlier):
3453 - For bandwidth accounting, calculate our expected bandwidth rate
3454 based on the time during which we were active and not in
3455 soft-hibernation during the last interval. Previously, we were
3456 also considering the time spent in soft-hibernation. If this
3457 was a long time, we would wind up underestimating our bandwidth
3458 by a lot, and skewing our wakeup time towards the start of the
3459 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3461 o Minor bugfixes (on 0.2.2.x):
3462 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
3463 which were disabled by the circuit build timeout changes in
3464 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
3465 - Make sure we don't warn about missing bandwidth weights when
3466 choosing bridges or other relays not in the consensus. Bugfix on
3467 0.2.2.10-alpha; fixes bug 1805.
3468 - In our logs, do not double-report signatures from unrecognized
3469 authorities both as "from unknown authority" and "not
3470 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
3473 Changes in version 0.2.2.16-alpha - 2010-09-17
3474 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
3475 evident at exit relays), and also continues to resolve all the little
3476 bugs that have been filling up trac lately.
3478 o Major bugfixes (stream-level fairness):
3479 - When receiving a circuit-level SENDME for a blocked circuit, try
3480 to package cells fairly from all the streams that had previously
3481 been blocked on that circuit. Previously, we had started with the
3482 oldest stream, and allowed each stream to potentially exhaust
3483 the circuit's package window. This gave older streams on any
3484 given circuit priority over newer ones. Fixes bug 1937. Detected
3485 originally by Camilo Viecco. This bug was introduced before the
3486 first Tor release, in svn commit r152: it is the new winner of
3487 the longest-lived bug prize.
3488 - When the exit relay got a circuit-level sendme cell, it started
3489 reading on the exit streams, even if had 500 cells queued in the
3490 circuit queue already, so the circuit queue just grew and grew in
3491 some cases. We fix this by not re-enabling reading on receipt of a
3492 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3493 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3495 - Newly created streams were allowed to read cells onto circuits,
3496 even if the circuit's cell queue was blocked and waiting to drain.
3497 This created potential unfairness, as older streams would be
3498 blocked, but newer streams would gladly fill the queue completely.
3499 We add code to detect this situation and prevent any stream from
3500 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3504 - Update to the September 1 2010 Maxmind GeoLite Country database.
3505 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3506 not. This would lead to a cookie that is still not group readable.
3507 Closes bug 1843. Suggested by katmagic.
3508 - When logging a rate-limited warning, we now mention how many messages
3509 got suppressed since the last warning.
3510 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3511 do individual connection-level rate limiting of clients. The torrc
3512 config options with the same names trump the consensus params, if
3513 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3514 consensus params which were broken from 0.2.2.7-alpha through
3515 0.2.2.14-alpha. Closes bug 1947.
3516 - When a router changes IP address or port, authorities now launch
3517 a new reachability test for it. Implements ticket 1899.
3518 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3519 2 no signature, 4 required" messages about consensus signatures
3520 easier to read, and make sure they get logged at the same severity
3521 as the messages explaining which keys are which. Fixes bug 1290.
3522 - Don't warn when we have a consensus that we can't verify because
3523 of missing certificates, unless those certificates are ones
3524 that we have been trying and failing to download. Fixes bug 1145.
3525 - If you configure your bridge with a known identity fingerprint,
3526 and the bridge authority is unreachable (as it is in at least
3527 one country now), fall back to directly requesting the descriptor
3528 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
3530 - When building with --enable-gcc-warnings on OpenBSD, disable
3531 warnings in system headers. This makes --enable-gcc-warnings
3532 pass on OpenBSD 4.8.
3534 o Minor bugfixes (on 0.2.1.x and earlier):
3535 - Authorities will now attempt to download consensuses if their
3536 own efforts to make a live consensus have failed. This change
3537 means authorities that restart will fetch a valid consensus, and
3538 it means authorities that didn't agree with the current consensus
3539 will still fetch and serve it if it has enough signatures. Bugfix
3540 on 0.2.0.9-alpha; fixes bug 1300.
3541 - Ensure DNS requests launched by "RESOLVE" commands from the
3542 controller respect the __LeaveStreamsUnattached setconf options. The
3543 same goes for requests launched via DNSPort or transparent
3544 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
3545 - Allow handshaking OR connections to take a full KeepalivePeriod
3546 seconds to handshake. Previously, we would close them after
3547 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3548 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3550 - Rate-limit "Failed to hand off onionskin" warnings.
3551 - Never relay a cell for a circuit we have already destroyed.
3552 Between marking a circuit as closeable and finally closing it,
3553 it may have been possible for a few queued cells to get relayed,
3554 even though they would have been immediately dropped by the next
3555 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
3556 - Never queue a cell for a circuit that's already been marked
3558 - Never vote for a server as "Running" if we have a descriptor for
3559 it claiming to be hibernating, and that descriptor was published
3560 more recently than our last contact with the server. Bugfix on
3561 0.2.0.3-alpha; fixes bug 911.
3562 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
3565 o Minor bugfixes (on 0.2.2.x):
3566 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
3567 down if a directory fetch fails and you've configured either
3568 bridges or EntryNodes. The intent was to mark the relay as down
3569 _unless_ you're using bridges or EntryNodes, since if you are
3570 then you could quickly run out of entry points.
3571 - Fix the Windows directory-listing code. A bug introduced in
3572 0.2.2.14-alpha could make Windows directory servers forget to load
3573 some of their cached v2 networkstatus files.
3574 - Really allow clients to use relays as bridges. Fixes bug 1776;
3575 bugfix on 0.2.2.15-alpha.
3576 - Demote a warn to info that happens when the CellStatistics option
3577 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
3578 Reported by Moritz Bartl.
3579 - On Windows, build correctly either with or without Unicode support.
3580 This is necessary so that Tor can support fringe platforms like
3581 Windows 98 (which has no Unicode), or Windows CE (which has no
3582 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
3585 - Add a unit test for cross-platform directory-listing code.
3588 Changes in version 0.2.2.15-alpha - 2010-08-18
3589 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
3590 fixes a variety of other bugs that were preventing performance
3591 experiments from moving forward, fixes several bothersome memory leaks,
3592 and generally closes a lot of smaller bugs that have been filling up
3596 - Stop assigning the HSDir flag to relays that disable their
3597 DirPort (and thus will refuse to answer directory requests). This
3598 fix should dramatically improve the reachability of hidden services:
3599 hidden services and hidden service clients pick six HSDir relays
3600 to store and retrieve the hidden service descriptor, and currently
3601 about half of the HSDir relays will refuse to work. Bugfix on
3602 0.2.0.10-alpha; fixes part of bug 1693.
3603 - The PerConnBWRate and Burst config options, along with the
3604 bwconnrate and bwconnburst consensus params, initialized each conn's
3605 token bucket values only when the connection is established. Now we
3606 update them if the config options change, and update them every time
3607 we get a new consensus. Otherwise we can encounter an ugly edge
3608 case where we initialize an OR conn to client-level bandwidth,
3609 but then later the relay joins the consensus and we leave it
3610 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
3611 - Fix a regression that caused Tor to rebind its ports if it receives
3612 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3615 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
3616 should give us approximately 40-50% more Guard-flagged nodes,
3617 improving the anonymity the Tor network can provide and also
3618 decreasing the dropoff in throughput that relays experience when
3619 they first get the Guard flag.
3620 - Allow enabling or disabling the *Statistics config options while
3624 - Update to the August 1 2010 Maxmind GeoLite Country database.
3625 - Have the controller interface give a more useful message than
3626 "Internal Error" in response to failed GETINFO requests.
3627 - Warn when the same option is provided more than once in a torrc
3628 file, on the command line, or in a single SETCONF statement, and
3629 the option is one that only accepts a single line. Closes bug 1384.
3630 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3631 Patch from mingw-san.
3632 - Add support for the country code "{??}" in torrc options like
3633 ExcludeNodes, to indicate all routers of unknown country. Closes
3635 - Relays report the number of bytes spent on answering directory
3636 requests in extra-info descriptors similar to {read,write}-history.
3637 Implements enhancement 1790.
3639 o Minor bugfixes (on 0.2.1.x and earlier):
3640 - Complain if PublishServerDescriptor is given multiple arguments that
3641 include 0 or 1. This configuration will be rejected in the future.
3642 Bugfix on 0.2.0.1-alpha; closes bug 1107.
3643 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
3644 Bugfix on 0.2.0.13-alpha; closes bug 928.
3645 - Change "Application request when we're believed to be offline."
3646 notice to "Application request when we haven't used client
3647 functionality lately.", to clarify that it's not an error. Bugfix
3648 on 0.0.9.3; fixes bug 1222.
3649 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
3650 would return "551 Internal error" rather than "552 Unrecognized key
3651 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
3652 - Users can't configure a regular relay to be their bridge. It didn't
3653 work because when Tor fetched the bridge descriptor, it found
3654 that it already had it, and didn't realize that the purpose of the
3655 descriptor had changed. Now we replace routers with a purpose other
3656 than bridge with bridge descriptors when fetching them. Bugfix on
3657 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
3658 refetch the descriptor with router purpose 'general', disabling
3660 - Fix a rare bug in rend_fn unit tests: we would fail a test when
3661 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
3662 on 0.2.0.10-alpha; fixes bug 1808.
3663 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3664 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3665 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3666 Servers can start sending this code when enough clients recognize
3667 it. Also update the spec to reflect this new reason. Bugfix on
3668 0.1.0.1-rc; fixes part of bug 1793.
3669 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
3670 when we switch from being a public relay to a bridge. Otherwise
3671 there will still be clients that see the relay in their consensus,
3672 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
3674 - Instead of giving an assertion failure on an internal mismatch
3675 on estimated freelist size, just log a BUG warning and try later.
3676 Mitigates but does not fix bug 1125.
3677 - Fix an assertion failure that could occur in caches or bridge users
3678 when using a very short voting interval on a testing network.
3679 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
3681 o Minor bugfixes (on 0.2.2.x):
3682 - Alter directory authorities to always consider Exit-flagged nodes
3683 as potential Guard nodes in their votes. The actual decision to
3684 use Exits as Guards is done in the consensus bandwidth weights.
3685 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
3686 - When the controller is reporting the purpose of circuits that
3687 didn't finish building before the circuit build timeout, it was
3688 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
3689 - Our libevent version parsing code couldn't handle versions like
3690 1.4.14b-stable and incorrectly warned the user about using an
3691 old and broken version of libevent. Treat 1.4.14b-stable like
3692 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
3694 - Don't use substitution references like $(VAR:MOD) when
3695 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
3696 '$(:x)' to 'x' rather than the empty string. This bites us in
3697 doc/ when configured with --disable-asciidoc. Bugfix on
3698 0.2.2.9-alpha; fixes bug 1773.
3699 - Remove a spurious hidden service server-side log notice about
3700 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
3702 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
3704 - Correctly report written bytes on linked connections. Found while
3705 implementing 1790. Bugfix on 0.2.2.4-alpha.
3706 - Fix three memory leaks: one in circuit_build_times_parse_state(),
3707 one in dirvote_add_signatures_to_pending_consensus(), and one every
3708 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
3709 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
3711 o Code simplifications and refactoring:
3712 - Take a first step towards making or.h smaller by splitting out
3713 function definitions for all source files in src/or/. Leave
3714 structures and defines in or.h for now.
3715 - Remove a bunch of unused function declarations as well as a block of
3716 #if 0'd code from the unit tests. Closes bug 1824.
3717 - New unit tests for exit-port history statistics; refactored exit
3718 statistics code to be more easily tested.
3719 - Remove the old debian/ directory from the main Tor distribution.
3720 The official Tor-for-debian git repository lives at the URL
3721 https://git.torproject.org/debian/tor.git
3724 Changes in version 0.2.2.14-alpha - 2010-07-12
3725 Tor 0.2.2.14-alpha greatly improves client-side handling of
3726 circuit build timeouts, which are used to estimate speed and improve
3727 performance. We also move to a much better GeoIP database, port Tor to
3728 Windows CE, introduce new compile flags that improve code security,
3729 add an eighth v3 directory authority, and address a lot of more
3733 - Tor directory authorities no longer crash when started with a
3734 cached-microdesc-consensus file in their data directory. Bugfix
3735 on 0.2.2.6-alpha; fixes bug 1532.
3736 - Treat an unset $HOME like an empty $HOME rather than triggering an
3737 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
3738 - Ignore negative and large circuit build timeout values that can
3739 happen during a suspend or hibernate. These values caused various
3740 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
3741 - Alter calculation of Pareto distribution parameter 'Xm' for
3742 Circuit Build Timeout learning to use the weighted average of the
3743 top N=3 modes (because we have three entry guards). Considering
3744 multiple modes should improve the timeout calculation in some cases,
3745 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
3747 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
3748 right censored distribution model. This approach improves over the
3749 synthetic timeout generation approach that was producing insanely
3750 high timeout values. Now we calculate build timeouts using truncated
3751 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
3752 - Do not close circuits that are under construction when they reach
3753 the circuit build timeout. Instead, leave them building (but do not
3754 use them) for up until the time corresponding to the 95th percentile
3755 on the Pareto CDF or 60 seconds, whichever is greater. This is done
3756 to provide better data for the new Pareto model. This percentile
3757 can be controlled by the consensus.
3760 - Move to the June 2010 Maxmind GeoLite country db (rather than the
3761 June 2009 ip-to-country GeoIP db) for our statistics that count
3762 how many users relays are seeing from each country. Now we have
3763 more accurate data for many African countries.
3764 - Port Tor to build and run correctly on Windows CE systems, using
3765 the wcecompat library. Contributed by Valerio Lupi.
3766 - New "--enable-gcc-hardening" ./configure flag (off by default)
3767 to turn on gcc compile time hardening options. It ensures
3768 that signed ints have defined behavior (-fwrapv), enables
3769 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
3770 with canaries (-fstack-protector-all), turns on ASLR protection if
3771 supported by the kernel (-fPIE, -pie), and adds additional security
3772 related warnings. Verified to work on Mac OS X and Debian Lenny.
3773 - New "--enable-linker-hardening" ./configure flag (off by default)
3774 to turn on ELF specific hardening features (relro, now). This does
3775 not work with Mac OS X or any other non-ELF binary format.
3777 o New directory authorities:
3778 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3782 - New config option "WarnUnsafeSocks 0" disables the warning that
3783 occurs whenever Tor receives a socks handshake using a version of
3784 the socks protocol that can only provide an IP address (rather
3785 than a hostname). Setups that do DNS locally over Tor are fine,
3786 and we shouldn't spam the logs in that case.
3787 - Convert the HACKING file to asciidoc, and add a few new sections
3788 to it, explaining how we use Git, how we make changelogs, and
3789 what should go in a patch.
3790 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
3791 event, to give information on the current rate of circuit timeouts
3792 over our stored history.
3793 - Add ability to disable circuit build time learning via consensus
3794 parameter and via a LearnCircuitBuildTimeout config option. Also
3795 automatically disable circuit build time calculation if we are
3796 either a AuthoritativeDirectory, or if we fail to write our state
3797 file. Fixes bug 1296.
3798 - More gracefully handle corrupt state files, removing asserts
3799 in favor of saving a backup and resetting state.
3800 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
3804 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3806 - When a2x fails, mention that the user could disable manpages instead
3807 of trying to fix their asciidoc installation.
3808 - Where available, use Libevent 2.0's periodic timers so that our
3809 once-per-second cleanup code gets called even more closely to
3810 once per second than it would otherwise. Fixes bug 943.
3811 - If you run a bridge that listens on multiple IP addresses, and
3812 some user configures a bridge address that uses a different IP
3813 address than your bridge writes in its router descriptor, and the
3814 user doesn't specify an identity key, their Tor would discard the
3815 descriptor because "it isn't one of our configured bridges", and
3816 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
3817 Bugfix on 0.2.0.3-alpha.
3818 - If OpenSSL fails to make a duplicate of a private or public key, log
3819 an error message and try to exit cleanly. May help with debugging
3820 if bug 1209 ever remanifests.
3821 - Save a couple bytes in memory allocation every time we escape
3822 certain characters in a string. Patch from Florian Zumbiehl.
3823 - Make it explicit that we don't cannibalize one-hop circuits. This
3824 happens in the wild, but doesn't turn out to be a problem because
3825 we fortunately don't use those circuits. Many thanks to outofwords
3826 for the initial analysis and to swissknife who confirmed that
3827 two-hop circuits are actually created.
3828 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
3829 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
3830 - Eliminate a case where a circuit build time warning was displayed
3831 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
3834 Changes in version 0.2.1.26 - 2010-05-02
3835 Tor 0.2.1.26 addresses the recent connection and memory overload
3836 problems we've been seeing on relays, especially relays with their
3837 DirPort open. If your relay has been crashing, or you turned it off
3838 because it used too many resources, give this release a try.
3840 This release also fixes yet another instance of broken OpenSSL libraries
3841 that was causing some relays to drop out of the consensus.
3844 - Teach relays to defend themselves from connection overload. Relays
3845 now close idle circuits early if it looks like they were intended
3846 for directory fetches. Relays are also more aggressive about closing
3847 TLS connections that have no circuits on them. Such circuits are
3848 unlikely to be re-used, and tens of thousands of them were piling
3849 up at the fast relays, causing the relays to run out of sockets
3850 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3851 their directory fetches over TLS).
3852 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3853 that claim to be earlier than 0.9.8m, but which have in reality
3854 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3855 behavior. Possible fix for some cases of bug 1346.
3856 - Directory mirrors were fetching relay descriptors only from v2
3857 directory authorities, rather than v3 authorities like they should.
3858 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3859 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3862 - Finally get rid of the deprecated and now harmful notion of "clique
3863 mode", where directory authorities maintain TLS connections to
3867 - In the util/threads test, no longer free the test_mutex before all
3868 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3869 - The master thread could starve the worker threads quite badly on
3870 certain systems, causing them to run only partially in the allowed
3871 window. This resulted in test failures. Now the master thread sleeps
3872 occasionally for a few microseconds while the two worker-threads
3873 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3876 Changes in version 0.2.2.13-alpha - 2010-04-24
3877 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
3878 problems we've been seeing on relays, especially relays with their
3879 DirPort open. If your relay has been crashing, or you turned it off
3880 because it used too many resources, give this release a try.
3883 - Teach relays to defend themselves from connection overload. Relays
3884 now close idle circuits early if it looks like they were intended
3885 for directory fetches. Relays are also more aggressive about closing
3886 TLS connections that have no circuits on them. Such circuits are
3887 unlikely to be re-used, and tens of thousands of them were piling
3888 up at the fast relays, causing the relays to run out of sockets
3889 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3890 their directory fetches over TLS).
3893 - Finally get rid of the deprecated and now harmful notion of "clique
3894 mode", where directory authorities maintain TLS connections to
3896 - Directory authorities now do an immediate reachability check as soon
3897 as they hear about a new relay. This change should slightly reduce
3898 the time between setting up a relay and getting listed as running
3899 in the consensus. It should also improve the time between setting
3900 up a bridge and seeing use by bridge users.
3901 - Directory authorities no longer launch a TLS connection to every
3902 relay as they startup. Now that we have 2k+ descriptors cached,
3903 the resulting network hiccup is becoming a burden. Besides,
3904 authorities already avoid voting about Running for the first half
3905 hour of their uptime.
3908 Changes in version 0.2.2.12-alpha - 2010-04-20
3909 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
3910 handle and vote on descriptors. It was causing relays to drop out of
3914 - Many relays have been falling out of the consensus lately because
3915 not enough authorities know about their descriptor for them to get
3916 a majority of votes. When we deprecated the v2 directory protocol,
3917 we got rid of the only way that v3 authorities can hear from each
3918 other about other descriptors. Now authorities examine every v3
3919 vote for new descriptors, and fetch them from that authority. Bugfix
3921 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
3922 and a warning in or.h related to bandwidth_weight_rule_t that
3923 prevented clean compile on OS X. Fixes bug 1363; bugfix on
3925 - Fix a segfault on relays when DirReqStatistics is enabled
3926 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
3930 - Demote a confusing TLS warning that relay operators might get when
3931 someone tries to talk to their OrPort. It is neither the operator's
3932 fault nor can they do anything about it. Fixes bug 1364; bugfix
3936 Changes in version 0.2.2.11-alpha - 2010-04-15
3937 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
3938 libraries that was causing some relays to drop out of the consensus.
3941 - Directory mirrors were fetching relay descriptors only from v2
3942 directory authorities, rather than v3 authorities like they should.
3943 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3944 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3945 - Fix a parsing error that made every possible value of
3946 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
3947 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
3948 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
3949 about the option without breaking older ones.
3950 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3951 that claim to be earlier than 0.9.8m, but which have in reality
3952 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3953 behavior. Possible fix for some cases of bug 1346.
3956 - Experiment with a more aggressive approach to preventing clients
3957 from making one-hop exit streams. Exit relays who want to try it
3958 out can set "RefuseUnknownExits 1" in their torrc, and then look
3959 for "Attempt by %s to open a stream" log messages. Let us know
3961 - Add support for statically linking zlib by specifying
3962 --enable-static-zlib, to go with our support for statically linking
3963 openssl and libevent. Resolves bug 1358.
3966 - Fix a segfault that happens whenever a Tor client that is using
3967 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
3969 - When we cleaned up the contrib/tor-exit-notice.html file, we left
3970 out the first line. Fixes bug 1295.
3971 - When building the manpage from a tarball, we required asciidoc, but
3972 the asciidoc -> roff/html conversion was already done for the
3973 tarball. Make 'make' complain only when we need asciidoc (either
3974 because we're compiling directly from git, or because we altered
3975 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
3976 - When none of the directory authorities vote on any params, Tor
3977 segfaulted when trying to make the consensus from the votes. We
3978 didn't trigger the bug in practice, because authorities do include
3979 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
3982 - In the util/threads test, no longer free the test_mutex before all
3983 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3984 - The master thread could starve the worker threads quite badly on
3985 certain systems, causing them to run only partially in the allowed
3986 window. This resulted in test failures. Now the master thread sleeps
3987 occasionally for a few microseconds while the two worker-threads
3988 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3991 Changes in version 0.2.2.10-alpha - 2010-03-07
3992 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
3993 could prevent relays from guessing their IP address correctly. It also
3994 starts the groundwork for another client-side performance boost, since
3995 currently we're not making efficient use of relays that have both the
3996 Guard flag and the Exit flag.
3999 - Fix a regression from our patch for bug 1244 that caused relays
4000 to guess their IP address incorrectly if they didn't set Address
4001 in their torrc and/or their address fails to resolve. Bugfix on
4002 0.2.2.9-alpha; fixes bug 1269.
4004 o Major features (performance):
4005 - Directory authorities now compute consensus weightings that instruct
4006 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4007 and no flag. Clients that use these weightings will distribute
4008 network load more evenly across these different relay types. The
4009 weightings are in the consensus so we can change them globally in
4010 the future. Extra thanks to "outofwords" for finding some nasty
4011 security bugs in the first implementation of this feature.
4013 o Minor features (performance):
4014 - Always perform router selections using weighted relay bandwidth,
4015 even if we don't need a high capacity circuit at the time. Non-fast
4016 circuits now only differ from fast ones in that they can use relays
4017 not marked with the Fast flag. This "feature" could turn out to
4018 be a horrible bug; we should investigate more before it goes into
4022 - Allow disabling building of the manpages. Skipping the manpage
4023 speeds up the build considerably.
4025 o Minor bugfixes (on 0.2.2.x):
4026 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4027 Bugfix on 0.2.2.9-alpha.
4028 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4029 config option. Bugfix on 0.2.2.7-alpha.
4030 - Ship the asciidoc-helper file in the tarball, so that people can
4031 build from source if they want to, and touching the .1.txt files
4032 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4034 o Minor bugfixes (on 0.2.1.x or earlier):
4035 - Fix a dereference-then-NULL-check sequence when publishing
4036 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4038 - Fix another dereference-then-NULL-check sequence. Bugfix on
4039 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4040 - Make sure we treat potentially not NUL-terminated strings correctly.
4041 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4043 o Code simplifications and refactoring:
4044 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4045 compliant. Based on a patch from Christian Kujau.
4046 - Don't use sed in asciidoc-helper anymore.
4047 - Make the build process fail if asciidoc cannot be found and
4048 building with asciidoc isn't disabled.
4051 Changes in version 0.2.2.9-alpha - 2010-02-22
4052 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4053 location of a directory authority, and cleans up a bunch of small bugs.
4055 o Directory authority changes:
4056 - Change IP address for dannenberg (v3 directory authority), and
4057 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4058 service directory authority) from the list.
4061 - Make Tor work again on the latest OS X: when deciding whether to
4062 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4063 version at run-time, not compile time. We need to do this because
4064 Apple doesn't update its dev-tools headers when it updates its
4065 libraries in a security patch.
4066 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4067 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4068 a memory leak when requesting a hidden service descriptor we've
4069 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4071 - Authorities could be tricked into giving out the Exit flag to relays
4072 that didn't allow exiting to any ports. This bug could screw
4073 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4074 1238. Bug discovered by Martin Kowalczyk.
4075 - When freeing a session key, zero it out completely. We only zeroed
4076 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4077 patched by ekir. Fixes bug 1254.
4080 - Fix static compilation by listing the openssl libraries in the right
4081 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4082 - Resume handling .exit hostnames in a special way: originally we
4083 stripped the .exit part and used the requested exit relay. In
4084 0.2.2.1-alpha we stopped treating them in any special way, meaning
4085 if you use a .exit address then Tor will pass it on to the exit
4086 relay. Now we reject the .exit stream outright, since that behavior
4087 might be more expected by the user. Found and diagnosed by Scott
4088 Bennett and Downie on or-talk.
4089 - Don't spam the controller with events when we have no file
4090 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4091 for log messages was already solved from bug 748.)
4092 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4094 - Make the DNSPort option work with libevent 2.x. Don't alter the
4095 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4096 - Emit a GUARD DROPPED controller event for a case we missed.
4097 - Make more fields in the controller protocol case-insensitive, since
4098 control-spec.txt said they were.
4099 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4100 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4101 - Fix a spec conformance issue: the network-status-version token
4102 must be the first token in a v3 consensus or vote. Discovered by
4103 parakeep. Bugfix on 0.2.0.3-alpha.
4105 o Code simplifications and refactoring:
4106 - Generate our manpage and HTML documentation using Asciidoc. This
4107 change should make it easier to maintain the documentation, and
4109 - Remove the --enable-iphone option. According to reports from Marco
4110 Bonetti, Tor builds fine without any special tweaking on recent
4111 iPhone SDK versions.
4112 - Removed some unnecessary files from the source distribution. The
4113 AUTHORS file has now been merged into the people page on the
4114 website. The roadmaps and design doc can now be found in the
4115 projects directory in svn.
4116 - Enabled various circuit build timeout constants to be controlled
4117 by consensus parameters. Also set better defaults for these
4118 parameters based on experimentation on broadband and simulated
4122 - The 'EXTENDCIRCUIT' control port command can now be used with
4123 a circ id of 0 and no path. This feature will cause Tor to build
4124 a new 'fast' general purpose circuit using its own path selection
4126 - Added a BUILDTIMEOUT_SET controller event to describe changes
4127 to the circuit build timeout.
4128 - Future-proof the controller protocol a bit by ignoring keyword
4129 arguments we do not recognize.
4130 - Expand homedirs passed to tor-checkkey. This should silence a
4131 coverity complaint about passing a user-supplied string into
4132 open() without checking it.
4135 Changes in version 0.2.1.25 - 2010-03-16
4136 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4137 prevent relays from guessing their IP address correctly. It also fixes
4138 several minor potential security bugs.
4141 - Fix a regression from our patch for bug 1244 that caused relays
4142 to guess their IP address incorrectly if they didn't set Address
4143 in their torrc and/or their address fails to resolve. Bugfix on
4144 0.2.1.23; fixes bug 1269.
4145 - When freeing a session key, zero it out completely. We only zeroed
4146 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4147 patched by ekir. Fixes bug 1254.
4150 - Fix a dereference-then-NULL-check sequence when publishing
4151 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4153 - Fix another dereference-then-NULL-check sequence. Bugfix on
4154 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4155 - Make sure we treat potentially not NUL-terminated strings correctly.
4156 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4160 Changes in version 0.2.1.24 - 2010-02-21
4161 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4165 - Work correctly out-of-the-box with even more vendor-patched versions
4166 of OpenSSL. In particular, make it so Debian and OS X don't need
4167 customized patches to run/build.
4170 Changes in version 0.2.1.23 - 2010-02-13
4171 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4172 again on the latest OS X, and updates the location of a directory
4175 o Major bugfixes (performance):
4176 - We were selecting our guards uniformly at random, and then weighting
4177 which of our guards we'd use uniformly at random. This imbalance
4178 meant that Tor clients were severely limited on throughput (and
4179 probably latency too) by the first hop in their circuit. Now we
4180 select guards weighted by currently advertised bandwidth. We also
4181 automatically discard guards picked using the old algorithm. Fixes
4182 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4185 - Make Tor work again on the latest OS X: when deciding whether to
4186 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4187 version at run-time, not compile time. We need to do this because
4188 Apple doesn't update its dev-tools headers when it updates its
4189 libraries in a security patch.
4190 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4191 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4192 a memory leak when requesting a hidden service descriptor we've
4193 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4196 o Directory authority changes:
4197 - Change IP address for dannenberg (v3 directory authority), and
4198 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4199 service directory authority) from the list.
4202 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4203 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4206 - Avoid a mad rush at the beginning of each month when each client
4207 rotates half of its guards. Instead we spread the rotation out
4208 throughout the month, but we still avoid leaving a precise timestamp
4209 in the state file about when we first picked the guard. Improves
4210 over the behavior introduced in 0.1.2.17.
4213 Changes in version 0.2.2.8-alpha - 2010-01-26
4214 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4215 causing bridge relays to disappear. If you're running a bridge,
4219 - Fix a memory corruption bug on bridges that occured during the
4220 inclusion of stats data in extra-info descriptors. Also fix the
4221 interface for geoip_get_bridge_stats* to prevent similar bugs in
4222 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4223 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4226 - Ignore OutboundBindAddress when connecting to localhost.
4227 Connections to localhost need to come _from_ localhost, or else
4228 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4232 Changes in version 0.2.2.7-alpha - 2010-01-19
4233 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4234 as laying the groundwork for further relay-side performance fixes. It
4235 also starts cleaning up client behavior with respect to the EntryNodes,
4236 ExitNodes, and StrictNodes config options.
4238 This release also rotates two directory authority keys, due to a
4239 security breach of some of the Torproject servers.
4241 o Directory authority changes:
4242 - Rotate keys (both v3 identity and relay identity) for moria1
4245 o Major features (performance):
4246 - We were selecting our guards uniformly at random, and then weighting
4247 which of our guards we'd use uniformly at random. This imbalance
4248 meant that Tor clients were severely limited on throughput (and
4249 probably latency too) by the first hop in their circuit. Now we
4250 select guards weighted by currently advertised bandwidth. We also
4251 automatically discard guards picked using the old algorithm. Fixes
4252 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4253 - When choosing which cells to relay first, relays can now favor
4254 circuits that have been quiet recently, to provide lower latency
4255 for low-volume circuits. By default, relays enable or disable this
4256 feature based on a setting in the consensus. You can override
4257 this default by using the new "CircuitPriorityHalflife" config
4258 option. Design and code by Ian Goldberg, Can Tang, and Chris
4260 - Add separate per-conn write limiting to go with the per-conn read
4261 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4262 but never per-conn write limits.
4263 - New consensus params "bwconnrate" and "bwconnburst" to let us
4264 rate-limit client connections as they enter the network. It's
4265 controlled in the consensus so we can turn it on and off for
4266 experiments. It's starting out off. Based on proposal 163.
4268 o Major features (relay selection options):
4269 - Switch to a StrictNodes config option, rather than the previous
4270 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
4271 "StrictExcludeNodes" option.
4272 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4273 change during a config reload, mark and discard all our origin
4274 circuits. This fix should address edge cases where we change the
4275 config options and but then choose a circuit that we created before
4277 - If EntryNodes or ExitNodes are set, be more willing to use an
4278 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
4280 - Make EntryNodes config option much more aggressive even when
4281 StrictNodes is not set. Before it would prepend your requested
4282 entrynodes to your list of guard nodes, but feel free to use others
4283 after that. Now it chooses only from your EntryNodes if any of
4284 those are available, and only falls back to others if a) they're
4285 all down and b) StrictNodes is not set.
4286 - Now we refresh your entry guards from EntryNodes at each consensus
4287 fetch -- rather than just at startup and then they slowly rot as
4288 the network changes.
4291 - Stop bridge directory authorities from answering dbg-stability.txt
4292 directory queries, which would let people fetch a list of all
4293 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4296 - Log a notice when we get a new control connection. Now it's easier
4297 for security-conscious users to recognize when a local application
4298 is knocking on their controller door. Suggested by bug 1196.
4299 - New config option "CircuitStreamTimeout" to override our internal
4300 timeout schedule for how many seconds until we detach a stream from
4301 a circuit and try a new circuit. If your network is particularly
4302 slow, you might want to set this to a number like 60.
4303 - New controller command "getinfo config-text". It returns the
4304 contents that Tor would write if you send it a SAVECONF command,
4305 so the controller can write the file to disk itself.
4306 - New options for SafeLogging to allow scrubbing only log messages
4307 generated while acting as a relay.
4308 - Ship the bridges spec file in the tarball too.
4309 - Avoid a mad rush at the beginning of each month when each client
4310 rotates half of its guards. Instead we spread the rotation out
4311 throughout the month, but we still avoid leaving a precise timestamp
4312 in the state file about when we first picked the guard. Improves
4313 over the behavior introduced in 0.1.2.17.
4315 o Minor bugfixes (compiling):
4316 - Fix compilation on OS X 10.3, which has a stub mlockall() but
4317 hides it. Bugfix on 0.2.2.6-alpha.
4318 - Fix compilation on Solaris by removing support for the
4319 DisableAllSwap config option. Solaris doesn't have an rlimit for
4320 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
4323 o Minor bugfixes (crashes):
4324 - Do not segfault when writing buffer stats when we haven't observed
4325 a single circuit to report about. Found by Fabian Lanze. Bugfix on
4327 - If we're in the pathological case where there's no exit bandwidth
4328 but there is non-exit bandwidth, or no guard bandwidth but there
4329 is non-guard bandwidth, don't crash during path selection. Bugfix
4331 - Fix an impossible-to-actually-trigger buffer overflow in relay
4332 descriptor generation. Bugfix on 0.1.0.15.
4334 o Minor bugfixes (privacy):
4335 - Fix an instance where a Tor directory mirror might accidentally
4336 log the IP address of a misbehaving Tor client. Bugfix on
4338 - Don't list Windows capabilities in relay descriptors. We never made
4339 use of them, and maybe it's a bad idea to publish them. Bugfix
4342 o Minor bugfixes (other):
4343 - Resolve an edge case in path weighting that could make us misweight
4344 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4345 - Fix statistics on client numbers by country as seen by bridges that
4346 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
4347 intervals instead of variable 12-to-48-hour intervals.
4348 - After we free an internal connection structure, overwrite it
4349 with a different memory value than we use for overwriting a freed
4350 internal circuit structure. Should help with debugging. Suggested
4352 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
4356 - Remove the HSAuthorityRecordStats option that version 0 hidden
4357 service authorities could have used to track statistics of overall
4358 hidden service usage.
4361 Changes in version 0.2.1.22 - 2010-01-19
4362 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4363 authorities -- it would tell you its whole history of bridge descriptors
4364 if you make the right directory request. This stable update also
4365 rotates two of the seven v3 directory authority keys and locations.
4367 o Directory authority changes:
4368 - Rotate keys (both v3 identity and relay identity) for moria1
4372 - Stop bridge directory authorities from answering dbg-stability.txt
4373 directory queries, which would let people fetch a list of all
4374 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4377 Changes in version 0.2.1.21 - 2009-12-21
4378 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4379 library. If you use Tor on Linux / Unix and you're getting SSL
4380 renegotiation errors, upgrading should help. We also recommend an
4381 upgrade if you're an exit relay.
4384 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4385 handshake from working unless we explicitly tell OpenSSL that we
4386 are using SSL renegotiation safely. We are, of course, but OpenSSL
4387 0.9.8l won't work unless we say we are.
4388 - Avoid crashing if the client is trying to upload many bytes and the
4389 circuit gets torn down at the same time, or if the flip side
4390 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4393 - Do not refuse to learn about authority certs and v2 networkstatus
4394 documents that are older than the latest consensus. This bug might
4395 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4396 Spotted and fixed by xmux.
4397 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4398 trigger platform-specific option misparsing case found by Coverity
4400 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4401 trigger assert. Fixes bug 1173.
4404 Changes in version 0.2.2.6-alpha - 2009-11-19
4405 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
4406 support for the new lower-footprint "microdescriptor" directory design,
4407 future-proofing our consensus format against new hash functions or
4408 other changes, and an Android port. It also makes Tor compatible with
4409 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
4412 - Directory authorities can now create, vote on, and serve multiple
4413 parallel formats of directory data as part of their voting process.
4414 Partially implements Proposal 162: "Publish the consensus in
4416 - Directory authorities can now agree on and publish small summaries
4417 of router information that clients can use in place of regular
4418 server descriptors. This transition will eventually allow clients
4419 to use far less bandwidth for downloading information about the
4420 network. Begins the implementation of Proposal 158: "Clients
4421 download consensus + microdescriptors".
4422 - The directory voting system is now extensible to use multiple hash
4423 algorithms for signatures and resource selection. Newer formats
4424 are signed with SHA256, with a possibility for moving to a better
4425 hash algorithm in the future.
4426 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4427 current and future memory pages via mlockall(). On supported
4428 platforms (modern Linux and probably BSD but not Windows or OS X),
4429 this should effectively disable any and all attempts to page out
4430 memory. This option requires that you start your Tor as root --
4431 if you use DisableAllSwap, please consider using the User option
4432 to properly reduce the privileges of your Tor.
4433 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4434 to help Tor build correctly for Android phones.
4437 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4438 handshake from working unless we explicitly tell OpenSSL that we
4439 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
4440 won't work unless we say we are.
4443 - Fix a crash bug when trying to initialize the evdns module in
4444 Libevent 2. Bugfix on 0.2.1.16-rc.
4445 - Stop logging at severity 'warn' when some other Tor client tries
4446 to establish a circuit with us using weak DH keys. It's a protocol
4447 violation, but that doesn't mean ordinary users need to hear about
4448 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4449 - Do not refuse to learn about authority certs and v2 networkstatus
4450 documents that are older than the latest consensus. This bug might
4451 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4452 Spotted and fixed by xmux.
4453 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4454 - If all authorities restart at once right before a consensus vote,
4455 nobody will vote about "Running", and clients will get a consensus
4456 with no usable relays. Instead, authorities refuse to build a
4457 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4458 - If your relay can't keep up with the number of incoming create
4459 cells, it would log one warning per failure into your logs. Limit
4460 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4461 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4462 on 0.2.0.3-alpha; fixes bug 1113.
4463 - Fix a memory leak on directory authorities during voting that was
4464 introduced in 0.2.2.1-alpha. Found via valgrind.
4467 Changes in version 0.2.1.20 - 2009-10-15
4468 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4469 services at once, prepares for more performance improvements, and
4470 fixes a bunch of smaller bugs.
4472 The Windows and OS X bundles also include a more recent Vidalia,
4473 and switch from Privoxy to Polipo.
4475 The OS X installers are now drag and drop. It's best to un-install
4476 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4477 you want to upgrade, you'll need to update the paths for Tor and Polipo
4478 in the Vidalia Settings window.
4481 - Send circuit or stream sendme cells when our window has decreased
4482 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4483 by Karsten when testing the "reduce circuit window" performance
4484 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4485 before the release of Tor 0.0.0. This is the new winner of the
4487 - Fix a remotely triggerable memory leak when a consensus document
4488 contains more than one signature from the same voter. Bugfix on
4490 - Avoid segfault in rare cases when finishing an introduction circuit
4491 as a client and finding out that we don't have an introduction key
4492 for it. Fixes bug 1073. Reported by Aaron Swartz.
4495 - Tor now reads the "circwindow" parameter out of the consensus,
4496 and uses that value for its circuit package window rather than the
4497 default of 1000 cells. Begins the implementation of proposal 168.
4499 o New directory authorities:
4500 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4502 - Move moria1 and tonga to alternate IP addresses.
4505 - Fix a signed/unsigned compile warning in 0.2.1.19.
4506 - Fix possible segmentation fault on directory authorities. Bugfix on
4508 - Fix an extremely rare infinite recursion bug that could occur if
4509 we tried to log a message after shutting down the log subsystem.
4510 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4511 - Fix an obscure bug where hidden services on 64-bit big-endian
4512 systems might mis-read the timestamp in v3 introduce cells, and
4513 refuse to connect back to the client. Discovered by "rotor".
4514 Bugfix on 0.2.1.6-alpha.
4515 - We were triggering a CLOCK_SKEW controller status event whenever
4516 we connect via the v2 connection protocol to any relay that has
4517 a wrong clock. Instead, we should only inform the controller when
4518 it's a trusted authority that claims our clock is wrong. Bugfix
4519 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4520 - We were telling the controller about CHECKING_REACHABILITY and
4521 REACHABILITY_FAILED status events whenever we launch a testing
4522 circuit or notice that one has failed. Instead, only tell the
4523 controller when we want to inform the user of overall success or
4524 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4526 - Don't warn when we're using a circuit that ends with a node
4527 excluded in ExcludeExitNodes, but the circuit is not used to access
4528 the outside world. This should help fix bug 1090. Bugfix on
4530 - Work around a small memory leak in some versions of OpenSSL that
4531 stopped the memory used by the hostname TLS extension from being
4535 - Add a "getinfo status/accepted-server-descriptor" controller
4536 command, which is the recommended way for controllers to learn
4537 whether our server descriptor has been successfully received by at
4538 least on directory authority. Un-recommend good-server-descriptor
4539 getinfo and status events until we have a better design for them.
4542 Changes in version 0.2.2.5-alpha - 2009-10-11
4543 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
4546 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
4548 o Directory authorities:
4549 - Temporarily (just for this release) move dizum to an alternate
4553 Changes in version 0.2.2.4-alpha - 2009-10-10
4554 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
4555 introduces a new unit test framework, shifts directry authority
4556 addresses around to reduce the impact from recent blocking events,
4557 and fixes a few smaller bugs.
4560 - Fix several more asserts in the circuit_build_times code, for
4561 example one that causes Tor to fail to start once we have
4562 accumulated 5000 build times in the state file. Bugfixes on
4563 0.2.2.2-alpha; fixes bug 1108.
4565 o New directory authorities:
4566 - Move moria1 and Tonga to alternate IP addresses.
4569 - Log SSL state transitions at debug level during handshake, and
4570 include SSL states in error messages. This may help debug future
4571 SSL handshake issues.
4572 - Add a new "Handshake" log domain for activities that happen
4573 during the TLS handshake.
4574 - Revert to the "June 3 2009" ip-to-country file. The September one
4575 seems to have removed most US IP addresses.
4576 - Directory authorities now reject Tor relays with versions less than
4577 0.1.2.14. This step cuts out four relays from the current network,
4578 none of which are very big.
4581 - Fix a couple of smaller issues with gathering statistics. Bugfixes
4583 - Fix two memory leaks in the error case of
4584 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
4585 - Don't count one-hop circuits when we're estimating how long it
4586 takes circuits to build on average. Otherwise we'll set our circuit
4587 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
4588 - Directory authorities no longer change their opinion of, or vote on,
4589 whether a router is Running, unless they have themselves been
4590 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4593 o Code simplifications and refactoring:
4594 - Revise our unit tests to use the "tinytest" framework, so we
4595 can run tests in their own processes, have smarter setup/teardown
4596 code, and so on. The unit test code has moved to its own
4597 subdirectory, and has been split into multiple modules.
4600 Changes in version 0.2.2.3-alpha - 2009-09-23
4601 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
4604 - Fix an overzealous assert in our new circuit build timeout code.
4605 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
4608 - If the networkstatus consensus tells us that we should use a
4609 negative circuit package window, ignore it. Otherwise we'll
4610 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
4613 Changes in version 0.2.2.2-alpha - 2009-09-21
4614 Tor 0.2.2.2-alpha introduces our latest performance improvement for
4615 clients: Tor tracks the average time it takes to build a circuit, and
4616 avoids using circuits that take too long to build. For fast connections,
4617 this feature can cut your expected latency in half. For slow or flaky
4618 connections, it could ruin your Tor experience. Let us know if it does!
4621 - Tor now tracks how long it takes to build client-side circuits
4622 over time, and adapts its timeout to local network performance.
4623 Since a circuit that takes a long time to build will also provide
4624 bad performance, we get significant latency improvements by
4625 discarding the slowest 20% of circuits. Specifically, Tor creates
4626 circuits more aggressively than usual until it has enough data
4627 points for a good timeout estimate. Implements proposal 151.
4628 We are especially looking for reports (good and bad) from users with
4629 both EDGE and broadband connections that can move from broadband
4630 to EDGE and find out if the build-time data in the .tor/state gets
4631 reset without loss of Tor usability. You should also see a notice
4632 log message telling you that Tor has reset its timeout.
4633 - Directory authorities can now vote on arbitary integer values as
4634 part of the consensus process. This is designed to help set
4635 network-wide parameters. Implements proposal 167.
4636 - Tor now reads the "circwindow" parameter out of the consensus,
4637 and uses that value for its circuit package window rather than the
4638 default of 1000 cells. Begins the implementation of proposal 168.
4641 - Fix a remotely triggerable memory leak when a consensus document
4642 contains more than one signature from the same voter. Bugfix on
4646 - Fix an extremely rare infinite recursion bug that could occur if
4647 we tried to log a message after shutting down the log subsystem.
4648 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4649 - Fix parsing for memory or time units given without a space between
4650 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
4651 - A networkstatus vote must contain exactly one signature. Spec
4652 conformance issue. Bugfix on 0.2.0.3-alpha.
4653 - Fix an obscure bug where hidden services on 64-bit big-endian
4654 systems might mis-read the timestamp in v3 introduce cells, and
4655 refuse to connect back to the client. Discovered by "rotor".
4656 Bugfix on 0.2.1.6-alpha.
4657 - We were triggering a CLOCK_SKEW controller status event whenever
4658 we connect via the v2 connection protocol to any relay that has
4659 a wrong clock. Instead, we should only inform the controller when
4660 it's a trusted authority that claims our clock is wrong. Bugfix
4661 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4662 - We were telling the controller about CHECKING_REACHABILITY and
4663 REACHABILITY_FAILED status events whenever we launch a testing
4664 circuit or notice that one has failed. Instead, only tell the
4665 controller when we want to inform the user of overall success or
4666 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4668 - Don't warn when we're using a circuit that ends with a node
4669 excluded in ExcludeExitNodes, but the circuit is not used to access
4670 the outside world. This should help fix bug 1090, but more problems
4671 remain. Bugfix on 0.2.1.6-alpha.
4672 - Work around a small memory leak in some versions of OpenSSL that
4673 stopped the memory used by the hostname TLS extension from being
4675 - Make our 'torify' script more portable; if we have only one of
4676 'torsocks' or 'tsocks' installed, don't complain to the user;
4677 and explain our warning about tsocks better.
4680 - Add a "getinfo status/accepted-server-descriptor" controller
4681 command, which is the recommended way for controllers to learn
4682 whether our server descriptor has been successfully received by at
4683 least on directory authority. Un-recommend good-server-descriptor
4684 getinfo and status events until we have a better design for them.
4685 - Update to the "September 4 2009" ip-to-country file.
4688 Changes in version 0.2.2.1-alpha - 2009-08-26
4689 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
4690 Tor clients to bootstrap on networks where only port 80 is reachable,
4691 makes it more straightforward to support hardware crypto accelerators,
4692 and starts the groundwork for gathering stats safely at relays.
4695 - Start the process of disabling ".exit" address notation, since it
4696 can be used for a variety of esoteric application-level attacks
4697 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
4700 o New directory authorities:
4701 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4705 - New AccelName and AccelDir options add support for dynamic OpenSSL
4706 hardware crypto acceleration engines.
4707 - Tor now supports tunneling all of its outgoing connections over
4708 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
4709 configuration options. Code by Christopher Davis.
4712 - Send circuit or stream sendme cells when our window has decreased
4713 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4714 by Karsten when testing the "reduce circuit window" performance
4715 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4716 before the release of Tor 0.0.0. This is the new winner of the
4719 o New options for gathering stats safely:
4720 - Directory mirrors that set "DirReqStatistics 1" write statistics
4721 about directory requests to disk every 24 hours. As compared to the
4722 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
4723 1) stats are written to disk exactly every 24 hours; 2) estimated
4724 shares of v2 and v3 requests are determined as mean values, not at
4725 the end of a measurement period; 3) unresolved requests are listed
4726 with country code '??'; 4) directories also measure download times.
4727 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
4728 number of exit streams and transferred bytes per port to disk every
4730 - Relays that set "CellStatistics 1" write statistics on how long
4731 cells spend in their circuit queues to disk every 24 hours.
4732 - Entry nodes that set "EntryStatistics 1" write statistics on the
4733 rough number and origins of connecting clients to disk every 24
4735 - Relays that write any of the above statistics to disk and set
4736 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
4737 their extra-info documents.
4740 - New --digests command-line switch to output the digests of the
4741 source files Tor was built with.
4742 - The "torify" script now uses torsocks where available.
4743 - The memarea code now uses a sentinel value at the end of each area
4744 to make sure nothing writes beyond the end of an area. This might
4745 help debug some conceivable causes of bug 930.
4746 - Time and memory units in the configuration file can now be set to
4747 fractional units. For example, "2.5 GB" is now a valid value for
4749 - Certain Tor clients (such as those behind check.torproject.org) may
4750 want to fetch the consensus in an extra early manner. To enable this
4751 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
4752 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
4753 as only certain clients who must have this information sooner should
4755 - Instead of adding the svn revision to the Tor version string, report
4756 the git commit (when we're building from a git checkout).
4759 - If any of the v3 certs we download are unparseable, we should
4760 actually notice the failure so we don't retry indefinitely. Bugfix
4761 on 0.2.0.x; reported by "rotator".
4762 - If the cached cert file is unparseable, warn but don't exit.
4763 - Fix possible segmentation fault on directory authorities. Bugfix on
4765 - When Tor fails to parse a descriptor of any kind, dump it to disk.
4766 Might help diagnosing bug 1051.
4768 o Deprecated and removed features:
4769 - The controller no longer accepts the old obsolete "addr-mappings/"
4770 or "unregistered-servers-" GETINFO values.
4771 - Hidden services no longer publish version 0 descriptors, and clients
4772 do not request or use version 0 descriptors. However, the old hidden
4773 service authorities still accept and serve version 0 descriptors
4774 when contacted by older hidden services/clients.
4775 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
4776 always on; using them is necessary for correct forward-compatible
4778 - Remove support for .noconnect style addresses. Nobody was using
4779 them, and they provided another avenue for detecting Tor users
4780 via application-level web tricks.
4782 o Packaging changes:
4783 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
4784 installer bundles. See
4785 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
4786 for details of what's new in Vidalia 0.2.3.
4787 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
4788 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
4789 configuration file, rather than the old Privoxy.
4790 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
4791 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
4792 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
4793 better compatibility with OS X 10.6, aka Snow Leopard.
4794 - OS X Vidalia Bundle: The multi-package installer is now replaced
4795 by a simple drag and drop to the /Applications folder. This change
4796 occurred with the upgrade to Vidalia 0.2.3.
4799 Changes in version 0.2.1.19 - 2009-07-28
4800 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
4801 services on Tor 0.2.1.3-alpha through 0.2.1.18.
4804 - Make accessing hidden services on 0.2.1.x work right again.
4805 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
4806 part of patch provided by "optimist".
4809 - When a relay/bridge is writing out its identity key fingerprint to
4810 the "fingerprint" file and to its logs, write it without spaces. Now
4811 it will look like the fingerprints in our bridges documentation,
4812 and confuse fewer users.
4815 - Relays no longer publish a new server descriptor if they change
4816 their MaxAdvertisedBandwidth config option but it doesn't end up
4817 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
4818 fixes bug 1026. Patch from Sebastian.
4819 - Avoid leaking memory every time we get a create cell but we have
4820 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
4821 fixes bug 1034. Reported by BarkerJr.
4824 Changes in version 0.2.1.18 - 2009-07-24
4825 Tor 0.2.1.18 lays the foundations for performance improvements,
4826 adds status events to help users diagnose bootstrap problems, adds
4827 optional authentication/authorization for hidden services, fixes a
4828 variety of potential anonymity problems, and includes a huge pile of
4829 other features and bug fixes.
4832 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
4835 Changes in version 0.2.1.17-rc - 2009-07-07
4836 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
4837 candidate for the 0.2.1.x series. It lays the groundwork for further
4838 client performance improvements, and also fixes a big bug with directory
4839 authorities that were causing them to assign Guard and Stable flags
4842 The Windows bundles also finally include the geoip database that we
4843 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
4844 should actually install Torbutton rather than giving you a cryptic
4845 failure message (oops).
4848 - Clients now use the bandwidth values in the consensus, rather than
4849 the bandwidth values in each relay descriptor. This approach opens
4850 the door to more accurate bandwidth estimates once the directory
4851 authorities start doing active measurements. Implements more of
4855 - When Tor clients restart after 1-5 days, they discard all their
4856 cached descriptors as too old, but they still use the cached
4857 consensus document. This approach is good for robustness, but
4858 bad for performance: since they don't know any bandwidths, they
4859 end up choosing at random rather than weighting their choice by
4860 speed. Fixed by the above feature of putting bandwidths in the
4861 consensus. Bugfix on 0.2.0.x.
4862 - Directory authorities were neglecting to mark relays down in their
4863 internal histories if the relays fall off the routerlist without
4864 ever being found unreachable. So there were relays in the histories
4865 that haven't been seen for eight months, and are listed as being
4866 up for eight months. This wreaked havoc on the "median wfu"
4867 and "median mtbf" calculations, in turn making Guard and Stable
4868 flags very wrong, hurting network performance. Fixes bugs 696 and
4869 969. Bugfix on 0.2.0.6-alpha.
4872 - Serve the DirPortFrontPage page even when we have been approaching
4873 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
4874 - The control port would close the connection before flushing long
4875 replies, such as the network consensus, if a QUIT command was issued
4876 before the reply had completed. Now, the control port flushes all
4877 pending replies before closing the connection. Also fixed a spurious
4878 warning when a QUIT command is issued after a malformed or rejected
4879 AUTHENTICATE command, but before the connection was closed. Patch
4880 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
4881 - When we can't find an intro key for a v2 hidden service descriptor,
4882 fall back to the v0 hidden service descriptor and log a bug message.
4883 Workaround for bug 1024.
4884 - Fix a log message that did not respect the SafeLogging option.
4888 - If we're a relay and we change our IP address, be more verbose
4889 about the reason that made us change. Should help track down
4890 further bugs for relays on dynamic IP addresses.
4893 Changes in version 0.2.0.35 - 2009-06-24
4895 - Avoid crashing in the presence of certain malformed descriptors.
4896 Found by lark, and by automated fuzzing.
4897 - Fix an edge case where a malicious exit relay could convince a
4898 controller that the client's DNS question resolves to an internal IP
4899 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4902 - Finally fix the bug where dynamic-IP relays disappear when their
4903 IP address changes: directory mirrors were mistakenly telling
4904 them their old address if they asked via begin_dir, so they
4905 never got an accurate answer about their new address, so they
4906 just vanished after a day. For belt-and-suspenders, relays that
4907 don't set Address in their config now avoid using begin_dir for
4908 all direct connections. Should fix bugs 827, 883, and 900.
4909 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4910 that would occur on some exit nodes when DNS failures and timeouts
4911 occurred in certain patterns. Fix for bug 957.
4914 - When starting with a cache over a few days old, do not leak
4915 memory for the obsolete router descriptors in it. Bugfix on
4916 0.2.0.33; fixes bug 672.
4917 - Hidden service clients didn't use a cached service descriptor that
4918 was older than 15 minutes, but wouldn't fetch a new one either,
4919 because there was already one in the cache. Now, fetch a v2
4920 descriptor unless the same descriptor was added to the cache within
4921 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4924 Changes in version 0.2.1.16-rc - 2009-06-20
4925 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
4926 a bunch of minor bugs.
4929 - Fix an edge case where a malicious exit relay could convince a
4930 controller that the client's DNS question resolves to an internal IP
4931 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4933 o Major performance improvements (on 0.2.0.x):
4934 - Disable and refactor some debugging checks that forced a linear scan
4935 over the whole server-side DNS cache. These accounted for over 50%
4936 of CPU time on a relatively busy exit node's gprof profile. Found
4938 - Disable some debugging checks that appeared in exit node profile
4942 - Update to the "June 3 2009" ip-to-country file.
4943 - Do not have tor-resolve automatically refuse all .onion addresses;
4944 if AutomapHostsOnResolve is set in your torrc, this will work fine.
4946 o Minor bugfixes (on 0.2.0.x):
4947 - Log correct error messages for DNS-related network errors on
4949 - Fix a race condition that could cause crashes or memory corruption
4950 when running as a server with a controller listening for log
4952 - Avoid crashing when we have a policy specified in a DirPolicy or
4953 SocksPolicy or ReachableAddresses option with ports set on it,
4954 and we re-load the policy. May fix bug 996.
4955 - Hidden service clients didn't use a cached service descriptor that
4956 was older than 15 minutes, but wouldn't fetch a new one either,
4957 because there was already one in the cache. Now, fetch a v2
4958 descriptor unless the same descriptor was added to the cache within
4959 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4961 o Minor bugfixes (on 0.2.1.x):
4962 - Don't warn users about low port and hibernation mix when they
4963 provide a *ListenAddress directive to fix that. Bugfix on
4965 - When switching back and forth between bridge mode, do not start
4966 gathering GeoIP data until two hours have passed.
4967 - Do not complain that the user has requested an excluded node as
4968 an exit when the node is not really an exit. This could happen
4969 because the circuit was for testing, or an introduction point.
4973 Changes in version 0.2.1.15-rc - 2009-05-25
4974 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
4975 series. It fixes a major bug on fast exit relays, as well as a variety
4978 o Major bugfixes (on 0.2.0.x):
4979 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4980 that would occur on some exit nodes when DNS failures and timeouts
4981 occurred in certain patterns. Fix for bug 957.
4983 o Minor bugfixes (on 0.2.0.x):
4984 - Actually return -1 in the error case for read_bandwidth_usage().
4985 Harmless bug, since we currently don't care about the return value
4986 anywhere. Bugfix on 0.2.0.9-alpha.
4987 - Provide a more useful log message if bug 977 (related to buffer
4988 freelists) ever reappears, and do not crash right away.
4989 - Fix an assertion failure on 64-bit platforms when we allocated
4990 memory right up to the end of a memarea, then realigned the memory
4991 one step beyond the end. Fixes a possible cause of bug 930.
4992 - Protect the count of open sockets with a mutex, so we can't
4993 corrupt it when two threads are closing or opening sockets at once.
4994 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
4995 - Don't allow a bridge to publish its router descriptor to a
4996 non-bridge directory authority. Fixes part of bug 932.
4997 - When we change to or from being a bridge, reset our counts of
4998 client usage by country. Fixes bug 932.
4999 - Fix a bug that made stream bandwidth get misreported to the
5001 - Stop using malloc_usable_size() to use more area than we had
5002 actually allocated: it was safe, but made valgrind really unhappy.
5003 - Fix a memory leak when v3 directory authorities load their keys
5004 and cert from disk. Bugfix on 0.2.0.1-alpha.
5006 o Minor bugfixes (on 0.2.1.x):
5007 - Fix use of freed memory when deciding to mark a non-addable
5008 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5011 Changes in version 0.2.1.14-rc - 2009-04-12
5012 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5013 series. It begins fixing some major performance problems, and also
5014 finally addresses the bug that was causing relays on dynamic IP
5015 addresses to fall out of the directory.
5018 - Clients replace entry guards that were chosen more than a few months
5019 ago. This change should significantly improve client performance,
5020 especially once more people upgrade, since relays that have been
5021 a guard for a long time are currently overloaded.
5023 o Major bugfixes (on 0.2.0):
5024 - Finally fix the bug where dynamic-IP relays disappear when their
5025 IP address changes: directory mirrors were mistakenly telling
5026 them their old address if they asked via begin_dir, so they
5027 never got an accurate answer about their new address, so they
5028 just vanished after a day. For belt-and-suspenders, relays that
5029 don't set Address in their config now avoid using begin_dir for
5030 all direct connections. Should fix bugs 827, 883, and 900.
5031 - Relays were falling out of the networkstatus consensus for
5032 part of a day if they changed their local config but the
5033 authorities discarded their new descriptor as "not sufficiently
5034 different". Now directory authorities accept a descriptor as changed
5035 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5037 - Avoid crashing in the presence of certain malformed descriptors.
5038 Found by lark, and by automated fuzzing.
5041 - When generating circuit events with verbose nicknames for
5042 controllers, try harder to look up nicknames for routers on a
5043 circuit. (Previously, we would look in the router descriptors we had
5044 for nicknames, but not in the consensus.) Partial fix for bug 941.
5045 - If the bridge config line doesn't specify a port, assume 443.
5046 This makes bridge lines a bit smaller and easier for users to
5048 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5049 bytes (aka 20KB/s), to match our documentation. Also update
5050 directory authorities so they always assign the Fast flag to relays
5051 with 20KB/s of capacity. Now people running relays won't suddenly
5052 find themselves not seeing any use, if the network gets faster
5054 - Update to the "April 3 2009" ip-to-country file.
5057 - Avoid trying to print raw memory to the logs when we decide to
5058 give up on downloading a given relay descriptor. Bugfix on
5060 - In tor-resolve, when the Tor client to use is specified by
5061 <hostname>:<port>, actually use the specified port rather than
5062 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5063 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5064 - When starting with a cache over a few days old, do not leak
5065 memory for the obsolete router descriptors in it. Bugfix on
5067 - Avoid double-free on list of successfully uploaded hidden
5068 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5069 - Change memarea_strndup() implementation to work even when
5070 duplicating a string at the end of a page. This bug was
5071 harmless for now, but could have meant crashes later. Fix by
5072 lark. Bugfix on 0.2.1.1-alpha.
5073 - Limit uploaded directory documents to be 16M rather than 500K.
5074 The directory authorities were refusing v3 consensus votes from
5075 other authorities, since the votes are now 504K. Fixes bug 959;
5076 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5077 - Directory authorities should never send a 503 "busy" response to
5078 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5082 Changes in version 0.2.1.13-alpha - 2009-03-09
5083 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5084 cleanups. We're finally getting close to a release candidate.
5087 - Correctly update the list of which countries we exclude as
5088 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5089 lark. Bugfix on 0.2.1.6-alpha.
5091 o Minor bugfixes (on 0.2.0.x and earlier):
5092 - Automatically detect MacOSX versions earlier than 10.4.0, and
5093 disable kqueue from inside Tor when running with these versions.
5094 We previously did this from the startup script, but that was no
5095 help to people who didn't use the startup script. Resolves bug 863.
5096 - When we had picked an exit node for a connection, but marked it as
5097 "optional", and it turned out we had no onion key for the exit,
5098 stop wanting that exit and try again. This situation may not
5099 be possible now, but will probably become feasible with proposal
5100 158. Spotted by rovv. Fixes another case of bug 752.
5101 - Clients no longer cache certificates for authorities they do not
5102 recognize. Bugfix on 0.2.0.9-alpha.
5103 - When we can't transmit a DNS request due to a network error, retry
5104 it after a while, and eventually transmit a failing response to
5105 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5106 - If the controller claimed responsibility for a stream, but that
5107 stream never finished making its connection, it would live
5108 forever in circuit_wait state. Now we close it after SocksTimeout
5109 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5110 - Drop begin cells to a hidden service if they come from the middle
5111 of a circuit. Patch from lark.
5112 - When we erroneously receive two EXTEND cells for the same circuit
5113 ID on the same connection, drop the second. Patch from lark.
5114 - Fix a crash that occurs on exit nodes when a nameserver request
5115 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5116 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5118 - Do not assume that a stack-allocated character array will be
5119 64-bit aligned on platforms that demand that uint64_t access is
5120 aligned. Possible fix for bug 604.
5121 - Parse dates and IPv4 addresses in a locale- and libc-independent
5122 manner, to avoid platform-dependent behavior on malformed input.
5123 - Build correctly when configured to build outside the main source
5124 path. Patch from Michael Gold.
5125 - We were already rejecting relay begin cells with destination port
5126 of 0. Now also reject extend cells with destination port or address
5127 of 0. Suggested by lark.
5129 o Minor bugfixes (on 0.2.1.x):
5130 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5131 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5132 - If we're an exit node, scrub the IP address to which we are exiting
5133 in the logs. Bugfix on 0.2.1.8-alpha.
5136 - On Linux, use the prctl call to re-enable core dumps when the user
5138 - New controller event NEWCONSENSUS that lists the networkstatus
5139 lines for every recommended relay. Now controllers like Torflow
5140 can keep up-to-date on which relays they should be using.
5141 - Update to the "February 26 2009" ip-to-country file.
5144 Changes in version 0.2.0.34 - 2009-02-08
5145 Tor 0.2.0.34 features several more security-related fixes. You should
5146 upgrade, especially if you run an exit relay (remote crash) or a
5147 directory authority (remote infinite loop), or you're on an older
5148 (pre-XP) or not-recently-patched Windows (remote exploit).
5150 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5151 have many known flaws, and nobody should be using them. You should
5152 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5153 stop using those packages and upgrade anyway.
5156 - Fix an infinite-loop bug on handling corrupt votes under certain
5157 circumstances. Bugfix on 0.2.0.8-alpha.
5158 - Fix a temporary DoS vulnerability that could be performed by
5159 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5160 - Avoid a potential crash on exit nodes when processing malformed
5161 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5162 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5163 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5166 - Fix compilation on systems where time_t is a 64-bit integer.
5167 Patch from Matthias Drochner.
5168 - Don't consider expiring already-closed client connections. Fixes
5169 bug 893. Bugfix on 0.0.2pre20.
5172 Changes in version 0.2.1.12-alpha - 2009-02-08
5173 Tor 0.2.1.12-alpha features several more security-related fixes. You
5174 should upgrade, especially if you run an exit relay (remote crash) or
5175 a directory authority (remote infinite loop), or you're on an older
5176 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5177 includes a big pile of minor bugfixes and cleanups.
5180 - Fix an infinite-loop bug on handling corrupt votes under certain
5181 circumstances. Bugfix on 0.2.0.8-alpha.
5182 - Fix a temporary DoS vulnerability that could be performed by
5183 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5184 - Avoid a potential crash on exit nodes when processing malformed
5185 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5188 - Let controllers actually ask for the "clients_seen" event for
5189 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5190 reported by Matt Edman.
5191 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5193 - Fix a bug in address parsing that was preventing bridges or hidden
5194 service targets from being at IPv6 addresses.
5195 - Solve a bug that kept hardware crypto acceleration from getting
5196 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5198 - Remove a bash-ism from configure.in to build properly on non-Linux
5199 platforms. Bugfix on 0.2.1.1-alpha.
5200 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5201 headers. Bugfix on 0.2.0.10-alpha.
5202 - Don't consider expiring already-closed client connections. Fixes
5203 bug 893. Bugfix on 0.0.2pre20.
5204 - Fix another interesting corner-case of bug 891 spotted by rovv:
5205 Previously, if two hosts had different amounts of clock drift, and
5206 one of them created a new connection with just the wrong timing,
5207 the other might decide to deprecate the new connection erroneously.
5208 Bugfix on 0.1.1.13-alpha.
5209 - Resolve a very rare crash bug that could occur when the user forced
5210 a nameserver reconfiguration during the middle of a nameserver
5211 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5212 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5213 Bugfix on 0.2.1.7-alpha.
5214 - If we're using bridges and our network goes away, be more willing
5215 to forgive our bridges and try again when we get an application
5216 request. Bugfix on 0.2.0.x.
5219 - Support platforms where time_t is 64 bits long. (Congratulations,
5220 NetBSD!) Patch from Matthias Drochner.
5221 - Add a 'getinfo status/clients-seen' controller command, in case
5222 controllers want to hear clients_seen events but connect late.
5225 - Disable GCC's strict alias optimization by default, to avoid the
5226 likelihood of its introducing subtle bugs whenever our code violates
5227 the letter of C99's alias rules.
5230 Changes in version 0.2.0.33 - 2009-01-21
5231 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5232 useful to users. It also finally fixes a bug where a relay or client
5233 that's been off for many days would take a long time to bootstrap.
5235 This update also fixes an important security-related bug reported by
5236 Ilja van Sprundel. You should upgrade. (We'll send out more details
5237 about the bug once people have had some time to upgrade.)
5240 - Fix a heap-corruption bug that may be remotely triggerable on
5241 some platforms. Reported by Ilja van Sprundel.
5244 - When a stream at an exit relay is in state "resolving" or
5245 "connecting" and it receives an "end" relay cell, the exit relay
5246 would silently ignore the end cell and not close the stream. If
5247 the client never closes the circuit, then the exit relay never
5248 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5250 - When sending CREATED cells back for a given circuit, use a 64-bit
5251 connection ID to find the right connection, rather than an addr:port
5252 combination. Now that we can have multiple OR connections between
5253 the same ORs, it is no longer possible to use addr:port to uniquely
5254 identify a connection.
5255 - Bridge relays that had DirPort set to 0 would stop fetching
5256 descriptors shortly after startup, and then briefly resume
5257 after a new bandwidth test and/or after publishing a new bridge
5258 descriptor. Bridge users that try to bootstrap from them would
5259 get a recent networkstatus but would get descriptors from up to
5260 18 hours earlier, meaning most of the descriptors were obsolete
5261 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5262 - Prevent bridge relays from serving their 'extrainfo' document
5263 to anybody who asks, now that extrainfo docs include potentially
5264 sensitive aggregated client geoip summaries. Bugfix on
5266 - If the cached networkstatus consensus is more than five days old,
5267 discard it rather than trying to use it. In theory it could be
5268 useful because it lists alternate directory mirrors, but in practice
5269 it just means we spend many minutes trying directory mirrors that
5270 are long gone from the network. Also discard router descriptors as
5271 we load them if they are more than five days old, since the onion
5272 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5275 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5276 could make gcc generate non-functional binary search code. Bugfix
5278 - Build correctly on platforms without socklen_t.
5279 - Compile without warnings on solaris.
5280 - Avoid potential crash on internal error during signature collection.
5281 Fixes bug 864. Patch from rovv.
5282 - Correct handling of possible malformed authority signing key
5283 certificates with internal signature types. Fixes bug 880.
5284 Bugfix on 0.2.0.3-alpha.
5285 - Fix a hard-to-trigger resource leak when logging credential status.
5287 - When we can't initialize DNS because the network is down, do not
5288 automatically stop Tor from starting. Instead, we retry failed
5289 dns_init() every 10 minutes, and change the exit policy to reject
5290 *:* until one succeeds. Fixes bug 691.
5291 - Use 64 bits instead of 32 bits for connection identifiers used with
5292 the controller protocol, to greatly reduce risk of identifier reuse.
5293 - When we're choosing an exit node for a circuit, and we have
5294 no pending streams, choose a good general exit rather than one that
5295 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5296 - Fix another case of assuming, when a specific exit is requested,
5297 that we know more than the user about what hosts it allows.
5298 Fixes one case of bug 752. Patch from rovv.
5299 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5300 seconds. Warn the user if lower values are given in the
5301 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5302 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5303 user if lower values are given in the configuration. Bugfix on
5304 0.1.1.17-rc. Patch by Sebastian.
5305 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5306 the cache because we already had a v0 descriptor with the same ID.
5307 Bugfix on 0.2.0.18-alpha.
5308 - Fix a race condition when freeing keys shared between main thread
5309 and CPU workers that could result in a memory leak. Bugfix on
5310 0.1.0.1-rc. Fixes bug 889.
5311 - Send a valid END cell back when a client tries to connect to a
5312 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5313 840. Patch from rovv.
5314 - Check which hops rendezvous stream cells are associated with to
5315 prevent possible guess-the-streamid injection attacks from
5316 intermediate hops. Fixes another case of bug 446. Based on patch
5318 - If a broken client asks a non-exit router to connect somewhere,
5319 do not even do the DNS lookup before rejecting the connection.
5320 Fixes another case of bug 619. Patch from rovv.
5321 - When a relay gets a create cell it can't decrypt (e.g. because it's
5322 using the wrong onion key), we were dropping it and letting the
5323 client time out. Now actually answer with a destroy cell. Fixes
5324 bug 904. Bugfix on 0.0.2pre8.
5326 o Minor bugfixes (hidden services):
5327 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5328 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5331 - Report the case where all signatures in a detached set are rejected
5332 differently than the case where there is an error handling the
5334 - When we realize that another process has modified our cached
5335 descriptors, print out a more useful error message rather than
5336 triggering an assertion. Fixes bug 885. Patch from Karsten.
5337 - Implement the 0x20 hack to better resist DNS poisoning: set the
5338 case on outgoing DNS requests randomly, and reject responses that do
5339 not match the case correctly. This logic can be disabled with the
5340 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5341 of servers that do not reliably preserve case in replies. See
5342 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5344 - Check DNS replies for more matching fields to better resist DNS
5346 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5347 compress cells, which are basically all encrypted, compressed, or
5351 Changes in version 0.2.1.11-alpha - 2009-01-20
5352 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
5353 week it will take a long time to bootstrap again" bug. It also fixes
5354 an important security-related bug reported by Ilja van Sprundel. You
5355 should upgrade. (We'll send out more details about the bug once people
5356 have had some time to upgrade.)
5359 - Fix a heap-corruption bug that may be remotely triggerable on
5360 some platforms. Reported by Ilja van Sprundel.
5363 - Discard router descriptors as we load them if they are more than
5364 five days old. Otherwise if Tor is off for a long time and then
5365 starts with cached descriptors, it will try to use the onion
5366 keys in those obsolete descriptors when building circuits. Bugfix
5367 on 0.2.0.x. Fixes bug 887.
5370 - Try to make sure that the version of Libevent we're running with
5371 is binary-compatible with the one we built with. May address bug
5373 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
5374 for bug 905. Bugfix on 0.2.1.7-alpha.
5375 - Add a new --enable-local-appdata configuration switch to change
5376 the default location of the datadir on win32 from APPDATA to
5377 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5378 entirely. Patch from coderman.
5381 - Make outbound DNS packets respect the OutboundBindAddress setting.
5382 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5383 - When our circuit fails at the first hop (e.g. we get a destroy
5384 cell back), avoid using that OR connection anymore, and also
5385 tell all the one-hop directory requests waiting for it that they
5386 should fail. Bugfix on 0.2.1.3-alpha.
5387 - In the torify(1) manpage, mention that tsocks will leak your
5391 Changes in version 0.2.1.10-alpha - 2009-01-06
5392 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
5393 would make the bridge relay not so useful if it had DirPort set to 0,
5394 and one that could let an attacker learn a little bit of information
5395 about the bridge's users), and a bug that would cause your Tor relay
5396 to ignore a circuit create request it can't decrypt (rather than reply
5397 with an error). It also fixes a wide variety of other bugs.
5400 - If the cached networkstatus consensus is more than five days old,
5401 discard it rather than trying to use it. In theory it could
5402 be useful because it lists alternate directory mirrors, but in
5403 practice it just means we spend many minutes trying directory
5404 mirrors that are long gone from the network. Helps bug 887 a bit;
5406 - Bridge relays that had DirPort set to 0 would stop fetching
5407 descriptors shortly after startup, and then briefly resume
5408 after a new bandwidth test and/or after publishing a new bridge
5409 descriptor. Bridge users that try to bootstrap from them would
5410 get a recent networkstatus but would get descriptors from up to
5411 18 hours earlier, meaning most of the descriptors were obsolete
5412 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5413 - Prevent bridge relays from serving their 'extrainfo' document
5414 to anybody who asks, now that extrainfo docs include potentially
5415 sensitive aggregated client geoip summaries. Bugfix on
5419 - New controller event "clients_seen" to report a geoip-based summary
5420 of which countries we've seen clients from recently. Now controllers
5421 like Vidalia can show bridge operators that they're actually making
5423 - Build correctly against versions of OpenSSL 0.9.8 or later built
5424 without support for deprecated functions.
5425 - Update to the "December 19 2008" ip-to-country file.
5427 o Minor bugfixes (on 0.2.0.x):
5428 - Authorities now vote for the Stable flag for any router whose
5429 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5430 - Do not remove routers as too old if we do not have any consensus
5431 document. Bugfix on 0.2.0.7-alpha.
5432 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5433 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5434 - When an exit relay resolves a stream address to a local IP address,
5435 do not just keep retrying that same exit relay over and
5436 over. Instead, just close the stream. Addresses bug 872. Bugfix
5437 on 0.2.0.32. Patch from rovv.
5438 - If a hidden service sends us an END cell, do not consider
5439 retrying the connection; just close it. Patch from rovv.
5440 - When we made bridge authorities stop serving bridge descriptors over
5441 unencrypted links, we also broke DirPort reachability testing for
5442 bridges. So bridges with a non-zero DirPort were printing spurious
5443 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5444 - When a relay gets a create cell it can't decrypt (e.g. because it's
5445 using the wrong onion key), we were dropping it and letting the
5446 client time out. Now actually answer with a destroy cell. Fixes
5447 bug 904. Bugfix on 0.0.2pre8.
5448 - Squeeze 2-5% out of client performance (according to oprofile) by
5449 improving the implementation of some policy-manipulation functions.
5451 o Minor bugfixes (on 0.2.1.x):
5452 - Make get_interface_address() function work properly again; stop
5453 guessing the wrong parts of our address as our address.
5454 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
5455 send on that circuit. Otherwise we might violate the proposal-110
5456 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
5458 - When we're sending non-EXTEND cells to the first hop in a circuit,
5459 for example to use an encrypted directory connection, we don't need
5460 to use RELAY_EARLY cells: the first hop knows what kind of cell
5461 it is, and nobody else can even see the cell type. Conserving
5462 RELAY_EARLY cells makes it easier to cannibalize circuits like
5464 - Stop logging nameserver addresses in reverse order.
5465 - If we are retrying a directory download slowly over and over, do
5466 not automatically give up after the 254th failure. Bugfix on
5468 - Resume reporting accurate "stream end" reasons to the local control
5469 port. They were lost in the changes for Proposal 148. Bugfix on
5472 o Deprecated and removed features:
5473 - The old "tor --version --version" command, which would print out
5474 the subversion "Id" of most of the source files, is now removed. It
5475 turned out to be less useful than we'd expected, and harder to
5478 o Code simplifications and refactoring:
5479 - Change our header file guard macros to be less likely to conflict
5480 with system headers. Adam Langley noticed that we were conflicting
5481 with log.h on Android.
5482 - Tool-assisted documentation cleanup. Nearly every function or
5483 static variable in Tor should have its own documentation now.
5486 Changes in version 0.2.1.9-alpha - 2008-12-25
5487 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
5489 o New directory authorities:
5490 - gabelmoo (the authority run by Karsten Loesing) now has a new
5494 - Never use a connection with a mismatched address to extend a
5495 circuit, unless that connection is canonical. A canonical
5496 connection is one whose address is authenticated by the router's
5497 identity key, either in a NETINFO cell or in a router descriptor.
5498 - Avoid a possible memory corruption bug when receiving hidden service
5499 descriptors. Bugfix on 0.2.1.6-alpha.
5502 - Fix a logic error that would automatically reject all but the first
5503 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
5504 part of bug 813/868. Bug spotted by coderman.
5505 - When a stream at an exit relay is in state "resolving" or
5506 "connecting" and it receives an "end" relay cell, the exit relay
5507 would silently ignore the end cell and not close the stream. If
5508 the client never closes the circuit, then the exit relay never
5509 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
5511 - When we can't initialize DNS because the network is down, do not
5512 automatically stop Tor from starting. Instead, retry failed
5513 dns_init() every 10 minutes, and change the exit policy to reject
5514 *:* until one succeeds. Fixes bug 691.
5517 - Give a better error message when an overzealous init script says
5518 "sudo -u username tor --user username". Makes Bug 882 easier for
5520 - When a directory authority gives us a new guess for our IP address,
5521 log which authority we used. Hopefully this will help us debug
5522 the recent complaints about bad IP address guesses.
5523 - Detect svn revision properly when we're using git-svn.
5524 - Try not to open more than one descriptor-downloading connection
5525 to an authority at once. This should reduce load on directory
5526 authorities. Fixes bug 366.
5527 - Add cross-certification to newly generated certificates, so that
5528 a signing key is enough information to look up a certificate.
5529 Partial implementation of proposal 157.
5530 - Start serving certificates by <identity digest, signing key digest>
5531 pairs. Partial implementation of proposal 157.
5532 - Clients now never report any stream end reason except 'MISC'.
5533 Implements proposal 148.
5534 - On platforms with a maximum syslog string length, truncate syslog
5535 messages to that length ourselves, rather than relying on the
5536 system to do it for us.
5537 - Optimize out calls to time(NULL) that occur for every IO operation,
5538 or for every cell. On systems where time() is a slow syscall,
5539 this fix will be slightly helpful.
5540 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5541 - When we download a descriptor that we then immediately (as
5542 a directory authority) reject, do not retry downloading it right
5543 away. Should save some bandwidth on authorities. Fix for bug
5544 888. Patch by Sebastian Hahn.
5545 - When a download gets us zero good descriptors, do not notify
5546 Tor that new directory information has arrived.
5547 - Avoid some nasty corner cases in the logic for marking connections
5548 as too old or obsolete or noncanonical for circuits. Partial
5551 o Minor features (controller):
5552 - New CONSENSUS_ARRIVED event to note when a new consensus has
5553 been fetched and validated.
5554 - When we realize that another process has modified our cached
5555 descriptors file, print out a more useful error message rather
5556 than triggering an assertion. Fixes bug 885. Patch from Karsten.
5557 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
5558 controllers to prevent SIGHUP from reloading the
5559 configuration. Fixes bug 856.
5562 - Resume using the correct "REASON=" stream when telling the
5563 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
5564 - When a canonical connection appears later in our internal list
5565 than a noncanonical one for a given OR ID, always use the
5566 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
5568 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5569 seconds. Warn the user if lower values are given in the
5570 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5571 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5572 user if lower values are given in the configuration. Bugfix on
5573 0.1.1.17-rc. Patch by Sebastian.
5574 - Fix a race condition when freeing keys shared between main thread
5575 and CPU workers that could result in a memory leak. Bugfix on
5576 0.1.0.1-rc. Fixes bug 889.
5578 o Minor bugfixes (hidden services):
5579 - Do not throw away existing introduction points on SIGHUP (bugfix on
5580 0.0.6pre1); also, do not stall hidden services because we're
5581 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
5582 by John Brooks. Patch by Karsten. Fixes bug 874.
5583 - Fix a memory leak when we decline to add a v2 rendezvous
5584 descriptor to the cache because we already had a v0 descriptor
5585 with the same ID. Bugfix on 0.2.0.18-alpha.
5587 o Deprecated and removed features:
5588 - RedirectExits has been removed. It was deprecated since
5590 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
5591 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
5592 - Cell pools are now always enabled; --disable-cell-pools is ignored.
5594 o Code simplifications and refactoring:
5595 - Rename the confusing or_is_obsolete field to the more appropriate
5596 is_bad_for_new_circs, and move it to or_connection_t where it
5598 - Move edge-only flags from connection_t to edge_connection_t: not
5599 only is this better coding, but on machines of plausible alignment,
5600 it should save 4-8 bytes per connection_t. "Every little bit helps."
5601 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
5602 for consistency; keep old option working for backward compatibility.
5603 - Simplify the code for finding connections to use for a circuit.
5606 Changes in version 0.2.1.8-alpha - 2008-12-08
5607 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
5608 builds better on unusual platforms like Solaris and old OS X, and
5609 fixes a variety of other issues.
5612 - New DirPortFrontPage option that takes an html file and publishes
5613 it as "/" on the DirPort. Now relay operators can provide a
5614 disclaimer without needing to set up a separate webserver. There's
5615 a sample disclaimer in contrib/tor-exit-notice.html.
5618 - When the client is choosing entry guards, now it selects at most
5619 one guard from a given relay family. Otherwise we could end up with
5620 all of our entry points into the network run by the same operator.
5621 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
5624 - Fix a DOS opportunity during the voting signature collection process
5625 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5626 - Fix a possible segfault when establishing an exit connection. Bugfix
5630 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
5632 - Made Tor a little less aggressive about deleting expired
5633 certificates. Partial fix for bug 854.
5634 - Stop doing unaligned memory access that generated bus errors on
5635 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
5636 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
5637 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
5638 - Make USR2 log-level switch take effect immediately. Bugfix on
5640 - If one win32 nameserver fails to get added, continue adding the
5641 rest, and don't automatically fail.
5642 - Use fcntl() for locking when flock() is not available. Should fix
5643 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
5644 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5645 could make gcc generate non-functional binary search code. Bugfix
5647 - Build correctly on platforms without socklen_t.
5648 - Avoid potential crash on internal error during signature collection.
5649 Fixes bug 864. Patch from rovv.
5650 - Do not use C's stdio library for writing to log files. This will
5651 improve logging performance by a minute amount, and will stop
5652 leaking fds when our disk is full. Fixes bug 861.
5653 - Stop erroneous use of O_APPEND in cases where we did not in fact
5654 want to re-seek to the end of a file before every last write().
5655 - Correct handling of possible malformed authority signing key
5656 certificates with internal signature types. Fixes bug 880. Bugfix
5658 - Fix a hard-to-trigger resource leak when logging credential status.
5662 - Directory mirrors no longer fetch the v1 directory or
5663 running-routers files. They are obsolete, and nobody asks for them
5664 anymore. This is the first step to making v1 authorities obsolete.
5666 o Minor features (controller):
5667 - Return circuit purposes in response to GETINFO circuit-status. Fixes
5671 Changes in version 0.2.0.32 - 2008-11-20
5672 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
5673 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5674 a smaller security flaw that might allow an attacker to access local
5675 services, further improves hidden service performance, and fixes a
5676 variety of other issues.
5679 - The "User" and "Group" config options did not clear the
5680 supplementary group entries for the Tor process. The "User" option
5681 is now more robust, and we now set the groups to the specified
5682 user's primary group. The "Group" option is now ignored. For more
5683 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5684 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5685 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
5686 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5687 consistently obeyed: if an exit relay refuses a stream because its
5688 exit policy doesn't allow it, we would remember what IP address
5689 the relay said the destination address resolves to, even if it's
5690 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5693 - Fix a DOS opportunity during the voting signature collection process
5694 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5696 o Major bugfixes (hidden services):
5697 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5698 we were failing the whole hidden service request when the v0
5699 descriptor fetch fails, even if the v2 fetch is still pending and
5700 might succeed. Similarly, if the last v2 fetch fails, we were
5701 failing the whole hidden service request even if a v0 fetch is
5702 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5703 - When extending a circuit to a hidden service directory to upload a
5704 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5705 requests failed, because the router descriptor has not been
5706 downloaded yet. In these cases, do not attempt to upload the
5707 rendezvous descriptor, but wait until the router descriptor is
5708 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
5709 descriptor from a hidden service directory for which the router
5710 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
5714 - Fix several infrequent memory leaks spotted by Coverity.
5715 - When testing for libevent functions, set the LDFLAGS variable
5716 correctly. Found by Riastradh.
5717 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5718 bootstrapping with tunneled directory connections. Bugfix on
5719 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5720 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5721 and we know that server B rejects most-but-not all connections to
5722 port 80, we would previously reject the connection. Now, we assume
5723 the user knows what they were asking for. Fixes bug 752. Bugfix
5724 on 0.0.9rc5. Diagnosed by BarkerJr.
5725 - If we overrun our per-second write limits a little, count this as
5726 having used up our write allocation for the second, and choke
5727 outgoing directory writes. Previously, we had only counted this when
5728 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
5729 Bugfix on 0.2.0.x (??).
5730 - Remove the old v2 directory authority 'lefkada' from the default
5731 list. It has been gone for many months.
5732 - Stop doing unaligned memory access that generated bus errors on
5733 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
5734 - Make USR2 log-level switch take effect immediately. Bugfix on
5737 o Minor bugfixes (controller):
5738 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
5739 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
5742 Changes in version 0.2.1.7-alpha - 2008-11-08
5743 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
5744 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5745 a smaller security flaw that might allow an attacker to access local
5746 services, adds better defense against DNS poisoning attacks on exit
5747 relays, further improves hidden service performance, and fixes a
5748 variety of other issues.
5751 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5752 consistently obeyed: if an exit relay refuses a stream because its
5753 exit policy doesn't allow it, we would remember what IP address
5754 the relay said the destination address resolves to, even if it's
5755 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5756 - The "User" and "Group" config options did not clear the
5757 supplementary group entries for the Tor process. The "User" option
5758 is now more robust, and we now set the groups to the specified
5759 user's primary group. The "Group" option is now ignored. For more
5760 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5761 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5762 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
5763 - Do not use or believe expired v3 authority certificates. Patch
5764 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
5767 - Now NodeFamily and MyFamily config options allow spaces in
5768 identity fingerprints, so it's easier to paste them in.
5769 Suggested by Lucky Green.
5770 - Implement the 0x20 hack to better resist DNS poisoning: set the
5771 case on outgoing DNS requests randomly, and reject responses that do
5772 not match the case correctly. This logic can be disabled with the
5773 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
5774 of servers that do not reliably preserve case in replies. See
5775 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5777 - Preserve case in replies to DNSPort requests in order to support
5778 the 0x20 hack for resisting DNS poisoning attacks.
5780 o Hidden service performance improvements:
5781 - When the client launches an introduction circuit, retry with a
5782 new circuit after 30 seconds rather than 60 seconds.
5783 - Launch a second client-side introduction circuit in parallel
5784 after a delay of 15 seconds (based on work by Christian Wilms).
5785 - Hidden services start out building five intro circuits rather
5786 than three, and when the first three finish they publish a service
5787 descriptor using those. Now we publish our service descriptor much
5788 faster after restart.
5791 - Minor fix in the warning messages when you're having problems
5792 bootstrapping; also, be more forgiving of bootstrap problems when
5793 we're still making incremental progress on a given bootstrap phase.
5794 - When we're choosing an exit node for a circuit, and we have
5795 no pending streams, choose a good general exit rather than one that
5796 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
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 - If a broken client asks a non-exit router to connect somewhere,
5801 do not even do the DNS lookup before rejecting the connection.
5802 Fixes another case of bug 619. Patch from rovv.
5803 - Fix another case of assuming, when a specific exit is requested,
5804 that we know more than the user about what hosts it allows.
5805 Fixes another case of bug 752. Patch from rovv.
5806 - Check which hops rendezvous stream cells are associated with to
5807 prevent possible guess-the-streamid injection attacks from
5808 intermediate hops. Fixes another case of bug 446. Based on patch
5810 - Avoid using a negative right-shift when comparing 32-bit
5811 addresses. Possible fix for bug 845 and bug 811.
5812 - Make the assert_circuit_ok() function work correctly on circuits that
5813 have already been marked for close.
5814 - Fix read-off-the-end-of-string error in unit tests when decoding
5815 introduction points.
5816 - Fix uninitialized size field for memory area allocation: may improve
5817 memory performance during directory parsing.
5818 - Treat duplicate certificate fetches as failures, so that we do
5819 not try to re-fetch an expired certificate over and over and over.
5820 - Do not say we're fetching a certificate when we'll in fact skip it
5821 because of a pending download.
5824 Changes in version 0.2.1.6-alpha - 2008-09-30
5825 Tor 0.2.1.6-alpha further improves performance and robustness of
5826 hidden services, starts work on supporting per-country relay selection,
5827 and fixes a variety of smaller issues.
5830 - Implement proposal 121: make it possible to build hidden services
5831 that only certain clients are allowed to connect to. This is
5832 enforced at several points, so that unauthorized clients are unable
5833 to send INTRODUCE cells to the service, or even (depending on the
5834 type of authentication) to learn introduction points. This feature
5835 raises the bar for certain kinds of active attacks against hidden
5836 services. Code by Karsten Loesing.
5837 - Relays now store and serve v2 hidden service descriptors by default,
5838 i.e., the new default value for HidServDirectoryV2 is 1. This is
5839 the last step in proposal 114, which aims to make hidden service
5840 lookups more reliable.
5841 - Start work to allow node restrictions to include country codes. The
5842 syntax to exclude nodes in a country with country code XX is
5843 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
5844 refinement to decide what config options should take priority if
5845 you ask to both use a particular node and exclude it.
5846 - Allow ExitNodes list to include IP ranges and country codes, just
5847 like the Exclude*Nodes lists. Patch from Robert Hogan.
5850 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
5851 Tor to fail to start if you had it configured to use a bridge
5852 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
5853 - When extending a circuit to a hidden service directory to upload a
5854 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5855 requests failed, because the router descriptor had not been
5856 downloaded yet. In these cases, we now wait until the router
5857 descriptor is downloaded, and then retry. Likewise, clients
5858 now skip over a hidden service directory if they don't yet have
5859 its router descriptor, rather than futilely requesting it and
5860 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
5862 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5863 we were failing the whole hidden service request when the v0
5864 descriptor fetch fails, even if the v2 fetch is still pending and
5865 might succeed. Similarly, if the last v2 fetch fails, we were
5866 failing the whole hidden service request even if a v0 fetch is
5867 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5868 - DNS replies need to have names matching their requests, but
5869 these names should be in the questions section, not necessarily
5870 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
5873 - Update to the "September 1 2008" ip-to-country file.
5874 - Allow ports 465 and 587 in the default exit policy again. We had
5875 rejected them in 0.1.0.15, because back in 2005 they were commonly
5876 misconfigured and ended up as spam targets. We hear they are better
5877 locked down these days.
5878 - Use a lockfile to make sure that two Tor processes are not
5879 simultaneously running with the same datadir.
5880 - Serve the latest v3 networkstatus consensus via the control
5881 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
5882 - Better logging about stability/reliability calculations on directory
5884 - Drop the requirement to have an open dir port for storing and
5885 serving v2 hidden service descriptors.
5886 - Directory authorities now serve a /tor/dbg-stability.txt URL to
5887 help debug WFU and MTBF calculations.
5888 - Implement most of Proposal 152: allow specialized servers to permit
5889 single-hop circuits, and clients to use those servers to build
5890 single-hop circuits when using a specialized controller. Patch
5891 from Josh Albrecht. Resolves feature request 768.
5892 - Add a -p option to tor-resolve for specifying the SOCKS port: some
5893 people find host:port too confusing.
5894 - Make TrackHostExit mappings expire a while after their last use, not
5895 after their creation. Patch from Robert Hogan.
5896 - Provide circuit purposes along with circuit events to the controller.
5899 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
5901 - Fixed some memory leaks -- some quite frequent, some almost
5902 impossible to trigger -- based on results from Coverity.
5903 - When testing for libevent functions, set the LDFLAGS variable
5904 correctly. Found by Riastradh.
5905 - Fix an assertion bug in parsing policy-related options; possible fix
5907 - Catch and report a few more bootstrapping failure cases when Tor
5908 fails to establish a TCP connection. Cleanup on 0.2.1.x.
5909 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5910 bootstrapping with tunneled directory connections. Bugfix on
5911 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5912 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5913 and we know that server B rejects most-but-not all connections to
5914 port 80, we would previously reject the connection. Now, we assume
5915 the user knows what they were asking for. Fixes bug 752. Bugfix
5916 on 0.0.9rc5. Diagnosed by BarkerJr.
5917 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
5918 service directories if they have no advertised dir port. Bugfix
5920 - If we overrun our per-second write limits a little, count this as
5921 having used up our write allocation for the second, and choke
5922 outgoing directory writes. Previously, we had only counted this when
5923 we had met our limits precisely. Fixes bug 824. Patch by rovv.
5924 Bugfix on 0.2.0.x (??).
5925 - Avoid a "0 divided by 0" calculation when calculating router uptime
5926 at directory authorities. Bugfix on 0.2.0.8-alpha.
5927 - Make DNS resolved controller events into "CLOSED", not
5928 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
5930 - Fix a bug where an unreachable relay would establish enough
5931 reachability testing circuits to do a bandwidth test -- if
5932 we already have a connection to the middle hop of the testing
5933 circuit, then it could establish the last hop by using the existing
5934 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
5935 circuits no longer use entry guards in 0.2.1.3-alpha.
5936 - If we have correct permissions on $datadir, we complain to stdout
5937 and fail to start. But dangerous permissions on
5938 $datadir/cached-status/ would cause us to open a log and complain
5939 there. Now complain to stdout and fail to start in both cases. Fixes
5940 bug 820, reported by seeess.
5941 - Remove the old v2 directory authority 'lefkada' from the default
5942 list. It has been gone for many months.
5944 o Code simplifications and refactoring:
5945 - Revise the connection_new functions so that a more typesafe variant
5946 exists. This will work better with Coverity, and let us find any
5947 actual mistakes we're making here.
5948 - Refactor unit testing logic so that dmalloc can be used sensibly
5949 with unit tests to check for memory leaks.
5950 - Move all hidden-service related fields from connection and circuit
5951 structure to substructures: this way they won't eat so much memory.
5954 Changes in version 0.2.0.31 - 2008-09-03
5955 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
5956 a big bug we're seeing where in rare cases traffic from one Tor stream
5957 gets mixed into another stream, and fixes a variety of smaller issues.
5960 - Make sure that two circuits can never exist on the same connection
5961 with the same circuit ID, even if one is marked for close. This
5962 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
5963 - Relays now reject risky extend cells: if the extend cell includes
5964 a digest of all zeroes, or asks to extend back to the relay that
5965 sent the extend cell, tear down the circuit. Ideas suggested
5967 - If not enough of our entry guards are available so we add a new
5968 one, we might use the new one even if it overlapped with the
5969 current circuit's exit relay (or its family). Anonymity bugfix
5970 pointed out by rovv.
5973 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5974 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5975 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5976 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5977 - Pick size of default geoip filename string correctly on windows.
5978 Fixes bug 806. Bugfix on 0.2.0.30.
5979 - Make the autoconf script accept the obsolete --with-ssl-dir
5980 option as an alias for the actually-working --with-openssl-dir
5981 option. Fix the help documentation to recommend --with-openssl-dir.
5982 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5983 - When using the TransPort option on OpenBSD, and using the User
5984 option to change UID and drop privileges, make sure to open
5985 /dev/pf before dropping privileges. Fixes bug 782. Patch from
5986 Christopher Davis. Bugfix on 0.1.2.1-alpha.
5987 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5988 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5989 on the client side when connecting to a hidden service. Bugfix
5990 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5991 - When closing an application-side connection because its circuit is
5992 getting torn down, generate the stream event correctly. Bugfix on
5993 0.1.2.x. Anonymous patch.
5996 Changes in version 0.2.1.5-alpha - 2008-08-31
5997 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
5998 in a lot of the infrastructure for adding authorization to hidden
5999 services, lays the groundwork for having clients read their load
6000 balancing information out of the networkstatus consensus rather than
6001 the individual router descriptors, addresses two potential anonymity
6002 issues, and fixes a variety of smaller issues.
6005 - Convert many internal address representations to optionally hold
6007 - Generate and accept IPv6 addresses in many protocol elements.
6008 - Make resolver code handle nameservers located at ipv6 addresses.
6009 - Begin implementation of proposal 121 ("Client authorization for
6010 hidden services"): configure hidden services with client
6011 authorization, publish descriptors for them, and configure
6012 authorization data for hidden services at clients. The next
6013 step is to actually access hidden services that perform client
6015 - More progress toward proposal 141: Network status consensus
6016 documents and votes now contain bandwidth information for each
6017 router and a summary of that router's exit policy. Eventually this
6018 will be used by clients so that they do not have to download every
6019 known descriptor before building circuits.
6021 o Major bugfixes (on 0.2.0.x and before):
6022 - When sending CREATED cells back for a given circuit, use a 64-bit
6023 connection ID to find the right connection, rather than an addr:port
6024 combination. Now that we can have multiple OR connections between
6025 the same ORs, it is no longer possible to use addr:port to uniquely
6026 identify a connection.
6027 - Relays now reject risky extend cells: if the extend cell includes
6028 a digest of all zeroes, or asks to extend back to the relay that
6029 sent the extend cell, tear down the circuit. Ideas suggested
6031 - If not enough of our entry guards are available so we add a new
6032 one, we might use the new one even if it overlapped with the
6033 current circuit's exit relay (or its family). Anonymity bugfix
6034 pointed out by rovv.
6037 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6038 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6039 - When using the TransPort option on OpenBSD, and using the User
6040 option to change UID and drop privileges, make sure to open /dev/pf
6041 before dropping privileges. Fixes bug 782. Patch from Christopher
6042 Davis. Bugfix on 0.1.2.1-alpha.
6043 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6044 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6045 - Add a missing safe_str() call for a debug log message.
6046 - Use 64 bits instead of 32 bits for connection identifiers used with
6047 the controller protocol, to greatly reduce risk of identifier reuse.
6048 - Make the autoconf script accept the obsolete --with-ssl-dir
6049 option as an alias for the actually-working --with-openssl-dir
6050 option. Fix the help documentation to recommend --with-openssl-dir.
6051 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6054 - Rate-limit too-many-sockets messages: when they happen, they happen
6055 a lot. Resolves bug 748.
6056 - Resist DNS poisoning a little better by making sure that names in
6057 answer sections match.
6058 - Print the SOCKS5 error message string as well as the error code
6059 when a tor-resolve request fails. Patch from Jacob.
6062 Changes in version 0.2.1.4-alpha - 2008-08-04
6063 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6066 - The address part of exit policies was not correctly written
6067 to router descriptors. This generated router descriptors that failed
6068 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6070 - Tor triggered a false assert when extending a circuit to a relay
6071 but we already have a connection open to that relay. Noticed by
6072 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6075 - Fix a hidden service logging bug: in some edge cases, the router
6076 descriptor of a previously picked introduction point becomes
6077 obsolete and we need to give up on it rather than continually
6078 complaining that it has become obsolete. Observed by xiando. Bugfix
6082 - Take out the TestVia config option, since it was a workaround for
6083 a bug that was fixed in Tor 0.1.1.21.
6086 Changes in version 0.2.1.3-alpha - 2008-08-03
6087 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6088 infinite-length circuit attacks (see proposal 110); fixes a bug that
6089 might cause exit relays to corrupt streams they send back; allows
6090 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6091 ExcludeExitNodes config options; and fixes a big pile of bugs.
6093 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6094 - Send a bootstrap problem "warn" event on the first problem if the
6095 reason is NO_ROUTE (that is, our network is down).
6098 - Implement most of proposal 110: The first K cells to be sent
6099 along a circuit are marked as special "early" cells; only K "early"
6100 cells will be allowed. Once this code is universal, we can block
6101 certain kinds of DOS attack by requiring that EXTEND commands must
6102 be sent using an "early" cell.
6105 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6106 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6107 on the client side when connecting to a hidden service. Bugfix
6108 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6109 - Ensure that two circuits can never exist on the same connection
6110 with the same circuit ID, even if one is marked for close. This
6111 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6114 - When relays do their initial bandwidth measurement, don't limit
6115 to just our entry guards for the test circuits. Otherwise we tend
6116 to have multiple test circuits going through a single entry guard,
6117 which makes our bandwidth test less accurate. Fixes part of bug 654;
6118 patch contributed by Josh Albrecht.
6119 - Add an ExcludeExitNodes option so users can list a set of nodes
6120 that should be be excluded from the exit node position, but
6121 allowed elsewhere. Implements proposal 151.
6122 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6123 ExcludeNodes and ExcludeExitNodes lists.
6124 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6125 be more efficient. Formerly it was quadratic in the number of
6126 servers; now it should be linear. Fixes bug 509.
6127 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6128 and n_conn_id_digest fields into a separate structure that's
6129 only needed when the circuit has not yet attached to an n_conn.
6132 - Change the contrib/tor.logrotate script so it makes the new
6133 logs as "_tor:_tor" rather than the default, which is generally
6134 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6135 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6136 warnings (occasionally), but it can also cause the compiler to
6137 eliminate error-checking code. Suggested by Peter Gutmann.
6138 - When a hidden service is giving up on an introduction point candidate
6139 that was not included in the last published rendezvous descriptor,
6140 don't reschedule publication of the next descriptor. Fixes bug 763.
6142 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6143 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6144 and nobody claims to be using them. Fixes bug 754. Bugfix on
6145 0.1.0.1-rc. Patch from Christian Wilms.
6146 - Fix a small alignment and memory-wasting bug on buffer chunks.
6149 o Minor bugfixes (controller):
6150 - When closing an application-side connection because its circuit
6151 is getting torn down, generate the stream event correctly.
6152 Bugfix on 0.1.2.x. Anonymous patch.
6155 - Remove all backward-compatibility code to support relays running
6156 versions of Tor so old that they no longer work at all on the
6160 Changes in version 0.2.0.30 - 2008-07-15
6162 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6163 warnings (occasionally), but it can also cause the compiler to
6164 eliminate error-checking code. Suggested by Peter Gutmann.
6167 Changes in version 0.2.0.29-rc - 2008-07-08
6168 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6169 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6172 - If you have more than one bridge but don't know their keys,
6173 you would only launch a request for the descriptor of the first one
6174 on your list. (Tor considered launching requests for the others, but
6175 found that it already had a connection on the way for $0000...0000
6176 so it didn't open another.) Bugfix on 0.2.0.x.
6177 - If you have more than one bridge but don't know their keys, and the
6178 connection to one of the bridges failed, you would cancel all
6179 pending bridge connections. (After all, they all have the same
6180 digest.) Bugfix on 0.2.0.x.
6181 - When a hidden service was trying to establish an introduction point,
6182 and Tor had built circuits preemptively for such purposes, we
6183 were ignoring all the preemptive circuits and launching a new one
6184 instead. Bugfix on 0.2.0.14-alpha.
6185 - When a hidden service was trying to establish an introduction point,
6186 and Tor *did* manage to reuse one of the preemptively built
6187 circuits, it didn't correctly remember which one it used,
6188 so it asked for another one soon after, until there were no
6189 more preemptive circuits, at which point it launched one from
6190 scratch. Bugfix on 0.0.9.x.
6191 - Make directory servers include the X-Your-Address-Is: http header in
6192 their responses even for begin_dir conns. Now clients who only
6193 ever use begin_dir connections still have a way to learn their IP
6194 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6197 - Fix a macro/CPP interaction that was confusing some compilers:
6198 some GCCs don't like #if/#endif pairs inside macro arguments.
6200 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6201 Fixes bug 704; fix from Steven Murdoch.
6202 - When opening /dev/null in finish_daemonize(), do not pass the
6203 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6204 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6205 - Correctly detect transparent proxy support on Linux hosts that
6206 require in.h to be included before netfilter_ipv4.h. Patch
6208 - Disallow session resumption attempts during the renegotiation
6209 stage of the v2 handshake protocol. Clients should never be trying
6210 session resumption at this point, but apparently some did, in
6211 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6212 found by Geoff Goodell.
6215 Changes in version 0.2.1.2-alpha - 2008-06-20
6216 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6217 make it easier to set up your own private Tor network; fixes several
6218 big bugs with using more than one bridge relay; fixes a big bug with
6219 offering hidden services quickly after Tor starts; and uses a better
6220 API for reporting potential bootstrapping problems to the controller.
6223 - New TestingTorNetwork config option to allow adjustment of
6224 previously constant values that, while reasonable, could slow
6225 bootstrapping. Implements proposal 135. Patch from Karsten.
6228 - If you have more than one bridge but don't know their digests,
6229 you would only learn a request for the descriptor of the first one
6230 on your list. (Tor considered launching requests for the others, but
6231 found that it already had a connection on the way for $0000...0000
6232 so it didn't open another.) Bugfix on 0.2.0.x.
6233 - If you have more than one bridge but don't know their digests,
6234 and the connection to one of the bridges failed, you would cancel
6235 all pending bridge connections. (After all, they all have the
6236 same digest.) Bugfix on 0.2.0.x.
6237 - When establishing a hidden service, introduction points that
6238 originate from cannibalized circuits are completely ignored and not
6239 included in rendezvous service descriptors. This might be another
6240 reason for delay in making a hidden service available. Bugfix
6241 from long ago (0.0.9.x?)
6244 - Allow OpenSSL to use dynamic locks if it wants.
6245 - When building a consensus, do not include routers that are down.
6246 This will cut down 30% to 40% on consensus size. Implements
6248 - In directory authorities' approved-routers files, allow
6249 fingerprints with or without space.
6250 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6251 controller can query our current bootstrap state in case it attaches
6252 partway through and wants to catch up.
6253 - Send an initial "Starting" bootstrap status event, so we have a
6254 state to start out in.
6257 - Asking for a conditional consensus at .../consensus/<fingerprints>
6258 would crash a dirserver if it did not already have a
6259 consensus. Bugfix on 0.2.1.1-alpha.
6260 - Clean up some macro/CPP interactions: some GCC versions don't like
6261 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
6264 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
6265 - Directory authorities shouldn't complain about bootstrapping
6266 problems just because they do a lot of reachability testing and
6267 some of the connection attempts fail.
6268 - Start sending "count" and "recommendation" key/value pairs in
6269 bootstrap problem status events, so the controller can hear about
6270 problems even before Tor decides they're worth reporting for sure.
6271 - If you're using bridges, generate "bootstrap problem" warnings
6272 as soon as you run out of working bridges, rather than waiting
6273 for ten failures -- which will never happen if you have less than
6275 - If we close our OR connection because there's been a circuit
6276 pending on it for too long, we were telling our bootstrap status
6277 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
6280 Changes in version 0.2.1.1-alpha - 2008-06-13
6281 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
6282 were making the Tor process bloat especially on Linux; makes our TLS
6283 handshake blend in better; sends "bootstrap phase" status events to
6284 the controller, so it can keep the user informed of progress (and
6285 problems) fetching directory information and establishing circuits;
6286 and adds a variety of smaller features.
6289 - More work on making our TLS handshake blend in: modify the list
6290 of ciphers advertised by OpenSSL in client mode to even more
6291 closely resemble a common web browser. We cheat a little so that
6292 we can advertise ciphers that the locally installed OpenSSL doesn't
6294 - Start sending "bootstrap phase" status events to the controller,
6295 so it can keep the user informed of progress fetching directory
6296 information and establishing circuits. Also inform the controller
6297 if we think we're stuck at a particular bootstrap phase. Implements
6299 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6300 cross-platform entropy collection again. We used to use it, then
6301 stopped using it because of a bug that could crash systems that
6302 called RAND_poll when they had a lot of fds open. It looks like the
6303 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6304 at startup, and to call RAND_poll() when we reseed later only if
6305 we have a non-buggy OpenSSL version.
6308 - When we choose to abandon a new entry guard because we think our
6309 older ones might be better, close any circuits pending on that
6310 new entry guard connection. This fix should make us recover much
6311 faster when our network is down and then comes back. Bugfix on
6312 0.1.2.8-beta; found by lodger.
6314 o Memory fixes and improvements:
6315 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6316 to avoid unused RAM in buffer chunks and memory pools.
6317 - Speed up parsing and cut down on memory fragmentation by using
6318 stack-style allocations for parsing directory objects. Previously,
6319 this accounted for over 40% of allocations from within Tor's code
6320 on a typical directory cache.
6321 - Use a Bloom filter rather than a digest-based set to track which
6322 descriptors we need to keep around when we're cleaning out old
6323 router descriptors. This speeds up the computation significantly,
6324 and may reduce fragmentation.
6325 - Reduce the default smartlist size from 32 to 16; it turns out that
6326 most smartlists hold around 8-12 elements tops.
6327 - Make dumpstats() log the fullness and size of openssl-internal
6329 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6330 patch to their OpenSSL, turn it on to save memory on servers. This
6331 patch will (with any luck) get included in a mainline distribution
6333 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6334 compress cells, which are basically all encrypted, compressed,
6338 - Stop reloading the router list from disk for no reason when we
6339 run out of reachable directory mirrors. Once upon a time reloading
6340 it would set the 'is_running' flag back to 1 for them. It hasn't
6341 done that for a long time.
6342 - In very rare situations new hidden service descriptors were
6343 published earlier than 30 seconds after the last change to the
6344 service. (We currently think that a hidden service descriptor
6345 that's been stable for 30 seconds is worth publishing.)
6348 - Allow separate log levels to be configured for different logging
6349 domains. For example, this allows one to log all notices, warnings,
6350 or errors, plus all memory management messages of level debug or
6351 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
6352 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
6353 and stop using a warning that had become unfixably verbose under
6355 - New --hush command-line option similar to --quiet. While --quiet
6356 disables all logging to the console on startup, --hush limits the
6357 output to messages of warning and error severity.
6358 - Servers support a new URL scheme for consensus downloads that
6359 allows the client to specify which authorities are trusted.
6360 The server then only sends the consensus if the client will trust
6361 it. Otherwise a 404 error is sent back. Clients use this
6362 new scheme when the server supports it (meaning it's running
6363 0.2.1.1-alpha or later). Implements proposal 134.
6364 - New configure/torrc options (--enable-geoip-stats,
6365 DirRecordUsageByCountry) to record how many IPs we've served
6366 directory info to in each country code, how many status documents
6367 total we've sent to each country code, and what share of the total
6368 directory requests we should expect to see.
6369 - Use the TLS1 hostname extension to more closely resemble browser
6371 - Lots of new unit tests.
6372 - Add a macro to implement the common pattern of iterating through
6373 two parallel lists in lockstep.
6376 Changes in version 0.2.0.28-rc - 2008-06-13
6377 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
6378 performance bug, and fixes a bunch of smaller bugs.
6381 - Fix a bug where, when we were choosing the 'end stream reason' to
6382 put in our relay end cell that we send to the exit relay, Tor
6383 clients on Windows were sometimes sending the wrong 'reason'. The
6384 anonymity problem is that exit relays may be able to guess whether
6385 the client is running Windows, thus helping partition the anonymity
6386 set. Down the road we should stop sending reasons to exit relays,
6387 or otherwise prevent future versions of this bug.
6390 - While setting up a hidden service, some valid introduction circuits
6391 were overlooked and abandoned. This might be the reason for
6392 the long delay in making a hidden service available. Bugfix on
6396 - Update to the "June 9 2008" ip-to-country file.
6397 - Run 'make test' as part of 'make dist', so we stop releasing so
6398 many development snapshots that fail their unit tests.
6401 - When we're checking if we have enough dir info for each relay
6402 to begin establishing circuits, make sure that we actually have
6403 the descriptor listed in the consensus, not just any descriptor.
6405 - Bridge relays no longer print "xx=0" in their extrainfo document
6406 for every single country code in the geoip db. Bugfix on
6408 - Only warn when we fail to load the geoip file if we were planning to
6409 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
6410 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6411 Tor won't realize it should publish a new relay descriptor. Fixes
6412 bug 688, reported by mfr. Bugfix on 0.1.2.x.
6413 - When we haven't had any application requests lately, don't bother
6414 logging that we have expired a bunch of descriptors. Bugfix
6416 - Make relay cells written on a connection count as non-padding when
6417 tracking how long a connection has been in use. Bugfix on
6418 0.2.0.1-alpha. Spotted by lodger.
6419 - Fix unit tests in 0.2.0.27-rc.
6420 - Fix compile on Windows.
6423 Changes in version 0.2.0.27-rc - 2008-06-03
6424 Tor 0.2.0.27-rc adds a few features we left out of the earlier
6425 release candidates. In particular, we now include an IP-to-country
6426 GeoIP database, so controllers can easily look up what country a
6427 given relay is in, and so bridge relays can give us some sanitized
6428 summaries about which countries are making use of bridges. (See proposal
6429 126-geoip-fetching.txt for details.)
6432 - Include an IP-to-country GeoIP file in the tarball, so bridge
6433 relays can report sanitized summaries of the usage they're seeing.
6436 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
6437 Robert Hogan. Fixes the first part of bug 681.
6438 - Make bridge authorities never serve extrainfo docs.
6439 - Add support to detect Libevent versions in the 1.4.x series
6441 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
6442 - Include a new contrib/tor-exit-notice.html file that exit relay
6443 operators can put on their website to help reduce abuse queries.
6446 - When tunneling an encrypted directory connection, and its first
6447 circuit fails, do not leave it unattached and ask the controller
6448 to deal. Fixes the second part of bug 681.
6449 - Make bridge authorities correctly expire old extrainfo documents
6453 Changes in version 0.2.0.26-rc - 2008-05-13
6454 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
6455 in Debian's OpenSSL packages. All users running any 0.2.0.x version
6456 should upgrade, whether they're running Debian or not.
6458 o Major security fixes:
6459 - Use new V3 directory authority keys on the tor26, gabelmoo, and
6460 moria1 V3 directory authorities. The old keys were generated with
6461 a vulnerable version of Debian's OpenSSL package, and must be
6462 considered compromised. Other authorities' keys were not generated
6463 with an affected version of OpenSSL.
6466 - List authority signatures as "unrecognized" based on DirServer
6467 lines, not on cert cache. Bugfix on 0.2.0.x.
6470 - Add a new V3AuthUseLegacyKey option to make it easier for
6471 authorities to change their identity keys if they have to.
6474 Changes in version 0.2.0.25-rc - 2008-04-23
6475 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
6478 - Remember to initialize threading before initializing logging.
6479 Otherwise, many BSD-family implementations will crash hard on
6480 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
6483 - Authorities correctly free policies on bad servers on
6484 exit. Fixes bug 672. Bugfix on 0.2.0.x.
6487 Changes in version 0.2.0.24-rc - 2008-04-22
6488 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
6489 v3 directory authority, makes relays with dynamic IP addresses and no
6490 DirPort notice more quickly when their IP address changes, fixes a few
6491 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
6493 o New directory authorities:
6494 - Take lefkada out of the list of v3 directory authorities, since
6495 it has been down for months.
6496 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
6500 - Detect address changes more quickly on non-directory mirror
6501 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
6503 o Minor features (security):
6504 - Reject requests for reverse-dns lookup of names that are in
6505 a private address space. Patch from lodger.
6506 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
6509 o Minor bugfixes (crashes):
6510 - Avoid a rare assert that can trigger when Tor doesn't have much
6511 directory information yet and it tries to fetch a v2 hidden
6512 service descriptor. Fixes bug 651, reported by nwf.
6513 - Initialize log mutex before initializing dmalloc. Otherwise,
6514 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
6515 - Use recursive pthread mutexes in order to avoid deadlock when
6516 logging debug-level messages to a controller. Bug spotted by nwf,
6517 bugfix on 0.2.0.16-alpha.
6519 o Minor bugfixes (resource management):
6520 - Keep address policies from leaking memory: start their refcount
6521 at 1, not 2. Bugfix on 0.2.0.16-alpha.
6522 - Free authority certificates on exit, so they don't look like memory
6523 leaks. Bugfix on 0.2.0.19-alpha.
6524 - Free static hashtables for policy maps and for TLS connections on
6525 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
6526 - Avoid allocating extra space when computing consensuses on 64-bit
6527 platforms. Bug spotted by aakova.
6529 o Minor bugfixes (misc):
6530 - Do not read the configuration file when we've only been told to
6531 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
6532 based on patch from Sebastian Hahn.
6533 - Exit relays that are used as a client can now reach themselves
6534 using the .exit notation, rather than just launching an infinite
6535 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
6536 - When attempting to open a logfile fails, tell us why.
6537 - Fix a dumb bug that was preventing us from knowing that we should
6538 preemptively build circuits to handle expected directory requests.
6539 Fixes bug 660. Bugfix on 0.1.2.x.
6540 - Warn less verbosely about clock skew from netinfo cells from
6541 untrusted sources. Fixes bug 663.
6542 - Make controller stream events for DNS requests more consistent,
6543 by adding "new stream" events for DNS requests, and removing
6544 spurious "stream closed" events" for cached reverse resolves.
6545 Patch from mwenge. Fixes bug 646.
6546 - Correctly notify one-hop connections when a circuit build has
6547 failed. Possible fix for bug 669. Found by lodger.
6550 Changes in version 0.2.0.23-rc - 2008-03-24
6551 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
6552 makes bootstrapping faster if the first directory mirror you contact
6553 is down. The bundles also include the new Vidalia 0.1.2 release.
6556 - When a tunneled directory request is made to a directory server
6557 that's down, notice after 30 seconds rather than 120 seconds. Also,
6558 fail any begindir streams that are pending on it, so they can
6559 retry elsewhere. This was causing multi-minute delays on bootstrap.
6562 Changes in version 0.2.0.22-rc - 2008-03-18
6563 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
6564 enables encrypted directory connections by default for non-relays, fixes
6565 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
6566 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
6569 - Enable encrypted directory connections by default for non-relays,
6570 so censor tools that block Tor directory connections based on their
6571 plaintext patterns will no longer work. This means Tor works in
6572 certain censored countries by default again.
6575 - Make sure servers always request certificates from clients during
6576 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
6577 - Do not enter a CPU-eating loop when a connection is closed in
6578 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
6579 diagnosed by lodger; bugfix on 0.2.0.20-rc.
6580 - Fix assertion failure that could occur when a blocked circuit
6581 became unblocked, and it had pending client DNS requests. Bugfix
6582 on 0.2.0.1-alpha. Fixes bug 632.
6584 o Minor bugfixes (on 0.1.2.x):
6585 - Generate "STATUS_SERVER" events rather than misspelled
6586 "STATUS_SEVER" events. Caught by mwenge.
6587 - When counting the number of bytes written on a TLS connection,
6588 look at the BIO actually used for writing to the network, not
6589 at the BIO used (sometimes) to buffer data for the network.
6590 Looking at different BIOs could result in write counts on the
6591 order of ULONG_MAX. Fixes bug 614.
6592 - On Windows, correctly detect errors when listing the contents of
6593 a directory. Fix from lodger.
6595 o Minor bugfixes (on 0.2.0.x):
6596 - Downgrade "sslv3 alert handshake failure" message to INFO.
6597 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
6598 left BandwidthRate and BandwidthBurst at the default, we would be
6599 silently limited by those defaults. Now raise them to match the
6600 RelayBandwidth* values.
6601 - Fix the SVK version detection logic to work correctly on a branch.
6602 - Make --enable-openbsd-malloc work correctly on Linux with alpha
6603 CPUs. Fixes bug 625.
6604 - Logging functions now check that the passed severity is sane.
6605 - Use proper log levels in the testsuite call of
6606 get_interface_address6().
6607 - When using a nonstandard malloc, do not use the platform values for
6608 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
6609 - Make the openbsd malloc code use 8k pages on alpha CPUs and
6611 - Detect mismatched page sizes when using --enable-openbsd-malloc.
6612 - Avoid double-marked-for-close warning when certain kinds of invalid
6613 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
6614 for bug 617. Bugfix on 0.2.0.1-alpha.
6615 - Make sure that the "NULL-means-reject *:*" convention is followed by
6616 all the policy manipulation functions, avoiding some possible crash
6617 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
6618 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
6619 actually works, and doesn't warn about every single reverse lookup.
6620 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
6623 - Only log guard node status when guard node status has changed.
6624 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
6625 make "INFO" 75% less verbose.
6628 Changes in version 0.2.0.21-rc - 2008-03-02
6629 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
6630 makes Tor work well with Vidalia again, fixes a rare assert bug,
6631 and fixes a pair of more minor bugs. The bundles also include Vidalia
6632 0.1.0 and Torbutton 1.1.16.
6635 - The control port should declare that it requires password auth
6636 when HashedControlSessionPassword is set too. Patch from Matt Edman;
6637 bugfix on 0.2.0.20-rc. Fixes bug 615.
6638 - Downgrade assert in connection_buckets_decrement() to a log message.
6639 This may help us solve bug 614, and in any case will make its
6640 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
6641 - We were sometimes miscounting the number of bytes read from the
6642 network, causing our rate limiting to not be followed exactly.
6643 Bugfix on 0.2.0.16-alpha. Reported by lodger.
6646 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
6647 OpenSSL versions should have been working fine. Diagnosis and patch
6648 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
6649 Bugfix on 0.2.0.20-rc.
6652 Changes in version 0.2.0.20-rc - 2008-02-24
6653 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
6654 makes more progress towards normalizing Tor's TLS handshake, makes
6655 hidden services work better again, helps relays bootstrap if they don't
6656 know their IP address, adds optional support for linking in openbsd's
6657 allocator or tcmalloc, allows really fast relays to scale past 15000
6658 sockets, and fixes a bunch of minor bugs reported by Veracode.
6661 - Enable the revised TLS handshake based on the one designed by
6662 Steven Murdoch in proposal 124, as revised in proposal 130. It
6663 includes version negotiation for OR connections as described in
6664 proposal 105. The new handshake is meant to be harder for censors
6665 to fingerprint, and it adds the ability to detect certain kinds of
6666 man-in-the-middle traffic analysis attacks. The version negotiation
6667 feature will allow us to improve Tor's link protocol more safely
6669 - Choose which bridge to use proportional to its advertised bandwidth,
6670 rather than uniformly at random. This should speed up Tor for
6671 bridge users. Also do this for people who set StrictEntryNodes.
6672 - When a TrackHostExits-chosen exit fails too many times in a row,
6673 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
6676 - Resolved problems with (re-)fetching hidden service descriptors.
6677 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
6679 - If we only ever used Tor for hidden service lookups or posts, we
6680 would stop building circuits and start refusing connections after
6681 24 hours, since we falsely believed that Tor was dormant. Reported
6682 by nwf; bugfix on 0.1.2.x.
6683 - Servers that don't know their own IP address should go to the
6684 authorities for their first directory fetch, even if their DirPort
6685 is off or if they don't know they're reachable yet. This will help
6686 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
6687 - When counting the number of open sockets, count not only the number
6688 of sockets we have received from the socket() call, but also
6689 the number we've gotten from accept() and socketpair(). This bug
6690 made us fail to count all sockets that we were using for incoming
6691 connections. Bugfix on 0.2.0.x.
6692 - Fix code used to find strings within buffers, when those strings
6693 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
6694 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
6695 - Add a new __HashedControlSessionPassword option for controllers
6696 to use for one-off session password hashes that shouldn't get
6697 saved to disk by SAVECONF --- Vidalia users were accumulating a
6698 pile of HashedControlPassword lines in their torrc files, one for
6699 each time they had restarted Tor and then clicked Save. Make Tor
6700 automatically convert "HashedControlPassword" to this new option but
6701 only when it's given on the command line. Partial fix for bug 586.
6703 o Minor features (performance):
6704 - Tune parameters for cell pool allocation to minimize amount of
6706 - Add OpenBSD malloc code from phk as an optional malloc
6707 replacement on Linux: some glibc libraries do very poorly
6708 with Tor's memory allocation patterns. Pass
6709 --enable-openbsd-malloc to get the replacement malloc code.
6710 - Add a --with-tcmalloc option to the configure script to link
6711 against tcmalloc (if present). Does not yet search for
6712 non-system include paths.
6713 - Stop imposing an arbitrary maximum on the number of file descriptors
6714 used for busy servers. Bug reported by Olaf Selke; patch from
6717 o Minor features (other):
6718 - When SafeLogging is disabled, log addresses along with all TLS
6720 - When building with --enable-gcc-warnings, check for whether Apple's
6721 warning "-Wshorten-64-to-32" is available.
6722 - Add a --passphrase-fd argument to the tor-gencert command for
6725 o Minor bugfixes (memory leaks and code problems):
6726 - We were leaking a file descriptor if Tor started with a zero-length
6727 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
6728 - Detect size overflow in zlib code. Reported by Justin Ferguson and
6730 - We were comparing the raw BridgePassword entry with a base64'ed
6731 version of it, when handling a "/tor/networkstatus-bridges"
6732 directory request. Now compare correctly. Noticed by Veracode.
6733 - Recover from bad tracked-since value in MTBF-history file.
6735 - Alter the code that tries to recover from unhandled write
6736 errors, to not try to flush onto a socket that's given us
6737 unhandled errors. Bugfix on 0.1.2.x.
6738 - Make Unix controlsockets work correctly on OpenBSD. Patch from
6739 tup. Bugfix on 0.2.0.3-alpha.
6741 o Minor bugfixes (other):
6742 - If we have an extra-info document for our server, always make
6743 it available on the control port, even if we haven't gotten
6744 a copy of it from an authority yet. Patch from mwenge.
6745 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
6746 - Directory mirrors no longer include a guess at the client's IP
6747 address if the connection appears to be coming from the same /24
6748 network; it was producing too many wrong guesses.
6749 - Make the new hidden service code respect the SafeLogging setting.
6750 Bugfix on 0.2.0.x. Patch from Karsten.
6751 - When starting as an authority, do not overwrite all certificates
6752 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
6753 - If we're trying to flush the last bytes on a connection (for
6754 example, when answering a directory request), reset the
6755 time-to-give-up timeout every time we manage to write something
6756 on the socket. Bugfix on 0.1.2.x.
6757 - Change the behavior of "getinfo status/good-server-descriptor"
6758 so it doesn't return failure when any authority disappears.
6759 - Even though the man page said that "TrackHostExits ." should
6760 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
6761 - Report TLS "zero return" case as a "clean close" and "IO error"
6762 as a "close". Stop calling closes "unexpected closes": existing
6763 Tors don't use SSL_close(), so having a connection close without
6764 the TLS shutdown handshake is hardly unexpected.
6765 - Send NAMESERVER_STATUS messages for a single failed nameserver
6768 o Code simplifications and refactoring:
6769 - Remove the tor_strpartition function: its logic was confused,
6770 and it was only used for one thing that could be implemented far
6774 Changes in version 0.2.0.19-alpha - 2008-02-09
6775 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
6776 handshake, makes path selection for relays more secure and IP address
6777 guessing more robust, and generally fixes a lot of bugs in preparation
6778 for calling the 0.2.0 branch stable.
6781 - Do not include recognizeable strings in the commonname part of
6782 Tor's x509 certificates.
6785 - If we're a relay, avoid picking ourselves as an introduction point,
6786 a rendezvous point, or as the final hop for internal circuits. Bug
6787 reported by taranis and lodger. Bugfix on 0.1.2.x.
6788 - Patch from "Andrew S. Lists" to catch when we contact a directory
6789 mirror at IP address X and he says we look like we're coming from
6790 IP address X. Bugfix on 0.1.2.x.
6792 o Minor features (security):
6793 - Be more paranoid about overwriting sensitive memory on free(),
6794 as a defensive programming tactic to ensure forward secrecy.
6796 o Minor features (directory authority):
6797 - Actually validate the options passed to AuthDirReject,
6798 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
6799 - Reject router descriptors with out-of-range bandwidthcapacity or
6800 bandwidthburst values.
6802 o Minor features (controller):
6803 - Reject controller commands over 1MB in length. This keeps rogue
6804 processes from running us out of memory.
6806 o Minor features (misc):
6807 - Give more descriptive well-formedness errors for out-of-range
6808 hidden service descriptor/protocol versions.
6809 - Make memory debugging information describe more about history
6810 of cell allocation, so we can help reduce our memory use.
6812 o Deprecated features (controller):
6813 - The status/version/num-versioning and status/version/num-concurring
6814 GETINFO options are no longer useful in the v3 directory protocol:
6815 treat them as deprecated, and warn when they're used.
6818 - When our consensus networkstatus has been expired for a while, stop
6819 being willing to build circuits using it. Fixes bug 401. Bugfix
6821 - Directory caches now fetch certificates from all authorities
6822 listed in a networkstatus consensus, even when they do not
6823 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
6824 - When connecting to a bridge without specifying its key, insert
6825 the connection into the identity-to-connection map as soon as
6826 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
6827 - Detect versions of OS X where malloc_good_size() is present in the
6828 library but never actually declared. Resolves bug 587. Bugfix
6830 - Stop incorrectly truncating zlib responses to directory authority
6831 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
6832 - Stop recommending that every server operator send mail to tor-ops.
6833 Resolves bug 597. Bugfix on 0.1.2.x.
6834 - Don't trigger an assert if we start a directory authority with a
6835 private IP address (like 127.0.0.1).
6836 - Avoid possible failures when generating a directory with routers
6837 with over-long versions strings, or too many flags set. Bugfix
6839 - If an attempt to launch a DNS resolve request over the control
6840 port fails because we have overrun the limit on the number of
6841 connections, tell the controller that the request has failed.
6842 - Avoid using too little bandwidth when our clock skips a few
6843 seconds. Bugfix on 0.1.2.x.
6844 - Fix shell error when warning about missing packages in configure
6845 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
6846 - Do not become confused when receiving a spurious VERSIONS-like
6847 cell from a confused v1 client. Bugfix on 0.2.0.x.
6848 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
6849 introduction points for a hidden service have failed. Patch from
6850 Karsten Loesing. Bugfix on 0.2.0.x.
6852 o Code simplifications and refactoring:
6853 - Remove some needless generality from cpuworker code, for improved
6855 - Stop overloading the circuit_t.onionskin field for both "onionskin
6856 from a CREATE cell that we are waiting for a cpuworker to be
6857 assigned" and "onionskin from an EXTEND cell that we are going to
6858 send to an OR as soon as we are connected". Might help with bug 600.
6859 - Add an in-place version of aes_crypt() so that we can avoid doing a
6860 needless memcpy() call on each cell payload.
6863 Changes in version 0.2.0.18-alpha - 2008-01-25
6864 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
6865 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
6866 that can warn or reject connections to ports generally associated with
6867 vulnerable-plaintext protocols.
6869 o New directory authorities:
6870 - Set up dannenberg (run by CCC) as the sixth v3 directory
6874 - Fix a major memory leak when attempting to use the v2 TLS
6875 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
6876 - We accidentally enabled the under-development v2 TLS handshake
6877 code, which was causing log entries like "TLS error while
6878 renegotiating handshake". Disable it again. Resolves bug 590.
6879 - We were computing the wrong Content-Length: header for directory
6880 responses that need to be compressed on the fly, causing clients
6881 asking for those items to always fail. Bugfix on 0.2.0.x; partially
6885 - Avoid going directly to the directory authorities even if you're a
6886 relay, if you haven't found yourself reachable yet or if you've
6887 decided not to advertise your dirport yet. Addresses bug 556.
6888 - If we've gone 12 hours since our last bandwidth check, and we
6889 estimate we have less than 50KB bandwidth capacity but we could
6890 handle more, do another bandwidth test.
6891 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
6892 Tor can warn and/or refuse connections to ports commonly used with
6893 vulnerable-plaintext protocols. Currently we warn on ports 23,
6894 109, 110, and 143, but we don't reject any.
6897 - When we setconf ClientOnly to 1, close any current OR and Dir
6898 listeners. Reported by mwenge.
6899 - When we get a consensus that's been signed by more people than
6900 we expect, don't log about it; it's not a big deal. Reported
6904 - Don't answer "/tor/networkstatus-bridges" directory requests if
6905 the request isn't encrypted.
6906 - Make "ClientOnly 1" config option disable directory ports too.
6907 - Patches from Karsten Loesing to make v2 hidden services more
6908 robust: work even when there aren't enough HSDir relays available;
6909 retry when a v2 rend desc fetch fails; but don't retry if we
6910 already have a usable v0 rend desc.
6913 Changes in version 0.2.0.17-alpha - 2008-01-17
6914 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
6917 - Make the tor-gencert man page get included correctly in the tarball.
6920 Changes in version 0.2.0.16-alpha - 2008-01-17
6921 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
6922 Loesing, and generally cleans up a lot of features and minor bugs.
6924 o New directory authorities:
6925 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
6928 o Major performance improvements:
6929 - Switch our old ring buffer implementation for one more like that
6930 used by free Unix kernels. The wasted space in a buffer with 1mb
6931 of data will now be more like 8k than 1mb. The new implementation
6932 also avoids realloc();realloc(); patterns that can contribute to
6933 memory fragmentation.
6936 - Configuration files now accept C-style strings as values. This
6937 helps encode characters not allowed in the current configuration
6938 file format, such as newline or #. Addresses bug 557.
6939 - Although we fixed bug 539 (where servers would send HTTP status 503
6940 responses _and_ send a body too), there are still servers out
6941 there that haven't upgraded. Therefore, make clients parse such
6942 bodies when they receive them.
6943 - When we're not serving v2 directory information, there is no reason
6944 to actually keep any around. Remove the obsolete files and directory
6945 on startup if they are very old and we aren't going to serve them.
6947 o Minor performance improvements:
6948 - Reference-count and share copies of address policy entries; only 5%
6949 of them were actually distinct.
6950 - Never walk through the list of logs if we know that no log is
6951 interested in a given message.
6954 - When an authority has not signed a consensus, do not try to
6955 download a nonexistent "certificate with key 00000000". Bugfix
6956 on 0.2.0.x. Fixes bug 569.
6957 - Fix a rare assert error when we're closing one of our threads:
6958 use a mutex to protect the list of logs, so we never write to the
6959 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
6960 bug 575, which is kind of the revenge of bug 222.
6961 - Patch from Karsten Loesing to complain less at both the client
6962 and the relay when a relay used to have the HSDir flag but doesn't
6963 anymore, and we try to upload a hidden service descriptor.
6964 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
6966 - Do not try to download missing certificates until we have tried
6967 to check our fallback consensus. Fixes bug 583.
6968 - Make bridges round reported GeoIP stats info up to the nearest
6969 estimate, not down. Now we can distinguish between "0 people from
6970 this country" and "1 person from this country".
6971 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
6972 - Avoid possible segfault if key generation fails in
6973 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
6974 - Avoid segfault in the case where a badly behaved v2 versioning
6975 directory sends a signed networkstatus with missing client-versions.
6977 - Avoid segfaults on certain complex invocations of
6978 router_get_by_hexdigest(). Bugfix on 0.1.2.
6979 - Correct bad index on array access in parse_http_time(). Bugfix
6981 - Fix possible bug in vote generation when server versions are present
6982 but client versions are not.
6983 - Fix rare bug on REDIRECTSTREAM control command when called with no
6984 port set: it could erroneously report an error when none had
6986 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
6987 compressing large objects and find ourselves with more than 4k
6988 left over. Bugfix on 0.2.0.
6989 - Fix a small memory leak when setting up a hidden service.
6990 - Fix a few memory leaks that could in theory happen under bizarre
6992 - Fix an assert if we post a general-purpose descriptor via the
6993 control port but that descriptor isn't mentioned in our current
6994 network consensus. Bug reported by Jon McLachlan; bugfix on
6997 o Minor features (controller):
6998 - Get NS events working again. Patch from tup.
6999 - The GETCONF command now escapes and quotes configuration values
7000 that don't otherwise fit into the torrc file.
7001 - The SETCONF command now handles quoted values correctly.
7003 o Minor features (directory authorities):
7004 - New configuration options to override default maximum number of
7005 servers allowed on a single IP address. This is important for
7006 running a test network on a single host.
7007 - Actually implement the -s option to tor-gencert.
7008 - Add a manual page for tor-gencert.
7010 o Minor features (bridges):
7011 - Bridge authorities no longer serve bridge descriptors over
7012 unencrypted connections.
7014 o Minor features (other):
7015 - Add hidden services and DNSPorts to the list of things that make
7016 Tor accept that it has running ports. Change starting Tor with no
7017 ports from a fatal error to a warning; we might change it back if
7018 this turns out to confuse anybody. Fixes bug 579.
7021 Changes in version 0.1.2.19 - 2008-01-17
7022 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7023 exit policy a little bit more conservative so it's safer to run an
7024 exit relay on a home system, and fixes a variety of smaller issues.
7027 - Exit policies now reject connections that are addressed to a
7028 relay's public (external) IP address too, unless
7029 ExitPolicyRejectPrivate is turned off. We do this because too
7030 many relays are running nearby to services that trust them based
7034 - When the clock jumps forward a lot, do not allow the bandwidth
7035 buckets to become negative. Fixes bug 544.
7036 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7037 on every successful resolve. Reported by Mike Perry.
7038 - Purge old entries from the "rephist" database and the hidden
7039 service descriptor database even when DirPort is zero.
7040 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7041 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7042 crashing or mis-answering these requests.
7043 - When we decide to send a 503 response to a request for servers, do
7044 not then also send the server descriptors: this defeats the whole
7045 purpose. Fixes bug 539.
7048 - Changing the ExitPolicyRejectPrivate setting should cause us to
7049 rebuild our server descriptor.
7050 - Fix handling of hex nicknames when answering controller requests for
7051 networkstatus by name, or when deciding whether to warn about
7052 unknown routers in a config option. (Patch from mwenge.)
7053 - Fix a couple of hard-to-trigger autoconf problems that could result
7054 in really weird results on platforms whose sys/types.h files define
7055 nonstandard integer types.
7056 - Don't try to create the datadir when running --verify-config or
7057 --hash-password. Resolves bug 540.
7058 - If we were having problems getting a particular descriptor from the
7059 directory caches, and then we learned about a new descriptor for
7060 that router, we weren't resetting our failure count. Reported
7062 - Although we fixed bug 539 (where servers would send HTTP status 503
7063 responses _and_ send a body too), there are still servers out there
7064 that haven't upgraded. Therefore, make clients parse such bodies
7065 when they receive them.
7066 - Run correctly on systems where rlim_t is larger than unsigned long.
7067 This includes some 64-bit systems.
7068 - Run correctly on platforms (like some versions of OS X 10.5) where
7069 the real limit for number of open files is OPEN_FILES, not rlim_max
7070 from getrlimit(RLIMIT_NOFILES).
7071 - Avoid a spurious free on base64 failure.
7072 - Avoid segfaults on certain complex invocations of
7073 router_get_by_hexdigest().
7074 - Fix rare bug on REDIRECTSTREAM control command when called with no
7075 port set: it could erroneously report an error when none had
7079 Changes in version 0.2.0.15-alpha - 2007-12-25
7080 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7081 features added in 0.2.0.13-alpha.
7084 - Fix several remotely triggerable asserts based on DirPort requests
7085 for a v2 or v3 networkstatus object before we were prepared. This
7086 was particularly bad for 0.2.0.13 and later bridge relays, who
7087 would never have a v2 networkstatus and would thus always crash
7088 when used. Bugfixes on 0.2.0.x.
7089 - Estimate the v3 networkstatus size more accurately, rather than
7090 estimating it at zero bytes and giving it artificially high priority
7091 compared to other directory requests. Bugfix on 0.2.0.x.
7094 - Fix configure.in logic for cross-compilation.
7095 - When we load a bridge descriptor from the cache, and it was
7096 previously unreachable, mark it as retriable so we won't just
7097 ignore it. Also, try fetching a new copy immediately. Bugfixes
7099 - The bridge GeoIP stats were counting other relays, for example
7100 self-reachability and authority-reachability tests.
7103 - Support compilation to target iPhone; patch from cjacker huang.
7104 To build for iPhone, pass the --enable-iphone option to configure.
7107 Changes in version 0.2.0.14-alpha - 2007-12-23
7109 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7110 without a datadirectory from a previous Tor install. Reported
7112 - Fix a crash when we fetch a descriptor that turns out to be
7113 unexpected (it used to be in our networkstatus when we started
7114 fetching it, but it isn't in our current networkstatus), and we
7115 aren't using bridges. Bugfix on 0.2.0.x.
7116 - Fix a crash when accessing hidden services: it would work the first
7117 time you use a given introduction point for your service, but
7118 on subsequent requests we'd be using garbage memory. Fixed by
7119 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7120 - Fix a crash when we load a bridge descriptor from disk but we don't
7121 currently have a Bridge line for it in our torrc. Bugfix on
7125 - If bridge authorities set BridgePassword, they will serve a
7126 snapshot of known bridge routerstatuses from their DirPort to
7127 anybody who knows that password. Unset by default.
7130 - Make the unit tests build again.
7131 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7132 - Make PublishServerDescriptor default to 1, so the default doesn't
7133 have to change as we invent new directory protocol versions.
7134 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7135 be included unless sys/time.h is already included. Fixes
7136 bug 553. Bugfix on 0.2.0.x.
7137 - If we receive a general-purpose descriptor and then receive an
7138 identical bridge-purpose descriptor soon after, don't discard
7139 the next one as a duplicate.
7142 - If BridgeRelay is set to 1, then the default for
7143 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7144 - If the user sets RelayBandwidthRate but doesn't set
7145 RelayBandwidthBurst, then make them equal rather than erroring out.
7148 Changes in version 0.2.0.13-alpha - 2007-12-21
7149 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7150 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7153 o New directory authorities:
7154 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7158 - Only update guard status (usable / not usable) once we have
7159 enough directory information. This was causing us to always pick
7160 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7161 causing us to discard all our guards on startup if we hadn't been
7162 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7163 - Purge old entries from the "rephist" database and the hidden
7164 service descriptor databases even when DirPort is zero. Bugfix
7166 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7167 after opening a circuit -- even a relayed circuit. Bugfix on
7169 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7170 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7171 crashing or mis-answering these types of requests.
7172 - Relays were publishing their server descriptor to v1 and v2
7173 directory authorities, but they didn't try publishing to v3-only
7174 authorities. Fix this; and also stop publishing to v1 authorities.
7176 - When we were reading router descriptors from cache, we were ignoring
7177 the annotations -- so for example we were reading in bridge-purpose
7178 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7179 - When we decided to send a 503 response to a request for servers, we
7180 were then also sending the server descriptors: this defeats the
7181 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7184 - Bridge relays now behave like clients with respect to time
7185 intervals for downloading new consensus documents -- otherwise they
7186 stand out. Bridge users now wait until the end of the interval,
7187 so their bridge relay will be sure to have a new consensus document.
7188 - Three new config options (AlternateDirAuthority,
7189 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7190 user selectively replace the default directory authorities by type,
7191 rather than the all-or-nothing replacement that DirServer offers.
7192 - Tor can now be configured to read a GeoIP file from disk in one
7193 of two formats. This can be used by controllers to map IP addresses
7194 to countries. Eventually, it may support exit-by-country.
7195 - When possible, bridge relays remember which countries users
7196 are coming from, and report aggregate information in their
7197 extra-info documents, so that the bridge authorities can learn
7198 where Tor is blocked.
7199 - Bridge directory authorities now do reachability testing on the
7200 bridges they know. They provide router status summaries to the
7201 controller via "getinfo ns/purpose/bridge", and also dump summaries
7202 to a file periodically.
7203 - Stop fetching directory info so aggressively if your DirPort is
7204 on but your ORPort is off; stop fetching v2 dir info entirely.
7205 You can override these choices with the new FetchDirInfoEarly
7209 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7210 consensus documents when there are too many relays at a single
7211 IP address. Now clear it in v2 network status documents too, and
7212 also clear it in routerinfo_t when the relay is no longer listed
7213 in the relevant networkstatus document.
7214 - Don't crash if we get an unexpected value for the
7215 PublishServerDescriptor config option. Reported by Matt Edman;
7216 bugfix on 0.2.0.9-alpha.
7217 - Our new v2 hidden service descriptor format allows descriptors
7218 that have no introduction points. But Tor crashed when we tried
7219 to build a descriptor with no intro points (and it would have
7220 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7222 - Fix building with dmalloc 5.5.2 with glibc.
7223 - Reject uploaded descriptors and extrainfo documents if they're
7224 huge. Otherwise we'll cache them all over the network and it'll
7225 clog everything up. Reported by Aljosha Judmayer.
7226 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7227 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7228 - When the DANGEROUS_VERSION controller status event told us we're
7229 running an obsolete version, it used the string "OLD" to describe
7230 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7231 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7232 - If we can't expand our list of entry guards (e.g. because we're
7233 using bridges or we have StrictEntryNodes set), don't mark relays
7234 down when they fail a directory request. Otherwise we're too quick
7235 to mark all our entry points down. Bugfix on 0.1.2.x.
7236 - Fix handling of hex nicknames when answering controller requests for
7237 networkstatus by name, or when deciding whether to warn about unknown
7238 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
7239 - Fix a couple of hard-to-trigger autoconf problems that could result
7240 in really weird results on platforms whose sys/types.h files define
7241 nonstandard integer types. Bugfix on 0.1.2.x.
7242 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
7243 - Don't crash on name lookup when we have no current consensus. Fixes
7244 bug 538; bugfix on 0.2.0.x.
7245 - Only Tors that want to mirror the v2 directory info should
7246 create the "cached-status" directory in their datadir. (All Tors
7247 used to create it.) Bugfix on 0.2.0.9-alpha.
7248 - Directory authorities should only automatically download Extra Info
7249 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
7252 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7253 consumers. (We already do this on HUP.)
7254 - Authorities and caches fetch the v2 networkstatus documents
7255 less often, now that v3 is encouraged.
7256 - Add a new config option BridgeRelay that specifies you want to
7257 be a bridge relay. Right now the only difference is that it makes
7258 you answer begin_dir requests, and it makes you cache dir info,
7259 even if your DirPort isn't on.
7260 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7261 ask about source, timestamp of arrival, purpose, etc. We need
7262 something like this to help Vidalia not do GeoIP lookups on bridge
7264 - Allow multiple HashedControlPassword config lines, to support
7265 multiple controller passwords.
7266 - Authorities now decide whether they're authoritative for a given
7267 router based on the router's purpose.
7268 - New config options AuthDirBadDir and AuthDirListBadDirs for
7269 authorities to mark certain relays as "bad directories" in the
7270 networkstatus documents. Also supports the "!baddir" directive in
7271 the approved-routers file.
7274 Changes in version 0.2.0.12-alpha - 2007-11-16
7275 This twelfth development snapshot fixes some more build problems as
7276 well as a few minor bugs.
7279 - Make it build on OpenBSD again. Patch from tup.
7280 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
7281 package-building for Red Hat, OS X, etc.
7283 o Minor bugfixes (on 0.1.2.x):
7284 - Changing the ExitPolicyRejectPrivate setting should cause us to
7285 rebuild our server descriptor.
7287 o Minor bugfixes (on 0.2.0.x):
7288 - When we're lacking a consensus, don't try to perform rendezvous
7289 operations. Reported by Karsten Loesing.
7290 - Fix a small memory leak whenever we decide against using a
7291 newly picked entry guard. Reported by Mike Perry.
7292 - When authorities detected more than two relays running on the same
7293 IP address, they were clearing all the status flags but forgetting
7294 to clear the "hsdir" flag. So clients were being told that a
7295 given relay was the right choice for a v2 hsdir lookup, yet they
7296 never had its descriptor because it was marked as 'not running'
7298 - If we're trying to fetch a bridge descriptor and there's no way
7299 the bridge authority could help us (for example, we don't know
7300 a digest, or there is no bridge authority), don't be so eager to
7301 fall back to asking the bridge authority.
7302 - If we're using bridges or have strictentrynodes set, and our
7303 chosen exit is in the same family as all our bridges/entry guards,
7304 then be flexible about families.
7307 - When we negotiate a v2 link-layer connection (not yet implemented),
7308 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7309 negotiated a v1 connection for their next step. Initial code for
7313 Changes in version 0.2.0.11-alpha - 2007-11-12
7314 This eleventh development snapshot fixes some build problems with
7315 the previous snapshot. It also includes a more secure-by-default exit
7316 policy for relays, fixes an enormous memory leak for exit relays, and
7317 fixes another bug where servers were falling out of the directory list.
7320 - Exit policies now reject connections that are addressed to a
7321 relay's public (external) IP address too, unless
7322 ExitPolicyRejectPrivate is turned off. We do this because too
7323 many relays are running nearby to services that trust them based
7324 on network address. Bugfix on 0.1.2.x.
7327 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7328 on every successful resolve. Reported by Mike Perry; bugfix
7330 - On authorities, never downgrade to old router descriptors simply
7331 because they're listed in the consensus. This created a catch-22
7332 where we wouldn't list a new descriptor because there was an
7333 old one in the consensus, and we couldn't get the new one in the
7334 consensus because we wouldn't list it. Possible fix for bug 548.
7335 Also, this might cause bug 543 to appear on authorities; if so,
7336 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
7338 o Packaging fixes on 0.2.0.10-alpha:
7339 - We were including instructions about what to do with the
7340 src/config/fallback-consensus file, but we weren't actually
7341 including it in the tarball. Disable all of that for now.
7344 - Allow people to say PreferTunnelledDirConns rather than
7345 PreferTunneledDirConns, for those alternate-spellers out there.
7348 - Don't reevaluate all the information from our consensus document
7349 just because we've downloaded a v2 networkstatus that we intend
7350 to cache. Fixes bug 545; bugfix on 0.2.0.x.
7353 Changes in version 0.2.0.10-alpha - 2007-11-10
7354 This tenth development snapshot adds a third v3 directory authority
7355 run by Mike Perry, adds most of Karsten Loesing's new hidden service
7356 descriptor format, fixes a bad crash bug and new bridge bugs introduced
7357 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
7358 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
7359 addresses many more minor issues.
7361 o New directory authorities:
7362 - Set up ides (run by Mike Perry) as the third v3 directory authority.
7365 - Allow tunnelled directory connections to ask for an encrypted
7366 "begin_dir" connection or an anonymized "uses a full Tor circuit"
7367 connection independently. Now we can make anonymized begin_dir
7368 connections for (e.g.) more secure hidden service posting and
7370 - More progress on proposal 114: code from Karsten Loesing to
7371 implement new hidden service descriptor format.
7372 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
7373 accommodate the growing number of servers that use the default
7374 and are reaching it.
7375 - Directory authorities use a new formula for selecting which nodes
7376 to advertise as Guards: they must be in the top 7/8 in terms of
7377 how long we have known about them, and above the median of those
7378 nodes in terms of weighted fractional uptime.
7379 - Make "not enough dir info yet" warnings describe *why* Tor feels
7380 it doesn't have enough directory info yet.
7383 - Stop servers from crashing if they set a Family option (or
7384 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
7386 - Make bridge users work again -- the move to v3 directories in
7387 0.2.0.9-alpha had introduced a number of bugs that made bridges
7388 no longer work for clients.
7389 - When the clock jumps forward a lot, do not allow the bandwidth
7390 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
7392 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
7393 - When the consensus lists a router descriptor that we previously were
7394 mirroring, but that we considered non-canonical, reload the
7395 descriptor as canonical. This fixes bug 543 where Tor servers
7396 would start complaining after a few days that they don't have
7397 enough directory information to build a circuit.
7398 - Consider replacing the current consensus when certificates arrive
7399 that make the pending consensus valid. Previously, we were only
7400 considering replacement when the new certs _didn't_ help.
7401 - Fix an assert error on startup if we didn't already have the
7402 consensus and certs cached in our datadirectory: we were caching
7403 the consensus in consensus_waiting_for_certs but then free'ing it
7405 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
7406 Request) if we need more v3 certs but we've already got pending
7407 requests for all of them.
7408 - Correctly back off from failing certificate downloads. Fixes
7410 - Authorities don't vote on the Running flag if they have been running
7411 for less than 30 minutes themselves. Fixes bug 547, where a newly
7412 started authority would vote that everyone was down.
7415 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7416 it, it had no AES, and it hasn't seen any security patches since
7420 - Clients now hold circuitless TLS connections open for 1.5 times
7421 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
7422 rebuild a new circuit over them within that timeframe. Previously,
7423 they held them open only for KeepalivePeriod (5 minutes).
7424 - Use "If-Modified-Since" to avoid retrieving consensus
7425 networkstatuses that we already have.
7426 - When we have no consensus, check FallbackNetworkstatusFile (defaults
7427 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
7428 we start knowing some directory caches.
7429 - When we receive a consensus from the future, warn about skew.
7430 - Improve skew reporting: try to give the user a better log message
7431 about how skewed they are, and how much this matters.
7432 - When we have a certificate for an authority, believe that
7433 certificate's claims about the authority's IP address.
7434 - New --quiet command-line option to suppress the default console log.
7435 Good in combination with --hash-password.
7436 - Authorities send back an X-Descriptor-Not-New header in response to
7437 an accepted-but-discarded descriptor upload. Partially implements
7439 - Make the log message for "tls error. breaking." more useful.
7440 - Better log messages about certificate downloads, to attempt to
7441 track down the second incarnation of bug 546.
7443 o Minor features (bridges):
7444 - If bridge users set UpdateBridgesFromAuthority, but the digest
7445 they ask for is a 404 from the bridge authority, they now fall
7446 back to trying the bridge directly.
7447 - Bridges now use begin_dir to publish their server descriptor to
7448 the bridge authority, even when they haven't set TunnelDirConns.
7450 o Minor features (controller):
7451 - When reporting clock skew, and we know that the clock is _at least
7452 as skewed_ as some value, but we don't know the actual value,
7453 report the value as a "minimum skew."
7456 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7457 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7461 - Refuse to start if both ORPort and UseBridges are set. Bugfix
7462 on 0.2.0.x, suggested by Matt Edman.
7463 - Don't stop fetching descriptors when FetchUselessDescriptors is
7464 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
7465 reported by tup and ioerror.
7466 - Better log message on vote from unknown authority.
7467 - Don't log "Launching 0 request for 0 router" message.
7469 o Minor bugfixes (memory leaks):
7470 - Stop leaking memory every time we parse a v3 certificate. Bugfix
7472 - Stop leaking memory every time we load a v3 certificate. Bugfix
7473 on 0.2.0.1-alpha. Fixes bug 536.
7474 - Stop leaking a cached networkstatus on exit. Bugfix on
7476 - Stop leaking voter information every time we free a consensus.
7477 Bugfix on 0.2.0.3-alpha.
7478 - Stop leaking signed data every time we check a voter signature.
7479 Bugfix on 0.2.0.3-alpha.
7480 - Stop leaking a signature every time we fail to parse a consensus or
7481 a vote. Bugfix on 0.2.0.3-alpha.
7482 - Stop leaking v2_download_status_map on shutdown. Bugfix on
7484 - Stop leaking conn->nickname every time we make a connection to a
7485 Tor relay without knowing its expected identity digest (e.g. when
7486 using bridges). Bugfix on 0.2.0.3-alpha.
7488 - Minor bugfixes (portability):
7489 - Run correctly on platforms where rlim_t is larger than unsigned
7490 long, and/or where the real limit for number of open files is
7491 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
7492 particular, these may be needed for OS X 10.5.
7495 Changes in version 0.1.2.18 - 2007-10-28
7496 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7497 hidden service introduction that were causing huge delays, and a big
7498 bug that was causing some servers to disappear from the network status
7499 lists for a few hours each day.
7501 o Major bugfixes (crashes):
7502 - If a connection is shut down abruptly because of something that
7503 happened inside connection_flushed_some(), do not call
7504 connection_finished_flushing(). Should fix bug 451:
7505 "connection_stop_writing: Assertion conn->write_event failed"
7506 Bugfix on 0.1.2.7-alpha.
7507 - Fix possible segfaults in functions called from
7508 rend_process_relay_cell().
7510 o Major bugfixes (hidden services):
7511 - Hidden services were choosing introduction points uniquely by
7512 hexdigest, but when constructing the hidden service descriptor
7513 they merely wrote the (potentially ambiguous) nickname.
7514 - Clients now use the v2 intro format for hidden service
7515 connections: they specify their chosen rendezvous point by identity
7516 digest rather than by (potentially ambiguous) nickname. These
7517 changes could speed up hidden service connections dramatically.
7519 o Major bugfixes (other):
7520 - Stop publishing a new server descriptor just because we get a
7521 HUP signal. This led (in a roundabout way) to some servers getting
7522 dropped from the networkstatus lists for a few hours each day.
7523 - When looking for a circuit to cannibalize, consider family as well
7524 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7525 circuit cannibalization).
7526 - When a router wasn't listed in a new networkstatus, we were leaving
7527 the flags for that router alone -- meaning it remained Named,
7528 Running, etc -- even though absence from the networkstatus means
7529 that it shouldn't be considered to exist at all anymore. Now we
7530 clear all the flags for routers that fall out of the networkstatus
7531 consensus. Fixes bug 529.
7534 - Don't try to access (or alter) the state file when running
7535 --list-fingerprint or --verify-config or --hash-password. Resolves
7537 - When generating information telling us how to extend to a given
7538 router, do not try to include the nickname if it is
7539 absent. Resolves bug 467.
7540 - Fix a user-triggerable segfault in expand_filename(). (There isn't
7541 a way to trigger this remotely.)
7542 - When sending a status event to the controller telling it that an
7543 OR address is reachable, set the port correctly. (Previously we
7544 were reporting the dir port.)
7545 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7546 command. Bugfix on 0.1.2.17.
7547 - When loading bandwidth history, do not believe any information in
7548 the future. Fixes bug 434.
7549 - When loading entry guard information, do not believe any information
7551 - When we have our clock set far in the future and generate an
7552 onion key, then re-set our clock to be correct, we should not stop
7553 the onion key from getting rotated.
7554 - On some platforms, accept() can return a broken address. Detect
7555 this more quietly, and deal accordingly. Fixes bug 483.
7556 - It's not actually an error to find a non-pending entry in the DNS
7557 cache when canceling a pending resolve. Don't log unless stuff
7558 is fishy. Resolves bug 463.
7559 - Don't reset trusted dir server list when we set a configuration
7560 option. Patch from Robert Hogan.
7561 - Don't try to create the datadir when running --verify-config or
7562 --hash-password. Resolves bug 540.
7565 Changes in version 0.2.0.9-alpha - 2007-10-24
7566 This ninth development snapshot switches clients to the new v3 directory
7567 system; allows servers to be listed in the network status even when they
7568 have the same nickname as a registered server; and fixes many other
7569 bugs including a big one that was causing some servers to disappear
7570 from the network status lists for a few hours each day.
7572 o Major features (directory system):
7573 - Clients now download v3 consensus networkstatus documents instead
7574 of v2 networkstatus documents. Clients and caches now base their
7575 opinions about routers on these consensus documents. Clients only
7576 download router descriptors listed in the consensus.
7577 - Authorities now list servers who have the same nickname as
7578 a different named server, but list them with a new flag,
7579 "Unnamed". Now we can list servers that happen to pick the same
7580 nickname as a server that registered two years ago and then
7581 disappeared. Partially implements proposal 122.
7582 - If the consensus lists a router as "Unnamed", the name is assigned
7583 to a different router: do not identify the router by that name.
7584 Partially implements proposal 122.
7585 - Authorities can now come to a consensus on which method to use to
7586 compute the consensus. This gives us forward compatibility.
7589 - Stop publishing a new server descriptor just because we HUP or
7590 when we find our DirPort to be reachable but won't actually publish
7591 it. New descriptors without any real changes are dropped by the
7592 authorities, and can screw up our "publish every 18 hours" schedule.
7594 - When a router wasn't listed in a new networkstatus, we were leaving
7595 the flags for that router alone -- meaning it remained Named,
7596 Running, etc -- even though absence from the networkstatus means
7597 that it shouldn't be considered to exist at all anymore. Now we
7598 clear all the flags for routers that fall out of the networkstatus
7599 consensus. Fixes bug 529; bugfix on 0.1.2.x.
7600 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
7601 extrainfo documents and then discard them immediately for not
7602 matching the latest router. Bugfix on 0.2.0.1-alpha.
7604 o Minor features (v3 directory protocol):
7605 - Allow tor-gencert to generate a new certificate without replacing
7607 - Allow certificates to include an address.
7608 - When we change our directory-cache settings, reschedule all voting
7609 and download operations.
7610 - Reattempt certificate downloads immediately on failure, as long as
7611 we haven't failed a threshold number of times yet.
7612 - Delay retrying consensus downloads while we're downloading
7613 certificates to verify the one we just got. Also, count getting a
7614 consensus that we already have (or one that isn't valid) as a failure,
7615 and count failing to get the certificates after 20 minutes as a
7617 - Build circuits and download descriptors even if our consensus is a
7618 little expired. (This feature will go away once authorities are
7621 o Minor features (router descriptor cache):
7622 - If we find a cached-routers file that's been sitting around for more
7623 than 28 days unmodified, then most likely it's a leftover from
7624 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
7626 - When we (as a cache) download a descriptor because it was listed
7627 in a consensus, remember when the consensus was supposed to expire,
7628 and don't expire the descriptor until then.
7630 o Minor features (performance):
7631 - Call routerlist_remove_old_routers() much less often. This should
7632 speed startup, especially on directory caches.
7633 - Don't try to launch new descriptor downloads quite so often when we
7634 already have enough directory information to build circuits.
7635 - Base64 decoding was actually showing up on our profile when parsing
7636 the initial descriptor file; switch to an in-process all-at-once
7637 implementation that's about 3.5x times faster than calling out to
7640 o Minor features (compilation):
7641 - Detect non-ASCII platforms (if any still exist) and refuse to
7642 build there: some of our code assumes that 'A' is 65 and so on.
7644 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
7645 - Make the "next period" votes into "current period" votes immediately
7646 after publishing the consensus; avoid a heisenbug that made them
7647 stick around indefinitely.
7648 - When we discard a vote as a duplicate, do not report this as
7650 - Treat missing v3 keys or certificates as an error when running as a
7651 v3 directory authority.
7652 - When we're configured to be a v3 authority, but we're only listed
7653 as a non-v3 authority in our DirServer line for ourself, correct
7655 - If an authority doesn't have a qualified hostname, just put
7656 its address in the vote. This fixes the problem where we referred to
7657 "moria on moria:9031."
7658 - Distinguish between detached signatures for the wrong period, and
7659 detached signatures for a divergent vote.
7660 - Fix a small memory leak when computing a consensus.
7661 - When there's no concensus, we were forming a vote every 30
7662 minutes, but writing the "valid-after" line in our vote based
7663 on our configured V3AuthVotingInterval: so unless the intervals
7664 matched up, we immediately rejected our own vote because it didn't
7665 start at the voting interval that caused us to construct a vote.
7667 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
7668 - Delete unverified-consensus when the real consensus is set.
7669 - Consider retrying a consensus networkstatus fetch immediately
7670 after one fails: don't wait 60 seconds to notice.
7671 - When fetching a consensus as a cache, wait until a newer consensus
7672 should exist before trying to replace the current one.
7673 - Use a more forgiving schedule for retrying failed consensus
7674 downloads than for other types.
7676 o Minor bugfixes (other directory issues):
7677 - Correct the implementation of "download votes by digest." Bugfix on
7679 - Authorities no longer send back "400 you're unreachable please fix
7680 it" errors to Tor servers that aren't online all the time. We're
7681 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
7683 o Minor bugfixes (controller):
7684 - Don't reset trusted dir server list when we set a configuration
7685 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
7686 - Respond to INT and TERM SIGNAL commands before we execute the
7687 signal, in case the signal shuts us down. We had a patch in
7688 0.1.2.1-alpha that tried to do this by queueing the response on
7689 the connection's buffer before shutting down, but that really
7690 isn't the same thing at all. Bug located by Matt Edman.
7692 o Minor bugfixes (misc):
7693 - Correctly check for bad options to the "PublishServerDescriptor"
7694 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
7695 - Stop leaking memory on failing case of base32_decode, and make
7696 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
7697 - Don't try to download extrainfo documents when we're trying to
7698 fetch enough directory info to build a circuit: having enough
7699 info should get priority. Bugfix on 0.2.0.x.
7700 - Don't complain that "your server has not managed to confirm that its
7701 ports are reachable" if we haven't been able to build any circuits
7702 yet. Bug found by spending four hours without a v3 consensus. Bugfix
7704 - Detect the reason for failing to mmap a descriptor file we just
7705 wrote, and give a more useful log message. Fixes bug 533. Bugfix
7708 o Code simplifications and refactoring:
7709 - Remove support for the old bw_accounting file: we've been storing
7710 bandwidth accounting information in the state file since
7711 0.1.2.5-alpha. This may result in bandwidth accounting errors
7712 if you try to upgrade from 0.1.1.x or earlier, or if you try to
7713 downgrade to 0.1.1.x or earlier.
7714 - New convenience code to locate a file within the DataDirectory.
7715 - Move non-authority functionality out of dirvote.c.
7716 - Refactor the arguments for router_pick_{directory_|trusteddir}server
7717 so that they all take the same named flags.
7720 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
7721 Unix users an easy way to script their Tor process (e.g. by
7722 adjusting bandwidth based on the time of the day).
7725 Changes in version 0.2.0.8-alpha - 2007-10-12
7726 This eighth development snapshot fixes a crash bug that's been bothering
7727 us since February 2007, lets bridge authorities store a list of bridge
7728 descriptors they've seen, gets v3 directory voting closer to working,
7729 starts caching v3 directory consensus documents on directory mirrors,
7730 and fixes a variety of smaller issues including some minor memory leaks.
7732 o Major features (router descriptor cache):
7733 - Store routers in a file called cached-descriptors instead of in
7734 cached-routers. Initialize cached-descriptors from cached-routers
7735 if the old format is around. The new format allows us to store
7736 annotations along with descriptors.
7737 - Use annotations to record the time we received each descriptor, its
7738 source, and its purpose.
7739 - Disable the SETROUTERPURPOSE controller command: it is now
7741 - Controllers should now specify cache=no or cache=yes when using
7742 the +POSTDESCRIPTOR command.
7743 - Bridge authorities now write bridge descriptors to disk, meaning
7744 we can export them to other programs and begin distributing them
7747 o Major features (directory authorities):
7748 - When a v3 authority is missing votes or signatures, it now tries
7750 - Directory authorities track weighted fractional uptime as well as
7751 weighted mean-time-between failures. WFU is suitable for deciding
7752 whether a node is "usually up", while MTBF is suitable for deciding
7753 whether a node is "likely to stay up." We need both, because
7754 "usually up" is a good requirement for guards, while "likely to
7755 stay up" is a good requirement for long-lived connections.
7757 o Major features (v3 directory system):
7758 - Caches now download v3 network status documents as needed,
7759 and download the descriptors listed in them.
7760 - All hosts now attempt to download and keep fresh v3 authority
7761 certificates, and re-attempt after failures.
7762 - More internal-consistency checks for vote parsing.
7764 o Major bugfixes (crashes):
7765 - If a connection is shut down abruptly because of something that
7766 happened inside connection_flushed_some(), do not call
7767 connection_finished_flushing(). Should fix bug 451. Bugfix on
7770 o Major bugfixes (performance):
7771 - Fix really bad O(n^2) performance when parsing a long list of
7772 routers: Instead of searching the entire list for an "extra-info "
7773 string which usually wasn't there, once for every routerinfo
7774 we read, just scan lines forward until we find one we like.
7776 - When we add data to a write buffer in response to the data on that
7777 write buffer getting low because of a flush, do not consider the
7778 newly added data as a candidate for immediate flushing, but rather
7779 make it wait until the next round of writing. Otherwise, we flush
7780 and refill recursively, and a single greedy TLS connection can
7781 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
7783 o Minor features (v3 authority system):
7784 - Add more ways for tools to download the votes that lead to the
7786 - Send a 503 when low on bandwidth and a vote, consensus, or
7787 certificate is requested.
7788 - If-modified-since is now implemented properly for all kinds of
7789 certificate requests.
7791 o Minor bugfixes (network statuses):
7792 - Tweak the implementation of proposal 109 slightly: allow at most
7793 two Tor servers on the same IP address, except if it's the location
7794 of a directory authority, in which case allow five. Bugfix on
7797 o Minor bugfixes (controller):
7798 - When sending a status event to the controller telling it that an
7799 OR address is reachable, set the port correctly. (Previously we
7800 were reporting the dir port.) Bugfix on 0.1.2.x.
7802 o Minor bugfixes (v3 directory system):
7803 - Fix logic to look up a cert by its signing key digest. Bugfix on
7805 - Only change the reply to a vote to "OK" if it's not already
7806 set. This gets rid of annoying "400 OK" log messages, which may
7807 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
7808 - When we get a valid consensus, recompute the voting schedule.
7809 - Base the valid-after time of a vote on the consensus voting
7810 schedule, not on our preferred schedule.
7811 - Make the return values and messages from signature uploads and
7812 downloads more sensible.
7813 - Fix a memory leak when serving votes and consensus documents, and
7814 another when serving certificates.
7816 o Minor bugfixes (performance):
7817 - Use a slightly simpler string hashing algorithm (copying Python's
7818 instead of Java's) and optimize our digest hashing algorithm to take
7819 advantage of 64-bit platforms and to remove some possibly-costly
7821 - Fix a minor memory leak whenever we parse guards from our state
7822 file. Bugfix on 0.2.0.7-alpha.
7823 - Fix a minor memory leak whenever we write out a file. Bugfix on
7825 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7826 command. Bugfix on 0.2.0.5-alpha.
7828 o Minor bugfixes (portability):
7829 - On some platforms, accept() can return a broken address. Detect
7830 this more quietly, and deal accordingly. Fixes bug 483.
7831 - Stop calling tor_strlower() on uninitialized memory in some cases.
7832 Bugfix in 0.2.0.7-alpha.
7834 o Minor bugfixes (usability):
7835 - Treat some 403 responses from directory servers as INFO rather than
7836 WARN-severity events.
7837 - It's not actually an error to find a non-pending entry in the DNS
7838 cache when canceling a pending resolve. Don't log unless stuff is
7839 fishy. Resolves bug 463.
7841 o Minor bugfixes (anonymity):
7842 - Never report that we've used more bandwidth than we're willing to
7843 relay: it leaks how much non-relay traffic we're using. Resolves
7845 - When looking for a circuit to cannibalize, consider family as well
7846 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7847 circuit cannibalization).
7849 o Code simplifications and refactoring:
7850 - Make a bunch of functions static. Remove some dead code.
7851 - Pull out about a third of the really big routerlist.c; put it in a
7852 new module, networkstatus.c.
7853 - Merge the extra fields in local_routerstatus_t back into
7854 routerstatus_t: we used to need one routerstatus_t for each
7855 authority's opinion, plus a local_routerstatus_t for the locally
7856 computed consensus opinion. To save space, we put the locally
7857 modified fields into local_routerstatus_t, and only the common
7858 stuff into routerstatus_t. But once v3 directories are in use,
7859 clients and caches will no longer need to hold authority opinions;
7860 thus, the rationale for keeping the types separate is now gone.
7861 - Make the code used to reschedule and reattempt downloads more
7863 - Turn all 'Are we a directory server/mirror?' logic into a call to
7865 - Remove the code to generate the oldest (v1) directory format.
7866 The code has been disabled since 0.2.0.5-alpha.
7869 Changes in version 0.2.0.7-alpha - 2007-09-21
7870 This seventh development snapshot makes bridges work again, makes bridge
7871 authorities work for the first time, fixes two huge performance flaws
7872 in hidden services, and fixes a variety of minor issues.
7874 o New directory authorities:
7875 - Set up moria1 and tor26 as the first v3 directory authorities. See
7876 doc/spec/dir-spec.txt for details on the new directory design.
7878 o Major bugfixes (crashes):
7879 - Fix possible segfaults in functions called from
7880 rend_process_relay_cell(). Bugfix on 0.1.2.x.
7882 o Major bugfixes (bridges):
7883 - Fix a bug that made servers send a "404 Not found" in response to
7884 attempts to fetch their server descriptor. This caused Tor servers
7885 to take many minutes to establish reachability for their DirPort,
7886 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
7887 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
7888 users configure that and specify a bridge with an identity
7889 fingerprint, now they will lookup the bridge descriptor at the
7890 default bridge authority via a one-hop tunnel, but once circuits
7891 are established they will switch to a three-hop tunnel for later
7892 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
7894 o Major bugfixes (hidden services):
7895 - Hidden services were choosing introduction points uniquely by
7896 hexdigest, but when constructing the hidden service descriptor
7897 they merely wrote the (potentially ambiguous) nickname.
7898 - Clients now use the v2 intro format for hidden service
7899 connections: they specify their chosen rendezvous point by identity
7900 digest rather than by (potentially ambiguous) nickname. Both
7901 are bugfixes on 0.1.2.x, and they could speed up hidden service
7902 connections dramatically. Thanks to Karsten Loesing.
7904 o Minor features (security):
7905 - As a client, do not believe any server that tells us that an
7906 address maps to an internal address space.
7907 - Make it possible to enable HashedControlPassword and
7908 CookieAuthentication at the same time.
7910 o Minor features (guard nodes):
7911 - Tag every guard node in our state file with the version that
7912 we believe added it, or with our own version if we add it. This way,
7913 if a user temporarily runs an old version of Tor and then switches
7914 back to a new one, she doesn't automatically lose her guards.
7916 o Minor features (speed):
7917 - When implementing AES counter mode, update only the portions of the
7918 counter buffer that need to change, and don't keep separate
7919 network-order and host-order counters when they are the same (i.e.,
7920 on big-endian hosts.)
7922 o Minor features (controller):
7923 - Accept LF instead of CRLF on controller, since some software has a
7924 hard time generating real Internet newlines.
7925 - Add GETINFO values for the server status events
7926 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
7930 - Routers no longer include bandwidth-history lines in their
7931 descriptors; this information is already available in extra-info
7932 documents, and including it in router descriptors took up 60%
7933 (!) of compressed router descriptor downloads. Completes
7934 implementation of proposal 104.
7935 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
7936 and TorControl.py, as they use the old v0 controller protocol,
7937 and are obsoleted by TorFlow anyway.
7938 - Drop support for v1 rendezvous descriptors, since we never used
7939 them anyway, and the code has probably rotted by now. Based on
7940 patch from Karsten Loesing.
7941 - On OSX, stop warning the user that kqueue support in libevent is
7942 "experimental", since it seems to have worked fine for ages.
7945 - When generating information telling us how to extend to a given
7946 router, do not try to include the nickname if it is absent. Fixes
7947 bug 467. Bugfix on 0.2.0.3-alpha.
7948 - Fix a user-triggerable (but not remotely-triggerable) segfault
7949 in expand_filename(). Bugfix on 0.1.2.x.
7950 - Fix a memory leak when freeing incomplete requests from DNSPort.
7951 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
7952 - Don't try to access (or alter) the state file when running
7953 --list-fingerprint or --verify-config or --hash-password. (Resolves
7954 bug 499.) Bugfix on 0.1.2.x.
7955 - Servers used to decline to publish their DirPort if their
7956 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
7957 were below a threshold. Now they only look at BandwidthRate and
7958 RelayBandwidthRate. Bugfix on 0.1.2.x.
7959 - Remove an optimization in the AES counter-mode code that assumed
7960 that the counter never exceeded 2^68. When the counter can be set
7961 arbitrarily as an IV (as it is by Karsten's new hidden services
7962 code), this assumption no longer holds. Bugfix on 0.1.2.x.
7963 - Resume listing "AUTHORITY" flag for authorities in network status.
7964 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
7966 o Code simplifications and refactoring:
7967 - Revamp file-writing logic so we don't need to have the entire
7968 contents of a file in memory at once before we write to disk. Tor,
7970 - Turn "descriptor store" into a full-fledged type.
7971 - Move all NT services code into a separate source file.
7972 - Unify all code that computes medians, percentile elements, etc.
7973 - Get rid of a needless malloc when parsing address policies.
7976 Changes in version 0.1.2.17 - 2007-08-30
7977 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
7978 X bundles. Vidalia 0.0.14 makes authentication required for the
7979 ControlPort in the default configuration, which addresses important
7980 security risks. Everybody who uses Vidalia (or another controller)
7983 In addition, this Tor update fixes major load balancing problems with
7984 path selection, which should speed things up a lot once many people
7987 o Major bugfixes (security):
7988 - We removed support for the old (v0) control protocol. It has been
7989 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
7990 become more of a headache than it's worth.
7992 o Major bugfixes (load balancing):
7993 - When choosing nodes for non-guard positions, weight guards
7994 proportionally less, since they already have enough load. Patch
7996 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
7997 will allow fast Tor servers to get more attention.
7998 - When we're upgrading from an old Tor version, forget our current
7999 guards and pick new ones according to the new weightings. These
8000 three load balancing patches could raise effective network capacity
8001 by a factor of four. Thanks to Mike Perry for measurements.
8003 o Major bugfixes (stream expiration):
8004 - Expire not-yet-successful application streams in all cases if
8005 they've been around longer than SocksTimeout. Right now there are
8006 some cases where the stream will live forever, demanding a new
8007 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8009 o Minor features (controller):
8010 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8011 is valid before any authentication has been received. It tells
8012 a controller what kind of authentication is expected, and what
8013 protocol is spoken. Implements proposal 119.
8015 o Minor bugfixes (performance):
8016 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8017 greatly speeding up loading cached-routers from disk on startup.
8018 - Disable sentinel-based debugging for buffer code: we squashed all
8019 the bugs that this was supposed to detect a long time ago, and now
8020 its only effect is to change our buffer sizes from nice powers of
8021 two (which platform mallocs tend to like) to values slightly over
8022 powers of two (which make some platform mallocs sad).
8024 o Minor bugfixes (misc):
8025 - If exit bandwidth ever exceeds one third of total bandwidth, then
8026 use the correct formula to weight exit nodes when choosing paths.
8027 Based on patch from Mike Perry.
8028 - Choose perfectly fairly among routers when choosing by bandwidth and
8029 weighting by fraction of bandwidth provided by exits. Previously, we
8030 would choose with only approximate fairness, and correct ourselves
8031 if we ran off the end of the list.
8032 - If we require CookieAuthentication but we fail to write the
8033 cookie file, we would warn but not exit, and end up in a state
8034 where no controller could authenticate. Now we exit.
8035 - If we require CookieAuthentication, stop generating a new cookie
8036 every time we change any piece of our config.
8037 - Refuse to start with certain directory authority keys, and
8038 encourage people using them to stop.
8039 - Terminate multi-line control events properly. Original patch
8041 - Fix a minor memory leak when we fail to find enough suitable
8042 servers to choose a circuit.
8043 - Stop leaking part of the descriptor when we run into a particularly
8044 unparseable piece of it.
8047 Changes in version 0.2.0.6-alpha - 2007-08-26
8048 This sixth development snapshot features a new Vidalia version in the
8049 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8050 the ControlPort in the default configuration, which addresses important
8053 In addition, this snapshot fixes major load balancing problems
8054 with path selection, which should speed things up a lot once many
8055 people have upgraded. The directory authorities also use a new
8056 mean-time-between-failure approach to tracking which servers are stable,
8057 rather than just looking at the most recent uptime.
8059 o New directory authorities:
8060 - Set up Tonga as the default bridge directory authority.
8063 - Directory authorities now track servers by weighted
8064 mean-times-between-failures. When we have 4 or more days of data,
8065 use measured MTBF rather than declared uptime to decide whether
8066 to call a router Stable. Implements proposal 108.
8068 o Major bugfixes (load balancing):
8069 - When choosing nodes for non-guard positions, weight guards
8070 proportionally less, since they already have enough load. Patch
8072 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8073 will allow fast Tor servers to get more attention.
8074 - When we're upgrading from an old Tor version, forget our current
8075 guards and pick new ones according to the new weightings. These
8076 three load balancing patches could raise effective network capacity
8077 by a factor of four. Thanks to Mike Perry for measurements.
8079 o Major bugfixes (descriptor parsing):
8080 - Handle unexpected whitespace better in malformed descriptors. Bug
8081 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8084 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8085 GETINFO for Torstat to use until it can switch to using extrainfos.
8086 - Optionally (if built with -DEXPORTMALLINFO) export the output
8087 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8091 - Do not intermix bridge routers with controller-added
8092 routers. (Bugfix on 0.2.0.x)
8093 - Do not fail with an assert when accept() returns an unexpected
8094 address family. Addresses but does not wholly fix bug 483. (Bugfix
8096 - Let directory authorities startup even when they can't generate
8097 a descriptor immediately, e.g. because they don't know their
8099 - Stop putting the authentication cookie in a file called "0"
8100 in your working directory if you don't specify anything for the
8101 new CookieAuthFile option. Reported by Matt Edman.
8102 - Make it possible to read the PROTOCOLINFO response in a way that
8103 conforms to our control-spec. Reported by Matt Edman.
8104 - Fix a minor memory leak when we fail to find enough suitable
8105 servers to choose a circuit. Bugfix on 0.1.2.x.
8106 - Stop leaking part of the descriptor when we run into a particularly
8107 unparseable piece of it. Bugfix on 0.1.2.x.
8108 - Unmap the extrainfo cache file on exit.
8111 Changes in version 0.2.0.5-alpha - 2007-08-19
8112 This fifth development snapshot fixes compilation on Windows again;
8113 fixes an obnoxious client-side bug that slowed things down and put
8114 extra load on the network; gets us closer to using the v3 directory
8115 voting scheme; makes it easier for Tor controllers to use cookie-based
8116 authentication; and fixes a variety of other bugs.
8119 - Version 1 directories are no longer generated in full. Instead,
8120 authorities generate and serve "stub" v1 directories that list
8121 no servers. This will stop Tor versions 0.1.0.x and earlier from
8122 working, but (for security reasons) nobody should be running those
8125 o Major bugfixes (compilation, 0.2.0.x):
8126 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8127 - Try to fix MSVC compilation: build correctly on platforms that do
8128 not define s6_addr16 or s6_addr32.
8129 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8132 o Major bugfixes (stream expiration):
8133 - Expire not-yet-successful application streams in all cases if
8134 they've been around longer than SocksTimeout. Right now there are
8135 some cases where the stream will live forever, demanding a new
8136 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8139 o Minor features (directory servers):
8140 - When somebody requests a list of statuses or servers, and we have
8141 none of those, return a 404 rather than an empty 200.
8143 o Minor features (directory voting):
8144 - Store v3 consensus status consensuses on disk, and reload them
8147 o Minor features (security):
8148 - Warn about unsafe ControlPort configurations.
8149 - Refuse to start with certain directory authority keys, and
8150 encourage people using them to stop.
8152 o Minor features (controller):
8153 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8154 is valid before any authentication has been received. It tells
8155 a controller what kind of authentication is expected, and what
8156 protocol is spoken. Implements proposal 119.
8157 - New config option CookieAuthFile to choose a new location for the
8158 cookie authentication file, and config option
8159 CookieAuthFileGroupReadable to make it group-readable.
8161 o Minor features (unit testing):
8162 - Add command-line arguments to unit-test executable so that we can
8163 invoke any chosen test from the command line rather than having
8164 to run the whole test suite at once; and so that we can turn on
8165 logging for the unit tests.
8167 o Minor bugfixes (on 0.1.2.x):
8168 - If we require CookieAuthentication but we fail to write the
8169 cookie file, we would warn but not exit, and end up in a state
8170 where no controller could authenticate. Now we exit.
8171 - If we require CookieAuthentication, stop generating a new cookie
8172 every time we change any piece of our config.
8173 - When loading bandwidth history, do not believe any information in
8174 the future. Fixes bug 434.
8175 - When loading entry guard information, do not believe any information
8177 - When we have our clock set far in the future and generate an
8178 onion key, then re-set our clock to be correct, we should not stop
8179 the onion key from getting rotated.
8180 - Clean up torrc sample config file.
8181 - Do not automatically run configure from autogen.sh. This
8182 non-standard behavior tended to annoy people who have built other
8185 o Minor bugfixes (on 0.2.0.x):
8186 - Fix a bug with AutomapHostsOnResolve that would always cause
8187 the second request to fail. Bug reported by Kate. Bugfix on
8189 - Fix a bug in ADDRMAP controller replies that would sometimes
8190 try to print a NULL. Patch from tup.
8191 - Read v3 directory authority keys from the right location.
8192 - Numerous bugfixes to directory voting code.
8195 Changes in version 0.1.2.16 - 2007-08-01
8196 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8197 remote attacker in certain situations to rewrite the user's torrc
8198 configuration file. This can completely compromise anonymity of users
8199 in most configurations, including those running the Vidalia bundles,
8200 TorK, etc. Or worse.
8202 o Major security fixes:
8203 - Close immediately after missing authentication on control port;
8204 do not allow multiple authentication attempts.
8207 Changes in version 0.2.0.4-alpha - 2007-08-01
8208 This fourth development snapshot fixes a critical security vulnerability
8209 for most users, specifically those running Vidalia, TorK, etc. Everybody
8210 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8212 o Major security fixes:
8213 - Close immediately after missing authentication on control port;
8214 do not allow multiple authentication attempts.
8216 o Major bugfixes (compilation):
8217 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8220 o Minor features (performance):
8221 - Be even more aggressive about releasing RAM from small
8222 empty buffers. Thanks to our free-list code, this shouldn't be too
8223 performance-intensive.
8224 - Disable sentinel-based debugging for buffer code: we squashed all
8225 the bugs that this was supposed to detect a long time ago, and
8226 now its only effect is to change our buffer sizes from nice
8227 powers of two (which platform mallocs tend to like) to values
8228 slightly over powers of two (which make some platform mallocs sad).
8229 - Log malloc statistics from mallinfo() on platforms where it
8233 Changes in version 0.2.0.3-alpha - 2007-07-29
8234 This third development snapshot introduces new experimental
8235 blocking-resistance features and a preliminary version of the v3
8236 directory voting design, and includes many other smaller features
8240 - The first pieces of our "bridge" design for blocking-resistance
8241 are implemented. People can run bridge directory authorities;
8242 people can run bridges; and people can configure their Tor clients
8243 with a set of bridges to use as the first hop into the Tor network.
8244 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
8246 - Create listener connections before we setuid to the configured
8247 User and Group. Now non-Windows users can choose port values
8248 under 1024, start Tor as root, and have Tor bind those ports
8249 before it changes to another UID. (Windows users could already
8251 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8252 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8253 on "vserver" accounts. (Patch from coderman.)
8254 - Be even more aggressive about separating local traffic from relayed
8255 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
8257 o Major features (experimental):
8258 - First cut of code for "v3 dir voting": directory authorities will
8259 vote on a common network status document rather than each publishing
8260 their own opinion. This code needs more testing and more corner-case
8261 handling before it's ready for use.
8264 - Directory authorities now call routers Fast if their bandwidth is
8265 at least 100KB/s, and consider their bandwidth adequate to be a
8266 Guard if it is at least 250KB/s, no matter the medians. This fix
8267 complements proposal 107. [Bugfix on 0.1.2.x]
8268 - Directory authorities now never mark more than 3 servers per IP as
8269 Valid and Running. (Implements proposal 109, by Kevin Bauer and
8271 - Minor change to organizationName and commonName generation
8272 procedures in TLS certificates during Tor handshakes, to invalidate
8273 some earlier censorware approaches. This is not a long-term
8274 solution, but applying it will give us a bit of time to look into
8275 the epidemiology of countermeasures as they spread.
8277 o Major bugfixes (directory):
8278 - Rewrite directory tokenization code to never run off the end of
8279 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
8281 o Minor features (controller):
8282 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8283 match requests to applications. (Patch from Robert Hogan.)
8284 - Report address and port correctly on connections to DNSPort. (Patch
8286 - Add a RESOLVE command to launch hostname lookups. (Original patch
8288 - Add GETINFO status/enough-dir-info to let controllers tell whether
8289 Tor has downloaded sufficient directory information. (Patch
8291 - You can now use the ControlSocket option to tell Tor to listen for
8292 controller connections on Unix domain sockets on systems that
8293 support them. (Patch from Peter Palfrader.)
8294 - STREAM NEW events are generated for DNSPort requests and for
8295 tunneled directory connections. (Patch from Robert Hogan.)
8296 - New "GETINFO address-mappings/*" command to get address mappings
8297 with expiry information. "addr-mappings/*" is now deprecated.
8300 o Minor features (misc):
8301 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8303 - The tor-gencert tool for v3 directory authorities now creates all
8304 files as readable to the file creator only, and write-protects
8305 the authority identity key.
8306 - When dumping memory usage, list bytes used in buffer memory
8308 - When running with dmalloc, dump more stats on hup and on exit.
8309 - Directory authorities now fail quickly and (relatively) harmlessly
8310 if they generate a network status document that is somehow
8313 o Traffic load balancing improvements:
8314 - If exit bandwidth ever exceeds one third of total bandwidth, then
8315 use the correct formula to weight exit nodes when choosing paths.
8316 (Based on patch from Mike Perry.)
8317 - Choose perfectly fairly among routers when choosing by bandwidth and
8318 weighting by fraction of bandwidth provided by exits. Previously, we
8319 would choose with only approximate fairness, and correct ourselves
8320 if we ran off the end of the list. [Bugfix on 0.1.2.x]
8322 o Performance improvements:
8323 - Be more aggressive with freeing buffer RAM or putting it on the
8325 - Use Critical Sections rather than Mutexes for synchronizing threads
8326 on win32; Mutexes are heavier-weight, and designed for synchronizing
8329 o Deprecated and removed features:
8330 - RedirectExits is now deprecated.
8331 - Stop allowing address masks that do not correspond to bit prefixes.
8332 We have warned about these for a really long time; now it's time
8333 to reject them. (Patch from croup.)
8335 o Minor bugfixes (directory):
8336 - Fix another crash bug related to extra-info caching. (Bug found by
8337 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
8338 - Directories no longer return a "304 not modified" when they don't
8339 have the networkstatus the client asked for. Also fix a memory
8340 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
8341 - We had accidentally labelled 0.1.2.x directory servers as not
8342 suitable for begin_dir requests, and had labelled no directory
8343 servers as suitable for uploading extra-info documents. [Bugfix
8346 o Minor bugfixes (dns):
8347 - Fix a crash when DNSPort is set more than once. (Patch from Robert
8348 Hogan.) [Bugfix on 0.2.0.2-alpha]
8349 - Add DNSPort connections to the global connection list, so that we
8350 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
8352 - Fix a dangling reference that could lead to a crash when DNSPort is
8353 changed or closed (Patch from Robert Hogan.) [Bugfix on
8356 o Minor bugfixes (controller):
8357 - Provide DNS expiry times in GMT, not in local time. For backward
8358 compatibility, ADDRMAP events only provide GMT expiry in an extended
8359 field. "GETINFO address-mappings" always does the right thing.
8360 - Use CRLF line endings properly in NS events.
8361 - Terminate multi-line control events properly. (Original patch
8362 from tup.) [Bugfix on 0.1.2.x-alpha]
8363 - Do not include spaces in SOURCE_ADDR fields in STREAM
8364 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
8367 Changes in version 0.1.2.15 - 2007-07-17
8368 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
8369 problems, fixes compilation on BSD, and fixes a variety of other
8370 bugs. Everybody should upgrade.
8372 o Major bugfixes (compilation):
8373 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
8375 o Major bugfixes (crashes):
8376 - Try even harder not to dereference the first character after
8377 an mmap(). Reported by lodger.
8378 - Fix a crash bug in directory authorities when we re-number the
8379 routerlist while inserting a new router.
8380 - When the cached-routers file is an even multiple of the page size,
8381 don't run off the end and crash. (Fixes bug 455; based on idea
8383 - Fix eventdns.c behavior on Solaris: It is critical to include
8384 orconfig.h _before_ sys/types.h, so that we can get the expected
8385 definition of _FILE_OFFSET_BITS.
8387 o Major bugfixes (security):
8388 - Fix a possible buffer overrun when using BSD natd support. Bug
8390 - When sending destroy cells from a circuit's origin, don't include
8391 the reason for tearing down the circuit. The spec says we didn't,
8392 and now we actually don't. Reported by lodger.
8393 - Keep streamids from different exits on a circuit separate. This
8394 bug may have allowed other routers on a given circuit to inject
8395 cells into streams. Reported by lodger; fixes bug 446.
8396 - If there's a never-before-connected-to guard node in our list,
8397 never choose any guards past it. This way we don't expand our
8398 guard list unless we need to.
8400 o Minor bugfixes (guard nodes):
8401 - Weight guard selection by bandwidth, so that low-bandwidth nodes
8402 don't get overused as guards.
8404 o Minor bugfixes (directory):
8405 - Correctly count the number of authorities that recommend each
8406 version. Previously, we were under-counting by 1.
8407 - Fix a potential crash bug when we load many server descriptors at
8408 once and some of them make others of them obsolete. Fixes bug 458.
8410 o Minor bugfixes (hidden services):
8411 - Stop tearing down the whole circuit when the user asks for a
8412 connection to a port that the hidden service didn't configure.
8415 o Minor bugfixes (misc):
8416 - On Windows, we were preventing other processes from reading
8417 cached-routers while Tor was running. Reported by janbar.
8418 - Fix a possible (but very unlikely) bug in picking routers by
8419 bandwidth. Add a log message to confirm that it is in fact
8420 unlikely. Patch from lodger.
8421 - Backport a couple of memory leak fixes.
8422 - Backport miscellaneous cosmetic bugfixes.
8425 Changes in version 0.2.0.2-alpha - 2007-06-02
8426 o Major bugfixes on 0.2.0.1-alpha:
8427 - Fix an assertion failure related to servers without extra-info digests.
8428 Resolves bugs 441 and 442.
8430 o Minor features (directory):
8431 - Support "If-Modified-Since" when answering HTTP requests for
8432 directories, running-routers documents, and network-status documents.
8433 (There's no need to support it for router descriptors, since those
8434 are downloaded by descriptor digest.)
8436 o Minor build issues:
8437 - Clear up some MIPSPro compiler warnings.
8438 - When building from a tarball on a machine that happens to have SVK
8439 installed, report the micro-revision as whatever version existed
8440 in the tarball, not as "x".
8443 Changes in version 0.2.0.1-alpha - 2007-06-01
8444 This early development snapshot provides new features for people running
8445 Tor as both a client and a server (check out the new RelayBandwidth
8446 config options); lets Tor run as a DNS proxy; and generally moves us
8447 forward on a lot of fronts.
8449 o Major features, server usability:
8450 - New config options RelayBandwidthRate and RelayBandwidthBurst:
8451 a separate set of token buckets for relayed traffic. Right now
8452 relayed traffic is defined as answers to directory requests, and
8453 OR connections that don't have any local circuits on them.
8455 o Major features, client usability:
8456 - A client-side DNS proxy feature to replace the need for
8457 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
8458 for DNS requests on port 9999, use the Tor network to resolve them
8459 anonymously, and send the reply back like a regular DNS server.
8460 The code still only implements a subset of DNS.
8461 - Make PreferTunneledDirConns and TunnelDirConns work even when
8462 we have no cached directory info. This means Tor clients can now
8463 do all of their connections protected by TLS.
8465 o Major features, performance and efficiency:
8466 - Directory authorities accept and serve "extra info" documents for
8467 routers. These documents contain fields from router descriptors
8468 that aren't usually needed, and that use a lot of excess
8469 bandwidth. Once these fields are removed from router descriptors,
8470 the bandwidth savings should be about 60%. [Partially implements
8472 - Servers upload extra-info documents to any authority that accepts
8473 them. Authorities (and caches that have been configured to download
8474 extra-info documents) download them as needed. [Partially implements
8476 - Change the way that Tor buffers data that it is waiting to write.
8477 Instead of queueing data cells in an enormous ring buffer for each
8478 client->OR or OR->OR connection, we now queue cells on a separate
8479 queue for each circuit. This lets us use less slack memory, and
8480 will eventually let us be smarter about prioritizing different kinds
8482 - Use memory pools to allocate cells with better speed and memory
8483 efficiency, especially on platforms where malloc() is inefficient.
8484 - Stop reading on edge connections when their corresponding circuit
8485 buffers are full; start again as the circuits empty out.
8487 o Major features, other:
8488 - Add an HSAuthorityRecordStats option that hidden service authorities
8489 can use to track statistics of overall hidden service usage without
8490 logging information that would be very useful to an attacker.
8491 - Start work implementing multi-level keys for directory authorities:
8492 Add a standalone tool to generate key certificates. (Proposal 103.)
8495 - Directory authorities now call routers Stable if they have an
8496 uptime of at least 30 days, even if that's not the median uptime
8497 in the network. Implements proposal 107, suggested by Kevin Bauer
8500 o Minor fixes (resource management):
8501 - Count the number of open sockets separately from the number
8502 of active connection_t objects. This will let us avoid underusing
8503 our allocated connection limit.
8504 - We no longer use socket pairs to link an edge connection to an
8505 anonymous directory connection or a DirPort test connection.
8506 Instead, we track the link internally and transfer the data
8507 in-process. This saves two sockets per "linked" connection (at the
8508 client and at the server), and avoids the nasty Windows socketpair()
8510 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
8511 for every single inactive connection_t. Free items from the
8512 4k/16k-buffer free lists when they haven't been used for a while.
8514 o Minor features (build):
8515 - Make autoconf search for libevent, openssl, and zlib consistently.
8516 - Update deprecated macros in configure.in.
8517 - When warning about missing headers, tell the user to let us
8518 know if the compile succeeds anyway, so we can downgrade the
8520 - Include the current subversion revision as part of the version
8521 string: either fetch it directly if we're in an SVN checkout, do
8522 some magic to guess it if we're in an SVK checkout, or use
8523 the last-detected version if we're building from a .tar.gz.
8524 Use this version consistently in log messages.
8526 o Minor features (logging):
8527 - Always prepend "Bug: " to any log message about a bug.
8528 - Put a platform string (e.g. "Linux i686") in the startup log
8529 message, so when people paste just their logs, we know if it's
8530 OpenBSD or Windows or what.
8531 - When logging memory usage, break down memory used in buffers by
8534 o Minor features (directory system):
8535 - New config option V2AuthoritativeDirectory that all directory
8536 authorities should set. This will let future authorities choose
8537 not to serve V2 directory information.
8538 - Directory authorities allow multiple router descriptors and/or extra
8539 info documents to be uploaded in a single go. This will make
8540 implementing proposal 104 simpler.
8542 o Minor features (controller):
8543 - Add a new config option __DisablePredictedCircuits designed for
8544 use by the controller, when we don't want Tor to build any circuits
8546 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
8547 so we can exit from the middle of the circuit.
8548 - Implement "getinfo status/circuit-established".
8549 - Implement "getinfo status/version/..." so a controller can tell
8550 whether the current version is recommended, and whether any versions
8551 are good, and how many authorities agree. (Patch from shibz.)
8553 o Minor features (hidden services):
8554 - Allow multiple HiddenServicePort directives with the same virtual
8555 port; when they occur, the user is sent round-robin to one
8556 of the target ports chosen at random. Partially fixes bug 393 by
8557 adding limited ad-hoc round-robining.
8559 o Minor features (other):
8561 - Add a new AutomapHostsOnResolve option: when it is enabled, any
8562 resolve request for hosts matching a given pattern causes Tor to
8563 generate an internal virtual address mapping for that host. This
8564 allows DNSPort to work sensibly with hidden service users. By
8565 default, .exit and .onion addresses are remapped; the list of
8566 patterns can be reconfigured with AutomapHostsSuffixes.
8567 - Add an "-F" option to tor-resolve to force a resolve for a .onion
8568 address. Thanks to the AutomapHostsOnResolve option, this is no
8569 longer a completely silly thing to do.
8570 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
8571 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
8572 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
8573 minus 1 byte: the actual maximum declared bandwidth.
8576 - Removed support for the old binary "version 0" controller protocol.
8577 This has been deprecated since 0.1.1, and warnings have been issued
8578 since 0.1.2. When we encounter a v0 control message, we now send
8579 back an error and close the connection.
8580 - Remove the old "dns worker" server DNS code: it hasn't been default
8581 since 0.1.2.2-alpha, and all the servers seem to be using the new
8584 o Minor bugfixes (portability):
8585 - Even though Windows is equally happy with / and \ as path separators,
8586 try to use \ consistently on Windows and / consistently on Unix: it
8587 makes the log messages nicer.
8588 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
8589 - Read resolv.conf files correctly on platforms where read() returns
8590 partial results on small file reads.
8592 o Minor bugfixes (directory):
8593 - Correctly enforce that elements of directory objects do not appear
8594 more often than they are allowed to appear.
8595 - When we are reporting the DirServer line we just parsed, we were
8596 logging the second stanza of the key fingerprint, not the first.
8598 o Minor bugfixes (logging):
8599 - When we hit an EOF on a log (probably because we're shutting down),
8600 don't try to remove the log from the list: just mark it as
8601 unusable. (Bulletproofs against bug 222.)
8603 o Minor bugfixes (other):
8604 - In the exitlist script, only consider the most recently published
8605 server descriptor for each server. Also, when the user requests
8606 a list of servers that _reject_ connections to a given address,
8607 explicitly exclude the IPs that also have servers that accept
8608 connections to that address. (Resolves bug 405.)
8609 - Stop allowing hibernating servers to be "stable" or "fast".
8610 - On Windows, we were preventing other processes from reading
8611 cached-routers while Tor was running. (Reported by janbar)
8612 - Make the NodeFamilies config option work. (Reported by
8613 lodger -- it has never actually worked, even though we added it
8615 - Check return values from pthread_mutex functions.
8616 - Don't save non-general-purpose router descriptors to the disk cache,
8617 because we have no way of remembering what their purpose was when
8619 - Add even more asserts to hunt down bug 417.
8620 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
8621 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
8622 Add a log message to confirm that it is in fact unlikely.
8624 o Minor bugfixes (controller):
8625 - Make 'getinfo fingerprint' return a 551 error if we're not a
8626 server, so we match what the control spec claims we do. Reported
8628 - Fix a typo in an error message when extendcircuit fails that
8629 caused us to not follow the \r\n-based delimiter protocol. Reported
8632 o Code simplifications and refactoring:
8633 - Stop passing around circuit_t and crypt_path_t pointers that are
8634 implicit in other procedure arguments.
8635 - Drop the old code to choke directory connections when the
8636 corresponding OR connections got full: thanks to the cell queue
8637 feature, OR conns don't get full any more.
8638 - Make dns_resolve() handle attaching connections to circuits
8639 properly, so the caller doesn't have to.
8640 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
8641 - Keep the connection array as a dynamic smartlist_t, rather than as
8642 a fixed-sized array. This is important, as the number of connections
8643 is becoming increasingly decoupled from the number of sockets.
8646 Changes in version 0.1.2.14 - 2007-05-25
8647 Tor 0.1.2.14 changes the addresses of two directory authorities (this
8648 change especially affects those who serve or use hidden services),
8649 and fixes several other crash- and security-related bugs.
8651 o Directory authority changes:
8652 - Two directory authorities (moria1 and moria2) just moved to new
8653 IP addresses. This change will particularly affect those who serve
8654 or use hidden services.
8656 o Major bugfixes (crashes):
8657 - If a directory server runs out of space in the connection table
8658 as it's processing a begin_dir request, it will free the exit stream
8659 but leave it attached to the circuit, leading to unpredictable
8660 behavior. (Reported by seeess, fixes bug 425.)
8661 - Fix a bug in dirserv_remove_invalid() that would cause authorities
8662 to corrupt memory under some really unlikely scenarios.
8663 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
8664 - Avoid segfaults when reading from mmaped descriptor file. (Reported
8667 o Major bugfixes (security):
8668 - When choosing an entry guard for a circuit, avoid using guards
8669 that are in the same family as the chosen exit -- not just guards
8670 that are exactly the chosen exit. (Reported by lodger.)
8672 o Major bugfixes (resource management):
8673 - If a directory authority is down, skip it when deciding where to get
8674 networkstatus objects or descriptors. Otherwise we keep asking
8675 every 10 seconds forever. Fixes bug 384.
8676 - Count it as a failure if we fetch a valid network-status but we
8677 don't want to keep it. Otherwise we'll keep fetching it and keep
8678 not wanting to keep it. Fixes part of bug 422.
8679 - If all of our dirservers have given us bad or no networkstatuses
8680 lately, then stop hammering them once per minute even when we
8681 think they're failed. Fixes another part of bug 422.
8684 - Actually set the purpose correctly for descriptors inserted with
8686 - When we have k non-v2 authorities in our DirServer config,
8687 we ignored the last k authorities in the list when updating our
8689 - Correctly back-off from requesting router descriptors that we are
8690 having a hard time downloading.
8691 - Read resolv.conf files correctly on platforms where read() returns
8692 partial results on small file reads.
8693 - Don't rebuild the entire router store every time we get 32K of
8694 routers: rebuild it when the journal gets very large, or when
8695 the gaps in the store get very large.
8698 - When routers publish SVN revisions in their router descriptors,
8699 authorities now include those versions correctly in networkstatus
8701 - Warn when using a version of libevent before 1.3b to run a server on
8702 OSX or BSD: these versions interact badly with userspace threads.
8705 Changes in version 0.1.2.13 - 2007-04-24
8706 This release features some major anonymity fixes, such as safer path
8707 selection; better client performance; faster bootstrapping, better
8708 address detection, and better DNS support for servers; write limiting as
8709 well as read limiting to make servers easier to run; and a huge pile of
8710 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
8712 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
8713 of the Freenode IRC network, remembering his patience and vision for
8714 free speech on the Internet.
8717 - Fix a memory leak when we ask for "all" networkstatuses and we
8718 get one we don't recognize.
8719 - Add more asserts to hunt down bug 417.
8720 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
8723 Changes in version 0.1.2.12-rc - 2007-03-16
8725 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
8726 directory information requested inside Tor connections (i.e. via
8727 begin_dir cells). It only triggered when the same connection was
8728 serving other data at the same time. Reported by seeess.
8731 - When creating a circuit via the controller, send a 'launched'
8732 event when we're done, so we follow the spec better.
8735 Changes in version 0.1.2.11-rc - 2007-03-15
8736 o Minor bugfixes (controller), reported by daejees:
8737 - Correct the control spec to match how the code actually responds
8738 to 'getinfo addr-mappings/*'.
8739 - The control spec described a GUARDS event, but the code
8740 implemented a GUARD event. Standardize on GUARD, but let people
8744 Changes in version 0.1.2.10-rc - 2007-03-07
8745 o Major bugfixes (Windows):
8746 - Do not load the NT services library functions (which may not exist)
8747 just to detect if we're a service trying to shut down. Now we run
8748 on Win98 and friends again.
8750 o Minor bugfixes (other):
8751 - Clarify a couple of log messages.
8752 - Fix a misleading socks5 error number.
8755 Changes in version 0.1.2.9-rc - 2007-03-02
8756 o Major bugfixes (Windows):
8757 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
8758 of the usual GCC "%llu". This prevents a bug when saving 64-bit
8759 int configuration values: the high-order 32 bits would get
8760 truncated. In particular, we were being bitten by the default
8761 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
8762 and maybe also bug 397.)
8764 o Minor bugfixes (performance):
8765 - Use OpenSSL's AES implementation on platforms where it's faster.
8766 This could save us as much as 10% CPU usage.
8768 o Minor bugfixes (server):
8769 - Do not rotate onion key immediately after setting it for the first
8772 o Minor bugfixes (directory authorities):
8773 - Stop calling servers that have been hibernating for a long time
8774 "stable". Also, stop letting hibernating or obsolete servers affect
8775 uptime and bandwidth cutoffs.
8776 - Stop listing hibernating servers in the v1 directory.
8778 o Minor bugfixes (hidden services):
8779 - Upload hidden service descriptors slightly less often, to reduce
8780 load on authorities.
8782 o Minor bugfixes (other):
8783 - Fix an assert that could trigger if a controller quickly set then
8784 cleared EntryNodes. Bug found by Udo van den Heuvel.
8785 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
8787 - Fix a potential race condition in the rpm installer. Found by
8789 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
8790 of 2 as indicating that the server is completely bad; it sometimes
8791 means that the server is just bad for the request in question. (may fix
8792 the last of bug 326.)
8793 - Disable encrypted directory connections when we don't have a server
8794 descriptor for the destination. We'll get this working again in
8798 Changes in version 0.1.2.8-beta - 2007-02-26
8799 o Major bugfixes (crashes):
8800 - Stop crashing when the controller asks us to resetconf more than
8801 one config option at once. (Vidalia 0.0.11 does this.)
8802 - Fix a crash that happened on Win98 when we're given command-line
8803 arguments: don't try to load NT service functions from advapi32.dll
8804 except when we need them. (Bug introduced in 0.1.2.7-alpha;
8806 - Fix a longstanding obscure crash bug that could occur when
8807 we run out of DNS worker processes. (Resolves bug 390.)
8809 o Major bugfixes (hidden services):
8810 - Correctly detect whether hidden service descriptor downloads are
8811 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
8813 o Major bugfixes (accounting):
8814 - When we start during an accounting interval before it's time to wake
8815 up, remember to wake up at the correct time. (May fix bug 342.)
8817 o Minor bugfixes (controller):
8818 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
8819 clear the corresponding on_circuit variable, and remember later
8820 that we don't need to send a redundant CLOSED event. Resolves part
8822 - Report events where a resolve succeeded or where we got a socks
8823 protocol error correctly, rather than calling both of them
8825 - Change reported stream target addresses to IP consistently when
8826 we finally get the IP from an exit node.
8827 - Send log messages to the controller even if they happen to be very
8830 o Minor bugfixes (other):
8831 - Display correct results when reporting which versions are
8832 recommended, and how recommended they are. (Resolves bug 383.)
8833 - Improve our estimates for directory bandwidth to be less random:
8834 guess that an unrecognized directory will have the average bandwidth
8835 from all known directories, not that it will have the average
8836 bandwidth from those directories earlier than it on the list.
8837 - If we start a server with ClientOnly 1, then set ClientOnly to 0
8838 and hup, stop triggering an assert based on an empty onion_key.
8839 - On platforms with no working mmap() equivalent, don't warn the
8840 user when cached-routers doesn't exist.
8841 - Warn the user when mmap() [or its equivalent] fails for some reason
8842 other than file-not-found.
8843 - Don't warn the user when cached-routers.new doesn't exist: that's
8844 perfectly fine when starting up for the first time.
8845 - When EntryNodes are configured, rebuild the guard list to contain,
8846 in order: the EntryNodes that were guards before; the rest of the
8847 EntryNodes; the nodes that were guards before.
8848 - Mask out all signals in sub-threads; only the libevent signal
8849 handler should be processing them. This should prevent some crashes
8850 on some machines using pthreads. (Patch from coderman.)
8851 - Fix switched arguments on memset in the implementation of
8852 tor_munmap() for systems with no mmap() call.
8853 - When Tor receives a router descriptor that it asked for, but
8854 no longer wants (because it has received fresh networkstatuses
8855 in the meantime), do not warn the user. Cache the descriptor if
8856 we're a cache; drop it if we aren't.
8857 - Make earlier entry guards _really_ get retried when the network
8859 - On a malformed DNS reply, always give an error to the corresponding
8861 - Build with recent libevents on platforms that do not define the
8862 nonstandard types "u_int8_t" and friends.
8864 o Minor features (controller):
8865 - Warn the user when an application uses the obsolete binary v0
8866 control protocol. We're planning to remove support for it during
8867 the next development series, so it's good to give people some
8869 - Add STREAM_BW events to report per-entry-stream bandwidth
8870 use. (Patch from Robert Hogan.)
8871 - Rate-limit SIGNEWNYM signals in response to controllers that
8872 impolitely generate them for every single stream. (Patch from
8873 mwenge; closes bug 394.)
8874 - Make REMAP stream events have a SOURCE (cache or exit), and
8875 make them generated in every case where we get a successful
8876 connected or resolved cell.
8878 o Minor bugfixes (performance):
8879 - Call router_have_min_dir_info half as often. (This is showing up in
8880 some profiles, but not others.)
8881 - When using GCC, make log_debug never get called at all, and its
8882 arguments never get evaluated, when no debug logs are configured.
8883 (This is showing up in some profiles, but not others.)
8886 - Remove some never-implemented options. Mark PathlenCoinWeight as
8888 - Implement proposal 106: Stop requiring clients to have well-formed
8889 certificates; stop checking nicknames in certificates. (Clients
8890 have certificates so that they can look like Tor servers, but in
8891 the future we might want to allow them to look like regular TLS
8892 clients instead. Nicknames in certificates serve no purpose other
8893 than making our protocol easier to recognize on the wire.)
8894 - Revise messages on handshake failure again to be even more clear about
8895 which are incoming connections and which are outgoing.
8896 - Discard any v1 directory info that's over 1 month old (for
8897 directories) or over 1 week old (for running-routers lists).
8898 - Do not warn when individual nodes in the configuration's EntryNodes,
8899 ExitNodes, etc are down: warn only when all possible nodes
8900 are down. (Fixes bug 348.)
8901 - Always remove expired routers and networkstatus docs before checking
8902 whether we have enough information to build circuits. (Fixes
8904 - Put a lower-bound on MaxAdvertisedBandwidth.
8907 Changes in version 0.1.2.7-alpha - 2007-02-06
8908 o Major bugfixes (rate limiting):
8909 - Servers decline directory requests much more aggressively when
8910 they're low on bandwidth. Otherwise they end up queueing more and
8911 more directory responses, which can't be good for latency.
8912 - But never refuse directory requests from local addresses.
8913 - Fix a memory leak when sending a 503 response for a networkstatus
8915 - Be willing to read or write on local connections (e.g. controller
8916 connections) even when the global rate limiting buckets are empty.
8917 - If our system clock jumps back in time, don't publish a negative
8918 uptime in the descriptor. Also, don't let the global rate limiting
8919 buckets go absurdly negative.
8920 - Flush local controller connection buffers periodically as we're
8921 writing to them, so we avoid queueing 4+ megabytes of data before
8924 o Major bugfixes (NT services):
8925 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
8926 command-line flag so that admins can override the default by saying
8927 "tor --service install --user "SomeUser"". This will not affect
8928 existing installed services. Also, warn the user that the service
8929 will look for its configuration file in the service user's
8930 %appdata% directory. (We can't do the 'hardwire the user's appdata
8931 directory' trick any more, since we may not have read access to that
8934 o Major bugfixes (other):
8935 - Previously, we would cache up to 16 old networkstatus documents
8936 indefinitely, if they came from nontrusted authorities. Now we
8937 discard them if they are more than 10 days old.
8938 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
8940 - Detect and reject malformed DNS responses containing circular
8942 - If exits are rare enough that we're not marking exits as guards,
8943 ignore exit bandwidth when we're deciding the required bandwidth
8945 - When we're handling a directory connection tunneled over Tor,
8946 don't fill up internal memory buffers with all the data we want
8947 to tunnel; instead, only add it if the OR connection that will
8948 eventually receive it has some room for it. (This can lead to
8949 slowdowns in tunneled dir connections; a better solution will have
8952 o Minor bugfixes (dns):
8953 - Add some defensive programming to eventdns.c in an attempt to catch
8954 possible memory-stomping bugs.
8955 - Detect and reject DNS replies containing IPv4 or IPv6 records with
8956 an incorrect number of bytes. (Previously, we would ignore the
8958 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
8959 in the correct order, and doesn't crash.
8960 - Free memory held in recently-completed DNS lookup attempts on exit.
8961 This was not a memory leak, but may have been hiding memory leaks.
8962 - Handle TTL values correctly on reverse DNS lookups.
8963 - Treat failure to parse resolv.conf as an error.
8965 o Minor bugfixes (other):
8966 - Fix crash with "tor --list-fingerprint" (reported by seeess).
8967 - When computing clock skew from directory HTTP headers, consider what
8968 time it was when we finished asking for the directory, not what
8970 - Expire socks connections if they spend too long waiting for the
8971 handshake to finish. Previously we would let them sit around for
8972 days, if the connecting application didn't close them either.
8973 - And if the socks handshake hasn't started, don't send a
8974 "DNS resolve socks failed" handshake reply; just close it.
8975 - Stop using C functions that OpenBSD's linker doesn't like.
8976 - Don't launch requests for descriptors unless we have networkstatuses
8977 from at least half of the authorities. This delays the first
8978 download slightly under pathological circumstances, but can prevent
8979 us from downloading a bunch of descriptors we don't need.
8980 - Do not log IPs with TLS failures for incoming TLS
8981 connections. (Fixes bug 382.)
8982 - If the user asks to use invalid exit nodes, be willing to use
8984 - Stop using the reserved ac_cv namespace in our configure script.
8985 - Call stat() slightly less often; use fstat() when possible.
8986 - Refactor the way we handle pending circuits when an OR connection
8987 completes or fails, in an attempt to fix a rare crash bug.
8988 - Only rewrite a conn's address based on X-Forwarded-For: headers
8989 if it's a parseable public IP address; and stop adding extra quotes
8990 to the resulting address.
8993 - Weight directory requests by advertised bandwidth. Now we can
8994 let servers enable write limiting but still allow most clients to
8995 succeed at their directory requests. (We still ignore weights when
8996 choosing a directory authority; I hope this is a feature.)
8999 - Create a new file ReleaseNotes which was the old ChangeLog. The
9000 new ChangeLog file now includes the summaries for all development
9002 - Check for addresses with invalid characters at the exit as well
9003 as at the client, and warn less verbosely when they fail. You can
9004 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9005 - Adapt a patch from goodell to let the contrib/exitlist script
9006 take arguments rather than require direct editing.
9007 - Inform the server operator when we decide not to advertise a
9008 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9009 was confusing Zax, so now we're hopefully more helpful.
9010 - Bring us one step closer to being able to establish an encrypted
9011 directory tunnel without knowing a descriptor first. Still not
9012 ready yet. As part of the change, now assume we can use a
9013 create_fast cell if we don't know anything about a router.
9014 - Allow exit nodes to use nameservers running on ports other than 53.
9015 - Servers now cache reverse DNS replies.
9016 - Add an --ignore-missing-torrc command-line option so that we can
9017 get the "use sensible defaults if the configuration file doesn't
9018 exist" behavior even when specifying a torrc location on the command
9021 o Minor features (controller):
9022 - Track reasons for OR connection failure; make these reasons
9023 available via the controller interface. (Patch from Mike Perry.)
9024 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9025 can learn when clients are sending malformed hostnames to Tor.
9026 - Clean up documentation for controller status events.
9027 - Add a REMAP status to stream events to note that a stream's
9028 address has changed because of a cached address or a MapAddress
9032 Changes in version 0.1.2.6-alpha - 2007-01-09
9034 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9035 connection handles more than 4 gigs in either direction, we crash.
9036 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9037 advertised exit node, somebody might try to exit from us when
9038 we're bootstrapping and before we've built our descriptor yet.
9039 Refuse the connection rather than crashing.
9042 - Warn if we (as a server) find that we've resolved an address that we
9043 weren't planning to resolve.
9044 - Warn that using select() on any libevent version before 1.1 will be
9045 unnecessarily slow (even for select()).
9046 - Flush ERR-level controller status events just like we currently
9047 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9048 the controller from learning about current events.
9050 o Minor features (more controller status events):
9051 - Implement EXTERNAL_ADDRESS server status event so controllers can
9052 learn when our address changes.
9053 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9054 can learn when directories reject our descriptor.
9055 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9056 can learn when a client application is speaking a non-socks protocol
9058 - Implement DANGEROUS_SOCKS client status event so controllers
9059 can learn when a client application is leaking DNS addresses.
9060 - Implement BUG general status event so controllers can learn when
9061 Tor is unhappy about its internal invariants.
9062 - Implement CLOCK_SKEW general status event so controllers can learn
9063 when Tor thinks the system clock is set incorrectly.
9064 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9065 server status events so controllers can learn when their descriptors
9066 are accepted by a directory.
9067 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9068 server status events so controllers can learn about Tor's progress in
9069 deciding whether it's reachable from the outside.
9070 - Implement BAD_LIBEVENT general status event so controllers can learn
9071 when we have a version/method combination in libevent that needs to
9073 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9074 and DNS_USELESS server status events so controllers can learn
9075 about changes to DNS server status.
9077 o Minor features (directory):
9078 - Authorities no longer recommend exits as guards if this would shift
9079 too much load to the exit nodes.
9082 Changes in version 0.1.2.5-alpha - 2007-01-06
9084 - Enable write limiting as well as read limiting. Now we sacrifice
9085 capacity if we're pushing out lots of directory traffic, rather
9086 than overrunning the user's intended bandwidth limits.
9087 - Include TLS overhead when counting bandwidth usage; previously, we
9088 would count only the bytes sent over TLS, but not the bytes used
9090 - Support running the Tor service with a torrc not in the same
9091 directory as tor.exe and default to using the torrc located in
9092 the %appdata%\Tor\ of the user who installed the service. Patch
9094 - Servers now check for the case when common DNS requests are going to
9095 wildcarded addresses (i.e. all getting the same answer), and change
9096 their exit policy to reject *:* if it's happening.
9097 - Implement BEGIN_DIR cells, so we can connect to the directory
9098 server via TLS to do encrypted directory requests rather than
9099 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9100 config options if you like.
9102 o Minor features (config and docs):
9103 - Start using the state file to store bandwidth accounting data:
9104 the bw_accounting file is now obsolete. We'll keep generating it
9105 for a while for people who are still using 0.1.2.4-alpha.
9106 - Try to batch changes to the state file so that we do as few
9107 disk writes as possible while still storing important things in
9109 - The state file and the bw_accounting file get saved less often when
9110 the AvoidDiskWrites config option is set.
9111 - Make PIDFile work on Windows (untested).
9112 - Add internal descriptions for a bunch of configuration options:
9113 accessible via controller interface and in comments in saved
9115 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9116 NNTP by default, so this seems like a sensible addition.
9117 - Clients now reject hostnames with invalid characters. This should
9118 avoid some inadvertent info leaks. Add an option
9119 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9120 is running a private network with hosts called @, !, and #.
9121 - Add a maintainer script to tell us which options are missing
9122 documentation: "make check-docs".
9123 - Add a new address-spec.txt document to describe our special-case
9124 addresses: .exit, .onion, and .noconnnect.
9126 o Minor features (DNS):
9127 - Ongoing work on eventdns infrastructure: now it has dns server
9128 and ipv6 support. One day Tor will make use of it.
9129 - Add client-side caching for reverse DNS lookups.
9130 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9131 - When we change nameservers or IP addresses, reset and re-launch
9132 our tests for DNS hijacking.
9134 o Minor features (directory):
9135 - Authorities now specify server versions in networkstatus. This adds
9136 about 2% to the size of compressed networkstatus docs, and allows
9137 clients to tell which servers support BEGIN_DIR and which don't.
9138 The implementation is forward-compatible with a proposed future
9139 protocol version scheme not tied to Tor versions.
9140 - DirServer configuration lines now have an orport= option so
9141 clients can open encrypted tunnels to the authorities without
9142 having downloaded their descriptors yet. Enabled for moria1,
9143 moria2, tor26, and lefkada now in the default configuration.
9144 - Directory servers are more willing to send a 503 "busy" if they
9145 are near their write limit, especially for v1 directory requests.
9146 Now they can use their limited bandwidth for actual Tor traffic.
9147 - Clients track responses with status 503 from dirservers. After a
9148 dirserver has given us a 503, we try not to use it until an hour has
9149 gone by, or until we have no dirservers that haven't given us a 503.
9150 - When we get a 503 from a directory, and we're not a server, we don't
9151 count the failure against the total number of failures allowed
9152 for the thing we're trying to download.
9153 - Report X-Your-Address-Is correctly from tunneled directory
9154 connections; don't report X-Your-Address-Is when it's an internal
9155 address; and never believe reported remote addresses when they're
9157 - Protect against an unlikely DoS attack on directory servers.
9158 - Add a BadDirectory flag to network status docs so that authorities
9159 can (eventually) tell clients about caches they believe to be
9162 o Minor features (controller):
9163 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9164 - Reimplement GETINFO so that info/names stays in sync with the
9166 - Implement "GETINFO fingerprint".
9167 - Implement "SETEVENTS GUARD" so controllers can get updates on
9168 entry guard status as it changes.
9170 o Minor features (clean up obsolete pieces):
9171 - Remove some options that have been deprecated since at least
9172 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9173 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9175 - We no longer look for identity and onion keys in "identity.key" and
9176 "onion.key" -- these were replaced by secret_id_key and
9177 secret_onion_key in 0.0.8pre1.
9178 - We no longer require unrecognized directory entries to be
9181 o Major bugfixes (security):
9182 - Stop sending the HttpProxyAuthenticator string to directory
9183 servers when directory connections are tunnelled through Tor.
9184 - Clients no longer store bandwidth history in the state file.
9185 - Do not log introduction points for hidden services if SafeLogging
9187 - When generating bandwidth history, round down to the nearest
9188 1k. When storing accounting data, round up to the nearest 1k.
9189 - When we're running as a server, remember when we last rotated onion
9190 keys, so that we will rotate keys once they're a week old even if
9191 we never stay up for a week ourselves.
9193 o Major bugfixes (other):
9194 - Fix a longstanding bug in eventdns that prevented the count of
9195 timed-out resolves from ever being reset. This bug caused us to
9196 give up on a nameserver the third time it timed out, and try it
9197 10 seconds later... and to give up on it every time it timed out
9199 - Take out the '5 second' timeout from the connection retry
9200 schedule. Now the first connect attempt will wait a full 10
9201 seconds before switching to a new circuit. Perhaps this will help
9202 a lot. Based on observations from Mike Perry.
9203 - Fix a bug on the Windows implementation of tor_mmap_file() that
9204 would prevent the cached-routers file from ever loading. Reported
9208 - Fix an assert failure when a directory authority sets
9209 AuthDirRejectUnlisted and then receives a descriptor from an
9210 unlisted router. Reported by seeess.
9211 - Avoid a double-free when parsing malformed DirServer lines.
9212 - Fix a bug when a BSD-style PF socket is first used. Patch from
9214 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9215 to resolve an address at a given exit node even when they ask for
9217 - Servers no longer ever list themselves in their "family" line,
9218 even if configured to do so. This makes it easier to configure
9219 family lists conveniently.
9220 - When running as a server, don't fall back to 127.0.0.1 when no
9221 nameservers are configured in /etc/resolv.conf; instead, make the
9222 user fix resolv.conf or specify nameservers explicitly. (Resolves
9224 - Stop accepting certain malformed ports in configured exit policies.
9225 - Don't re-write the fingerprint file every restart, unless it has
9227 - Stop warning when a single nameserver fails: only warn when _all_ of
9228 our nameservers have failed. Also, when we only have one nameserver,
9229 raise the threshold for deciding that the nameserver is dead.
9230 - Directory authorities now only decide that routers are reachable
9231 if their identity keys are as expected.
9232 - When the user uses bad syntax in the Log config line, stop
9233 suggesting other bad syntax as a replacement.
9234 - Correctly detect ipv6 DNS capability on OpenBSD.
9236 o Minor bugfixes (controller):
9237 - Report the circuit number correctly in STREAM CLOSED events. Bug
9238 reported by Mike Perry.
9239 - Do not report bizarre values for results of accounting GETINFOs
9240 when the last second's write or read exceeds the allotted bandwidth.
9241 - Report "unrecognized key" rather than an empty string when the
9242 controller tries to fetch a networkstatus that doesn't exist.
9245 Changes in version 0.1.1.26 - 2006-12-14
9246 o Security bugfixes:
9247 - Stop sending the HttpProxyAuthenticator string to directory
9248 servers when directory connections are tunnelled through Tor.
9249 - Clients no longer store bandwidth history in the state file.
9250 - Do not log introduction points for hidden services if SafeLogging
9254 - Fix an assert failure when a directory authority sets
9255 AuthDirRejectUnlisted and then receives a descriptor from an
9256 unlisted router (reported by seeess).
9259 Changes in version 0.1.2.4-alpha - 2006-12-03
9261 - Add support for using natd; this allows FreeBSDs earlier than
9262 5.1.2 to have ipfw send connections through Tor without using
9263 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9266 - Make all connections to addresses of the form ".noconnect"
9267 immediately get closed. This lets application/controller combos
9268 successfully test whether they're talking to the same Tor by
9269 watching for STREAM events.
9270 - Make cross.sh cross-compilation script work even when autogen.sh
9271 hasn't been run. (Patch from Michael Mohr.)
9272 - Statistics dumped by -USR2 now include a breakdown of public key
9273 operations, for profiling.
9276 - Fix a major leak when directory authorities parse their
9277 approved-routers list, a minor memory leak when we fail to pick
9278 an exit node, and a few rare leaks on errors.
9279 - Handle TransPort connections even when the server sends data before
9280 the client sends data. Previously, the connection would just hang
9281 until the client sent data. (Patch from tup based on patch from
9283 - Avoid assert failure when our cached-routers file is empty on
9287 - Don't log spurious warnings when we see a circuit close reason we
9288 don't recognize; it's probably just from a newer version of Tor.
9289 - Have directory authorities allow larger amounts of drift in uptime
9290 without replacing the server descriptor: previously, a server that
9291 restarted every 30 minutes could have 48 "interesting" descriptors
9293 - Start linking to the Tor specification and Tor reference manual
9294 correctly in the Windows installer.
9295 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9296 Tor/Privoxy we also uninstall Vidalia.
9297 - Resume building on Irix64, and fix a lot of warnings from its
9299 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
9300 when we're running as a client.
9303 Changes in version 0.1.1.25 - 2006-11-04
9305 - When a client asks us to resolve (rather than connect to)
9306 an address, and we have a cached answer, give them the cached
9307 answer. Previously, we would give them no answer at all.
9308 - We were building exactly the wrong circuits when we predict
9309 hidden service requirements, meaning Tor would have to build all
9310 its circuits on demand.
9311 - If none of our live entry guards have a high uptime, but we
9312 require a guard with a high uptime, try adding a new guard before
9313 we give up on the requirement. This patch should make long-lived
9314 connections more stable on average.
9315 - When testing reachability of our DirPort, don't launch new
9316 tests when there's already one in progress -- unreachable
9317 servers were stacking up dozens of testing streams.
9319 o Security bugfixes:
9320 - When the user sends a NEWNYM signal, clear the client-side DNS
9321 cache too. Otherwise we continue to act on previous information.
9324 - Avoid a memory corruption bug when creating a hash table for
9326 - Avoid possibility of controller-triggered crash when misusing
9327 certain commands from a v0 controller on platforms that do not
9328 handle printf("%s",NULL) gracefully.
9329 - Avoid infinite loop on unexpected controller input.
9330 - Don't log spurious warnings when we see a circuit close reason we
9331 don't recognize; it's probably just from a newer version of Tor.
9332 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9333 Tor/Privoxy we also uninstall Vidalia.
9336 Changes in version 0.1.2.3-alpha - 2006-10-29
9338 - Prepare for servers to publish descriptors less often: never
9339 discard a descriptor simply for being too old until either it is
9340 recommended by no authorities, or until we get a better one for
9341 the same router. Make caches consider retaining old recommended
9342 routers for even longer.
9343 - If most authorities set a BadExit flag for a server, clients
9344 don't think of it as a general-purpose exit. Clients only consider
9345 authorities that advertise themselves as listing bad exits.
9346 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9347 headers for content, so that we can work better in the presence of
9348 caching HTTP proxies.
9349 - Allow authorities to list nodes as bad exits by fingerprint or by
9352 o Minor features, controller:
9353 - Add a REASON field to CIRC events; for backward compatibility, this
9354 field is sent only to controllers that have enabled the extended
9355 event format. Also, add additional reason codes to explain why
9356 a given circuit has been destroyed or truncated. (Patches from
9358 - Add a REMOTE_REASON field to extended CIRC events to tell the
9359 controller about why a remote OR told us to close a circuit.
9360 - Stream events also now have REASON and REMOTE_REASON fields,
9361 working much like those for circuit events.
9362 - There's now a GETINFO ns/... field so that controllers can ask Tor
9363 about the current status of a router.
9364 - A new event type "NS" to inform a controller when our opinion of
9365 a router's status has changed.
9366 - Add a GETINFO events/names and GETINFO features/names so controllers
9367 can tell which events and features are supported.
9368 - A new CLEARDNSCACHE signal to allow controllers to clear the
9369 client-side DNS cache without expiring circuits.
9371 o Security bugfixes:
9372 - When the user sends a NEWNYM signal, clear the client-side DNS
9373 cache too. Otherwise we continue to act on previous information.
9376 - Avoid sending junk to controllers or segfaulting when a controller
9377 uses EVENT_NEW_DESC with verbose nicknames.
9378 - Stop triggering asserts if the controller tries to extend hidden
9379 service circuits (reported by mwenge).
9380 - Avoid infinite loop on unexpected controller input.
9381 - When the controller does a "GETINFO network-status", tell it
9382 about even those routers whose descriptors are very old, and use
9383 long nicknames where appropriate.
9384 - Change NT service functions to be loaded on demand. This lets us
9385 build with MinGW without breaking Tor for Windows 98 users.
9386 - Do DirPort reachability tests less often, since a single test
9387 chews through many circuits before giving up.
9388 - In the hidden service example in torrc.sample, stop recommending
9389 esoteric and discouraged hidden service options.
9390 - When stopping an NT service, wait up to 10 sec for it to actually
9391 stop. Patch from Matt Edman; resolves bug 295.
9392 - Fix handling of verbose nicknames with ORCONN controller events:
9393 make them show up exactly when requested, rather than exactly when
9395 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
9396 printing a duplicate "$" in the keys we send (reported by mwenge).
9397 - Correctly set maximum connection limit on Cygwin. (This time
9399 - Try to detect Windows correctly when cross-compiling.
9400 - Detect the size of the routers file correctly even if it is
9401 corrupted (on systems without mmap) or not page-aligned (on systems
9402 with mmap). This bug was harmless.
9403 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
9404 to open a stream fails; now we do in more cases. This should
9405 make clients able to find a good exit faster in some cases, since
9406 unhandleable requests will now get an error rather than timing out.
9407 - Resolve two memory leaks when rebuilding the on-disk router cache
9408 (reported by fookoowa).
9409 - Clean up minor code warnings suggested by the MIPSpro C compiler,
9410 and reported by some Centos users.
9411 - Controller signals now work on non-Unix platforms that don't define
9412 SIGUSR1 and SIGUSR2 the way we expect.
9413 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
9414 values before failing, and always enables eventdns.
9415 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
9416 Try to fix this in configure.in by checking for most functions
9417 before we check for libevent.
9420 Changes in version 0.1.2.2-alpha - 2006-10-07
9422 - Make our async eventdns library on-by-default for Tor servers,
9423 and plan to deprecate the separate dnsworker threads.
9424 - Add server-side support for "reverse" DNS lookups (using PTR
9425 records so clients can determine the canonical hostname for a given
9426 IPv4 address). Only supported by servers using eventdns; servers
9427 now announce in their descriptors whether they support eventdns.
9428 - Specify and implement client-side SOCKS5 interface for reverse DNS
9429 lookups (see doc/socks-extensions.txt).
9430 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
9431 connect to directory servers through Tor. Previously, clients needed
9432 to find Tor exits to make private connections to directory servers.
9433 - Avoid choosing Exit nodes for entry or middle hops when the
9434 total bandwidth available from non-Exit nodes is much higher than
9435 the total bandwidth available from Exit nodes.
9436 - Workaround for name servers (like Earthlink's) that hijack failing
9437 DNS requests and replace the no-such-server answer with a "helpful"
9438 redirect to an advertising-driven search portal. Also work around
9439 DNS hijackers who "helpfully" decline to hijack known-invalid
9440 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
9441 lets you turn it off.
9442 - Send out a burst of long-range padding cells once we've established
9443 that we're reachable. Spread them over 4 circuits, so hopefully
9444 a few will be fast. This exercises our bandwidth and bootstraps
9445 us into the directory more quickly.
9447 o New/improved config options:
9448 - Add new config option "ResolvConf" to let the server operator
9449 choose an alternate resolve.conf file when using eventdns.
9450 - Add an "EnforceDistinctSubnets" option to control our "exclude
9451 servers on the same /16" behavior. It's still on by default; this
9452 is mostly for people who want to operate private test networks with
9453 all the machines on the same subnet.
9454 - If one of our entry guards is on the ExcludeNodes list, or the
9455 directory authorities don't think it's a good guard, treat it as
9456 if it were unlisted: stop using it as a guard, and throw it off
9457 the guards list if it stays that way for a long time.
9458 - Allow directory authorities to be marked separately as authorities
9459 for the v1 directory protocol, the v2 directory protocol, and
9460 as hidden service directories, to make it easier to retire old
9461 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9462 to continue being hidden service authorities too.
9463 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9465 o Minor features, controller:
9466 - Fix CIRC controller events so that controllers can learn the
9467 identity digests of non-Named servers used in circuit paths.
9468 - Let controllers ask for more useful identifiers for servers. Instead
9469 of learning identity digests for un-Named servers and nicknames
9470 for Named servers, the new identifiers include digest, nickname,
9471 and indication of Named status. Off by default; see control-spec.txt
9472 for more information.
9473 - Add a "getinfo address" controller command so it can display Tor's
9474 best guess to the user.
9475 - New controller event to alert the controller when our server
9476 descriptor has changed.
9477 - Give more meaningful errors on controller authentication failure.
9479 o Minor features, other:
9480 - When asked to resolve a hostname, don't use non-exit servers unless
9481 requested to do so. This allows servers with broken DNS to be
9482 useful to the network.
9483 - Divide eventdns log messages into warn and info messages.
9484 - Reserve the nickname "Unnamed" for routers that can't pick
9485 a hostname: any router can call itself Unnamed; directory
9486 authorities will never allocate Unnamed to any particular router;
9487 clients won't believe that any router is the canonical Unnamed.
9488 - Only include function names in log messages for info/debug messages.
9489 For notice/warn/err, the content of the message should be clear on
9490 its own, and printing the function name only confuses users.
9491 - Avoid some false positives during reachability testing: don't try
9492 to test via a server that's on the same /24 as us.
9493 - If we fail to build a circuit to an intended enclave, and it's
9494 not mandatory that we use that enclave, stop wanting it.
9495 - When eventdns is enabled, allow multithreaded builds on NetBSD and
9496 OpenBSD. (We had previously disabled threads on these platforms
9497 because they didn't have working thread-safe resolver functions.)
9499 o Major bugfixes, anonymity/security:
9500 - If a client asked for a server by name, and there's a named server
9501 in our network-status but we don't have its descriptor yet, we
9502 could return an unnamed server instead.
9503 - Fix NetBSD bug that could allow someone to force uninitialized RAM
9504 to be sent to a server's DNS resolver. This only affects NetBSD
9505 and other platforms that do not bounds-check tolower().
9506 - Reject (most) attempts to use Tor circuits with length one. (If
9507 many people start using Tor as a one-hop proxy, exit nodes become
9508 a more attractive target for compromise.)
9509 - Just because your DirPort is open doesn't mean people should be
9510 able to remotely teach you about hidden service descriptors. Now
9511 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9513 o Major bugfixes, other:
9514 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
9515 - When a client asks the server to resolve (not connect to)
9516 an address, and it has a cached answer, give them the cached answer.
9517 Previously, the server would give them no answer at all.
9518 - Allow really slow clients to not hang up five minutes into their
9519 directory downloads (suggested by Adam J. Richter).
9520 - We were building exactly the wrong circuits when we anticipated
9521 hidden service requirements, meaning Tor would have to build all
9522 its circuits on demand.
9523 - Avoid crashing when we mmap a router cache file of size 0.
9524 - When testing reachability of our DirPort, don't launch new
9525 tests when there's already one in progress -- unreachable
9526 servers were stacking up dozens of testing streams.
9528 o Minor bugfixes, correctness:
9529 - If we're a directory mirror and we ask for "all" network status
9530 documents, we would discard status documents from authorities
9532 - Avoid a memory corruption bug when creating a hash table for
9534 - Avoid controller-triggered crash when misusing certain commands
9535 from a v0 controller on platforms that do not handle
9536 printf("%s",NULL) gracefully.
9537 - Don't crash when a controller sends a third argument to an
9538 "extendcircuit" request.
9539 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9540 response; fix error code when "getinfo dir/status/" fails.
9541 - Avoid crash when telling controller stream-status and a stream
9543 - Patch from Adam Langley to fix assert() in eventdns.c.
9544 - Fix a debug log message in eventdns to say "X resolved to Y"
9545 instead of "X resolved to X".
9546 - Make eventdns give strings for DNS errors, not just error numbers.
9547 - Track unreachable entry guards correctly: don't conflate
9548 'unreachable by us right now' with 'listed as down by the directory
9549 authorities'. With the old code, if a guard was unreachable by
9550 us but listed as running, it would clog our guard list forever.
9551 - Behave correctly in case we ever have a network with more than
9552 2GB/s total advertised capacity.
9553 - Make TrackExitHosts case-insensitive, and fix the behavior of
9554 ".suffix" TrackExitHosts items to avoid matching in the middle of
9556 - Finally fix the openssl warnings from newer gccs that believe that
9557 ignoring a return value is okay, but casting a return value and
9558 then ignoring it is a sign of madness.
9559 - Prevent the contrib/exitlist script from printing the same
9560 result more than once.
9561 - Patch from Steve Hildrey: Generate network status correctly on
9562 non-versioning dirservers.
9563 - Don't listen to the X-Your-Address-Is hint if you did the lookup
9564 via Tor; otherwise you'll think you're the exit node's IP address.
9566 o Minor bugfixes, performance:
9567 - Two small performance improvements on parsing descriptors.
9568 - Major performance improvement on inserting descriptors: change
9569 algorithm from O(n^2) to O(n).
9570 - Make the common memory allocation path faster on machines where
9571 malloc(0) returns a pointer.
9572 - Start remembering X-Your-Address-Is directory hints even if you're
9573 a client, so you can become a server more smoothly.
9574 - Avoid duplicate entries on MyFamily line in server descriptor.
9576 o Packaging, features:
9577 - Remove architecture from OS X builds. The official builds are
9578 now universal binaries.
9579 - The Debian package now uses --verify-config when (re)starting,
9580 to distinguish configuration errors from other errors.
9581 - Update RPMs to require libevent 1.1b.
9583 o Packaging, bugfixes:
9584 - Patches so Tor builds with MinGW on Windows.
9585 - Patches so Tor might run on Cygwin again.
9586 - Resume building on non-gcc compilers and ancient gcc. Resume
9587 building with the -O0 compile flag. Resume building cleanly on
9589 - Run correctly on OS X platforms with case-sensitive filesystems.
9590 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
9591 - Add autoconf checks so Tor can build on Solaris x86 again.
9594 - Documented (and renamed) ServerDNSSearchDomains and
9595 ServerDNSResolvConfFile options.
9596 - Be clearer that the *ListenAddress directives can be repeated
9600 Changes in version 0.1.1.24 - 2006-09-29
9602 - Allow really slow clients to not hang up five minutes into their
9603 directory downloads (suggested by Adam J. Richter).
9604 - Fix major performance regression from 0.1.0.x: instead of checking
9605 whether we have enough directory information every time we want to
9606 do something, only check when the directory information has changed.
9607 This should improve client CPU usage by 25-50%.
9608 - Don't crash if, after a server has been running for a while,
9609 it can't resolve its hostname.
9612 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9613 - Don't crash when the controller receives a third argument to an
9614 "extendcircuit" request.
9615 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9616 response; fix error code when "getinfo dir/status/" fails.
9617 - Fix configure.in to not produce broken configure files with
9618 more recent versions of autoconf. Thanks to Clint for his auto*
9620 - Fix security bug on NetBSD that could allow someone to force
9621 uninitialized RAM to be sent to a server's DNS resolver. This
9622 only affects NetBSD and other platforms that do not bounds-check
9624 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
9625 methods: these are known to be buggy.
9626 - If we're a directory mirror and we ask for "all" network status
9627 documents, we would discard status documents from authorities
9631 Changes in version 0.1.2.1-alpha - 2006-08-27
9633 - Add "eventdns" async dns library from Adam Langley, tweaked to
9634 build on OSX and Windows. Only enabled if you pass the
9635 --enable-eventdns argument to configure.
9636 - Allow servers with no hostname or IP address to learn their
9637 IP address by asking the directory authorities. This code only
9638 kicks in when you would normally have exited with a "no address"
9639 error. Nothing's authenticated, so use with care.
9640 - Rather than waiting a fixed amount of time between retrying
9641 application connections, we wait only 5 seconds for the first,
9642 10 seconds for the second, and 15 seconds for each retry after
9643 that. Hopefully this will improve the expected user experience.
9644 - Patch from Tup to add support for transparent AP connections:
9645 this basically bundles the functionality of trans-proxy-tor
9646 into the Tor mainline. Now hosts with compliant pf/netfilter
9647 implementations can redirect TCP connections straight to Tor
9648 without diverting through SOCKS. Needs docs.
9649 - Busy directory servers save lots of memory by spooling server
9650 descriptors, v1 directories, and v2 networkstatus docs to buffers
9651 as needed rather than en masse. Also mmap the cached-routers
9652 files, so we don't need to keep the whole thing in memory too.
9653 - Automatically avoid picking more than one node from the same
9654 /16 network when constructing a circuit.
9655 - Revise and clean up the torrc.sample that we ship with; add
9656 a section for BandwidthRate and BandwidthBurst.
9659 - Split circuit_t into origin_circuit_t and or_circuit_t, and
9660 split connection_t into edge, or, dir, control, and base structs.
9661 These will save quite a bit of memory on busy servers, and they'll
9662 also help us track down bugs in the code and bugs in the spec.
9663 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
9664 or later. Log when we are doing this, so we can diagnose it when
9665 it fails. (Also, recommend libevent 1.1b for kqueue and
9666 win32 methods; deprecate libevent 1.0b harder; make libevent
9667 recommendation system saner.)
9668 - Start being able to build universal binaries on OS X (thanks
9670 - Export the default exit policy via the control port, so controllers
9671 don't need to guess what it is / will be later.
9672 - Add a man page entry for ProtocolWarnings.
9673 - Add TestVia config option to the man page.
9674 - Remove even more protocol-related warnings from Tor server logs,
9675 such as bad TLS handshakes and malformed begin cells.
9676 - Stop fetching descriptors if you're not a dir mirror and you
9677 haven't tried to establish any circuits lately. [This currently
9678 causes some dangerous behavior, because when you start up again
9679 you'll use your ancient server descriptors.]
9680 - New DirPort behavior: if you have your dirport set, you download
9681 descriptors aggressively like a directory mirror, whether or not
9683 - Get rid of the router_retry_connections notion. Now routers
9684 no longer try to rebuild long-term connections to directory
9685 authorities, and directory authorities no longer try to rebuild
9686 long-term connections to all servers. We still don't hang up
9687 connections in these two cases though -- we need to look at it
9688 more carefully to avoid flapping, and we likely need to wait til
9689 0.1.1.x is obsolete.
9690 - Drop compatibility with obsolete Tors that permit create cells
9691 to have the wrong circ_id_type.
9692 - Re-enable per-connection rate limiting. Get rid of the "OP
9693 bandwidth" concept. Lay groundwork for "bandwidth classes" --
9694 separate global buckets that apply depending on what sort of conn
9696 - Start publishing one minute or so after we find our ORPort
9697 to be reachable. This will help reduce the number of descriptors
9698 we have for ourselves floating around, since it's quite likely
9699 other things (e.g. DirPort) will change during that minute too.
9700 - Fork the v1 directory protocol into its own spec document,
9701 and mark dir-spec.txt as the currently correct (v2) spec.
9704 - When we find our DirPort to be reachable, publish a new descriptor
9705 so we'll tell the world (reported by pnx).
9706 - Publish a new descriptor after we hup/reload. This is important
9707 if our config has changed such that we'll want to start advertising
9708 our DirPort now, etc.
9709 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9710 - When we have a state file we cannot parse, tell the user and
9711 move it aside. Now we avoid situations where the user starts
9712 Tor in 1904, Tor writes a state file with that timestamp in it,
9713 the user fixes her clock, and Tor refuses to start.
9714 - Fix configure.in to not produce broken configure files with
9715 more recent versions of autoconf. Thanks to Clint for his auto*
9717 - "tor --verify-config" now exits with -1(255) or 0 depending on
9718 whether the config options are bad or good.
9719 - Resolve bug 321 when using dnsworkers: append a period to every
9720 address we resolve at the exit node, so that we do not accidentally
9721 pick up local addresses, and so that failing searches are retried
9722 in the resolver search domains. (This is already solved for
9723 eventdns.) (This breaks Blossom servers for now.)
9724 - If we are using an exit enclave and we can't connect, e.g. because
9725 its webserver is misconfigured to not listen on localhost, then
9726 back off and try connecting from somewhere else before we fail.
9729 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
9730 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
9731 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
9732 when the IP address is mapped through MapAddress to a hostname.
9733 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
9734 useless IPv6 DNS resolves.
9735 - Patch suggested by Karsten Loesing: respond to SIGNAL command
9736 before we execute the signal, in case the signal shuts us down.
9737 - Clean up AllowInvalidNodes man page entry.
9738 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
9739 - Add more asserts to track down an assert error on a windows Tor
9740 server with connection_add being called with socket == -1.
9741 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
9742 - Fix misleading log messages: an entry guard that is "unlisted",
9743 as well as not known to be "down" (because we've never heard
9744 of it), is not therefore "up".
9745 - Remove code to special-case "-cvs" ending, since it has not
9746 actually mattered since 0.0.9.
9747 - Make our socks5 handling more robust to broken socks clients:
9748 throw out everything waiting on the buffer in between socks
9749 handshake phases, since they can't possibly (so the theory
9750 goes) have predicted what we plan to respond to them.
9753 Changes in version 0.1.1.23 - 2006-07-30
9755 - Fast Tor servers, especially exit nodes, were triggering asserts
9756 due to a bug in handling the list of pending DNS resolves. Some
9757 bugs still remain here; we're hunting them.
9758 - Entry guards could crash clients by sending unexpected input.
9759 - More fixes on reachability testing: if you find yourself reachable,
9760 then don't ever make any client requests (so you stop predicting
9761 circuits), then hup or have your clock jump, then later your IP
9762 changes, you won't think circuits are working, so you won't try to
9763 test reachability, so you won't publish.
9766 - Avoid a crash if the controller does a resetconf firewallports
9767 and then a setconf fascistfirewall=1.
9768 - Avoid an integer underflow when the dir authority decides whether
9769 a router is stable: we might wrongly label it stable, and compute
9770 a slightly wrong median stability, when a descriptor is published
9772 - Fix a place where we might trigger an assert if we can't build our
9773 own server descriptor yet.
9776 Changes in version 0.1.1.22 - 2006-07-05
9778 - Fix a big bug that was causing servers to not find themselves
9779 reachable if they changed IP addresses. Since only 0.1.1.22+
9780 servers can do reachability testing correctly, now we automatically
9781 make sure to test via one of these.
9782 - Fix to allow clients and mirrors to learn directory info from
9783 descriptor downloads that get cut off partway through.
9784 - Directory authorities had a bug in deciding if a newly published
9785 descriptor was novel enough to make everybody want a copy -- a few
9786 servers seem to be publishing new descriptors many times a minute.
9788 - Fix a rare bug that was causing some servers to complain about
9789 "closing wedged cpuworkers" and skip some circuit create requests.
9790 - Make the Exit flag in directory status documents actually work.
9793 Changes in version 0.1.1.21 - 2006-06-10
9794 o Crash and assert fixes from 0.1.1.20:
9795 - Fix a rare crash on Tor servers that have enabled hibernation.
9796 - Fix a seg fault on startup for Tor networks that use only one
9797 directory authority.
9798 - Fix an assert from a race condition that occurs on Tor servers
9799 while exiting, where various threads are trying to log that they're
9800 exiting, and delete the logs, at the same time.
9801 - Make our unit tests pass again on certain obscure platforms.
9804 - Add support for building SUSE RPM packages.
9805 - Speed up initial bootstrapping for clients: if we are making our
9806 first ever connection to any entry guard, then don't mark it down
9808 - When only one Tor server in the network is labelled as a guard,
9809 and we've already picked him, we would cycle endlessly picking him
9810 again, being unhappy about it, etc. Now we specifically exclude
9811 current guards when picking a new guard.
9812 - Servers send create cells more reliably after the TLS connection
9813 is established: we were sometimes forgetting to send half of them
9814 when we had more than one pending.
9815 - If we get a create cell that asks us to extend somewhere, but the
9816 Tor server there doesn't match the expected digest, we now send
9817 a destroy cell back, rather than silently doing nothing.
9818 - Make options->RedirectExit work again.
9819 - Make cookie authentication for the controller work again.
9820 - Stop being picky about unusual characters in the arguments to
9821 mapaddress. It's none of our business.
9822 - Add a new config option "TestVia" that lets you specify preferred
9823 middle hops to use for test circuits. Perhaps this will let me
9824 debug the reachability problems better.
9826 o Log / documentation fixes:
9827 - If we're a server and some peer has a broken TLS certificate, don't
9828 log about it unless ProtocolWarnings is set, i.e., we want to hear
9829 about protocol violations by others.
9830 - Fix spelling of VirtualAddrNetwork in man page.
9831 - Add a better explanation at the top of the autogenerated torrc file
9832 about what happened to our old torrc.
9835 Changes in version 0.1.1.20 - 2006-05-23
9837 - Downgrade a log severity where servers complain that they're
9839 - Avoid a compile warning on FreeBSD.
9840 - Remove string size limit on NEWDESC messages; solve bug 291.
9841 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
9842 more thoroughly when we're running on windows.
9845 Changes in version 0.1.1.19-rc - 2006-05-03
9847 - Regenerate our local descriptor if it's dirty and we try to use
9848 it locally (e.g. if it changes during reachability detection).
9849 - If we setconf our ORPort to 0, we continued to listen on the
9850 old ORPort and receive connections.
9851 - Avoid a second warning about machine/limits.h on Debian
9853 - Be willing to add our own routerinfo into the routerlist.
9854 Now authorities will include themselves in their directories
9855 and network-statuses.
9856 - Stop trying to upload rendezvous descriptors to every
9857 directory authority: only try the v1 authorities.
9858 - Servers no longer complain when they think they're not
9859 registered with the directory authorities. There were too many
9861 - Backport dist-rpm changes so rpms can be built without errors.
9864 - Implement an option, VirtualAddrMask, to set which addresses
9865 get handed out in response to mapaddress requests. This works
9866 around a bug in tsocks where 127.0.0.0/8 is never socksified.
9869 Changes in version 0.1.1.18-rc - 2006-04-10
9871 - Work harder to download live network-statuses from all the
9872 directory authorities we know about. Improve the threshold
9873 decision logic so we're more robust to edge cases.
9874 - When fetching rendezvous descriptors, we were willing to ask
9875 v2 authorities too, which would always return 404.
9878 - Stop listing down or invalid nodes in the v1 directory. This will
9879 reduce its bulk by about 1/3, and reduce load on directory
9881 - When deciding whether a router is Fast or Guard-worthy, consider
9882 his advertised BandwidthRate and not just the BandwidthCapacity.
9883 - No longer ship INSTALL and README files -- they are useless now.
9884 - Force rpmbuild to behave and honor target_cpu.
9885 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
9886 - Start to include translated versions of the tor-doc-*.html
9887 files, along with the screenshots. Still needs more work.
9888 - Start sending back 512 and 451 errors if mapaddress fails,
9889 rather than not sending anything back at all.
9890 - When we fail to bind or listen on an incoming or outgoing
9891 socket, we should close it before failing. otherwise we just
9892 leak it. (thanks to weasel for finding.)
9893 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
9894 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
9895 - Make NoPublish (even though deprecated) work again.
9896 - Fix a minor security flaw where a versioning auth dirserver
9897 could list a recommended version many times in a row to make
9898 clients more convinced that it's recommended.
9899 - Fix crash bug if there are two unregistered servers running
9900 with the same nickname, one of them is down, and you ask for
9901 them by nickname in your EntryNodes or ExitNodes. Also, try
9902 to pick the one that's running rather than an arbitrary one.
9903 - Fix an infinite loop we could hit if we go offline for too long.
9904 - Complain when we hit WSAENOBUFS on recv() or write() too.
9905 Perhaps this will help us hunt the bug.
9906 - If you're not a versioning dirserver, don't put the string
9907 "client-versions \nserver-versions \n" in your network-status.
9908 - Lower the minimum required number of file descriptors to 1000,
9909 so we can have some overhead for Valgrind on Linux, where the
9910 default ulimit -n is 1024.
9913 - Add tor.dizum.com as the fifth authoritative directory server.
9914 - Add a new config option FetchUselessDescriptors, off by default,
9915 for when you plan to run "exitlist" on your client and you want
9916 to know about even the non-running descriptors.
9919 Changes in version 0.1.1.17-rc - 2006-03-28
9921 - Clients and servers since 0.1.1.10-alpha have been expiring
9922 connections whenever they are idle for 5 minutes and they *do*
9923 have circuits on them. Oops. With this new version, clients will
9924 discard their previous entry guard choices and avoid choosing
9925 entry guards running these flawed versions.
9926 - Fix memory leak when uncompressing concatenated zlib streams. This
9927 was causing substantial leaks over time on Tor servers.
9928 - The v1 directory was including servers as much as 48 hours old,
9929 because that's how the new routerlist->routers works. Now only
9930 include them if they're 20 hours old or less.
9933 - Resume building on irix64, netbsd 2.0, etc.
9934 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
9936 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
9937 and it is confusing some users.
9938 - Mirrors stop caching the v1 directory so often.
9939 - Make the max number of old descriptors that a cache will hold
9940 rise with the number of directory authorities, so we can scale.
9941 - Change our win32 uname() hack to be more forgiving about what
9942 win32 versions it thinks it's found.
9945 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
9947 - When the controller's *setconf commands fail, collect an error
9948 message in a string and hand it back to the controller.
9949 - Make the v2 dir's "Fast" flag based on relative capacity, just
9950 like "Stable" is based on median uptime. Name everything in the
9951 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
9952 - Log server fingerprint on startup, so new server operators don't
9953 have to go hunting around their filesystem for it.
9954 - Return a robots.txt on our dirport to discourage google indexing.
9955 - Let the controller ask for GETINFO dir/status/foo so it can ask
9956 directly rather than connecting to the dir port. Only works when
9957 dirport is set for now.
9959 o New config options rather than constants in the code:
9960 - SocksTimeout: How long do we let a socks connection wait
9961 unattached before we fail it?
9962 - CircuitBuildTimeout: Cull non-open circuits that were born
9963 at least this many seconds ago.
9964 - CircuitIdleTimeout: Cull open clean circuits that were born
9965 at least this many seconds ago.
9968 Changes in version 0.1.1.16-rc - 2006-03-18
9969 o Bugfixes on 0.1.1.15-rc:
9970 - Fix assert when the controller asks to attachstream a connect-wait
9971 or resolve-wait stream.
9972 - Now do address rewriting when the controller asks us to attach
9973 to a particular circuit too. This will let Blossom specify
9974 "moria2.exit" without having to learn what moria2's IP address is.
9975 - Make the "tor --verify-config" command-line work again, so people
9976 can automatically check if their torrc will parse.
9977 - Authoritative dirservers no longer require an open connection from
9978 a server to consider him "reachable". We need this change because
9979 when we add new auth dirservers, old servers won't know not to
9981 - Let Tor build on Sun CC again.
9982 - Fix an off-by-one buffer size in dirserv.c that magically never
9983 hit our three authorities but broke sjmurdoch's own tor network.
9984 - If we as a directory mirror don't know of any v1 directory
9985 authorities, then don't try to cache any v1 directories.
9986 - Stop warning about unknown servers in our family when they are
9987 given as hex digests.
9988 - Stop complaining as quickly to the server operator that he
9989 hasn't registered his nickname/key binding.
9990 - Various cleanups so we can add new V2 Auth Dirservers.
9991 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
9992 reflect the updated flags in our v2 dir protocol.
9993 - Resume allowing non-printable characters for exit streams (both
9994 for connecting and for resolving). Now we tolerate applications
9995 that don't follow the RFCs. But continue to block malformed names
9998 o Bugfixes on 0.1.0.x:
9999 - Fix assert bug in close_logs(): when we close and delete logs,
10000 remove them all from the global "logfiles" list.
10001 - Fix minor integer overflow in calculating when we expect to use up
10002 our bandwidth allocation before hibernating.
10003 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10004 there are multiple SSLs installed with different versions.
10005 - When we try to be a server and Address is not explicitly set and
10006 our hostname resolves to a private IP address, try to use an
10007 interface address if it has a public address. Now Windows machines
10008 that think of themselves as localhost can work by default.
10011 - Let the controller ask for GETINFO dir/server/foo so it can ask
10012 directly rather than connecting to the dir port.
10013 - Let the controller tell us about certain router descriptors
10014 that it doesn't want Tor to use in circuits. Implement
10015 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10016 - New config option SafeSocks to reject all application connections
10017 using unsafe socks protocols. Defaults to off.
10020 Changes in version 0.1.1.15-rc - 2006-03-11
10021 o Bugfixes and cleanups:
10022 - When we're printing strings from the network, don't try to print
10023 non-printable characters. This protects us against shell escape
10024 sequence exploits, and also against attacks to fool humans into
10025 misreading their logs.
10026 - Fix a bug where Tor would fail to establish any connections if you
10027 left it off for 24 hours and then started it: we were happy with
10028 the obsolete network statuses, but they all referred to router
10029 descriptors that were too old to fetch, so we ended up with no
10030 valid router descriptors.
10031 - Fix a seg fault in the controller's "getinfo orconn-status"
10032 command while listing status on incoming handshaking connections.
10033 Introduce a status name "NEW" for these connections.
10034 - If we get a linelist or linelist_s config option from the torrc
10035 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10036 silently resetting it to its default.
10037 - Don't abandon entry guards until they've been down or gone for
10039 - Cleaner and quieter log messages.
10042 - New controller signal NEWNYM that makes new application requests
10043 use clean circuits.
10044 - Add a new circuit purpose 'controller' to let the controller ask
10045 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10046 controller command to let you specify the purpose if you're
10047 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10048 command to let you change a circuit's purpose after it's been
10050 - Accept "private:*" in routerdesc exit policies; not generated yet
10051 because older Tors do not understand it.
10052 - Add BSD-style contributed startup script "rc.subr" from Peter
10056 Changes in version 0.1.1.14-alpha - 2006-02-20
10057 o Bugfixes on 0.1.1.x:
10058 - Don't die if we ask for a stdout or stderr log (even implicitly)
10059 and we're set to RunAsDaemon -- just warn.
10060 - We still had a few bugs in the OR connection rotation code that
10061 caused directory servers to slowly aggregate connections to other
10062 fast Tor servers. This time for sure!
10063 - Make log entries on Win32 include the name of the function again.
10064 - We were treating a pair of exit policies if they were equal even
10065 if one said accept and the other said reject -- causing us to
10066 not always publish a new descriptor since we thought nothing
10068 - Retry pending server downloads as well as pending networkstatus
10069 downloads when we unexpectedly get a socks request.
10070 - We were ignoring the IS_FAST flag in the directory status,
10071 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10073 - If the controller's SAVECONF command fails (e.g. due to file
10074 permissions), let the controller know that it failed.
10077 - If we're trying to be a Tor server and running Windows 95/98/ME
10078 as a server, explain that we'll likely crash.
10079 - When we're a server, a client asks for an old-style directory,
10080 and our write bucket is empty, don't give it to him. This way
10081 small servers can continue to serve the directory *sometimes*,
10082 without getting overloaded.
10083 - Compress exit policies even more -- look for duplicate lines
10085 - Clients now honor the "guard" flag in the router status when
10086 picking entry guards, rather than looking at is_fast or is_stable.
10087 - Retain unrecognized lines in $DATADIR/state file, so that we can
10088 be forward-compatible.
10089 - Generate 18.0.0.0/8 address policy format in descs when we can;
10090 warn when the mask is not reducible to a bit-prefix.
10091 - Let the user set ControlListenAddress in the torrc. This can be
10092 dangerous, but there are some cases (like a secured LAN) where it
10094 - Split ReachableAddresses into ReachableDirAddresses and
10095 ReachableORAddresses, so we can restrict Dir conns to port 80
10096 and OR conns to port 443.
10097 - Now we can target arch and OS in rpm builds (contributed by
10098 Phobos). Also make the resulting dist-rpm filename match the
10100 - New config options to help controllers: FetchServerDescriptors
10101 and FetchHidServDescriptors for whether to fetch server
10102 info and hidserv info or let the controller do it, and
10103 PublishServerDescriptor and PublishHidServDescriptors.
10104 - Also let the controller set the __AllDirActionsPrivate config
10105 option if you want all directory fetches/publishes to happen via
10106 Tor (it assumes your controller bootstraps your circuits).
10109 Changes in version 0.1.0.17 - 2006-02-17
10110 o Crash bugfixes on 0.1.0.x:
10111 - When servers with a non-zero DirPort came out of hibernation,
10112 sometimes they would trigger an assert.
10114 o Other important bugfixes:
10115 - On platforms that don't have getrlimit (like Windows), we were
10116 artificially constraining ourselves to a max of 1024
10117 connections. Now just assume that we can handle as many as 15000
10118 connections. Hopefully this won't cause other problems.
10120 o Backported features:
10121 - When we're a server, a client asks for an old-style directory,
10122 and our write bucket is empty, don't give it to him. This way
10123 small servers can continue to serve the directory *sometimes*,
10124 without getting overloaded.
10125 - Whenever you get a 503 in response to a directory fetch, try
10126 once more. This will become important once servers start sending
10127 503's whenever they feel busy.
10128 - Fetch a new directory every 120 minutes, not every 40 minutes.
10129 Now that we have hundreds of thousands of users running the old
10130 directory algorithm, it's starting to hurt a lot.
10131 - Bump up the period for forcing a hidden service descriptor upload
10132 from 20 minutes to 1 hour.
10135 Changes in version 0.1.1.13-alpha - 2006-02-09
10136 o Crashes in 0.1.1.x:
10137 - When you tried to setconf ORPort via the controller, Tor would
10138 crash. So people using TorCP to become a server were sad.
10139 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10140 servers. The problem appears to be something do with OpenSSL's
10141 random number generation, or how we call it, or something. Let me
10142 know if the crashes continue.
10143 - Turn crypto hardware acceleration off by default, until we find
10144 somebody smart who can test it for us. (It appears to produce
10145 seg faults in at least some cases.)
10146 - Fix a rare assert error when we've tried all intro points for
10147 a hidden service and we try fetching the service descriptor again:
10148 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10151 - Fix a major load balance bug: we were round-robining in 16 KB
10152 chunks, and servers with bandwidthrate of 20 KB, while downloading
10153 a 600 KB directory, would starve their other connections. Now we
10154 try to be a bit more fair.
10155 - Dir authorities and mirrors were never expiring the newest
10156 descriptor for each server, causing memory and directory bloat.
10157 - Fix memory-bloating and connection-bloating bug on servers: We
10158 were never closing any connection that had ever had a circuit on
10159 it, because we were checking conn->n_circuits == 0, yet we had a
10160 bug that let it go negative.
10161 - Make Tor work using squid as your http proxy again -- squid
10162 returns an error if you ask for a URL that's too long, and it uses
10163 a really generic error message. Plus, many people are behind a
10164 transparent squid so they don't even realize it.
10165 - On platforms that don't have getrlimit (like Windows), we were
10166 artificially constraining ourselves to a max of 1024
10167 connections. Now just assume that we can handle as many as 15000
10168 connections. Hopefully this won't cause other problems.
10169 - Add a new config option ExitPolicyRejectPrivate which defaults to
10170 1. This means all exit policies will begin with rejecting private
10171 addresses, unless the server operator explicitly turns it off.
10174 - Clients no longer download descriptors for non-running
10176 - Before we add new directory authorities, we should make it
10177 clear that only v1 authorities should receive/publish hidden
10178 service descriptors.
10181 - As soon as we've fetched some more directory info, immediately
10182 try to download more server descriptors. This way we don't have
10183 a 10 second pause during initial bootstrapping.
10184 - Remove even more loud log messages that the server operator can't
10186 - When we're running an obsolete or un-recommended version, make
10187 the log message more clear about what the problem is and what
10188 versions *are* still recommended.
10189 - Provide a more useful warn message when our onion queue gets full:
10190 the CPU is too slow or the exit policy is too liberal.
10191 - Don't warn when we receive a 503 from a dirserver/cache -- this
10192 will pave the way for them being able to refuse if they're busy.
10193 - When we fail to bind a listener, try to provide a more useful
10194 log message: e.g., "Is Tor already running?"
10195 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10196 Goldberg can prove things about our handshake protocol more
10198 - MaxConn has been obsolete for a while now. Document the ConnLimit
10199 config option, which is a *minimum* number of file descriptors
10200 that must be available else Tor refuses to start.
10201 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10202 if you log to syslog and want something other than LOG_DAEMON.
10203 - Make dirservers generate a separate "guard" flag to mean,
10204 "would make a good entry guard". Make clients parse it and vote
10205 on it. Not used by clients yet.
10206 - Implement --with-libevent-dir option to ./configure. Also, improve
10207 search techniques to find libevent, and use those for openssl too.
10208 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10209 - Only start testing reachability once we've established a
10210 circuit. This will make startup on dirservers less noisy.
10211 - Don't try to upload hidden service descriptors until we have
10212 established a circuit.
10213 - Fix the controller's "attachstream 0" command to treat conn like
10214 it just connected, doing address remapping, handling .exit and
10215 .onion idioms, and so on. Now we're more uniform in making sure
10216 that the controller hears about new and closing connections.
10219 Changes in version 0.1.1.12-alpha - 2006-01-11
10220 o Bugfixes on 0.1.1.x:
10221 - The fix to close duplicate server connections was closing all
10222 Tor client connections if they didn't establish a circuit
10223 quickly enough. Oops.
10224 - Fix minor memory issue (double-free) that happened on exit.
10226 o Bugfixes on 0.1.0.x:
10227 - Tor didn't warn when it failed to open a log file.
10230 Changes in version 0.1.1.11-alpha - 2006-01-10
10231 o Crashes in 0.1.1.x:
10232 - Include all the assert/crash fixes from 0.1.0.16.
10233 - If you start Tor and then quit very quickly, there were some
10234 races that tried to free things that weren't allocated yet.
10235 - Fix a rare memory stomp if you're running hidden services.
10236 - Fix segfault when specifying DirServer in config without nickname.
10237 - Fix a seg fault when you finish connecting to a server but at
10238 that moment you dump his server descriptor.
10239 - Extendcircuit and Attachstream controller commands would
10240 assert/crash if you don't give them enough arguments.
10241 - Fix an assert error when we're out of space in the connection_list
10242 and we try to post a hidden service descriptor (reported by weasel).
10243 - If you specify a relative torrc path and you set RunAsDaemon in
10244 your torrc, then it chdir()'s to the new directory. If you HUP,
10245 it tries to load the new torrc location, fails, and exits.
10246 The fix: no longer allow a relative path to torrc using -f.
10249 - Implement "entry guards": automatically choose a handful of entry
10250 nodes and stick with them for all circuits. Only pick new guards
10251 when the ones you have are unsuitable, and if the old guards
10252 become suitable again, switch back. This will increase security
10253 dramatically against certain end-point attacks. The EntryNodes
10254 config option now provides some hints about which entry guards you
10255 want to use most; and StrictEntryNodes means to only use those.
10256 - New directory logic: download by descriptor digest, not by
10257 fingerprint. Caches try to download all listed digests from
10258 authorities; clients try to download "best" digests from caches.
10259 This avoids partitioning and isolating attacks better.
10260 - Make the "stable" router flag in network-status be the median of
10261 the uptimes of running valid servers, and make clients pay
10262 attention to the network-status flags. Thus the cutoff adapts
10263 to the stability of the network as a whole, making IRC, IM, etc
10264 connections more reliable.
10267 - Tor servers with dynamic IP addresses were needing to wait 18
10268 hours before they could start doing reachability testing using
10269 the new IP address and ports. This is because they were using
10270 the internal descriptor to learn what to test, yet they were only
10271 rebuilding the descriptor once they decided they were reachable.
10272 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
10273 to download certain server descriptors, throw them away, and then
10274 fetch them again after 30 minutes. Now mirrors throw away these
10275 server descriptors so clients can't get them.
10276 - We were leaving duplicate connections to other ORs open for a week,
10277 rather than closing them once we detect a duplicate. This only
10278 really affected authdirservers, but it affected them a lot.
10279 - Spread the authdirservers' reachability testing over the entire
10280 testing interval, so we don't try to do 500 TLS's at once every
10284 - If the network is down, and we try to connect to a conn because
10285 we have a circuit in mind, and we timeout (30 seconds) because the
10286 network never answers, we were expiring the circuit, but we weren't
10287 obsoleting the connection or telling the entry_guards functions.
10288 - Some Tor servers process billions of cells per day. These statistics
10289 need to be uint64_t's.
10290 - Check for integer overflows in more places, when adding elements
10291 to smartlists. This could possibly prevent a buffer overflow
10292 on malicious huge inputs. I don't see any, but I haven't looked
10294 - ReachableAddresses kept growing new "reject *:*" lines on every
10296 - When you "setconf log" via the controller, it should remove all
10297 logs. We were automatically adding back in a "log notice stdout".
10298 - Newly bootstrapped Tor networks couldn't establish hidden service
10299 circuits until they had nodes with high uptime. Be more tolerant.
10300 - We were marking servers down when they could not answer every piece
10301 of the directory request we sent them. This was far too harsh.
10302 - Fix the torify (tsocks) config file to not use Tor for localhost
10304 - Directory authorities now go to the proper authority when asking for
10305 a networkstatus, even when they want a compressed one.
10306 - Fix a harmless bug that was causing Tor servers to log
10307 "Got an end because of misc error, but we're not an AP. Closing."
10308 - Authorities were treating their own descriptor changes as cosmetic,
10309 meaning the descriptor available in the network-status and the
10310 descriptor that clients downloaded were different.
10311 - The OS X installer was adding a symlink for tor_resolve but
10312 the binary was called tor-resolve (reported by Thomas Hardly).
10313 - Workaround a problem with some http proxies where they refuse GET
10314 requests that specify "Content-Length: 0" (reported by Adrian).
10315 - Fix wrong log message when you add a "HiddenServiceNodes" config
10316 line without any HiddenServiceDir line (reported by Chris Thomas).
10319 - Write the TorVersion into the state file so we have a prayer of
10320 keeping forward and backward compatibility.
10321 - Revive the FascistFirewall config option rather than eliminating it:
10322 now it's a synonym for ReachableAddresses *:80,*:443.
10323 - Clients choose directory servers from the network status lists,
10324 not from their internal list of router descriptors. Now they can
10325 go to caches directly rather than needing to go to authorities
10327 - Directory authorities ignore router descriptors that have only
10328 cosmetic differences: do this for 0.1.0.x servers now too.
10329 - Add a new flag to network-status indicating whether the server
10330 can answer v2 directory requests too.
10331 - Authdirs now stop whining so loudly about bad descriptors that
10332 they fetch from other dirservers. So when there's a log complaint,
10333 it's for sure from a freshly uploaded descriptor.
10334 - Reduce memory requirements in our structs by changing the order
10336 - There used to be two ways to specify your listening ports in a
10337 server descriptor: on the "router" line and with a separate "ports"
10338 line. Remove support for the "ports" line.
10339 - New config option "AuthDirRejectUnlisted" for auth dirservers as
10340 a panic button: if we get flooded with unusable servers we can
10341 revert to only listing servers in the approved-routers file.
10342 - Auth dir servers can now mark a fingerprint as "!reject" or
10343 "!invalid" in the approved-routers file (as its nickname), to
10344 refuse descriptors outright or include them but marked as invalid.
10345 - Servers store bandwidth history across restarts/crashes.
10346 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10347 get a better idea of why their circuits failed. Not used yet.
10348 - Directory mirrors now cache up to 16 unrecognized network-status
10349 docs. Now we can add new authdirservers and they'll be cached too.
10350 - When picking a random directory, prefer non-authorities if any
10352 - New controller option "getinfo desc/all-recent" to fetch the
10353 latest server descriptor for every router that Tor knows about.
10356 Changes in version 0.1.0.16 - 2006-01-02
10357 o Crash bugfixes on 0.1.0.x:
10358 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10359 corrupting the heap, losing FDs, or crashing when we need to resize
10360 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10361 - It turns out sparc64 platforms crash on unaligned memory access
10362 too -- so detect and avoid this.
10363 - Handle truncated compressed data correctly (by detecting it and
10365 - Fix possible-but-unlikely free(NULL) in control.c.
10366 - When we were closing connections, there was a rare case that
10367 stomped on memory, triggering seg faults and asserts.
10368 - Avoid potential infinite recursion when building a descriptor. (We
10369 don't know that it ever happened, but better to fix it anyway.)
10370 - We were neglecting to unlink marked circuits from soon-to-close OR
10371 connections, which caused some rare scribbling on freed memory.
10372 - Fix a memory stomping race bug when closing the joining point of two
10373 rendezvous circuits.
10374 - Fix an assert in time parsing found by Steven Murdoch.
10376 o Other bugfixes on 0.1.0.x:
10377 - When we're doing reachability testing, provide more useful log
10378 messages so the operator knows what to expect.
10379 - Do not check whether DirPort is reachable when we are suppressing
10380 advertising it because of hibernation.
10381 - When building with -static or on Solaris, we sometimes needed -ldl.
10382 - When we're deciding whether a stream has enough circuits around
10383 that can handle it, count the freshly dirty ones and not the ones
10384 that are so dirty they won't be able to handle it.
10385 - When we're expiring old circuits, we had a logic error that caused
10386 us to close new rendezvous circuits rather than old ones.
10387 - Give a more helpful log message when you try to change ORPort via
10388 the controller: you should upgrade Tor if you want that to work.
10389 - We were failing to parse Tor versions that start with "Tor ".
10390 - Tolerate faulty streams better: when a stream fails for reason
10391 exitpolicy, stop assuming that the router is lying about his exit
10392 policy. When a stream fails for reason misc, allow it to retry just
10393 as if it was resolvefailed. When a stream has failed three times,
10394 reset its failure count so we can try again and get all three tries.
10397 Changes in version 0.1.1.10-alpha - 2005-12-11
10398 o Correctness bugfixes on 0.1.0.x:
10399 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10400 corrupting the heap, losing FDs, or crashing when we need to resize
10401 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10402 - Stop doing the complex voodoo overkill checking for insecure
10403 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
10404 - When we were closing connections, there was a rare case that
10405 stomped on memory, triggering seg faults and asserts.
10406 - We were neglecting to unlink marked circuits from soon-to-close OR
10407 connections, which caused some rare scribbling on freed memory.
10408 - When we're deciding whether a stream has enough circuits around
10409 that can handle it, count the freshly dirty ones and not the ones
10410 that are so dirty they won't be able to handle it.
10411 - Recover better from TCP connections to Tor servers that are
10412 broken but don't tell you (it happens!); and rotate TLS
10413 connections once a week.
10414 - When we're expiring old circuits, we had a logic error that caused
10415 us to close new rendezvous circuits rather than old ones.
10416 - Fix a scary-looking but apparently harmless bug where circuits
10417 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
10418 servers, and never switch to state CIRCUIT_STATE_OPEN.
10419 - When building with -static or on Solaris, we sometimes needed to
10421 - Give a useful message when people run Tor as the wrong user,
10422 rather than telling them to start chowning random directories.
10423 - We were failing to inform the controller about new .onion streams.
10425 o Security bugfixes on 0.1.0.x:
10426 - Refuse server descriptors if the fingerprint line doesn't match
10427 the included identity key. Tor doesn't care, but other apps (and
10428 humans) might actually be trusting the fingerprint line.
10429 - We used to kill the circuit when we receive a relay command we
10430 don't recognize. Now we just drop it.
10431 - Start obeying our firewall options more rigorously:
10432 . If we can't get to a dirserver directly, try going via Tor.
10433 . Don't ever try to connect (as a client) to a place our
10434 firewall options forbid.
10435 . If we specify a proxy and also firewall options, obey the
10436 firewall options even when we're using the proxy: some proxies
10437 can only proxy to certain destinations.
10438 - Fix a bug found by Lasse Overlier: when we were making internal
10439 circuits (intended to be cannibalized later for rendezvous and
10440 introduction circuits), we were picking them so that they had
10441 useful exit nodes. There was no need for this, and it actually
10442 aids some statistical attacks.
10443 - Start treating internal circuits and exit circuits separately.
10444 It's important to keep them separate because internal circuits
10445 have their last hops picked like middle hops, rather than like
10446 exit hops. So exiting on them will break the user's expectations.
10448 o Bugfixes on 0.1.1.x:
10449 - Take out the mis-feature where we tried to detect IP address
10450 flapping for people with DynDNS, and chose not to upload a new
10451 server descriptor sometimes.
10452 - Try to be compatible with OpenSSL 0.9.6 again.
10453 - Log fix: when the controller is logging about .onion addresses,
10454 sometimes it didn't include the ".onion" part of the address.
10455 - Don't try to modify options->DirServers internally -- if the
10456 user didn't specify any, just add the default ones directly to
10457 the trusted dirserver list. This fixes a bug where people running
10458 controllers would use SETCONF on some totally unrelated config
10459 option, and Tor would start yelling at them about changing their
10461 - Let the controller's redirectstream command specify a port, in
10462 case the controller wants to change that too.
10463 - When we requested a pile of server descriptors, we sometimes
10464 accidentally launched a duplicate request for the first one.
10465 - Bugfix for trackhostexits: write down the fingerprint of the
10466 chosen exit, not its nickname, because the chosen exit might not
10468 - When parsing foo.exit, if foo is unknown, and we are leaving
10469 circuits unattached, set the chosen_exit field and leave the
10470 address empty. This matters because controllers got confused
10472 - Directory authorities no longer try to download server
10473 descriptors that they know they will reject.
10475 o Features and updates:
10476 - Replace balanced trees with hash tables: this should make stuff
10477 significantly faster.
10478 - Resume using the AES counter-mode implementation that we ship,
10479 rather than OpenSSL's. Ours is significantly faster.
10480 - Many other CPU and memory improvements.
10481 - Add a new config option FastFirstHopPK (on by default) so clients
10482 do a trivial crypto handshake for their first hop, since TLS has
10483 already taken care of confidentiality and authentication.
10484 - Add a new config option TestSocks so people can see if their
10485 applications are using socks4, socks4a, socks5-with-ip, or
10486 socks5-with-hostname. This way they don't have to keep mucking
10487 with tcpdump and wondering if something got cached somewhere.
10488 - Warn when listening on a public address for socks. I suspect a
10489 lot of people are setting themselves up as open socks proxies,
10490 and they have no idea that jerks on the Internet are using them,
10491 since they simply proxy the traffic into the Tor network.
10492 - Add "private:*" as an alias in configuration for policies. Now
10493 you can simplify your exit policy rather than needing to list
10494 every single internal or nonroutable network space.
10495 - Add a new controller event type that allows controllers to get
10496 all server descriptors that were uploaded to a router in its role
10497 as authoritative dirserver.
10498 - Start shipping socks-extensions.txt, tor-doc-unix.html,
10499 tor-doc-server.html, and stylesheet.css in the tarball.
10500 - Stop shipping tor-doc.html in the tarball.
10503 Changes in version 0.1.1.9-alpha - 2005-11-15
10504 o Usability improvements:
10505 - Start calling it FooListenAddress rather than FooBindAddress,
10506 since few of our users know what it means to bind an address
10508 - Reduce clutter in server logs. We're going to try to make
10509 them actually usable now. New config option ProtocolWarnings that
10510 lets you hear about how _other Tors_ are breaking the protocol. Off
10512 - Divide log messages into logging domains. Once we put some sort
10513 of interface on this, it will let people looking at more verbose
10514 log levels specify the topics they want to hear more about.
10515 - Make directory servers return better http 404 error messages
10516 instead of a generic "Servers unavailable".
10517 - Check for even more Windows version flags when writing the platform
10518 string in server descriptors, and note any we don't recognize.
10519 - Clean up more of the OpenSSL memory when exiting, so we can detect
10520 memory leaks better.
10521 - Make directory authorities be non-versioning, non-naming by
10522 default. Now we can add new directory servers without requiring
10523 their operators to pay close attention.
10524 - When logging via syslog, include the pid whenever we provide
10525 a log entry. Suggested by Todd Fries.
10527 o Performance improvements:
10528 - Directory servers now silently throw away new descriptors that
10529 haven't changed much if the timestamps are similar. We do this to
10530 tolerate older Tor servers that upload a new descriptor every 15
10531 minutes. (It seemed like a good idea at the time.)
10532 - Inline bottleneck smartlist functions; use fast versions by default.
10533 - Add a "Map from digest to void*" abstraction digestmap_t so we
10534 can do less hex encoding/decoding. Use it in router_get_by_digest()
10535 to resolve a performance bottleneck.
10536 - Allow tor_gzip_uncompress to extract as much as possible from
10537 truncated compressed data. Try to extract as many
10538 descriptors as possible from truncated http responses (when
10539 DIR_PURPOSE_FETCH_ROUTERDESC).
10540 - Make circ->onionskin a pointer, not a static array. moria2 was using
10541 125000 circuit_t's after it had been up for a few weeks, which
10542 translates to 20+ megs of wasted space.
10543 - The private half of our EDH handshake keys are now chosen out
10544 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
10546 o Security improvements:
10547 - Start making directory caches retain old routerinfos, so soon
10548 clients can start asking by digest of descriptor rather than by
10549 fingerprint of server.
10550 - Add half our entropy from RAND_poll in OpenSSL. This knows how
10551 to use egd (if present), openbsd weirdness (if present), vms/os2
10552 weirdness (if we ever port there), and more in the future.
10554 o Bugfixes on 0.1.0.x:
10555 - Do round-robin writes of at most 16 kB per write. This might be
10556 more fair on loaded Tor servers, and it might resolve our Windows
10557 crash bug. It might also slow things down.
10558 - Our TLS handshakes were generating a single public/private
10559 keypair for the TLS context, rather than making a new one for
10560 each new connections. Oops. (But we were still rotating them
10561 periodically, so it's not so bad.)
10562 - When we were cannibalizing a circuit with a particular exit
10563 node in mind, we weren't checking to see if that exit node was
10564 already present earlier in the circuit. Oops.
10565 - When a Tor server's IP changes (e.g. from a dyndns address),
10566 upload a new descriptor so clients will learn too.
10567 - Really busy servers were keeping enough circuits open on stable
10568 connections that they were wrapping around the circuit_id
10569 space. (It's only two bytes.) This exposed a bug where we would
10570 feel free to reuse a circuit_id even if it still exists but has
10571 been marked for close. Try to fix this bug. Some bug remains.
10572 - If we would close a stream early (e.g. it asks for a .exit that
10573 we know would refuse it) but the LeaveStreamsUnattached config
10574 option is set by the controller, then don't close it.
10576 o Bugfixes on 0.1.1.8-alpha:
10577 - Fix a big pile of memory leaks, some of them serious.
10578 - Do not try to download a routerdesc if we would immediately reject
10580 - Resume inserting a newline between all router descriptors when
10581 generating (old style) signed directories, since our spec says
10583 - When providing content-type application/octet-stream for
10584 server descriptors using .z, we were leaving out the
10585 content-encoding header. Oops. (Everything tolerated this just
10586 fine, but that doesn't mean we need to be part of the problem.)
10587 - Fix a potential seg fault in getconf and getinfo using version 1
10588 of the controller protocol.
10589 - Avoid crash: do not check whether DirPort is reachable when we
10590 are suppressing it because of hibernation.
10591 - Make --hash-password not crash on exit.
10594 Changes in version 0.1.1.8-alpha - 2005-10-07
10595 o New features (major):
10596 - Clients don't download or use the directory anymore. Now they
10597 download and use network-statuses from the trusted dirservers,
10598 and fetch individual server descriptors as needed from mirrors.
10599 See dir-spec.txt for all the gory details.
10600 - Be more conservative about whether to advertise our DirPort.
10601 The main change is to not advertise if we're running at capacity
10602 and either a) we could hibernate or b) our capacity is low and
10603 we're using a default DirPort.
10604 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
10606 o New features (minor):
10607 - Try to be smart about when to retry network-status and
10608 server-descriptor fetches. Still needs some tuning.
10609 - Stop parsing, storing, or using running-routers output (but
10610 mirrors still cache and serve it).
10611 - Consider a threshold of versioning dirservers (dirservers who have
10612 an opinion about which Tor versions are still recommended) before
10613 deciding whether to warn the user that he's obsolete.
10614 - Dirservers can now reject/invalidate by key and IP, with the
10615 config options "AuthDirInvalid" and "AuthDirReject". This is
10616 useful since currently we automatically list servers as running
10617 and usable even if we know they're jerks.
10618 - Provide dire warnings to any users who set DirServer; move it out
10619 of torrc.sample and into torrc.complete.
10620 - Add MyFamily to torrc.sample in the server section.
10621 - Add nicknames to the DirServer line, so we can refer to them
10622 without requiring all our users to memorize their IP addresses.
10623 - When we get an EOF or a timeout on a directory connection, note
10624 how many bytes of serverdesc we are dropping. This will help
10625 us determine whether it is smart to parse incomplete serverdesc
10627 - Add a new function to "change pseudonyms" -- that is, to stop
10628 using any currently-dirty circuits for new streams, so we don't
10629 link new actions to old actions. Currently it's only called on
10630 HUP (or SIGNAL RELOAD).
10631 - On sighup, if UseHelperNodes changed to 1, use new circuits.
10632 - Start using RAND_bytes rather than RAND_pseudo_bytes from
10633 OpenSSL. Also, reseed our entropy every hour, not just at
10634 startup. And entropy in 512-bit chunks, not 160-bit chunks.
10636 o Fixes on 0.1.1.7-alpha:
10637 - Nobody ever implemented EVENT_ADDRMAP for control protocol
10638 version 0, so don't let version 0 controllers ask for it.
10639 - If you requested something with too many newlines via the
10640 v1 controller protocol, you could crash tor.
10641 - Fix a number of memory leaks, including some pretty serious ones.
10642 - Re-enable DirPort testing again, so Tor servers will be willing
10643 to advertise their DirPort if it's reachable.
10644 - On TLS handshake, only check the other router's nickname against
10645 its expected nickname if is_named is set.
10647 o Fixes forward-ported from 0.1.0.15:
10648 - Don't crash when we don't have any spare file descriptors and we
10649 try to spawn a dns or cpu worker.
10650 - Make the numbers in read-history and write-history into uint64s,
10651 so they don't overflow and publish negatives in the descriptor.
10653 o Fixes on 0.1.0.x:
10654 - For the OS X package's modified privoxy config file, comment
10655 out the "logfile" line so we don't log everything passed
10657 - We were whining about using socks4 or socks5-with-local-lookup
10658 even when it's an IP in the "virtual" range we designed exactly
10660 - We were leaking some memory every time the client changes IPs.
10661 - Never call free() on tor_malloc()d memory. This will help us
10662 use dmalloc to detect memory leaks.
10663 - Check for named servers when looking them up by nickname;
10664 warn when we'recalling a non-named server by its nickname;
10665 don't warn twice about the same name.
10666 - Try to list MyFamily elements by key, not by nickname, and warn
10667 if we've not heard of the server.
10668 - Make windows platform detection (uname equivalent) smarter.
10669 - It turns out sparc64 doesn't like unaligned access either.
10672 Changes in version 0.1.0.15 - 2005-09-23
10673 o Bugfixes on 0.1.0.x:
10674 - Reject ports 465 and 587 (spam targets) in default exit policy.
10675 - Don't crash when we don't have any spare file descriptors and we
10676 try to spawn a dns or cpu worker.
10677 - Get rid of IgnoreVersion undocumented config option, and make us
10678 only warn, never exit, when we're running an obsolete version.
10679 - Don't try to print a null string when your server finds itself to
10680 be unreachable and the Address config option is empty.
10681 - Make the numbers in read-history and write-history into uint64s,
10682 so they don't overflow and publish negatives in the descriptor.
10683 - Fix a minor memory leak in smartlist_string_remove().
10684 - We were only allowing ourselves to upload a server descriptor at
10685 most every 20 minutes, even if it changed earlier than that.
10686 - Clean up log entries that pointed to old URLs.
10689 Changes in version 0.1.1.7-alpha - 2005-09-14
10690 o Fixes on 0.1.1.6-alpha:
10691 - Exit servers were crashing when people asked them to make a
10692 connection to an address not in their exit policy.
10693 - Looking up a non-existent stream for a v1 control connection would
10695 - Fix a seg fault if we ask a dirserver for a descriptor by
10696 fingerprint but he doesn't know about him.
10697 - SETCONF was appending items to linelists, not clearing them.
10698 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
10699 out and refuse the setconf if it would fail.
10700 - Downgrade the dirserver log messages when whining about
10704 - Add Peter Palfrader's check-tor script to tor/contrib/
10705 It lets you easily check whether a given server (referenced by
10706 nickname) is reachable by you.
10707 - Numerous changes to move towards client-side v2 directories. Not
10710 o Fixes on 0.1.0.x:
10711 - If the user gave tor an odd number of command-line arguments,
10712 we were silently ignoring the last one. Now we complain and fail.
10713 [This wins the oldest-bug prize -- this bug has been present since
10714 November 2002, as released in Tor 0.0.0.]
10715 - Do not use unaligned memory access on alpha, mips, or mipsel.
10716 It *works*, but is very slow, so we treat them as if it doesn't.
10717 - Retry directory requests if we fail to get an answer we like
10718 from a given dirserver (we were retrying before, but only if
10719 we fail to connect).
10720 - When writing the RecommendedVersions line, sort them first.
10721 - When the client asked for a rendezvous port that the hidden
10722 service didn't want to provide, we were sending an IP address
10723 back along with the end cell. Fortunately, it was zero. But stop
10725 - Correct "your server is reachable" log entries to indicate that
10726 it was self-testing that told us so.
10729 Changes in version 0.1.1.6-alpha - 2005-09-09
10730 o Fixes on 0.1.1.5-alpha:
10731 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
10732 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
10733 - Fix bug with tor_memmem finding a match at the end of the string.
10734 - Make unit tests run without segfaulting.
10735 - Resolve some solaris x86 compile warnings.
10736 - Handle duplicate lines in approved-routers files without warning.
10737 - Fix bug where as soon as a server refused any requests due to his
10738 exit policy (e.g. when we ask for localhost and he tells us that's
10739 127.0.0.1 and he won't do it), we decided he wasn't obeying his
10740 exit policy using him for any exits.
10741 - Only do openssl hardware accelerator stuff if openssl version is
10744 o New controller features/fixes:
10745 - Add a "RESETCONF" command so you can set config options like
10746 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
10747 a config option in the torrc with no value, then it clears it
10748 entirely (rather than setting it to its default).
10749 - Add a "GETINFO config-file" to tell us where torrc is.
10750 - Avoid sending blank lines when GETINFO replies should be empty.
10751 - Add a QUIT command for the controller (for using it manually).
10752 - Fix a bug in SAVECONF that was adding default dirservers and
10753 other redundant entries to the torrc file.
10755 o Start on the new directory design:
10756 - Generate, publish, cache, serve new network-status format.
10757 - Publish individual descriptors (by fingerprint, by "all", and by
10759 - Publish client and server recommended versions separately.
10760 - Allow tor_gzip_uncompress() to handle multiple concatenated
10761 compressed strings. Serve compressed groups of router
10762 descriptors. The compression logic here could be more
10764 - Distinguish v1 authorities (all currently trusted directories)
10765 from v2 authorities (all trusted directories).
10766 - Change DirServers config line to note which dirs are v1 authorities.
10767 - Add configuration option "V1AuthoritativeDirectory 1" which
10768 moria1, moria2, and tor26 should set.
10769 - Remove option when getting directory cache to see whether they
10770 support running-routers; they all do now. Replace it with one
10771 to see whether caches support v2 stuff.
10774 - Dirservers now do their own external reachability testing of each
10775 Tor server, and only list them as running if they've been found to
10776 be reachable. We also send back warnings to the server's logs if
10777 it uploads a descriptor that we already believe is unreachable.
10778 - Implement exit enclaves: if we know an IP address for the
10779 destination, and there's a running Tor server at that address
10780 which allows exit to the destination, then extend the circuit to
10781 that exit first. This provides end-to-end encryption and end-to-end
10782 authentication. Also, if the user wants a .exit address or enclave,
10783 use 4 hops rather than 3, and cannibalize a general circ for it
10785 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
10786 controller. Also, rotate dns and cpu workers if the controller
10787 changes options that will affect them; and initialize the dns
10788 worker cache tree whether or not we start out as a server.
10789 - Only upload a new server descriptor when options change, 18
10790 hours have passed, uptime is reset, or bandwidth changes a lot.
10791 - Check [X-]Forwarded-For headers in HTTP requests when generating
10792 log messages. This lets people run dirservers (and caches) behind
10793 Apache but still know which IP addresses are causing warnings.
10795 o Config option changes:
10796 - Replace (Fascist)Firewall* config options with a new
10797 ReachableAddresses option that understands address policies.
10798 For example, "ReachableAddresses *:80,*:443"
10799 - Get rid of IgnoreVersion undocumented config option, and make us
10800 only warn, never exit, when we're running an obsolete version.
10801 - Make MonthlyAccountingStart config option truly obsolete now.
10803 o Fixes on 0.1.0.x:
10804 - Reject ports 465 and 587 in the default exit policy, since
10805 people have started using them for spam too.
10806 - It turns out we couldn't bootstrap a network since we added
10807 reachability detection in 0.1.0.1-rc. Good thing the Tor network
10808 has never gone down. Add an AssumeReachable config option to let
10809 servers and dirservers bootstrap. When we're trying to build a
10810 high-uptime or high-bandwidth circuit but there aren't enough
10811 suitable servers, try being less picky rather than simply failing.
10812 - Our logic to decide if the OR we connected to was the right guy
10813 was brittle and maybe open to a mitm for unverified routers.
10814 - We weren't cannibalizing circuits correctly for
10815 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
10816 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
10817 build those from scratch. This should make hidden services faster.
10818 - Predict required circuits better, with an eye toward making hidden
10819 services faster on the service end.
10820 - Retry streams if the exit node sends back a 'misc' failure. This
10821 should result in fewer random failures. Also, after failing
10822 from resolve failed or misc, reset the num failures, so we give
10823 it a fair shake next time we try.
10824 - Clean up the rendezvous warn log msgs, and downgrade some to info.
10825 - Reduce severity on logs about dns worker spawning and culling.
10826 - When we're shutting down and we do something like try to post a
10827 server descriptor or rendezvous descriptor, don't complain that
10828 we seem to be unreachable. Of course we are, we're shutting down.
10829 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
10830 We don't use them yet, but maybe one day our DNS resolver will be
10831 able to discover them.
10832 - Make ContactInfo mandatory for authoritative directory servers.
10833 - Require server descriptors to list IPv4 addresses -- hostnames
10834 are no longer allowed. This also fixes some potential security
10835 problems with people providing hostnames as their address and then
10836 preferentially resolving them to partition users.
10837 - Change log line for unreachability to explicitly suggest /etc/hosts
10838 as the culprit. Also make it clearer what IP address and ports we're
10839 testing for reachability.
10840 - Put quotes around user-supplied strings when logging so users are
10841 more likely to realize if they add bad characters (like quotes)
10843 - Let auth dir servers start without specifying an Address config
10845 - Make unit tests (and other invocations that aren't the real Tor)
10846 run without launching listeners, creating subdirectories, and so on.
10849 Changes in version 0.1.1.5-alpha - 2005-08-08
10850 o Bugfixes included in 0.1.0.14.
10852 o Bugfixes on 0.1.0.x:
10853 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
10854 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
10855 it would silently using ignore the 6668.
10858 Changes in version 0.1.0.14 - 2005-08-08
10859 o Bugfixes on 0.1.0.x:
10860 - Fix the other half of the bug with crypto handshakes
10862 - Fix an assert trigger if you send a 'signal term' via the
10863 controller when it's listening for 'event info' messages.
10866 Changes in version 0.1.1.4-alpha - 2005-08-04
10867 o Bugfixes included in 0.1.0.13.
10870 - Improve tor_gettimeofday() granularity on windows.
10871 - Make clients regenerate their keys when their IP address changes.
10872 - Implement some more GETINFO goodness: expose helper nodes, config
10873 options, getinfo keys.
10876 Changes in version 0.1.0.13 - 2005-08-04
10877 o Bugfixes on 0.1.0.x:
10878 - Fix a critical bug in the security of our crypto handshakes.
10879 - Fix a size_t underflow in smartlist_join_strings2() that made
10880 it do bad things when you hand it an empty smartlist.
10881 - Fix Windows installer to ship Tor license (thanks to Aphex for
10882 pointing out this oversight) and put a link to the doc directory
10884 - Explicitly set no-unaligned-access for sparc: it turns out the
10885 new gcc's let you compile broken code, but that doesn't make it
10889 Changes in version 0.1.1.3-alpha - 2005-07-23
10890 o Bugfixes on 0.1.1.2-alpha:
10891 - Fix a bug in handling the controller's "post descriptor"
10893 - Fix several bugs in handling the controller's "extend circuit"
10895 - Fix a bug in handling the controller's "stream status" event.
10896 - Fix an assert failure if we have a controller listening for
10897 circuit events and we go offline.
10898 - Re-allow hidden service descriptors to publish 0 intro points.
10899 - Fix a crash when generating your hidden service descriptor if
10900 you don't have enough intro points already.
10902 o New features on 0.1.1.2-alpha:
10903 - New controller function "getinfo accounting", to ask how
10904 many bytes we've used in this time period.
10905 - Experimental support for helper nodes: a lot of the risk from
10906 a small static adversary comes because users pick new random
10907 nodes every time they rebuild a circuit. Now users will try to
10908 stick to the same small set of entry nodes if they can. Not
10909 enabled by default yet.
10911 o Bugfixes on 0.1.0.12:
10912 - If you're an auth dir server, always publish your dirport,
10913 even if you haven't yet found yourself to be reachable.
10914 - Fix a size_t underflow in smartlist_join_strings2() that made
10915 it do bad things when you hand it an empty smartlist.
10918 Changes in version 0.1.0.12 - 2005-07-18
10919 o New directory servers:
10920 - tor26 has changed IP address.
10922 o Bugfixes on 0.1.0.x:
10923 - Fix a possible double-free in tor_gzip_uncompress().
10924 - When --disable-threads is set, do not search for or link against
10925 pthreads libraries.
10926 - Don't trigger an assert if an authoritative directory server
10927 claims its dirport is 0.
10928 - Fix bug with removing Tor as an NT service: some people were
10929 getting "The service did not return an error." Thanks to Matt
10933 Changes in version 0.1.1.2-alpha - 2005-07-15
10934 o New directory servers:
10935 - tor26 has changed IP address.
10937 o Bugfixes on 0.1.0.x, crashes/leaks:
10938 - Port the servers-not-obeying-their-exit-policies fix from
10940 - Fix an fd leak in start_daemon().
10941 - On Windows, you can't always reopen a port right after you've
10942 closed it. So change retry_listeners() to only close and re-open
10943 ports that have changed.
10944 - Fix a possible double-free in tor_gzip_uncompress().
10946 o Bugfixes on 0.1.0.x, usability:
10947 - When tor_socketpair() fails in Windows, give a reasonable
10948 Windows-style errno back.
10949 - Let people type "tor --install" as well as "tor -install" when
10951 want to make it an NT service.
10952 - NT service patch from Matt Edman to improve error messages.
10953 - When the controller asks for a config option with an abbreviated
10954 name, give the full name in our response.
10955 - Correct the man page entry on TrackHostExitsExpire.
10956 - Looks like we were never delivering deflated (i.e. compressed)
10957 running-routers lists, even when asked. Oops.
10958 - When --disable-threads is set, do not search for or link against
10959 pthreads libraries.
10961 o Bugfixes on 0.1.1.x:
10962 - Fix a seg fault with autodetecting which controller version is
10966 - New hidden service descriptor format: put a version in it, and
10967 let people specify introduction/rendezvous points that aren't
10968 in "the directory" (which is subjective anyway).
10969 - Allow the DEBUG controller event to work again. Mark certain log
10970 entries as "don't tell this to controllers", so we avoid cycles.
10973 Changes in version 0.1.0.11 - 2005-06-30
10974 o Bugfixes on 0.1.0.x:
10975 - Fix major security bug: servers were disregarding their
10976 exit policies if clients behaved unexpectedly.
10977 - Make OS X init script check for missing argument, so we don't
10978 confuse users who invoke it incorrectly.
10979 - Fix a seg fault in "tor --hash-password foo".
10980 - The MAPADDRESS control command was broken.
10983 Changes in version 0.1.1.1-alpha - 2005-06-29
10985 - Make OS X init script check for missing argument, so we don't
10986 confuse users who invoke it incorrectly.
10987 - Fix a seg fault in "tor --hash-password foo".
10988 - Fix a possible way to DoS dirservers.
10989 - When we complain that your exit policy implicitly allows local or
10990 private address spaces, name them explicitly so operators can
10992 - Make the log message less scary when all the dirservers are
10993 temporarily unreachable.
10994 - We were printing the number of idle dns workers incorrectly when
10998 - Revised controller protocol (version 1) that uses ascii rather
10999 than binary. Add supporting libraries in python and java so you
11000 can use the controller from your applications without caring how
11001 our protocol works.
11002 - Spiffy new support for crypto hardware accelerators. Can somebody
11006 Changes in version 0.0.9.10 - 2005-06-16
11007 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11008 - Refuse relay cells that claim to have a length larger than the
11009 maximum allowed. This prevents a potential attack that could read
11010 arbitrary memory (e.g. keys) from an exit server's process
11014 Changes in version 0.1.0.10 - 2005-06-14
11015 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11016 libevent before 1.1a.
11019 Changes in version 0.1.0.9-rc - 2005-06-09
11021 - Reset buf->highwater every time buf_shrink() is called, not just on
11022 a successful shrink. This was causing significant memory bloat.
11023 - Fix buffer overflow when checking hashed passwords.
11024 - Security fix: if seeding the RNG on Win32 fails, quit.
11025 - Allow seeding the RNG on Win32 even when you're not running as
11027 - Disable threading on Solaris too. Something is wonky with it,
11028 cpuworkers, and reentrant libs.
11029 - Reenable the part of the code that tries to flush as soon as an
11030 OR outbuf has a full TLS record available. Perhaps this will make
11031 OR outbufs not grow as huge except in rare cases, thus saving lots
11032 of CPU time plus memory.
11033 - Reject malformed .onion addresses rather then passing them on as
11034 normal web requests.
11035 - Adapt patch from Adam Langley: fix possible memory leak in
11036 tor_lookup_hostname().
11037 - Initialize libevent later in the startup process, so the logs are
11038 already established by the time we start logging libevent warns.
11039 - Use correct errno on win32 if libevent fails.
11040 - Check and warn about known-bad/slow libevent versions.
11041 - Pay more attention to the ClientOnly config option.
11042 - Have torctl.in/tor.sh.in check for location of su binary (needed
11044 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11045 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11046 HttpProxyAuthenticator
11047 - Stop warning about sigpipes in the logs. We're going to
11048 pretend that getting these occassionally is normal and fine.
11049 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11051 installer screens; and don't put stuff into StartupItems unless
11052 the user asks you to.
11053 - Require servers that use the default dirservers to have public IP
11054 addresses. We have too many servers that are configured with private
11055 IPs and their admins never notice the log entries complaining that
11056 their descriptors are being rejected.
11057 - Add OSX uninstall instructions. An actual uninstall script will
11061 Changes in version 0.1.0.8-rc - 2005-05-23
11063 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11064 panics. Disable kqueue on all OS X Tors.
11065 - Fix RPM: remove duplicate line accidentally added to the rpm
11067 - Disable threads on openbsd too, since its gethostaddr is not
11069 - Tolerate libevent 0.8 since it still works, even though it's
11071 - Enable building on Red Hat 9.0 again.
11072 - Allow the middle hop of the testing circuit to be running any
11073 version, now that most of them have the bugfix to let them connect
11074 to unknown servers. This will allow reachability testing to work
11075 even when 0.0.9.7-0.0.9.9 become obsolete.
11076 - Handle relay cells with rh.length too large. This prevents
11077 a potential attack that could read arbitrary memory (maybe even
11078 keys) from the exit server's process.
11079 - We screwed up the dirport reachability testing when we don't yet
11080 have a cached version of the directory. Hopefully now fixed.
11081 - Clean up router_load_single_router() (used by the controller),
11082 so it doesn't seg fault on error.
11083 - Fix a minor memory leak when somebody establishes an introduction
11084 point at your Tor server.
11085 - If a socks connection ends because read fails, don't warn that
11086 you're not sending a socks reply back.
11089 - Add HttpProxyAuthenticator config option too, that works like
11090 the HttpsProxyAuthenticator config option.
11091 - Encode hashed controller passwords in hex instead of base64,
11092 to make it easier to write controllers.
11095 Changes in version 0.1.0.7-rc - 2005-05-17
11097 - Fix a bug in the OS X package installer that prevented it from
11098 installing on Tiger.
11099 - Fix a script bug in the OS X package installer that made it
11100 complain during installation.
11101 - Find libevent even if it's hiding in /usr/local/ and your
11102 CFLAGS and LDFLAGS don't tell you to look there.
11103 - Be able to link with libevent as a shared library (the default
11104 after 1.0d), even if it's hiding in /usr/local/lib and even
11105 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11106 assuming you're running gcc. Otherwise fail and give a useful
11108 - Fix a bug in the RPM packager: set home directory for _tor to
11109 something more reasonable when first installing.
11110 - Free a minor amount of memory that is still reachable on exit.
11113 Changes in version 0.1.0.6-rc - 2005-05-14
11115 - Implement --disable-threads configure option. Disable threads on
11116 netbsd by default, because it appears to have no reentrant resolver
11118 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11119 release (1.1) detects and disables kqueue if it's broken.
11120 - Append default exit policy before checking for implicit internal
11121 addresses. Now we don't log a bunch of complaints on startup
11122 when using the default exit policy.
11123 - Some people were putting "Address " in their torrc, and they had
11124 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11125 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11126 LOCALSTATEDIR/tor instead.
11127 - Fix fragmented-message bug in TorControl.py.
11128 - Resolve a minor bug which would prevent unreachable dirports
11129 from getting suppressed in the published descriptor.
11130 - When the controller gave us a new descriptor, we weren't resolving
11131 it immediately, so Tor would think its address was 0.0.0.0 until
11132 we fetched a new directory.
11133 - Fix an uppercase/lowercase case error in suppressing a bogus
11134 libevent warning on some Linuxes.
11137 - Begin scrubbing sensitive strings from logs by default. Turn off
11138 the config option SafeLogging if you need to do debugging.
11139 - Switch to a new buffer management algorithm, which tries to avoid
11140 reallocing and copying quite as much. In first tests it looks like
11141 it uses *more* memory on average, but less cpu.
11142 - First cut at support for "create-fast" cells. Clients can use
11143 these when extending to their first hop, since the TLS already
11144 provides forward secrecy and authentication. Not enabled on
11146 - When dirservers refuse a router descriptor, we now log its
11147 contactinfo, platform, and the poster's IP address.
11148 - Call tor_free_all instead of connections_free_all after forking, to
11149 save memory on systems that need to fork.
11150 - Whine at you if you're a server and you don't set your contactinfo.
11151 - Implement --verify-config command-line option to check if your torrc
11152 is valid without actually launching Tor.
11153 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11154 rather than just rejecting it.
11157 Changes in version 0.1.0.5-rc - 2005-04-27
11159 - Stop trying to print a null pointer if an OR conn fails because
11160 we didn't like its cert.
11162 - Switch our internal buffers implementation to use a ring buffer,
11163 to hopefully improve performance for fast servers a lot.
11164 - Add HttpsProxyAuthenticator support (basic auth only), based
11165 on patch from Adam Langley.
11166 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11167 the fast servers that have been joining lately.
11168 - Give hidden service accesses extra time on the first attempt,
11169 since 60 seconds is often only barely enough. This might improve
11171 - Improve performance for dirservers: stop re-parsing the whole
11172 directory every time you regenerate it.
11173 - Add more debugging info to help us find the weird dns freebsd
11174 pthreads bug; cleaner debug messages to help track future issues.
11177 Changes in version 0.0.9.9 - 2005-04-23
11178 o Bugfixes on 0.0.9.x:
11179 - If unofficial Tor clients connect and send weird TLS certs, our
11180 Tor server triggers an assert. This release contains a minimal
11181 backport from the broader fix that we put into 0.1.0.4-rc.
11184 Changes in version 0.1.0.4-rc - 2005-04-23
11186 - If unofficial Tor clients connect and send weird TLS certs, our
11187 Tor server triggers an assert. Stop asserting, and start handling
11188 TLS errors better in other situations too.
11189 - When the controller asks us to tell it about all the debug-level
11190 logs, it turns out we were generating debug-level logs while
11191 telling it about them, which turns into a bad loop. Now keep
11192 track of whether you're sending a debug log to the controller,
11193 and don't log when you are.
11194 - Fix the "postdescriptor" feature of the controller interface: on
11195 non-complete success, only say "done" once.
11197 - Clients are now willing to load balance over up to 2mB, not 1mB,
11198 of advertised bandwidth capacity.
11199 - Add a NoPublish config option, so you can be a server (e.g. for
11200 testing running Tor servers in other Tor networks) without
11201 publishing your descriptor to the primary dirservers.
11204 Changes in version 0.1.0.3-rc - 2005-04-08
11205 o Improvements on 0.1.0.2-rc:
11206 - Client now retries when streams end early for 'hibernating' or
11207 'resource limit' reasons, rather than failing them.
11208 - More automated handling for dirserver operators:
11209 - Automatically approve nodes running 0.1.0.2-rc or later,
11210 now that the the reachability detection stuff is working.
11211 - Now we allow two unverified servers with the same nickname
11212 but different keys. But if a nickname is verified, only that
11213 nickname+key are allowed.
11214 - If you're an authdirserver connecting to an address:port,
11215 and it's not the OR you were expecting, forget about that
11216 descriptor. If he *was* the one you were expecting, then forget
11217 about all other descriptors for that address:port.
11218 - Allow servers to publish descriptors from 12 hours in the future.
11219 Corollary: only whine about clock skew from the dirserver if
11220 he's a trusted dirserver (since now even verified servers could
11221 have quite wrong clocks).
11222 - Adjust maximum skew and age for rendezvous descriptors: let skew
11223 be 48 hours rather than 90 minutes.
11224 - Efficiency improvements:
11225 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11226 it much faster to look up a circuit for each relay cell.
11227 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11228 since they're eating our cpu on exit nodes.
11229 - Stop wasting time doing a case insensitive comparison for every
11230 dns name every time we do any lookup. Canonicalize the names to
11231 lowercase and be done with it.
11232 - Start sending 'truncated' cells back rather than destroy cells,
11233 if the circuit closes in front of you. This means we won't have
11234 to abandon partially built circuits.
11235 - Only warn once per nickname from add_nickname_list_to_smartlist
11236 per failure, so an entrynode or exitnode choice that's down won't
11238 - Put a note in the torrc about abuse potential with the default
11240 - Revise control spec and implementation to allow all log messages to
11241 be sent to controller with their severities intact (suggested by
11242 Matt Edman). Update TorControl to handle new log event types.
11243 - Provide better explanation messages when controller's POSTDESCRIPTOR
11245 - Stop putting nodename in the Platform string in server descriptors.
11246 It doesn't actually help, and it is confusing/upsetting some people.
11248 o Bugfixes on 0.1.0.2-rc:
11249 - We were printing the host mask wrong in exit policies in server
11250 descriptors. This isn't a critical bug though, since we were still
11251 obeying the exit policy internally.
11252 - Fix Tor when compiled with libevent but without pthreads: move
11253 connection_unregister() from _connection_free() to
11255 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
11256 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
11257 when we look through the connection array, we'll find any of the
11258 cpu/dnsworkers. This is no good.
11260 o Bugfixes on 0.0.9.8:
11261 - Fix possible bug on threading platforms (e.g. win32) which was
11262 leaking a file descriptor whenever a cpuworker or dnsworker died.
11263 - When using preferred entry or exit nodes, ignore whether the
11264 circuit wants uptime or capacity. They asked for the nodes, they
11266 - chdir() to your datadirectory at the *end* of the daemonize process,
11267 not the beginning. This was a problem because the first time you
11268 run tor, if your datadir isn't there, and you have runasdaemon set
11269 to 1, it will try to chdir to it before it tries to create it. Oops.
11270 - Handle changed router status correctly when dirserver reloads
11271 fingerprint file. We used to be dropping all unverified descriptors
11272 right then. The bug was hidden because we would immediately
11273 fetch a directory from another dirserver, which would include the
11274 descriptors we just dropped.
11275 - When we're connecting to an OR and he's got a different nickname/key
11276 than we were expecting, only complain loudly if we're an OP or a
11277 dirserver. Complaining loudly to the OR admins just confuses them.
11278 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11279 artificially capped at 500kB.
11282 Changes in version 0.0.9.8 - 2005-04-07
11283 o Bugfixes on 0.0.9.x:
11284 - We have a bug that I haven't found yet. Sometimes, very rarely,
11285 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11286 thinks of itself as idle. This meant that no new circuits ever got
11287 established. Here's a workaround to kill any cpuworker that's been
11288 busy for more than 100 seconds.
11291 Changes in version 0.1.0.2-rc - 2005-04-01
11292 o Bugfixes on 0.1.0.1-rc:
11293 - Fixes on reachability detection:
11294 - Don't check for reachability while hibernating.
11295 - If ORPort is reachable but DirPort isn't, still publish the
11296 descriptor, but zero out DirPort until it's found reachable.
11297 - When building testing circs for ORPort testing, use only
11298 high-bandwidth nodes, so fewer circuits fail.
11299 - Complain about unreachable ORPort separately from unreachable
11300 DirPort, so the user knows what's going on.
11301 - Make sure we only conclude ORPort reachability if we didn't
11302 initiate the conn. Otherwise we could falsely conclude that
11303 we're reachable just because we connected to the guy earlier
11304 and he used that same pipe to extend to us.
11305 - Authdirservers shouldn't do ORPort reachability detection,
11306 since they're in clique mode, so it will be rare to find a
11307 server not already connected to them.
11308 - When building testing circuits, always pick middle hops running
11309 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
11310 bug. (This is a kludge; it will go away when 0.0.9.x becomes
11312 - When we decide we're reachable, actually publish our descriptor
11314 - Fix bug in redirectstream in the controller.
11315 - Fix the state descriptor strings so logs don't claim edge streams
11316 are in a different state than they actually are.
11317 - Use recent libevent features when possible (this only really affects
11318 win32 and osx right now, because the new libevent with these
11319 features hasn't been released yet). Add code to suppress spurious
11321 - Prevent possible segfault in connection_close_unattached_ap().
11322 - Fix newlines on torrc in win32.
11323 - Improve error msgs when tor-resolve fails.
11325 o Improvements on 0.0.9.x:
11326 - New experimental script tor/contrib/ExerciseServer.py (needs more
11327 work) that uses the controller interface to build circuits and
11328 fetch pages over them. This will help us bootstrap servers that
11329 have lots of capacity but haven't noticed it yet.
11330 - New experimental script tor/contrib/PathDemo.py (needs more work)
11331 that uses the controller interface to let you choose whole paths
11333 "<hostname>.<path,separated by dots>.<length of path>.path"
11334 - When we've connected to an OR and handshaked but didn't like
11335 the result, we were closing the conn without sending destroy
11336 cells back for pending circuits. Now send those destroys.
11339 Changes in version 0.0.9.7 - 2005-04-01
11340 o Bugfixes on 0.0.9.x:
11341 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11342 - Compare identity to identity, not to nickname, when extending to
11343 a router not already in the directory. This was preventing us from
11344 extending to unknown routers. Oops.
11345 - Make sure to create OS X Tor user in <500 range, so we aren't
11346 creating actual system users.
11347 - Note where connection-that-hasn't-sent-end was marked, and fix
11348 a few really loud instances of this harmless bug (it's fixed more
11352 Changes in version 0.1.0.1-rc - 2005-03-28
11354 - Add reachability testing. Your Tor server will automatically try
11355 to see if its ORPort and DirPort are reachable from the outside,
11356 and it won't upload its descriptor until it decides they are.
11357 - Handle unavailable hidden services better. Handle slow or busy
11358 hidden services better.
11359 - Add support for CONNECTing through https proxies, with "HttpsProxy"
11361 - New exit policy: accept most low-numbered ports, rather than
11362 rejecting most low-numbered ports.
11363 - More Tor controller support (still experimental). See
11364 http://tor.eff.org/doc/control-spec.txt for all the new features,
11365 including signals to emulate unix signals from any platform;
11366 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
11367 closestream; closecircuit; etc.
11368 - Make nt services work and start on startup on win32 (based on
11369 patch by Matt Edman).
11370 - Add a new AddressMap config directive to rewrite incoming socks
11371 addresses. This lets you, for example, declare an implicit
11372 required exit node for certain sites.
11373 - Add a new TrackHostExits config directive to trigger addressmaps
11374 for certain incoming socks addresses -- for sites that break when
11375 your exit keeps changing (based on patch by Mike Perry).
11376 - Redo the client-side dns cache so it's just an addressmap too.
11377 - Notice when our IP changes, and reset stats/uptime/reachability.
11378 - When an application is using socks5, give him the whole variety of
11379 potential socks5 responses (connect refused, host unreachable, etc),
11380 rather than just "success" or "failure".
11381 - A more sane version numbering system. See
11382 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
11383 - New contributed script "exitlist": a simple python script to
11384 parse directories and find Tor nodes that exit to listed
11386 - New contributed script "privoxy-tor-toggle" to toggle whether
11387 Privoxy uses Tor. Seems to be configured for Debian by default.
11388 - Report HTTP reasons to client when getting a response from directory
11389 servers -- so you can actually know what went wrong.
11390 - New config option MaxAdvertisedBandwidth which lets you advertise
11391 a low bandwidthrate (to not attract as many circuits) while still
11392 allowing a higher bandwidthrate in reality.
11394 o Robustness/stability fixes:
11395 - Make Tor use Niels Provos's libevent instead of its current
11396 poll-but-sometimes-select mess. This will let us use faster async
11397 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
11399 - pthread support now too. This was forced because when we forked,
11400 we ended up wasting a lot of duplicate ram over time. Also switch
11401 to foo_r versions of some library calls to allow reentry and
11403 - Better handling for heterogeneous / unreliable nodes:
11404 - Annotate circuits w/ whether they aim to contain high uptime nodes
11405 and/or high capacity nodes. When building circuits, choose
11407 - This means that every single node in an intro rend circuit,
11408 not just the last one, will have a minimum uptime.
11409 - New config option LongLivedPorts to indicate application streams
11410 that will want high uptime circuits.
11411 - Servers reset uptime when a dir fetch entirely fails. This
11412 hopefully reflects stability of the server's network connectivity.
11413 - If somebody starts his tor server in Jan 2004 and then fixes his
11414 clock, don't make his published uptime be a year.
11415 - Reset published uptime when you wake up from hibernation.
11416 - Introduce a notion of 'internal' circs, which are chosen without
11417 regard to the exit policy of the last hop. Intro and rendezvous
11418 circs must be internal circs, to avoid leaking information. Resolve
11419 and connect streams can use internal circs if they want.
11420 - New circuit pooling algorithm: make sure to have enough circs around
11421 to satisfy any predicted ports, and also make sure to have 2 internal
11422 circs around if we've required internal circs lately (and with high
11423 uptime if we've seen that lately too).
11424 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
11425 which describes how often we retry making new circuits if current
11426 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
11427 how long we're willing to make use of an already-dirty circuit.
11428 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
11429 circ as necessary, if there are any completed ones lying around
11430 when we try to launch one.
11431 - Make hidden services try to establish a rendezvous for 30 seconds,
11432 rather than for n (where n=3) attempts to build a circuit.
11433 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
11434 "ShutdownWaitLength".
11435 - Try to be more zealous about calling connection_edge_end when
11436 things go bad with edge conns in connection.c.
11437 - Revise tor-spec to add more/better stream end reasons.
11438 - Revise all calls to connection_edge_end to avoid sending "misc",
11439 and to take errno into account where possible.
11442 - Fix a race condition that can trigger an assert, when we have a
11443 pending create cell and an OR connection fails right then.
11444 - Fix several double-mark-for-close bugs, e.g. where we were finding
11445 a conn for a cell even if that conn is already marked for close.
11446 - Make sequence of log messages when starting on win32 with no config
11447 file more reasonable.
11448 - When choosing an exit node for a new non-internal circ, don't take
11449 into account whether it'll be useful for any pending x.onion
11450 addresses -- it won't.
11451 - Turn addr_policy_compare from a tristate to a quadstate; this should
11452 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
11453 for google.com" problem.
11454 - Make "platform" string in descriptor more accurate for Win32 servers,
11455 so it's not just "unknown platform".
11456 - Fix an edge case in parsing config options (thanks weasel).
11457 If they say "--" on the commandline, it's not an option.
11458 - Reject odd-looking addresses at the client (e.g. addresses that
11459 contain a colon), rather than having the server drop them because
11461 - tor-resolve requests were ignoring .exit if there was a working circuit
11462 they could use instead.
11463 - REUSEADDR on normal platforms means you can rebind to the port
11464 right after somebody else has let it go. But REUSEADDR on win32
11465 means to let you bind to the port _even when somebody else
11466 already has it bound_! So, don't do that on Win32.
11467 - Change version parsing logic: a version is "obsolete" if it is not
11468 recommended and (1) there is a newer recommended version in the
11469 same series, or (2) there are no recommended versions in the same
11470 series, but there are some recommended versions in a newer series.
11471 A version is "new" if it is newer than any recommended version in
11473 - Stop most cases of hanging up on a socks connection without sending
11477 - Require BandwidthRate to be at least 20kB/s for servers.
11478 - When a dirserver causes you to give a warn, mention which dirserver
11480 - New config option DirAllowPrivateAddresses for authdirservers.
11481 Now by default they refuse router descriptors that have non-IP or
11482 private-IP addresses.
11483 - Stop publishing socksport in the directory, since it's not
11484 actually meant to be public. For compatibility, publish a 0 there
11486 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
11487 smart" value, that is low for servers and high for clients.
11488 - If our clock jumps forward by 100 seconds or more, assume something
11489 has gone wrong with our network and abandon all not-yet-used circs.
11490 - Warn when exit policy implicitly allows local addresses.
11491 - If we get an incredibly skewed timestamp from a dirserver mirror
11492 that isn't a verified OR, don't warn -- it's probably him that's
11494 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
11495 cookies to disk and doesn't log each web request to disk. (Thanks
11496 to Brett Carrington for pointing this out.)
11497 - When a client asks us for a dir mirror and we don't have one,
11498 launch an attempt to get a fresh one.
11499 - If we're hibernating and we get a SIGINT, exit immediately.
11500 - Add --with-dmalloc ./configure option, to track memory leaks.
11501 - And try to free all memory on closing, so we can detect what
11503 - Cache local dns resolves correctly even when they're .exit
11505 - Give a better warning when some other server advertises an
11506 ORPort that is actually an apache running ssl.
11507 - Add "opt hibernating 1" to server descriptor to make it clearer
11508 whether the server is hibernating.
11511 Changes in version 0.0.9.6 - 2005-03-24
11512 o Bugfixes on 0.0.9.x (crashes and asserts):
11513 - Add new end stream reasons to maintainance branch. Fix bug where
11514 reason (8) could trigger an assert. Prevent bug from recurring.
11515 - Apparently win32 stat wants paths to not end with a slash.
11516 - Fix assert triggers in assert_cpath_layer_ok(), where we were
11517 blowing away the circuit that conn->cpath_layer points to, then
11518 checking to see if the circ is well-formed. Backport check to make
11519 sure we dont use the cpath on a closed connection.
11520 - Prevent circuit_resume_edge_reading_helper() from trying to package
11521 inbufs for marked-for-close streams.
11522 - Don't crash on hup if your options->address has become unresolvable.
11523 - Some systems (like OS X) sometimes accept() a connection and tell
11524 you the remote host is 0.0.0.0:0. If this happens, due to some
11525 other mis-features, we get confused; so refuse the conn for now.
11527 o Bugfixes on 0.0.9.x (other):
11528 - Fix harmless but scary "Unrecognized content encoding" warn message.
11529 - Add new stream error reason: TORPROTOCOL reason means "you are not
11530 speaking a version of Tor I understand; say bye-bye to your stream."
11531 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
11532 into the future, now that we are more tolerant of skew. This
11533 resolves a bug where a Tor server would refuse to cache a directory
11534 because all the directories it gets are too far in the future;
11535 yet the Tor server never logs any complaints about clock skew.
11536 - Mac packaging magic: make man pages useable, and do not overwrite
11537 existing torrc files.
11538 - Make OS X log happily to /var/log/tor/tor.log
11541 Changes in version 0.0.9.5 - 2005-02-22
11542 o Bugfixes on 0.0.9.x:
11543 - Fix an assert race at exit nodes when resolve requests fail.
11544 - Stop picking unverified dir mirrors--it only leads to misery.
11545 - Patch from Matt Edman to make NT services work better. Service
11546 support is still not compiled into the executable by default.
11547 - Patch from Dmitri Bely so the Tor service runs better under
11548 the win32 SYSTEM account.
11549 - Make tor-resolve actually work (?) on Win32.
11550 - Fix a sign bug when getrlimit claims to have 4+ billion
11551 file descriptors available.
11552 - Stop refusing to start when bandwidthburst == bandwidthrate.
11553 - When create cells have been on the onion queue more than five
11554 seconds, just send back a destroy and take them off the list.
11557 Changes in version 0.0.9.4 - 2005-02-03
11558 o Bugfixes on 0.0.9:
11559 - Fix an assert bug that took down most of our servers: when
11560 a server claims to have 1 GB of bandwidthburst, don't
11562 - Don't crash as badly if we have spawned the max allowed number
11563 of dnsworkers, or we're out of file descriptors.
11564 - Block more file-sharing ports in the default exit policy.
11565 - MaxConn is now automatically set to the hard limit of max
11566 file descriptors we're allowed (ulimit -n), minus a few for
11568 - Give a clearer message when servers need to raise their
11569 ulimit -n when they start running out of file descriptors.
11570 - SGI Compatibility patches from Jan Schaumann.
11571 - Tolerate a corrupt cached directory better.
11572 - When a dirserver hasn't approved your server, list which one.
11573 - Go into soft hibernation after 95% of the bandwidth is used,
11574 not 99%. This is especially important for daily hibernators who
11575 have a small accounting max. Hopefully it will result in fewer
11576 cut connections when the hard hibernation starts.
11577 - Load-balance better when using servers that claim more than
11578 800kB/s of capacity.
11579 - Make NT services work (experimental, only used if compiled in).
11582 Changes in version 0.0.9.3 - 2005-01-21
11583 o Bugfixes on 0.0.9:
11584 - Backport the cpu use fixes from main branch, so busy servers won't
11585 need as much processor time.
11586 - Work better when we go offline and then come back, or when we
11587 run Tor at boot before the network is up. We do this by
11588 optimistically trying to fetch a new directory whenever an
11589 application request comes in and we think we're offline -- the
11590 human is hopefully a good measure of when the network is back.
11591 - Backport some minimal hidserv bugfixes: keep rend circuits open as
11592 long as you keep using them; actually publish hidserv descriptors
11593 shortly after they change, rather than waiting 20-40 minutes.
11594 - Enable Mac startup script by default.
11595 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
11596 - When you update AllowUnverifiedNodes or FirewallPorts via the
11597 controller's setconf feature, we were always appending, never
11599 - When you update HiddenServiceDir via setconf, it was screwing up
11600 the order of reading the lines, making it fail.
11601 - Do not rewrite a cached directory back to the cache; otherwise we
11602 will think it is recent and not fetch a newer one on startup.
11603 - Workaround for webservers that lie about Content-Encoding: Tor
11604 now tries to autodetect compressed directories and compression
11605 itself. This lets us Proxypass dir fetches through apache.
11608 Changes in version 0.0.9.2 - 2005-01-04
11609 o Bugfixes on 0.0.9 (crashes and asserts):
11610 - Fix an assert on startup when the disk is full and you're logging
11612 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
11613 style address, then we'd crash.
11614 - Fix an assert trigger when the running-routers string we get from
11615 a dirserver is broken.
11616 - Make worker threads start and run on win32. Now win32 servers
11618 - Bandaid (not actually fix, but now it doesn't crash) an assert
11619 where the dns worker dies mysteriously and the main Tor process
11620 doesn't remember anything about the address it was resolving.
11622 o Bugfixes on 0.0.9 (Win32):
11623 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
11624 name out of the warning/assert messages.
11625 - Fix a superficial "unhandled error on read" bug on win32.
11626 - The win32 installer no longer requires a click-through for our
11627 license, since our Free Software license grants rights but does not
11629 - Win32: When connecting to a dirserver fails, try another one
11630 immediately. (This was already working for non-win32 Tors.)
11631 - Stop trying to parse $HOME on win32 when hunting for default
11633 - Make tor-resolve.c work on win32 by calling network_init().
11635 o Bugfixes on 0.0.9 (other):
11636 - Make 0.0.9.x build on Solaris again.
11637 - Due to a fencepost error, we were blowing away the \n when reporting
11638 confvalue items in the controller. So asking for multiple config
11639 values at once couldn't work.
11640 - When listing circuits that are pending on an opening OR connection,
11641 if we're an OR we were listing circuits that *end* at us as
11642 being pending on every listener, dns/cpu worker, etc. Stop that.
11643 - Dirservers were failing to create 'running-routers' or 'directory'
11644 strings if we had more than some threshold of routers. Fix them so
11645 they can handle any number of routers.
11646 - Fix a superficial "Duplicate mark for close" bug.
11647 - Stop checking for clock skew for OR connections, even for servers.
11648 - Fix a fencepost error that was chopping off the last letter of any
11649 nickname that is the maximum allowed nickname length.
11650 - Update URLs in log messages so they point to the new website.
11651 - Fix a potential problem in mangling server private keys while
11652 writing to disk (not triggered yet, as far as we know).
11653 - Include the licenses for other free software we include in Tor,
11654 now that we're shipping binary distributions more regularly.
11657 Changes in version 0.0.9.1 - 2004-12-15
11658 o Bugfixes on 0.0.9:
11659 - Make hibernation actually work.
11660 - Make HashedControlPassword config option work.
11661 - When we're reporting event circuit status to a controller,
11662 don't use the stream status code.
11665 Changes in version 0.0.9 - 2004-12-12
11667 - Clean up manpage and torrc.sample file.
11668 - Clean up severities and text of log warnings.
11670 - Make servers trigger an assert when they enter hibernation.
11673 Changes in version 0.0.9rc7 - 2004-12-08
11674 o Bugfixes on 0.0.9rc:
11675 - Fix a stack-trashing crash when an exit node begins hibernating.
11676 - Avoid looking at unallocated memory while considering which
11677 ports we need to build circuits to cover.
11678 - Stop a sigpipe: when an 'end' cell races with eof from the app,
11679 we shouldn't hold-open-until-flush if the eof arrived first.
11680 - Fix a bug with init_cookie_authentication() in the controller.
11681 - When recommending new-format log lines, if the upper bound is
11682 LOG_ERR, leave it implicit.
11684 o Bugfixes on 0.0.8.1:
11685 - Fix a whole slew of memory leaks.
11686 - Fix isspace() and friends so they still make Solaris happy
11687 but also so they don't trigger asserts on win32.
11688 - Fix parse_iso_time on platforms without strptime (eg win32).
11689 - win32: tolerate extra "readable" events better.
11690 - win32: when being multithreaded, leave parent fdarray open.
11691 - Make unit tests work on win32.
11694 Changes in version 0.0.9rc6 - 2004-12-06
11695 o Bugfixes on 0.0.9pre:
11696 - Clean up some more integer underflow opportunities (not exploitable
11698 - While hibernating, hup should not regrow our listeners.
11699 - Send an end to the streams we close when we hibernate, rather
11700 than just chopping them off.
11701 - React to eof immediately on non-open edge connections.
11703 o Bugfixes on 0.0.8.1:
11704 - Calculate timeout for waiting for a connected cell from the time
11705 we sent the begin cell, not from the time the stream started. If
11706 it took a long time to establish the circuit, we would time out
11707 right after sending the begin cell.
11708 - Fix router_compare_addr_to_addr_policy: it was not treating a port
11709 of * as always matching, so we were picking reject *:* nodes as
11710 exit nodes too. Oops.
11713 - New circuit building strategy: keep a list of ports that we've
11714 used in the past 6 hours, and always try to have 2 circuits open
11715 or on the way that will handle each such port. Seed us with port
11716 80 so web users won't complain that Tor is "slow to start up".
11717 - Make kill -USR1 dump more useful stats about circuits.
11718 - When warning about retrying or giving up, print the address, so
11719 the user knows which one it's talking about.
11720 - If you haven't used a clean circuit in an hour, throw it away,
11721 just to be on the safe side. (This means after 6 hours a totally
11722 unused Tor client will have no circuits open.)
11725 Changes in version 0.0.9rc5 - 2004-12-01
11726 o Bugfixes on 0.0.8.1:
11727 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
11728 - Let resolve conns retry/expire also, rather than sticking around
11730 - If we are using select, make sure we stay within FD_SETSIZE.
11732 o Bugfixes on 0.0.9pre:
11733 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
11734 but doesn't seem to be currently; thanks to Ilja van Sprundel for
11736 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
11737 instead. Impose minima and maxima for all *Period options; impose
11738 even tighter maxima for fetching if we are a caching dirserver.
11739 Clip rather than rejecting.
11740 - Fetch cached running-routers from servers that serve it (that is,
11741 authdirservers and servers running 0.0.9rc5-cvs or later.)
11744 - Accept *:706 (silc) in default exit policy.
11745 - Implement new versioning format for post 0.1.
11746 - Support "foo.nickname.exit" addresses, to let Alice request the
11747 address "foo" as viewed by exit node "nickname". Based on a patch
11749 - Make tor --version --version dump the cvs Id of every file.
11752 Changes in version 0.0.9rc4 - 2004-11-28
11753 o Bugfixes on 0.0.8.1:
11754 - Make windows sockets actually non-blocking (oops), and handle
11755 win32 socket errors better.
11757 o Bugfixes on 0.0.9rc1:
11758 - Actually catch the -USR2 signal.
11761 Changes in version 0.0.9rc3 - 2004-11-25
11762 o Bugfixes on 0.0.8.1:
11763 - Flush the log file descriptor after we print "Tor opening log file",
11764 so we don't see those messages days later.
11766 o Bugfixes on 0.0.9rc1:
11767 - Make tor-resolve work again.
11768 - Avoid infinite loop in tor-resolve if tor hangs up on it.
11769 - Fix an assert trigger for clients/servers handling resolves.
11772 Changes in version 0.0.9rc2 - 2004-11-24
11773 o Bugfixes on 0.0.9rc1:
11774 - I broke socks5 support while fixing the eof bug.
11775 - Allow unitless bandwidths and intervals; they default to bytes
11777 - New servers don't start out hibernating; they are active until
11778 they run out of bytes, so they have a better estimate of how
11779 long it takes, and so their operators can know they're working.
11782 Changes in version 0.0.9rc1 - 2004-11-23
11783 o Bugfixes on 0.0.8.1:
11784 - Finally fix a bug that's been plaguing us for a year:
11785 With high load, circuit package window was reaching 0. Whenever
11786 we got a circuit-level sendme, we were reading a lot on each
11787 socket, but only writing out a bit. So we would eventually reach
11788 eof. This would be noticed and acted on even when there were still
11789 bytes sitting in the inbuf.
11790 - When poll() is interrupted, we shouldn't believe the revents values.
11792 o Bugfixes on 0.0.9pre6:
11793 - Fix hibernate bug that caused pre6 to be broken.
11794 - Don't keep rephist info for routers that haven't had activity for
11795 24 hours. (This matters now that clients have keys, since we track
11797 - Never call close_temp_logs while validating log options.
11798 - Fix backslash-escaping on tor.sh.in and torctl.in.
11801 - Implement weekly/monthly/daily accounting: now you specify your
11802 hibernation properties by
11803 AccountingMax N bytes|KB|MB|GB|TB
11804 AccountingStart day|week|month [day] HH:MM
11805 Defaults to "month 1 0:00".
11806 - Let bandwidth and interval config options be specified as 5 bytes,
11807 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
11808 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
11809 get back to normal.)
11810 - If your requested entry or exit node has advertised bandwidth 0,
11812 - Be more greedy about filling up relay cells -- we try reading again
11813 once we've processed the stuff we read, in case enough has arrived
11814 to fill the last cell completely.
11815 - Apply NT service patch from Osamu Fujino. Still needs more work.
11818 Changes in version 0.0.9pre6 - 2004-11-15
11819 o Bugfixes on 0.0.8.1:
11820 - Fix assert failure on malformed socks4a requests.
11821 - Use identity comparison, not nickname comparison, to choose which
11822 half of circuit-ID-space each side gets to use. This is needed
11823 because sometimes we think of a router as a nickname, and sometimes
11824 as a hex ID, and we can't predict what the other side will do.
11825 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
11826 write() call will fail and we handle it there.
11827 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
11828 and smartlist_len, which are two major profiling offenders.
11830 o Bugfixes on 0.0.9pre5:
11831 - Fix a bug in read_all that was corrupting config files on windows.
11832 - When we're raising the max number of open file descriptors to
11833 'unlimited', don't log that we just raised it to '-1'.
11834 - Include event code with events, as required by control-spec.txt.
11835 - Don't give a fingerprint when clients do --list-fingerprint:
11836 it's misleading, because it will never be the same again.
11837 - Stop using strlcpy in tor_strndup, since it was slowing us
11839 - Remove warn on startup about missing cached-directory file.
11840 - Make kill -USR1 work again.
11841 - Hibernate if we start tor during the "wait for wakeup-time" phase
11842 of an accounting interval. Log our hibernation plans better.
11843 - Authoritative dirservers now also cache their directory, so they
11844 have it on start-up.
11847 - Fetch running-routers; cache running-routers; compress
11848 running-routers; serve compressed running-routers.z
11849 - Add NSI installer script contributed by J Doe.
11850 - Commit VC6 and VC7 workspace/project files.
11851 - Commit a tor.spec for making RPM files, with help from jbash.
11852 - Add contrib/torctl.in contributed by Glenn Fink.
11853 - Implement the control-spec's SAVECONF command, to write your
11854 configuration to torrc.
11855 - Get cookie authentication for the controller closer to working.
11856 - Include control-spec.txt in the tarball.
11857 - When set_conf changes our server descriptor, upload a new copy.
11858 But don't upload it too often if there are frequent changes.
11859 - Document authentication config in man page, and document signals
11861 - Clean up confusing parts of man page and torrc.sample.
11862 - Make expand_filename handle ~ and ~username.
11863 - Use autoconf to enable largefile support where necessary. Use
11864 ftello where available, since ftell can fail at 2GB.
11865 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
11866 log more informatively.
11867 - Give a slightly more useful output for "tor -h".
11868 - Refuse application socks connections to port 0.
11869 - Check clock skew for verified servers, but allow unverified
11870 servers and clients to have any clock skew.
11871 - Break DirFetchPostPeriod into:
11872 - DirFetchPeriod for fetching full directory,
11873 - StatusFetchPeriod for fetching running-routers,
11874 - DirPostPeriod for posting server descriptor,
11875 - RendPostPeriod for posting hidden service descriptors.
11876 - Make sure the hidden service descriptors are at a random offset
11877 from each other, to hinder linkability.
11880 Changes in version 0.0.9pre5 - 2004-11-09
11881 o Bugfixes on 0.0.9pre4:
11882 - Fix a seg fault in unit tests (doesn't affect main program).
11883 - Fix an assert bug where a hidden service provider would fail if
11884 the first hop of his rendezvous circuit was down.
11885 - Hidden service operators now correctly handle version 1 style
11886 INTRODUCE1 cells (nobody generates them still, so not a critical
11888 - If do_hup fails, actually notice.
11889 - Handle more errnos from accept() without closing the listener.
11890 Some OpenBSD machines were closing their listeners because
11891 they ran out of file descriptors.
11892 - Send resolve cells to exit routers that are running a new
11893 enough version of the resolve code to work right.
11894 - Better handling of winsock includes on non-MSV win32 compilers.
11895 - Some people had wrapped their tor client/server in a script
11896 that would restart it whenever it died. This did not play well
11897 with our "shut down if your version is obsolete" code. Now people
11898 don't fetch a new directory if their local cached version is
11900 - Make our autogen.sh work on ksh as well as bash.
11903 - Hibernation: New config option "AccountingMaxKB" lets you
11904 set how many KBytes per month you want to allow your server to
11905 consume. Rather than spreading those bytes out evenly over the
11906 month, we instead hibernate for some of the month and pop up
11907 at a deterministic time, work until the bytes are consumed, then
11908 hibernate again. Config option "MonthlyAccountingStart" lets you
11909 specify which day of the month your billing cycle starts on.
11910 - Control interface: a separate program can now talk to your
11911 client/server over a socket, and get/set config options, receive
11912 notifications of circuits and streams starting/finishing/dying,
11913 bandwidth used, etc. The next step is to get some GUIs working.
11914 Let us know if you want to help out. See doc/control-spec.txt .
11915 - Ship a contrib/tor-control.py as an example script to interact
11916 with the control port.
11917 - "tor --hash-password zzyxz" will output a salted password for
11918 use in authenticating to the control interface.
11919 - New log format in config:
11920 "Log minsev[-maxsev] stdout|stderr|syslog" or
11921 "Log minsev[-maxsev] file /var/foo"
11924 - DirPolicy config option, to let people reject incoming addresses
11925 from their dirserver.
11926 - "tor --list-fingerprint" will list your identity key fingerprint
11928 - Add "pass" target for RedirectExit, to make it easier to break
11929 out of a sequence of RedirectExit rules.
11930 - Clients now generate a TLS cert too, in preparation for having
11931 them act more like real nodes.
11932 - Ship src/win32/ in the tarball, so people can use it to build.
11933 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
11935 - New "router-status" line in directory, to better bind each verified
11936 nickname to its identity key.
11937 - Deprecate unofficial config option abbreviations, and abbreviations
11938 not on the command line.
11939 - Add a pure-C tor-resolve implementation.
11940 - Use getrlimit and friends to ensure we can reach MaxConn (currently
11941 1024) file descriptors.
11943 o Code security improvements, inspired by Ilja:
11944 - Replace sprintf with snprintf. (I think they were all safe, but
11946 - Replace strcpy/strncpy with strlcpy in more places.
11947 - Avoid strcat; use snprintf or strlcat instead.
11948 - snprintf wrapper with consistent (though not C99) overflow behavior.
11951 Changes in version 0.0.9pre4 - 2004-10-17
11952 o Bugfixes on 0.0.9pre3:
11953 - If the server doesn't specify an exit policy, use the real default
11954 exit policy, not reject *:*.
11955 - Ignore fascistfirewall when uploading/downloading hidden service
11956 descriptors, since we go through Tor for those; and when using
11957 an HttpProxy, since we assume it can reach them all.
11958 - When looking for an authoritative dirserver, use only the ones
11959 configured at boot. Don't bother looking in the directory.
11960 - The rest of the fix for get_default_conf_file() on older win32.
11961 - Make 'Routerfile' config option obsolete.
11964 - New 'MyFamily nick1,...' config option for a server to
11965 specify other servers that shouldn't be used in the same circuit
11966 with it. Only believed if nick1 also specifies us.
11967 - New 'NodeFamily nick1,nick2,...' config option for a client to
11968 specify nodes that it doesn't want to use in the same circuit.
11969 - New 'Redirectexit pattern address:port' config option for a
11970 server to redirect exit connections, e.g. to a local squid.
11973 Changes in version 0.0.9pre3 - 2004-10-13
11974 o Bugfixes on 0.0.8.1:
11975 - Better torrc example lines for dirbindaddress and orbindaddress.
11976 - Improved bounds checking on parsed ints (e.g. config options and
11977 the ones we find in directories.)
11978 - Better handling of size_t vs int, so we're more robust on 64
11980 - Fix the rest of the bug where a newly started OR would appear
11981 as unverified even after we've added his fingerprint and hupped
11983 - Fix a bug from 0.0.7: when read() failed on a stream, we would
11984 close it without sending back an end. So 'connection refused'
11985 would simply be ignored and the user would get no response.
11987 o Bugfixes on 0.0.9pre2:
11988 - Serving the cached-on-disk directory to people is bad. We now
11989 provide no directory until we've fetched a fresh one.
11990 - Workaround for bug on windows where cached-directories get crlf
11992 - Make get_default_conf_file() work on older windows too.
11993 - If we write a *:* exit policy line in the descriptor, don't write
11994 any more exit policy lines.
11997 - Use only 0.0.9pre1 and later servers for resolve cells.
11998 - Make the dirservers file obsolete.
11999 - Include a dir-signing-key token in directories to tell the
12000 parsing entity which key is being used to sign.
12001 - Remove the built-in bulky default dirservers string.
12002 - New config option "Dirserver %s:%d [fingerprint]", which can be
12003 repeated as many times as needed. If no dirservers specified,
12004 default to moria1,moria2,tor26.
12005 - Make moria2 advertise a dirport of 80, so people behind firewalls
12006 will be able to get a directory.
12007 - Http proxy support
12008 - Dirservers translate requests for http://%s:%d/x to /x
12009 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12010 be routed through this host.
12011 - Clients ask for /tor/x rather than /x for new enough dirservers.
12012 This way we can one day coexist peacefully with apache.
12013 - Clients specify a "Host: %s%d" http header, to be compatible
12014 with more proxies, and so running squid on an exit node can work.
12017 Changes in version 0.0.8.1 - 2004-10-13
12019 - Fix a seg fault that can be triggered remotely for Tor
12020 clients/servers with an open dirport.
12021 - Fix a rare assert trigger, where routerinfos for entries in
12022 our cpath would expire while we're building the path.
12023 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12024 - Fix a rare seg fault for people running hidden services on
12025 intermittent connections.
12026 - Fix a bug in parsing opt keywords with objects.
12027 - Fix a stale pointer assert bug when a stream detaches and
12029 - Fix a string format vulnerability (probably not exploitable)
12030 in reporting stats locally.
12031 - Fix an assert trigger: sometimes launching circuits can fail
12032 immediately, e.g. because too many circuits have failed recently.
12033 - Fix a compile warning on 64 bit platforms.
12036 Changes in version 0.0.9pre2 - 2004-10-03
12038 - Make fetching a cached directory work for 64-bit platforms too.
12039 - Make zlib.h a required header, not an optional header.
12042 Changes in version 0.0.9pre1 - 2004-10-01
12044 - Stop using separate defaults for no-config-file and
12045 empty-config-file. Now you have to explicitly turn off SocksPort,
12046 if you don't want it open.
12047 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12048 - Improve man page to mention more of the 0.0.8 features.
12049 - Fix a rare seg fault for people running hidden services on
12050 intermittent connections.
12051 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12053 - Fix more dns related bugs: send back resolve_failed and end cells
12054 more reliably when the resolve fails, rather than closing the
12055 circuit and then trying to send the cell. Also attach dummy resolve
12056 connections to a circuit *before* calling dns_resolve(), to fix
12057 a bug where cached answers would never be sent in RESOLVED cells.
12058 - When we run out of disk space, or other log writing error, don't
12059 crash. Just stop logging to that log and continue.
12060 - We were starting to daemonize before we opened our logs, so if
12061 there were any problems opening logs, we would complain to stderr,
12062 which wouldn't work, and then mysteriously exit.
12063 - Fix a rare bug where sometimes a verified OR would connect to us
12064 before he'd uploaded his descriptor, which would cause us to
12065 assign conn->nickname as though he's unverified. Now we look through
12066 the fingerprint list to see if he's there.
12067 - Fix a rare assert trigger, where routerinfos for entries in
12068 our cpath would expire while we're building the path.
12071 - Clients can ask dirservers for /dir.z to get a compressed version
12072 of the directory. Only works for servers running 0.0.9, of course.
12073 - Make clients cache directories and use them to seed their router
12074 lists at startup. This means clients have a datadir again.
12075 - Configuration infrastructure support for warning on obsolete
12077 - Respond to content-encoding headers by trying to uncompress as
12079 - Reply with a deflated directory when a client asks for "dir.z".
12080 We could use allow-encodings instead, but allow-encodings isn't
12081 specified in HTTP 1.0.
12082 - Raise the max dns workers from 50 to 100.
12083 - Discourage people from setting their dirfetchpostperiod more often
12084 than once per minute.
12085 - Protect dirservers from overzealous descriptor uploading -- wait
12086 10 seconds after directory gets dirty, before regenerating.
12089 Changes in version 0.0.8 - 2004-08-25
12090 o Port it to SunOS 5.9 / Athena
12093 Changes in version 0.0.8rc2 - 2004-08-20
12094 o Make it compile on cygwin again.
12095 o When picking unverified routers, skip those with low uptime and/or
12096 low bandwidth, depending on what properties you care about.
12099 Changes in version 0.0.8rc1 - 2004-08-18
12100 o Changes from 0.0.7.3:
12102 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12103 don't put it into the client dns cache.
12104 - If a begin failed due to exit policy, but we believe the IP address
12105 should have been allowed, switch that router to exitpolicy reject *:*
12106 until we get our next directory.
12108 - Clients choose nodes proportional to advertised bandwidth.
12109 - Avoid using nodes with low uptime as introduction points.
12110 - Handle servers with dynamic IP addresses: don't replace
12111 options->Address with the resolved one at startup, and
12112 detect our address right before we make a routerinfo each time.
12113 - 'FascistFirewall' option to pick dirservers and ORs on specific
12114 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12115 which ports are open. (Defaults to 80,443)
12116 - Be more aggressive about trying to make circuits when the network
12117 has changed (e.g. when you unsuspend your laptop).
12118 - Check for time skew on http headers; report date in response to
12120 - If the entrynode config line has only one node, don't pick it as
12122 - Add strict{entry|exit}nodes config options. If set to 1, then
12123 we refuse to build circuits that don't include the specified entry
12125 - OutboundBindAddress config option, to bind to a specific
12126 IP address for outgoing connect()s.
12127 - End truncated log entries (e.g. directories) with "[truncated]".
12129 o Patches to 0.0.8preX:
12131 - Patches to compile and run on win32 again (maybe)?
12132 - Fix crash when looking for ~/.torrc with no $HOME set.
12133 - Fix a race bug in the unit tests.
12134 - Handle verified/unverified name collisions better when new
12135 routerinfo's arrive in a directory.
12136 - Sometimes routers were getting entered into the stats before
12137 we'd assigned their identity_digest. Oops.
12138 - Only pick and establish intro points after we've gotten a
12141 - AllowUnverifiedNodes config option to let circuits choose no-name
12142 routers in entry,middle,exit,introduction,rendezvous positions.
12143 Allow middle and rendezvous positions by default.
12144 - Add a man page for tor-resolve.
12147 Changes in version 0.0.7.3 - 2004-08-12
12148 o Stop dnsworkers from triggering an assert failure when you
12149 ask them to resolve the host "".
12152 Changes in version 0.0.8pre3 - 2004-08-09
12153 o Changes from 0.0.7.2:
12154 - Allow multiple ORs with same nickname in routerlist -- now when
12155 people give us one identity key for a nickname, then later
12156 another, we don't constantly complain until the first expires.
12157 - Remember used bandwidth (both in and out), and publish 15-minute
12158 snapshots for the past day into our descriptor.
12159 - You can now fetch $DIRURL/running-routers to get just the
12160 running-routers line, not the whole descriptor list. (But
12161 clients don't use this yet.)
12162 - When people mistakenly use Tor as an http proxy, point them
12163 at the tor-doc.html rather than the INSTALL.
12164 - Remove our mostly unused -- and broken -- hex_encode()
12165 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12166 for pointing out this bug.)
12167 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12168 fewer problems with people using the wrong key.
12169 - Change the default exit policy to reject the default edonkey,
12170 kazaa, gnutella ports.
12171 - Add replace_file() to util.[ch] to handle win32's rename().
12173 o Changes from 0.0.8preX:
12174 - Fix two bugs in saving onion keys to disk when rotating, so
12175 hopefully we'll get fewer people using old onion keys.
12176 - Fix an assert error that was making SocksPolicy not work.
12177 - Be willing to expire routers that have an open dirport -- it's
12178 just the authoritative dirservers we want to not forget.
12179 - Reject tor-resolve requests for .onion addresses early, so we
12180 don't build a whole rendezvous circuit and then fail.
12181 - When you're warning a server that he's unverified, don't cry
12182 wolf unpredictably.
12183 - Fix a race condition: don't try to extend onto a connection
12184 that's still handshaking.
12185 - For servers in clique mode, require the conn to be open before
12186 you'll choose it for your path.
12187 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12188 end relay cell, etc.
12189 - Measure bandwidth capacity over the last 24 hours, not just 12
12190 - Bugfix: authoritative dirservers were making and signing a new
12191 directory for each client, rather than reusing the cached one.
12194 Changes in version 0.0.8pre2 - 2004-08-04
12195 o Changes from 0.0.7.2:
12197 - Check directory signature _before_ you decide whether you're
12198 you're running an obsolete version and should exit.
12199 - Check directory signature _before_ you parse the running-routers
12200 list to decide who's running or verified.
12201 - Bugfixes and features:
12202 - Check return value of fclose while writing to disk, so we don't
12203 end up with broken files when servers run out of disk space.
12204 - Log a warning if the user uses an unsafe socks variant, so people
12205 are more likely to learn about privoxy or socat.
12206 - Dirservers now include RFC1123-style dates in the HTTP headers,
12207 which one day we will use to better detect clock skew.
12209 o Changes from 0.0.8pre1:
12210 - Make it compile without warnings again on win32.
12211 - Log a warning if you're running an unverified server, to let you
12212 know you might want to get it verified.
12213 - Only pick a default nickname if you plan to be a server.
12216 Changes in version 0.0.8pre1 - 2004-07-23
12218 - Made our unit tests compile again on OpenBSD 3.5, and tor
12219 itself compile again on OpenBSD on a sparc64.
12220 - We were neglecting milliseconds when logging on win32, so
12221 everything appeared to happen at the beginning of each second.
12223 o Protocol changes:
12224 - 'Extend' relay cell payloads now include the digest of the
12225 intended next hop's identity key. Now we can verify that we're
12226 extending to the right router, and also extend to routers we
12227 hadn't heard of before.
12230 - Tor nodes can now act as relays (with an advertised ORPort)
12231 without being manually verified by the dirserver operators.
12232 - Uploaded descriptors of unverified routers are now accepted
12233 by the dirservers, and included in the directory.
12234 - Verified routers are listed by nickname in the running-routers
12235 list; unverified routers are listed as "$<fingerprint>".
12236 - We now use hash-of-identity-key in most places rather than
12237 nickname or addr:port, for improved security/flexibility.
12238 - To avoid Sybil attacks, paths still use only verified servers.
12239 But now we have a chance to play around with hybrid approaches.
12240 - Nodes track bandwidth usage to estimate capacity (not used yet).
12241 - ClientOnly option for nodes that never want to become servers.
12242 - Directory caching.
12243 - "AuthoritativeDir 1" option for the official dirservers.
12244 - Now other nodes (clients and servers) will cache the latest
12245 directory they've pulled down.
12246 - They can enable their DirPort to serve it to others.
12247 - Clients will pull down a directory from any node with an open
12248 DirPort, and check the signature/timestamp correctly.
12249 - Authoritative dirservers now fetch directories from other
12250 authdirservers, to stay better synced.
12251 - Running-routers list tells who's down also, along with noting
12252 if they're verified (listed by nickname) or unverified (listed
12254 - Allow dirservers to serve running-router list separately.
12255 This isn't used yet.
12256 - ORs connect-on-demand to other ORs
12257 - If you get an extend cell to an OR you're not connected to,
12258 connect, handshake, and forward the create cell.
12259 - The authoritative dirservers stay connected to everybody,
12260 and everybody stays connected to 0.0.7 servers, but otherwise
12261 clients/servers expire unused connections after 5 minutes.
12262 - When servers get a sigint, they delay 30 seconds (refusing new
12263 connections) then exit. A second sigint causes immediate exit.
12264 - File and name management:
12265 - Look for .torrc if no CONFDIR "torrc" is found.
12266 - If no datadir is defined, then choose, make, and secure ~/.tor
12268 - If torrc not found, exitpolicy reject *:*.
12269 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
12270 - If no nickname is defined, derive default from hostname.
12271 - Rename secret key files, e.g. identity.key -> secret_id_key,
12272 to discourage people from mailing their identity key to tor-ops.
12273 - Refuse to build a circuit before the directory has arrived --
12274 it won't work anyway, since you won't know the right onion keys
12276 - Try other dirservers immediately if the one you try is down. This
12277 should tolerate down dirservers better now.
12278 - Parse tor version numbers so we can do an is-newer-than check
12279 rather than an is-in-the-list check.
12280 - New socks command 'resolve', to let us shim gethostbyname()
12282 - A 'tor_resolve' script to access the socks resolve functionality.
12283 - A new socks-extensions.txt doc file to describe our
12284 interpretation and extensions to the socks protocols.
12285 - Add a ContactInfo option, which gets published in descriptor.
12286 - Publish OR uptime in descriptor (and thus in directory) too.
12287 - Write tor version at the top of each log file
12288 - New docs in the tarball:
12290 - Document that you should proxy your SSL traffic too.
12293 Changes in version 0.0.7.2 - 2004-07-07
12294 o A better fix for the 0.0.0.0 problem, that will hopefully
12295 eliminate the remaining related assertion failures.
12298 Changes in version 0.0.7.1 - 2004-07-04
12299 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
12300 since internally we use 0.0.0.0 to signify "not yet resolved".
12303 Changes in version 0.0.7 - 2004-06-07
12304 o Updated the man page to reflect the new features.
12307 Changes in version 0.0.7rc2 - 2004-06-06
12308 o Changes from 0.0.7rc1:
12309 - Make it build on Win32 again.
12310 o Changes from 0.0.6.2:
12311 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12315 Changes in version 0.0.7rc1 - 2004-06-02
12317 - On sighup, we were adding another log without removing the first
12318 one. So log messages would get duplicated n times for n sighups.
12319 - Several cases of using a connection after we'd freed it. The
12320 problem was that connections that are pending resolve are in both
12321 the pending_resolve tree, and also the circuit's resolving_streams
12322 list. When you want to remove one, you must remove it from both.
12323 - Fix a double-mark-for-close where an end cell arrived for a
12324 resolving stream, and then the resolve failed.
12325 - Check directory signatures based on name of signer, not on whom
12326 we got the directory from. This will let us cache directories more
12329 - Crank up some of our constants to handle more users.
12332 Changes in version 0.0.7pre1 - 2004-06-02
12333 o Fixes for crashes and other obnoxious bugs:
12334 - Fix an epipe bug: sometimes when directory connections failed
12335 to connect, we would give them a chance to flush before closing
12337 - When we detached from a circuit because of resolvefailed, we
12338 would immediately try the same circuit twice more, and then
12339 give up on the resolve thinking we'd tried three different
12341 - Limit the number of intro circuits we'll attempt to build for a
12342 hidden service per 15-minute period.
12343 - Check recommended-software string *early*, before actually parsing
12344 the directory. Thus we can detect an obsolete version and exit,
12345 even if the new directory format doesn't parse.
12346 o Fixes for security bugs:
12347 - Remember which nodes are dirservers when you startup, and if a
12348 random OR enables his dirport, don't automatically assume he's
12349 a trusted dirserver.
12351 - Directory connections were asking the wrong poll socket to
12352 start writing, and not asking themselves to start writing.
12353 - When we detached from a circuit because we sent a begin but
12354 didn't get a connected, we would use it again the first time;
12355 but after that we would correctly switch to a different one.
12356 - Stop warning when the first onion decrypt attempt fails; they
12357 will sometimes legitimately fail now that we rotate keys.
12358 - Override unaligned-access-ok check when $host_cpu is ia64 or
12359 arm. Apparently they allow it but the kernel whines.
12360 - Dirservers try to reconnect periodically too, in case connections
12362 - Fix some memory leaks in directory servers.
12363 - Allow backslash in Win32 filenames.
12364 - Made Tor build complain-free on FreeBSD, hopefully without
12365 breaking other BSD builds. We'll see.
12367 - Doxygen markup on all functions and global variables.
12368 - Make directory functions update routerlist, not replace it. So
12369 now directory disagreements are not so critical a problem.
12370 - Remove the upper limit on number of descriptors in a dirserver's
12371 directory (not that we were anywhere close).
12372 - Allow multiple logfiles at different severity ranges.
12373 - Allow *BindAddress to specify ":port" rather than setting *Port
12374 separately. Allow multiple instances of each BindAddress config
12375 option, so you can bind to multiple interfaces if you want.
12376 - Allow multiple exit policy lines, which are processed in order.
12377 Now we don't need that huge line with all the commas in it.
12378 - Enable accept/reject policies on SOCKS connections, so you can bind
12379 to 0.0.0.0 but still control who can use your OP.
12382 Changes in version 0.0.6.2 - 2004-05-16
12383 o Our integrity-checking digest was checking only the most recent cell,
12384 not the previous cells like we'd thought.
12385 Thanks to Stefan Mark for finding the flaw!
12388 Changes in version 0.0.6.1 - 2004-05-06
12389 o Fix two bugs in our AES counter-mode implementation (this affected
12390 onion-level stream encryption, but not TLS-level). It turns
12391 out we were doing something much more akin to a 16-character
12392 polyalphabetic cipher. Oops.
12393 Thanks to Stefan Mark for finding the flaw!
12394 o Retire moria3 as a directory server, and add tor26 as a directory
12398 Changes in version 0.0.6 - 2004-05-02
12399 [version bump only]
12402 Changes in version 0.0.6rc4 - 2004-05-01
12403 o Update the built-in dirservers list to use the new directory format
12404 o Fix a rare seg fault: if a node offering a hidden service attempts
12405 to build a circuit to Alice's rendezvous point and fails before it
12406 reaches the last hop, it retries with a different circuit, but
12408 o Handle windows socket errors correctly.
12411 Changes in version 0.0.6rc3 - 2004-04-28
12412 o Don't expire non-general excess circuits (if we had enough
12413 circuits open, we were expiring rendezvous circuits -- even
12414 when they had a stream attached. oops.)
12415 o Fetch randomness from /dev/urandom better (not via fopen/fread)
12416 o Better debugging for tls errors
12417 o Some versions of openssl have an SSL_pending function that erroneously
12418 returns bytes when there is a non-application record pending.
12419 o Set Content-Type on the directory and hidserv descriptor.
12420 o Remove IVs from cipher code, since AES-ctr has none.
12421 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
12422 o We were using an array of length zero in a few places.
12423 o win32's gethostbyname can't resolve an IP to an IP.
12424 o win32's close can't close a socket.
12427 Changes in version 0.0.6rc2 - 2004-04-26
12428 o Fix a bug where we were closing tls connections intermittently.
12429 It turns out openssl keeps its errors around -- so if an error
12430 happens, and you don't ask about it, and then another openssl
12431 operation happens and succeeds, and you ask if there was an error,
12432 it tells you about the first error. Fun fun.
12433 o Fix a bug that's been lurking since 27 may 03 (!)
12434 When passing back a destroy cell, we would use the wrong circ id.
12435 'Mostly harmless', but still worth fixing.
12436 o Since we don't support truncateds much, don't bother sending them;
12437 just close the circ.
12438 o check for <machine/limits.h> so we build on NetBSD again (I hope).
12439 o don't crash if a conn that sent a begin has suddenly lost its circuit
12440 (this was quite rare).
12443 Changes in version 0.0.6rc1 - 2004-04-25
12444 o We now rotate link (tls context) keys and onion keys.
12445 o CREATE cells now include oaep padding, so you can tell
12446 if you decrypted them correctly.
12447 o Add bandwidthburst to server descriptor.
12448 o Directories now say which dirserver signed them.
12449 o Use a tor_assert macro that logs failed assertions too.
12452 Changes in version 0.0.6pre5 - 2004-04-18
12453 o changes from 0.0.6pre4:
12454 - make tor build on broken freebsd 5.2 installs
12455 - fix a failed assert when you try an intro point, get a nack, and try
12456 a second one and it works.
12457 - when alice uses a port that the hidden service doesn't accept,
12458 it now sends back an end cell (denied by exit policy). otherwise
12459 alice would just have to wait to time out.
12460 - fix another rare bug: when we had tried all the intro
12461 points for a hidden service, we fetched the descriptor
12462 again, but we left our introcirc thinking it had already
12463 sent an intro, so it kept waiting for a response...
12464 - bugfix: when you sleep your hidden-service laptop, as soon
12465 as it wakes up it tries to upload a service descriptor, but
12466 socketpair fails for some reason (localhost not up yet?).
12467 now we simply give up on that upload, and we'll try again later.
12468 i'd still like to find the bug though.
12469 - if an intro circ waiting for an ack dies before getting one, then
12471 - we were reusing stale service descriptors and refetching usable
12475 Changes in version 0.0.6pre4 - 2004-04-14
12476 o changes from 0.0.6pre3:
12477 - when bob fails to connect to the rendezvous point, and his
12478 circ didn't fail because of the rendezvous point itself, then
12479 he retries a couple of times
12480 - we expire introduction and rendezvous circs more thoroughly
12481 (sometimes they were hanging around forever)
12482 - we expire unattached rendezvous streams that have been around
12483 too long (they were sticking around forever).
12484 - fix a measly fencepost error that was crashing everybody with
12488 Changes in version 0.0.6pre3 - 2004-04-14
12489 o changes from 0.0.6pre2:
12490 - make hup work again
12491 - fix some memory leaks for dirservers
12492 - allow more skew in rendezvous descriptor timestamps, to help
12493 handle people like blanu who don't know what time it is
12494 - normal circs are 3 hops, but some rend/intro circs are 4, if
12495 the initiator doesn't get to choose the last hop
12496 - send acks for introductions, so alice can know whether to try
12498 - bob publishes intro points more correctly
12499 o changes from 0.0.5:
12500 - fix an assert trigger that's been plaguing us since the days
12501 of 0.0.2prexx (thanks weasel!)
12502 - retry stream correctly when we fail to connect because of
12503 exit-policy-reject (should try another) or can't-resolve-address
12504 (also should try another, because dns on random internet servers
12506 - when we hup a dirserver and we've *removed* a server from the
12507 approved-routers list, now we remove that server from the
12508 in-memory directories too
12511 Changes in version 0.0.6pre2 - 2004-04-08
12512 o We fixed our base32 implementation. Now it works on all architectures.
12515 Changes in version 0.0.6pre1 - 2004-04-08
12517 - Hidden services and rendezvous points are implemented. Go to
12518 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
12519 hidden services. (This only works via a socks4a proxy such as
12520 Privoxy, and currently it's quite slow.)
12523 Changes in version 0.0.5 - 2004-03-30
12524 [version bump only]
12527 Changes in version 0.0.5rc3 - 2004-03-29
12528 o Install torrc as torrc.sample -- we no longer clobber your
12530 o Re-enable recommendedversion checking (we broke it in rc2, oops)
12531 o Add in a 'notice' log level for things the operator should hear
12532 but that aren't warnings
12535 Changes in version 0.0.5rc2 - 2004-03-29
12536 o Hold socks connection open until reply is flushed (if possible)
12537 o Make exit nodes resolve IPs to IPs immediately, rather than asking
12538 the dns farm to do it.
12539 o Fix c99 aliasing warnings in rephist.c
12540 o Don't include server descriptors that are older than 24 hours in the
12542 o Give socks 'reject' replies their whole 15s to attempt to flush,
12543 rather than seeing the 60s timeout and assuming the flush had failed.
12544 o Clean automake droppings from the cvs repository
12547 Changes in version 0.0.5rc1 - 2004-03-28
12548 o Fix mangled-state bug in directory fetching (was causing sigpipes).
12549 o Only build circuits after we've fetched the directory: clients were
12550 using only the directory servers before they'd fetched a directory.
12551 This also means longer startup time; so it goes.
12552 o Fix an assert trigger where an OP would fail to handshake, and we'd
12553 expect it to have a nickname.
12554 o Work around a tsocks bug: do a socks reject when AP connection dies
12555 early, else tsocks goes into an infinite loop.
12558 Changes in version 0.0.4 - 2004-03-26
12559 o When connecting to a dirserver or OR and the network is down,
12563 Changes in version 0.0.3 - 2004-03-26
12564 o Warn and fail if server chose a nickname with illegal characters
12565 o Port to Solaris and Sparc:
12566 - include missing header fcntl.h
12567 - have autoconf find -lsocket -lnsl automatically
12568 - deal with hardware word alignment
12569 - make uname() work (solaris has a different return convention)
12570 - switch from using signal() to sigaction()
12571 o Preliminary work on reputation system:
12572 - Keep statistics on success/fail of connect attempts; they're published
12573 by kill -USR1 currently.
12574 - Add a RunTesting option to try to learn link state by creating test
12575 circuits, even when SocksPort is off.
12576 - Remove unused open circuits when there are too many.
12579 Changes in version 0.0.2 - 2004-03-19
12580 - Include strlcpy and strlcat for safer string ops
12581 - define INADDR_NONE so we compile (but still not run) on solaris
12584 Changes in version 0.0.2pre27 - 2004-03-14
12586 - Allow internal tor networks (we were rejecting internal IPs,
12587 now we allow them if they're set explicitly).
12588 - And fix a few endian issues.
12591 Changes in version 0.0.2pre26 - 2004-03-14
12593 - If a stream times out after 15s without a connected cell, don't
12594 try that circuit again: try a new one.
12595 - Retry streams at most 4 times. Then give up.
12596 - When a dirserver gets a descriptor from an unknown router, it
12597 logs its fingerprint (so the dirserver operator can choose to
12598 accept it even without mail from the server operator).
12599 - Inform unapproved servers when we reject their descriptors.
12600 - Make tor build on Windows again. It works as a client, who knows
12602 - Clearer instructions in the torrc for how to set up a server.
12603 - Be more efficient about reading fd's when our global token bucket
12604 (used for rate limiting) becomes empty.
12606 - Stop asserting that computers always go forward in time. It's
12608 - When we sent a cell (e.g. destroy) and then marked an OR connection
12609 expired, we might close it before finishing a flush if the other
12610 side isn't reading right then.
12611 - Don't allow dirservers to start if they haven't defined
12612 RecommendedVersions
12613 - We were caching transient dns failures. Oops.
12614 - Prevent servers from publishing an internal IP as their address.
12615 - Address a strcat vulnerability in circuit.c
12618 Changes in version 0.0.2pre25 - 2004-03-04
12620 - Put the OR's IP in its router descriptor, not its fqdn. That way
12621 we'll stop being stalled by gethostbyname for nodes with flaky dns,
12624 - If the user typed in an address that didn't resolve, the server
12628 Changes in version 0.0.2pre24 - 2004-03-03
12630 - Fix an assertion failure in dns.c, where we were trying to dequeue
12631 a pending dns resolve even if it wasn't pending
12632 - Fix a spurious socks5 warning about still trying to write after the
12633 connection is finished.
12634 - Hold certain marked_for_close connections open until they're finished
12635 flushing, rather than losing bytes by closing them too early.
12636 - Correctly report the reason for ending a stream
12637 - Remove some duplicate calls to connection_mark_for_close
12638 - Put switch_id and start_daemon earlier in the boot sequence, so it
12639 will actually try to chdir() to options.DataDirectory
12640 - Make 'make test' exit(1) if a test fails; fix some unit tests
12641 - Make tor fail when you use a config option it doesn't know about,
12642 rather than warn and continue.
12643 - Make --version work
12644 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
12647 Changes in version 0.0.2pre23 - 2004-02-29
12649 - Print a statement when the first circ is finished, so the user
12650 knows it's working.
12651 - If a relay cell is unrecognized at the end of the circuit,
12652 send back a destroy. (So attacks to mutate cells are more
12654 - New config option 'excludenodes' to avoid certain nodes for circuits.
12655 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
12656 so you can collect coredumps there.
12658 - Fix a bug in tls flushing where sometimes data got wedged and
12659 didn't flush until more data got sent. Hopefully this bug was
12660 a big factor in the random delays we were seeing.
12661 - Make 'connected' cells include the resolved IP, so the client
12662 dns cache actually gets populated.
12663 - Disallow changing from ORPort=0 to ORPort>0 on hup.
12664 - When we time-out on a stream and detach from the circuit, send an
12665 end cell down it first.
12666 - Only warn about an unknown router (in exitnodes, entrynodes,
12667 excludenodes) after we've fetched a directory.
12670 Changes in version 0.0.2pre22 - 2004-02-26
12672 - Servers publish less revealing uname information in descriptors.
12673 - More memory tracking and assertions, to crash more usefully when
12675 - If the default torrc isn't there, just use some default defaults.
12676 Plus provide an internal dirservers file if they don't have one.
12677 - When the user tries to use Tor as an http proxy, give them an http
12678 501 failure explaining that we're a socks proxy.
12679 - Dump a new router.desc on hup, to help confused people who change
12680 their exit policies and then wonder why router.desc doesn't reflect
12682 - Clean up the generic tor.sh init script that we ship with.
12684 - If the exit stream is pending on the resolve, and a destroy arrives,
12685 then the stream wasn't getting removed from the pending list. I
12686 think this was the one causing recent server crashes.
12687 - Use a more robust poll on OSX 10.3, since their poll is flaky.
12688 - When it couldn't resolve any dirservers, it was useless from then on.
12689 Now it reloads the RouterFile (or default dirservers) if it has no
12691 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
12692 many users don't even *have* a /usr/local/sbin/.
12695 Changes in version 0.0.2pre21 - 2004-02-18
12697 - There's a ChangeLog file that actually reflects the changelog.
12698 - There's a 'torify' wrapper script, with an accompanying
12699 tor-tsocks.conf, that simplifies the process of using tsocks for
12700 tor. It even has a man page.
12701 - The tor binary gets installed to sbin rather than bin now.
12702 - Retry streams where the connected cell hasn't arrived in 15 seconds
12703 - Clean up exit policy handling -- get the default out of the torrc,
12704 so we can update it without forcing each server operator to fix
12706 - Allow imaps and pop3s in default exit policy
12708 - Prevent picking middleman nodes as the last node in the circuit
12711 Changes in version 0.0.2pre20 - 2004-01-30
12713 - We now have a deb package, and it's in debian unstable. Go to
12714 it, apt-getters. :)
12715 - I've split the TotalBandwidth option into BandwidthRate (how many
12716 bytes per second you want to allow, long-term) and
12717 BandwidthBurst (how many bytes you will allow at once before the cap
12718 kicks in). This better token bucket approach lets you, say, set
12719 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
12720 performance while not exceeding your monthly bandwidth quota.
12721 - Push out a tls record's worth of data once you've got it, rather
12722 than waiting until you've read everything waiting to be read. This
12723 may improve performance by pipelining better. We'll see.
12724 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
12725 from failed circuits (if they haven't been connected yet) and attach
12727 - Expire old streams that haven't managed to connect. Some day we'll
12728 have them reattach to new circuits instead.
12731 - Fix several memory leaks that were causing servers to become bloated
12733 - Fix a few very rare assert triggers. A few more remain.
12734 - Setuid to User _before_ complaining about running as root.
12737 Changes in version 0.0.2pre19 - 2004-01-07
12739 - Fix deadlock condition in dns farm. We were telling a child to die by
12740 closing the parent's file descriptor to him. But newer children were
12741 inheriting the open file descriptor from the parent, and since they
12742 weren't closing it, the socket never closed, so the child never read
12743 eof, so he never knew to exit. Similarly, dns workers were holding
12744 open other sockets, leading to all sorts of chaos.
12745 - New cleaner daemon() code for forking and backgrounding.
12746 - If you log to a file, it now prints an entry at the top of the
12747 logfile so you know it's working.
12748 - The onionskin challenge length was 30 bytes longer than necessary.
12749 - Started to patch up the spec so it's not quite so out of date.
12752 Changes in version 0.0.2pre18 - 2004-01-02
12754 - Fix endian issues with the 'integrity' field in the relay header.
12755 - Fix a potential bug where connections in state
12756 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
12759 Changes in version 0.0.2pre17 - 2003-12-30
12761 - Made --debuglogfile (or any second log file, actually) work.
12762 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
12763 adversary could force us into an infinite loop.
12766 - Each onionskin handshake now includes a hash of the computed key,
12767 to prove the server's identity and help perfect forward secrecy.
12768 - Changed cell size from 256 to 512 bytes (working toward compatibility
12770 - Changed cell length to 2 bytes, and moved it to the relay header.
12771 - Implemented end-to-end integrity checking for the payloads of
12773 - Separated streamid from 'recognized' (otherwise circuits will get
12774 messed up when we try to have streams exit from the middle). We
12775 use the integrity-checking to confirm that a cell is addressed to
12777 - Randomize the initial circid and streamid values, so an adversary who
12778 breaks into a node can't learn how many circuits or streams have
12782 Changes in version 0.0.2pre16 - 2003-12-14
12784 - Fixed a bug that made HUP trigger an assert
12785 - Fixed a bug where a circuit that immediately failed wasn't being
12786 counted as a failed circuit in counting retries.
12789 - Now we close the circuit when we get a truncated cell: otherwise we're
12790 open to an anonymity attack where a bad node in the path truncates
12791 the circuit and then we open streams at him.
12792 - Add port ranges to exit policies
12793 - Add a conservative default exit policy
12794 - Warn if you're running tor as root
12795 - on HUP, retry OR connections and close/rebind listeners
12796 - options.EntryNodes: try these nodes first when picking the first node
12797 - options.ExitNodes: if your best choices happen to include any of
12798 your preferred exit nodes, you choose among just those preferred
12800 - options.ExcludedNodes: nodes that are never picked in path building
12803 Changes in version 0.0.2pre15 - 2003-12-03
12804 o Robustness and bugfixes:
12805 - Sometimes clients would cache incorrect DNS resolves, which would
12806 really screw things up.
12807 - An OP that goes offline would slowly leak all its sockets and stop
12809 - A wide variety of bugfixes in exit node selection, exit policy
12810 handling, and processing pending streams when a new circuit is
12812 - Pick nodes for a path only from those the directory says are up
12813 - Choose randomly from all running dirservers, not always the first one
12814 - Increase allowed http header size for directory fetch.
12815 - Stop writing to stderr (if we're daemonized it will be closed).
12816 - Enable -g always, so cores will be more useful to me.
12817 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
12820 - Wrote a man page. It lists commonly used options.
12823 - Change default loglevel to warn.
12824 - Make PidFile default to null rather than littering in your CWD.
12825 - OnionRouter config option is now obsolete. Instead it just checks
12827 - Moved to a single unified torrc file for both clients and servers.
12830 Changes in version 0.0.2pre14 - 2003-11-29
12831 o Robustness and bugfixes:
12832 - Force the admin to make the DataDirectory himself
12833 - to get ownership/permissions right
12834 - so clients no longer make a DataDirectory and then never use it
12835 - fix bug where a client who was offline for 45 minutes would never
12836 pull down a directory again
12837 - fix (or at least hide really well) the dns assert bug that was
12838 causing server crashes
12839 - warnings and improved robustness wrt clockskew for certs
12840 - use the native daemon(3) to daemonize, when available
12841 - exit if bind() fails
12842 - exit if neither socksport nor orport is defined
12843 - include our own tor_timegm (Win32 doesn't have its own)
12844 - bugfix for win32 with lots of connections
12845 - fix minor bias in PRNG
12846 - make dirserver more robust to corrupt cached directory
12849 - Wrote the design document (woo)
12851 o Circuit building and exit policies:
12852 - Circuits no longer try to use nodes that the directory has told them
12854 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
12855 bitcounts (18.0.0.0/8).
12856 - Make AP connections standby for a circuit if no suitable circuit
12857 exists, rather than failing
12858 - Circuits choose exit node based on addr/port, exit policies, and
12859 which AP connections are standing by
12860 - Bump min pathlen from 2 to 3
12861 - Relay end cells have a payload to describe why the stream ended.
12862 - If the stream failed because of exit policy, try again with a new
12864 - Clients have a dns cache to remember resolved addresses.
12865 - Notice more quickly when we have no working circuits
12868 - APPort is now called SocksPort
12869 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
12871 - RecommendedVersions is now a config variable rather than
12872 hardcoded (for dirservers)
12873 - Reloads config on HUP
12874 - Usage info on -h or --help
12875 - If you set User and Group config vars, it'll setu/gid to them.
12878 Changes in version 0.0.2pre13 - 2003-10-19
12879 o General stability:
12880 - SSL_write no longer fails when it returns WANTWRITE and the number
12881 of bytes in the buf has changed by the next SSL_write call.
12882 - Fix segfault fetching directory when network is down
12883 - Fix a variety of minor memory leaks
12884 - Dirservers reload the fingerprints file on HUP, so I don't have
12885 to take down the network when I approve a new router
12886 - Default server config file has explicit Address line to specify fqdn
12889 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
12890 - Make listener connections not ever alloc bufs
12892 o Autoconf improvements:
12893 - don't clobber an external CFLAGS in ./configure
12894 - Make install now works
12895 - create var/lib/tor on make install
12896 - autocreate a tor.sh initscript to help distribs
12897 - autocreate the torrc and sample-server-torrc with correct paths
12899 o Log files and Daemonizing now work:
12900 - If --DebugLogFile is specified, log to it at -l debug
12901 - If --LogFile is specified, use it instead of commandline
12902 - If --RunAsDaemon is set, tor forks and backgrounds on startup