1 Changes in version 0.2.3.25 - 2012-11-19
2 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
3 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
5 programmer, and friend. Unstinting in his dedication to the cause of
6 freedom, he inspired and helped many of us as we began our work on
7 anonymity, and inspires us still. Please honor his memory by writing
8 software to protect people's freedoms, and by helping others to do so.
10 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
11 significantly reduced directory overhead (via microdescriptors),
12 enormous crypto performance improvements for fast relays on new
13 enough hardware, a new v3 TLS handshake protocol that can better
14 resist fingerprinting, support for protocol obfuscation plugins (aka
15 pluggable transports), better scalability for hidden services, IPv6
16 support for bridges, performance improvements like allowing clients
17 to skip the first round-trip on the circuit ("optimistic data") and
18 refilling token buckets more often, a new "stream isolation" design
19 to isolate different applications on different circuits, and many
20 stability, security, and privacy fixes.
23 - Tor tries to wipe potentially sensitive data after using it, so
24 that if some subsequent security failure exposes Tor's memory,
25 the damage will be limited. But we had a bug where the compiler
26 was eliminating these wipe operations when it decided that the
27 memory was no longer visible to a (correctly running) program,
28 hence defeating our attempt at defense in depth. We fix that
29 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
30 is unlikely to optimize away. Future versions of Tor may use
31 a less ridiculously heavy approach for this. Fixes bug 7352.
32 Reported in an article by Andrey Karpov.
35 - Fix a harmless bug when opting against publishing a relay descriptor
36 because DisableNetwork is set. Fixes bug 7464; bugfix on
40 Changes in version 0.2.4.6-alpha - 2012-11-13
41 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
42 makes our defense-in-depth memory wiping more reliable, and begins to
43 count IPv6 addresses in bridge statistics,
46 - Fix an assertion failure that could occur when closing a connection
47 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
49 - Tor tries to wipe potentially sensitive data after using it, so
50 that if some subsequent security failure exposes Tor's memory,
51 the damage will be limited. But we had a bug where the compiler
52 was eliminating these wipe operations when it decided that the
53 memory was no longer visible to a (correctly running) program,
54 hence defeating our attempt at defense in depth. We fix that
55 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
56 is unlikely to optimize away. Future versions of Tor may use
57 a less ridiculously heavy approach for this. Fixes bug 7352.
58 Reported in an article by Andrey Karpov.
61 - Add GeoIP database for IPv6 addresses. The new config option
63 - Bridge statistics now count bridge clients connecting over IPv6:
64 bridge statistics files now list "bridge-ip-versions" and
65 extra-info documents list "geoip6-db-digest". The control protocol
66 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
67 implementation by "shkoo", addressing ticket 5055.
70 - Warn when we are binding low ports when hibernation is enabled;
71 previously we had warned when we were _advertising_ low ports with
72 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
73 - Fix a harmless bug when opting against publishing a relay descriptor
74 because DisableNetwork is set. Fixes bug 7464; bugfix on
76 - Add warning message when a managed proxy dies during configuration.
77 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
78 - Fix a linking error when building tor-fw-helper without miniupnp.
79 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
80 - Check for closing an or_connection_t without going through correct
81 channel functions; emit a warning and then call
82 connection_or_close_for_error() so we don't assert as in bugs 7212
84 - Compile correctly on compilers without C99 designated initializer
85 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
86 - Avoid a possible assert that can occur when channel_send_destroy() is
87 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
88 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
89 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
90 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
91 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
93 o Code simplification and refactoring:
94 - Start using OpenBSD's implementation of queue.h, so that we don't
95 need to hand-roll our own pointer and list structures whenever we
96 need them. (We can't rely on a sys/queue.h, since some operating
97 systems don't have them, and the ones that do have them don't all
98 present the same extensions.)
101 Changes in version 0.2.4.5-alpha - 2012-10-25
102 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
103 two important security vulnerabilities that could lead to remotely
104 triggerable relay crashes, fix a major bug that was preventing clients
105 from choosing suitable exit nodes, and refactor some of our code.
107 o Major bugfixes (security, also in 0.2.3.24-rc):
108 - Fix a group of remotely triggerable assertion failures related to
109 incorrect link protocol negotiation. Found, diagnosed, and fixed
110 by "some guy from France". Fix for CVE-2012-2250; bugfix on
112 - Fix a denial of service attack by which any directory authority
113 could crash all the others, or by which a single v2 directory
114 authority could crash everybody downloading v2 directory
115 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
117 o Major bugfixes (also in 0.2.3.24-rc):
118 - When parsing exit policy summaries from microdescriptors, we had
119 previously been ignoring the last character in each one, so that
120 "accept 80,443,8080" would be treated by clients as indicating
121 a node that allows access to ports 80, 443, and 808. That would
122 lead to clients attempting connections that could never work,
123 and ignoring exit nodes that would support their connections. Now
124 clients parse these exit policy summaries correctly. Fixes bug 7192;
125 bugfix on 0.2.3.1-alpha.
127 o Minor bugfixes (also in 0.2.3.24-rc):
128 - Clients now consider the ClientRejectInternalAddresses config option
129 when using a microdescriptor consensus stanza to decide whether
130 an exit relay would allow exiting to an internal address. Fixes
131 bug 7190; bugfix on 0.2.3.1-alpha.
134 - Only disable TLS session ticket support when running as a TLS
135 server. Now clients will blend better with regular Firefox
136 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
138 o Code simplification and refactoring:
139 - Start using OpenBSD's implementation of queue.h (originally by
141 - Move the entry node code from circuitbuild.c to its own file.
142 - Move the circuit build timeout tracking code from circuitbuild.c
146 Changes in version 0.2.3.24-rc - 2012-10-25
147 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
148 could lead to remotely triggerable relay crashes, and fixes
149 a major bug that was preventing clients from choosing suitable exit
152 o Major bugfixes (security):
153 - Fix a group of remotely triggerable assertion failures related to
154 incorrect link protocol negotiation. Found, diagnosed, and fixed
155 by "some guy from France". Fix for CVE-2012-2250; bugfix on
157 - Fix a denial of service attack by which any directory authority
158 could crash all the others, or by which a single v2 directory
159 authority could crash everybody downloading v2 directory
160 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
163 - When parsing exit policy summaries from microdescriptors, we had
164 previously been ignoring the last character in each one, so that
165 "accept 80,443,8080" would be treated by clients as indicating
166 a node that allows access to ports 80, 443, and 808. That would
167 lead to clients attempting connections that could never work,
168 and ignoring exit nodes that would support their connections. Now
169 clients parse these exit policy summaries correctly. Fixes bug 7192;
170 bugfix on 0.2.3.1-alpha.
173 - Clients now consider the ClientRejectInternalAddresses config option
174 when using a microdescriptor consensus stanza to decide whether
175 an exit relay would allow exiting to an internal address. Fixes
176 bug 7190; bugfix on 0.2.3.1-alpha.
179 Changes in version 0.2.4.4-alpha - 2012-10-20
180 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
181 vulnerability introduced by a change in OpenSSL, fixes a remotely
182 triggerable assert, and adds new channel_t and circuitmux_t abstractions
183 that will make it easier to test new connection transport and cell
184 scheduling algorithms.
186 o New directory authorities (also in 0.2.3.23-rc):
187 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
188 authority. Closes ticket 5749.
190 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
191 - Disable TLS session tickets. OpenSSL's implementation was giving
192 our TLS session keys the lifetime of our TLS context objects, when
193 perfect forward secrecy would want us to discard anything that
194 could decrypt a link connection as soon as the link connection
195 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
196 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
197 - Discard extraneous renegotiation attempts once the V3 link
198 protocol has been initiated. Failure to do so left us open to
199 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
200 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
202 o Internal abstraction features:
203 - Introduce new channel_t abstraction between circuits and
204 or_connection_t to allow for implementing alternate OR-to-OR
205 transports. A channel_t is an abstract object which can either be a
206 cell-bearing channel, which is responsible for authenticating and
207 handshaking with the remote OR and transmitting cells to and from
208 it, or a listening channel, which spawns new cell-bearing channels
209 at the request of remote ORs. Implements part of ticket 6465.
210 - Also new is the channel_tls_t subclass of channel_t, adapting it
211 to the existing or_connection_t code. The V2/V3 protocol handshaking
212 code which formerly resided in command.c has been moved below the
213 channel_t abstraction layer and may be found in channeltls.c now.
214 Implements the rest of ticket 6465.
215 - Introduce new circuitmux_t storing the queue of circuits for
216 a channel; this encapsulates and abstracts the queue logic and
217 circuit selection policy, and allows the latter to be overridden
218 easily by switching out a policy object. The existing EWMA behavior
219 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
221 o Required libraries:
222 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
223 strongly recommended.
226 - Warn users who run hidden services on a Tor client with
227 UseEntryGuards disabled that their hidden services will be
228 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
229 attack which motivated Tor to support entry guards in the first
230 place). Resolves ticket 6889.
231 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
232 dhill. Resolves ticket 6982.
233 - Option OutboundBindAddress can be specified multiple times and
234 accepts IPv6 addresses. Resolves ticket 6876.
236 o Minor bugfixes (also in 0.2.3.23-rc):
237 - Don't serve or accept v2 hidden service descriptors over a
238 relay's DirPort. It's never correct to do so, and disabling it
239 might make it more annoying to exploit any bugs that turn up in the
240 descriptor-parsing code. Fixes bug 7149.
241 - Fix two cases in src/or/transports.c where we were calling
242 fmt_addr() twice in a parameter list. Bug found by David
243 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
244 - Fix memory leaks whenever we logged any message about the "path
245 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
246 - When relays refuse a "create" cell because their queue of pending
247 create cells is too big (typically because their cpu can't keep up
248 with the arrival rate), send back reason "resource limit" rather
249 than reason "internal", so network measurement scripts can get a
250 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
253 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
254 - Free some more still-in-use memory at exit, to make hunting for
255 memory leaks easier. Resolves bug 7029.
256 - When a Tor client gets a "truncated" relay cell, the first byte of
257 its payload specifies why the circuit was truncated. We were
258 ignoring this 'reason' byte when tearing down the circuit, resulting
259 in the controller not being told why the circuit closed. Now we
260 pass the reason from the truncated cell to the controller. Bugfix
261 on 0.1.2.3-alpha; fixes bug 7039.
262 - Downgrade "Failed to hand off onionskin" messages to "debug"
263 severity, since they're typically redundant with the "Your computer
264 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
265 - Make clients running with IPv6 bridges connect over IPv6 again,
266 even without setting new config options ClientUseIPv6 and
267 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
268 - Use square brackets around IPv6 addresses in numerous places
269 that needed them, including log messages, HTTPS CONNECT proxy
270 requests, TransportProxy statefile entries, and pluggable transport
271 extra-info lines. Fixes bug 7011; patch by David Fifield.
273 o Code refactoring and cleanup:
274 - Source files taken from other packages now reside in src/ext;
275 previously they were scattered around the rest of Tor.
276 - Avoid use of reserved identifiers in our C code. The C standard
277 doesn't like us declaring anything that starts with an
278 underscore, so let's knock it off before we get in trouble. Fix
279 for bug 1031; bugfix on the first Tor commit.
282 Changes in version 0.2.3.23-rc - 2012-10-20
283 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
284 vulnerability introduced by a change in OpenSSL, and fixes a variety
285 of smaller bugs in preparation for the release.
287 o New directory authorities:
288 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
289 authority. Closes ticket 5749.
291 o Major bugfixes (security/privacy):
292 - Disable TLS session tickets. OpenSSL's implementation was giving
293 our TLS session keys the lifetime of our TLS context objects, when
294 perfect forward secrecy would want us to discard anything that
295 could decrypt a link connection as soon as the link connection
296 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
297 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
298 - Discard extraneous renegotiation attempts once the V3 link
299 protocol has been initiated. Failure to do so left us open to
300 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
301 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
304 - Fix a possible crash bug when checking for deactivated circuits
305 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
306 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
308 o Minor bugfixes (on 0.2.3.x):
309 - Fix two cases in src/or/transports.c where we were calling
310 fmt_addr() twice in a parameter list. Bug found by David
311 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
312 - Convert an assert in the pathbias code to a log message. The assert
313 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
314 bugfix on 0.2.3.17-beta.
315 - Fix memory leaks whenever we logged any message about the "path
316 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
318 o Minor bugfixes (on 0.2.2.x and earlier):
319 - Don't serve or accept v2 hidden service descriptors over a relay's
320 DirPort. It's never correct to do so, and disabling it might
321 make it more annoying to exploit any bugs that turn up in the
322 descriptor-parsing code. Fixes bug 7149.
323 - When relays refuse a "create" cell because their queue of pending
324 create cells is too big (typically because their cpu can't keep up
325 with the arrival rate), send back reason "resource limit" rather
326 than reason "internal", so network measurement scripts can get a
327 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
328 - Correct file sizes when reading binary files on Cygwin, to avoid
329 a bug where Tor would fail to read its state file. Fixes bug 6844;
330 bugfix on 0.1.2.7-alpha.
331 - Avoid undefined behaviour when parsing the list of supported
332 rendezvous/introduction protocols in a hidden service descriptor.
333 Previously, Tor would have confused (as-yet-unused) protocol version
334 numbers greater than 32 with lower ones on many platforms. Fixes
335 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
337 o Documentation fixes:
338 - Clarify that hidden services are TCP only. Fixes bug 6024.
341 Changes in version 0.2.4.3-alpha - 2012-09-22
342 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
343 assertion, resumes letting relays test reachability of their DirPort,
344 and cleans up a bunch of smaller bugs.
347 - Fix an assertion failure in tor_timegm() that could be triggered
348 by a badly formatted directory object. Bug found by fuzzing with
349 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
352 - Fix a possible crash bug when checking for deactivated circuits
353 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
354 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
355 - Allow routers to detect that their own DirPorts are running. When
356 we removed support for versions_supports_begindir, we also
357 accidentally removed the mechanism we used to self-test our
358 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
359 bugfix on 0.2.4.2-alpha.
362 - Switch to a completely time-invariant approach for picking nodes
363 weighted by bandwidth. Our old approach would run through the
364 part of the loop after it had made its choice slightly slower
365 than it ran through the part of the loop before it had made its
366 choice. Addresses ticket 6538.
367 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
368 by tor2web clients allows hidden services to identity tor2web
369 clients through their repeated selection of the same rendezvous
370 and introduction point circuit endpoints (their guards). Resolves
374 - Enable Tor to read configuration, state, and key information from
375 a FIFO. Previously Tor would only read from files with a positive
376 stat.st_size. Code from meejah; fixes bug 6044.
379 - Correct file sizes when reading binary files on Cygwin, to avoid
380 a bug where Tor would fail to read its state file. Fixes bug 6844;
381 bugfix on 0.1.2.7-alpha.
382 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
383 bugfix on 0.2.0.3-alpha.
384 - When complaining about a client port on a public address, log
385 which address we're complaining about. Fixes bug 4020; bugfix on
386 0.2.3.3-alpha. Patch by Tom Fitzhenry.
387 - Convert an assert in the pathbias code to a log message. The assert
388 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
389 bugfix on 0.2.3.17-beta.
390 - Our new buildsystem was overzealous about rebuilding manpages: it
391 would rebuild them all whenever any one of them changed. Now our
392 dependency checking should be correct. Fixes bug 6843; bugfix on
394 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
395 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
396 - Correct log printout about which address family is preferred
397 when connecting to a bridge with both an IPv4 and IPv6 OR port.
398 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
400 o Minor bugfixes (code cleanliness):
401 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
402 with large values. This situation was untriggered, but nevertheless
403 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
404 - Reject consensus votes with more than 64 known-flags. We aren't even
405 close to that limit yet, and our code doesn't handle it correctly.
406 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
407 - Avoid undefined behaviour when parsing the list of supported
408 rendezvous/introduction protocols in a hidden service descriptor.
409 Previously, Tor would have confused (as-yet-unused) protocol version
410 numbers greater than 32 with lower ones on many platforms. Fixes
411 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
412 - Fix handling of rendezvous client authorization types over 8.
413 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
414 - Fix building with older versions of GCC (2.95, for one) that don't
415 like preprocessor directives inside macro arguments. Found by
416 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
417 - Switch weighted node selection rule from using a list of doubles
418 to using a list of int64_t. This change should make the process
419 slightly easier to debug and maintain. Needed to finish ticket 6538.
421 o Code simplification and refactoring:
422 - Move the generic "config" code into a new file, and have "config.c"
423 hold only torrc- and state-related code. Resolves ticket 6823.
424 - Move the core of our "choose a weighted element at random" logic
425 into its own function, and give it unit tests. Now the logic is
426 testable, and a little less fragile too.
427 - Removed the testing_since field of node_t, which hasn't been used
428 for anything since 0.2.0.9-alpha.
430 o Documentation fixes:
431 - Clarify that hidden services are TCP only. Fixes bug 6024.
432 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
436 Changes in version 0.2.3.22-rc - 2012-09-11
437 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
441 - Fix an assertion failure in tor_timegm() that could be triggered
442 by a badly formatted directory object. Bug found by fuzzing with
443 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
446 - Avoid segfault when starting up having run with an extremely old
447 version of Tor and parsing its state file. Fixes bug 6801; bugfix
451 Changes in version 0.2.2.39 - 2012-09-11
452 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
456 - Fix an assertion failure in tor_timegm() that could be triggered
457 by a badly formatted directory object. Bug found by fuzzing with
458 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
459 - Do not crash when comparing an address with port value 0 to an
460 address policy. This bug could have been used to cause a remote
461 assertion failure by or against directory authorities, or to
462 allow some applications to crash clients. Fixes bug 6690; bugfix
466 Changes in version 0.2.4.2-alpha - 2012-09-10
467 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
468 raises the default rate limiting even more, and makes the bootstrapping
469 log messages less noisy.
472 - Automatically forward the TCP ports of pluggable transport
473 proxies using tor-fw-helper if PortForwarding is enabled. Implements
477 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
478 to 1GB/1GB. The previous defaults were intended to be "basically
479 infinite", but it turns out they're now limiting our 100mbit+
480 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
481 last time we raised it).
484 - Detect when we're running with a version of OpenSSL other than the
485 one we compiled with. This has occasionally given people hard-to-
487 - Log fewer lines at level "notice" about our OpenSSL and Libevent
488 versions and capabilities when everything is going right. Resolves
490 - Directory authorities no long accept descriptors for any version of
491 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
492 These versions are insecure, unsupported, or both. Implements
496 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
497 to start with a triple-underscore so the controller won't touch it.
498 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
499 - Avoid segfault when starting up having run with an extremely old
500 version of Tor and parsing its state file. Fixes bug 6801; bugfix
502 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
503 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
504 - Don't follow the NULL pointer if microdescriptor generation fails.
505 (This does not appear to be triggerable, but it's best to be safe.)
506 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
507 - Fix mis-declared dependencies on src/common/crypto.c and
508 src/or/tor_main.c that could break out-of-tree builds under some
509 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
510 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
511 6778; bugfix on 0.2.4.1-alpha.
512 - Fix a harmless (in this case) build warning for implicitly
513 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
516 - Now that all versions before 0.2.2.x are disallowed, we no longer
517 need to work around their missing features. Thus we can remove a
518 bunch of compatibility code.
521 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
522 TCP ports to forward. In the past it only accepted two ports:
523 the ORPort and the DirPort.
526 Changes in version 0.2.4.1-alpha - 2012-09-05
527 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
528 bridgedb; lets relays use IPv6 addresses and directory authorities
529 advertise them; and switches to a cleaner build interface.
531 This is the first alpha release in a new series, so expect there to
532 be bugs. Users who would rather test out a more stable branch should
533 stay with 0.2.3.x for now.
535 o Major features (bridges):
536 - Bridges now report the pluggable transports they support to the
537 bridge authority, so it can pass the supported transports on to
538 bridgedb and/or eventually do reachability testing. Implements
541 o Major features (IPv6):
542 - Bridge authorities now accept IPv6 bridge addresses and include
543 them in network status documents. Implements ticket 5534.
544 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
545 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
546 to happen. Implements ticket 5535.
547 - All kind of relays, not just bridges, can now advertise an IPv6
548 OR port. Implements ticket 6362.
549 - Directory authorities vote on IPv6 OR ports using the new consensus
550 method 14. Implements ticket 6363.
552 o Major features (build):
553 - Switch to a nonrecursive Makefile structure. Now instead of each
554 Makefile.am invoking other Makefile.am's, there is a master
555 Makefile.am that includes the others. This change makes our build
556 process slightly more maintainable, and improves parallelism for
557 building with make -j. Original patch by Stewart Smith; various
558 fixes by Jim Meyering.
559 - Where available, we now use automake's "silent" make rules by
560 default, so that warnings are easier to spot. You can get the old
561 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
563 o Minor features (code security and spec conformance):
564 - Clear keys and key-derived material left on the stack in
565 rendservice.c and rendclient.c. Check return value of
566 crypto_pk_write_private_key_to_string() in end_service_load_keys().
567 These fixes should make us more forward-secure against cold-boot
568 attacks and the like. Fixes bug 2385.
569 - Reject EXTEND cells sent to nonexistent streams. According to the
570 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
571 we were only checking for stream IDs that were currently in use.
572 Found while hunting for more instances of bug 6271. Bugfix on
573 0.0.2pre8, which introduced incremental circuit construction.
575 o Minor features (streamlining);
576 - No longer include the "opt" prefix when generating routerinfos
577 or v2 directories: it has been needless since Tor 0.1.2. Closes
579 - Remove some now-needless code that tried to aggressively flush
580 OR connections as data was added to them. Since 0.2.0.1-alpha, our
581 cell queue logic has saved us from the failure mode that this code
582 was supposed to prevent. Removing this code will limit the number
583 of baroque control flow paths through Tor's network logic. Reported
584 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
586 o Minor features (controller):
587 - Add a "GETINFO signal/names" control port command. Implements
589 - Provide default values for all options via "GETINFO config/defaults".
590 Implements ticket 4971.
592 o Minor features (IPv6):
593 - New config option "AuthDirHasIPv6Connectivity 1" that directory
594 authorities should set if they have IPv6 connectivity and want to
595 do reachability tests for IPv6 relays. Implements feature 5974.
596 - A relay with an IPv6 OR port now sends that address in NETINFO
597 cells (in addition to its other address). Implements ticket 6364.
599 o Minor features (log messages):
600 - Omit the first heartbeat log message, because it never has anything
601 useful to say, and it clutters up the bootstrapping messages.
602 Resolves ticket 6758.
603 - Don't log about reloading the microdescriptor cache at startup. Our
604 bootstrap warnings are supposed to tell the user when there's a
605 problem, and our bootstrap notices say when there isn't. Resolves
606 ticket 6759; bugfix on 0.2.2.6-alpha.
607 - Don't log "I learned some more directory information" when we're
608 reading cached directory information. Reserve it for when new
609 directory information arrives in response to a fetch. Resolves
611 - Prevent rounding error in path bias counts when scaling
612 them down, and use the correct scale factor default. Also demote
613 some path bias related log messages down a level and make others
614 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
615 - We no longer warn so much when generating manpages from their
618 o Code simplifications and refactoring:
619 - Enhance our internal sscanf replacement so that we can eliminate
620 the last remaining uses of the system sscanf. (Though those uses
621 of sscanf were safe, sscanf itself is generally error prone, so
622 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
624 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
625 - Move last_reachable and testing_since from routerinfo_t to node_t.
626 Implements ticket 5529.
627 - Add replaycache_t structure, functions and unit tests, then refactor
628 rend_service_introduce() to be more clear to read, improve, debug,
629 and test. Resolves bug 6177.
630 - Finally remove support for malloc_good_size and malloc_usable_size.
631 We had hoped that these functions would let us eke a little more
632 memory out of our malloc implementation. Unfortunately, the only
633 implementations that provided these functions are also ones that
634 are already efficient about not overallocation: they never got us
635 more than 7 or so bytes per allocation. Removing them saves us a
636 little code complexity and a nontrivial amount of build complexity.
639 - Tor maintainers now require Automake version 1.9 or later to build
640 Tor from the Git repository. (Automake is not required when building
641 from a source distribution.)
644 Changes in version 0.2.3.21-rc - 2012-09-05
645 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
646 series. It fixes a trio of potential security bugs, fixes a bug where
647 we were leaving some of the fast relays out of the microdescriptor
648 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
649 and cleans up other smaller issues.
651 o Major bugfixes (security):
652 - Tear down the circuit if we get an unexpected SENDME cell. Clients
653 could use this trick to make their circuits receive cells faster
654 than our flow control would have allowed, or to gum up the network,
655 or possibly to do targeted memory denial-of-service attacks on
656 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
657 from July 2002, before the release of Tor 0.0.0. We had committed
658 this patch previously, but we had to revert it because of bug 6271.
659 Now that 6271 is fixed, this patch appears to work.
660 - Reject any attempt to extend to an internal address. Without
661 this fix, a router could be used to probe addresses on an internal
662 network to see whether they were accepting connections. Fixes bug
663 6710; bugfix on 0.0.8pre1.
664 - Do not crash when comparing an address with port value 0 to an
665 address policy. This bug could have been used to cause a remote
666 assertion failure by or against directory authorities, or to
667 allow some applications to crash clients. Fixes bug 6690; bugfix
671 - Remove the upper bound on microdescriptor length. We were hitting
672 the limit for routers with complex exit policies or family
673 declarations, causing clients to not use them. Fixes the first
674 piece of bug 6404; fix on 0.2.2.6-alpha.
675 - Detect "ORPort 0" as meaning, uniformly, that we're not running
676 as a relay. Previously, some of our code would treat the presence
677 of any ORPort line as meaning that we should act like a relay,
678 even though our new listener code would correctly not open any
679 ORPorts for ORPort 0. Similar bugs in other Port options are also
680 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
683 - Avoid a pair of double-free and use-after-mark bugs that can
684 occur with certain timings in canceled and re-received DNS
685 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
686 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
687 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
688 - Allow one-hop directory fetching circuits the full "circuit build
689 timeout" period, rather than just half of it, before failing them
690 and marking the relay down. This fix should help reduce cases where
691 clients declare relays (or worse, bridges) unreachable because
692 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
693 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
695 - Authorities no longer include any router in their microdescriptor
696 consensuses for which they couldn't generate or agree on a
697 microdescriptor. Fixes the second piece of bug 6404; fix on
699 - Detect and reject attempts to specify both "FooPort" and
700 "FooPort 0" in the same configuration domain. (It's still okay
701 to have a FooPort in your configuration file, and use "FooPort 0"
702 on the command line to disable it.) Fixes the second half of bug
703 6507; bugfix on 0.2.3.3-alpha.
704 - Make wildcarded addresses (that is, ones beginning with "*.") work
705 when provided via the controller's MapAddress command. Previously,
706 they were accepted, but we never actually noticed that they were
707 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
708 - Avoid crashing on a malformed state file where EntryGuardPathBias
709 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
710 - Add a (probably redundant) memory clear between iterations of
711 the router status voting loop, to prevent future coding errors
712 where data might leak between iterations of the loop. Resolves
715 o Minor bugfixes (log messages):
716 - Downgrade "set buildtimeout to low value" messages to "info"
717 severity; they were never an actual problem, there was never
718 anything reasonable to do about them, and they tended to spam logs
719 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
720 - Downgrade path-bias warning messages to "info". We'll try to get
721 them working better in 0.2.4. Add internal circuit construction
722 state to protect against the noisy warn message "Unexpectedly high
723 circuit_successes". Also add some additional rate-limited notice
724 messages to help determine the root cause of the warn. Fixes bug
725 6475. Bugfix against 0.2.3.17-beta.
726 - Move log message when unable to find a microdesc in a routerstatus
727 entry to parse time. Previously we'd spam this warning every time
728 we tried to figure out which microdescriptors to download. Fixes
729 the third piece of bug 6404; fix on 0.2.3.18-rc.
732 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
733 change when the authority is deciding whether to accept a newly
734 uploaded descriptor. Implements ticket 6423.
735 - Add missing documentation for consensus and microdesc files.
736 Resolves ticket 6732.
739 Changes in version 0.2.2.38 - 2012-08-12
740 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
741 attack that could in theory leak path information.
744 - Avoid an uninitialized memory read when reading a vote or consensus
745 document that has an unrecognized flavor name. This read could
746 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
747 - Try to leak less information about what relays a client is
748 choosing to a side-channel attacker. Previously, a Tor client would
749 stop iterating through the list of available relays as soon as it
750 had chosen one, thus finishing a little earlier when it picked
751 a router earlier in the list. If an attacker can recover this
752 timing information (nontrivial but not proven to be impossible),
753 they could learn some coarse-grained information about which relays
754 a client was picking (middle nodes in particular are likelier to
755 be affected than exits). The timing attack might be mitigated by
756 other factors (see bug 6537 for some discussion), but it's best
757 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
760 Changes in version 0.2.3.20-rc - 2012-08-05
761 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
762 series. It fixes a pair of code security bugs and a potential anonymity
763 issue, updates our RPM spec files, and cleans up other smaller issues.
766 - Avoid read-from-freed-memory and double-free bugs that could occur
767 when a DNS request fails while launching it. Fixes bug 6480;
768 bugfix on 0.2.0.1-alpha.
769 - Avoid an uninitialized memory read when reading a vote or consensus
770 document that has an unrecognized flavor name. This read could
771 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
772 - Try to leak less information about what relays a client is
773 choosing to a side-channel attacker. Previously, a Tor client would
774 stop iterating through the list of available relays as soon as it
775 had chosen one, thus finishing a little earlier when it picked
776 a router earlier in the list. If an attacker can recover this
777 timing information (nontrivial but not proven to be impossible),
778 they could learn some coarse-grained information about which relays
779 a client was picking (middle nodes in particular are likelier to
780 be affected than exits). The timing attack might be mitigated by
781 other factors (see bug 6537 for some discussion), but it's best
782 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
785 - Try to make the warning when giving an obsolete SOCKSListenAddress
786 a little more useful.
787 - Terminate active server managed proxies if Tor stops being a
788 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
789 - Provide a better error message about possible OSX Asciidoc failure
790 reasons. Fixes bug 6436.
791 - Warn when Tor is configured to use accounting in a way that can
792 link a hidden service to some other hidden service or public
793 address. Resolves ticket 6490.
796 - Check return value of fputs() when writing authority certificate
797 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
798 - Ignore ServerTransportPlugin lines when Tor is not configured as
799 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
800 - When disabling guards for having too high a proportion of failed
801 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
805 - Update our default RPM spec files to work with mock and rpmbuild
806 on RHEL/Fedora. They have an updated set of dependencies and
807 conflicts, a fix for an ancient typo when creating the "_tor"
808 user, and better instructions. Thanks to Ondrej Mikle for the
809 patch series. Fixes bug 6043.
812 - Make it possible to set the TestingTorNetwork configuration
813 option using AlternateDirAuthority and AlternateBridgeAuthority
814 as an alternative to setting DirServer. Addresses ticket 6377.
817 - Clarify the documentation for the Alternate*Authority options.
819 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
821 o Code simplification and refactoring:
822 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
823 10 lines. Also, don't nest them. Doing so in the past has
824 led to hard-to-debug code. The new style is to use the
825 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
828 Changes in version 0.2.3.19-rc - 2012-07-06
829 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
830 series. It fixes the compile on Windows, reverts to a GeoIP database
831 that isn't as broken, and fixes a flow control bug that has been around
832 since the beginning of Tor.
835 - Fix a bug handling SENDME cells on nonexistent streams that could
836 result in bizarre window values. Report and patch contributed
837 pseudonymously. Fixes part of bug 6271. This bug was introduced
838 before the first Tor release, in svn commit r152.
839 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
840 June 2012 database, Maxmind marked many Tor relays as country "A1",
841 which will cause risky behavior for clients that set EntryNodes
842 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
843 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
844 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
847 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
848 bugfix on 0.2.1.10-alpha.
851 Changes in version 0.2.3.18-rc - 2012-06-28
852 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
853 series. It fixes a few smaller bugs, but generally appears stable.
854 Please test it and let us know whether it is!
857 - Allow wildcarded mapaddress targets to be specified on the
858 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
859 - Make our linker option detection code more robust against linkers
860 such as on FreeBSD 8, where a bad combination of options completes
861 successfully but makes an unrunnable binary. Fixes bug 6173;
862 bugfix on 0.2.3.17-beta.
864 o Minor bugfixes (on 0.2.2.x and earlier):
865 - Avoid a false positive in the util/threads unit test by increasing
866 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
867 - Replace "Sending publish request" log messages with "Launching
868 upload", so that they no longer confusingly imply that we're
869 sending something to a directory we might not even be connected
870 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
871 - Make sure to set *socket_error in all error cases in
872 connection_connect(), so it can't produce a warning about
873 errno being zero from errno_to_orconn_end_reason(). Bugfix on
874 0.2.1.1-alpha; resolves ticket 6028.
875 - Downgrade "Got a certificate, but we already have it" log messages
876 from warning to info, except when we're a dirauth. Fixes bug 5238;
877 bugfix on 0.2.1.7-alpha.
878 - When checking for requested signatures on the latest consensus
879 before serving it to a client, make sure to check the right
880 consensus flavor. Bugfix on 0.2.2.6-alpha.
881 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
882 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
884 o Minor bugfixes (on 0.2.3.x):
885 - Make format_helper_exit_status() avoid unnecessary space padding
886 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
888 - Downgrade a message about cleaning the microdescriptor cache to
889 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
890 - Log a BUG message at severity INFO if we have a networkstatus with
891 a missing entry for some microdescriptor. Continues on a patch
893 - Improve the log message when a managed proxy fails to launch. Fixes
894 bug 5099; bugfix on 0.2.3.6-alpha.
895 - Don't do DNS lookups when parsing corrupted managed proxy protocol
896 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
897 - When formatting wildcarded address mappings for the controller,
898 be sure to include "*." as appropriate. Partially fixes bug 6244;
899 bugfix on 0.2.3.9-alpha.
900 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
901 Bugfix on 0.2.3.13-alpha.
902 - Stop logging messages about running with circuit timeout learning
903 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
904 - Disable a spurious warning about reading on a marked and flushing
905 connection. We shouldn't be doing that, but apparently we
906 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
907 - Fix a bug that stopped AllowDotExit from working on addresses
908 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
911 o Code simplification, refactoring, unit tests:
912 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
913 Libevent's notion of cached time when possible.
914 - Remove duplicate code for invoking getrlimit() from control.c.
915 - Add a unit test for the environment_variable_names_equal function.
918 - Document the --defaults-torrc option, and the new (in 0.2.3)
919 semantics for overriding, extending, and clearing lists of
920 options. Closes bug 4748.
923 Changes in version 0.2.3.17-beta - 2012-06-15
924 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
925 gets our TLS handshake back on track for being able to blend in with
926 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
927 with Vidalia, and otherwise continues to get us closer to a release
931 - Enable gcc and ld hardening by default. Resolves ticket 5210.
932 - Update TLS cipher list to match Firefox 8 and later. Resolves
934 - Implement the client side of proposal 198: remove support for
935 clients falsely claiming to support standard ciphersuites that
936 they can actually provide. As of modern OpenSSL versions, it's not
937 necessary to fake any standard ciphersuite, and doing so prevents
938 us from using better ciphersuites in the future, since servers
939 can't know whether an advertised ciphersuite is really supported or
940 not. Some hosts -- notably, ones with very old versions of OpenSSL
941 or where OpenSSL has been built with ECC disabled -- will stand
942 out because of this change; TBB users should not be affected.
945 - Change the default value for DynamicDHGroups (introduced in
946 0.2.3.9-alpha) to 0. This feature can make Tor relays less
947 identifiable by their use of the mod_ssl DH group, but at
948 the cost of some usability (#4721) and bridge tracing (#6087)
949 regressions. Resolves ticket 5598.
950 - Send a CRLF at the end of each STATUS_* control protocol event. This
951 bug tickled a bug in Vidalia which would make it freeze. Fixes
952 bug 6094; bugfix on 0.2.3.16-alpha.
955 - Disable writing on marked-for-close connections when they are
956 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
957 bug 5263; bugfix on 0.0.2pre13, where we first added a special
958 case for flushing marked connections.
959 - Detect SSL handshake even when the initial attempt to write the
960 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
961 - Change the AllowDotExit rules so they should actually work.
962 We now enforce AllowDotExit only immediately after receiving an
963 address via SOCKS or DNSPort: other sources are free to provide
964 .exit addresses after the resolution occurs. Fixes bug 3940;
965 bugfix on 0.2.2.1-alpha.
966 - Fix a (harmless) integer overflow in cell statistics reported by
967 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
968 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
969 right places and never depends on the consensus parameters or
970 computes adaptive timeouts when it is disabled. Fixes bug 5049;
971 bugfix on 0.2.2.14-alpha.
972 - When building Tor on Windows with -DUNICODE (not default), ensure
973 that error messages, filenames, and DNS server names are always
974 NUL-terminated when we convert them to a single-byte encoding.
975 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
976 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
977 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
978 - Fix an edge case where TestingTorNetwork is set but the authorities
979 and relays all have an uptime of zero, where the private Tor network
980 could briefly lack support for hidden services. Fixes bug 3886;
981 bugfix on 0.2.2.18-alpha.
982 - Correct the manpage's descriptions for the default values of
983 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
985 - Fix the documentation for the --hush and --quiet command line
986 options, which changed their behavior back in 0.2.3.3-alpha.
987 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
991 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
992 more information to it, so that we can track it down in case it
993 returns again. Mitigates bug 5235.
994 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
995 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
996 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
997 - Warn the user when HTTPProxy, but no other proxy type, is
998 configured. This can cause surprising behavior: it doesn't send
999 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1000 directory traffic only. Resolves ticket 4663.
1001 - Issue a notice if a guard completes less than 40% of your circuits.
1002 Threshold is configurable by torrc option PathBiasNoticeRate and
1003 consensus parameter pb_noticepct. There is additional, off-by-
1004 default code to disable guards which fail too many circuits.
1005 Addresses ticket 5458.
1006 - Update to the June 6 2012 Maxmind GeoLite Country database.
1008 o Code simplifications and refactoring:
1009 - Remove validate_pluggable_transports_config(): its warning
1010 message is now handled by connection_or_connect().
1013 Changes in version 0.2.2.37 - 2012-06-06
1014 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
1015 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1019 - Work around a bug in OpenSSL that broke renegotiation with TLS
1020 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1021 the v2 Tor connection protocol when both sides were using OpenSSL
1022 1.0.1 would fail. Resolves ticket 6033.
1023 - When waiting for a client to renegotiate, don't allow it to add
1024 any bytes to the input buffer. This fixes a potential DoS issue.
1025 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1026 - Fix an edge case where if we fetch or publish a hidden service
1027 descriptor, we might build a 4-hop circuit and then use that circuit
1028 for exiting afterwards -- even if the new last hop doesn't obey our
1029 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1032 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1033 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1036 - Tell GCC and Clang to check for any errors in format strings passed
1037 to the tor_v*(print|scan)f functions.
1040 Changes in version 0.2.3.16-alpha - 2012-06-05
1041 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
1042 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1043 currently). It also fixes a variety of smaller bugs and other cleanups
1044 that get us closer to a release candidate.
1046 o Major bugfixes (general):
1047 - Work around a bug in OpenSSL that broke renegotiation with TLS
1048 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1049 the v2 Tor connection protocol when both sides were using OpenSSL
1050 1.0.1 would fail. Resolves ticket 6033.
1051 - When waiting for a client to renegotiate, don't allow it to add
1052 any bytes to the input buffer. This fixes a potential DoS issue.
1053 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1054 - Pass correct OR address to managed proxies (like obfsproxy),
1055 even when ORListenAddress is used. Fixes bug 4865; bugfix on
1057 - The advertised platform of a router now includes only its operating
1058 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
1059 service pack level (for Windows) or its CPU architecture (for Unix).
1060 We also no longer include the "git-XYZ" tag in the version. Resolves
1063 o Major bugfixes (clients):
1064 - If we are unable to find any exit that supports our predicted ports,
1065 stop calling them predicted, so that we don't loop and build
1066 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1067 which introduced predicted ports.
1068 - Fix an edge case where if we fetch or publish a hidden service
1069 descriptor, we might build a 4-hop circuit and then use that circuit
1070 for exiting afterwards -- even if the new last hop doesn't obey our
1071 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1072 - Check at each new consensus whether our entry guards were picked
1073 long enough ago that we should rotate them. Previously, we only
1074 did this check at startup, which could lead to us holding a guard
1075 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1076 - When fetching a bridge descriptor from a bridge authority,
1077 always do so anonymously, whether we have been able to open
1078 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1079 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1080 but we'll need to wait for bug 6010 before it's actually usable.
1082 o Major bugfixes (directory authorities):
1083 - When computing weight parameters, behave more robustly in the
1084 presence of a bad bwweightscale value. Previously, the authorities
1085 would crash if they agreed on a sufficiently broken weight_scale
1086 value: now, they use a reasonable default and carry on. Partial
1087 fix for 5786; bugfix on 0.2.2.17-alpha.
1088 - Check more thoroughly to prevent a rogue authority from
1089 double-voting on any consensus directory parameter. Previously,
1090 authorities would crash in this case if the total number of
1091 votes for any parameter exceeded the number of active voters,
1092 but would let it pass otherwise. Partial fix for bug 5786; bugfix
1096 - Rate-limit log messages when asked to connect anonymously to
1097 a private address. When these hit, they tended to hit fast and
1098 often. Also, don't bother trying to connect to addresses that we
1099 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
1100 reply makes us think we have been lied to, even when the address the
1101 client tried to connect to was "localhost." Resolves ticket 2822.
1102 - Allow packagers to insert an extra string in server descriptor
1103 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
1104 Resolves the rest of ticket 2988.
1105 - Raise the threshold of server descriptors needed (75%) and exit
1106 server descriptors needed (50%) before we will declare ourselves
1107 bootstrapped. This will make clients start building circuits a
1108 little later, but makes the initially constructed circuits less
1109 skewed and less in conflict with further directory fetches. Fixes
1111 - Close any connection that sends unrecognized junk before the
1112 handshake. Solves an issue noted in bug 4369.
1113 - Improve log messages about managed transports. Resolves ticket 5070.
1114 - Tag a bridge's descriptor as "never to be sent unencrypted".
1115 This shouldn't matter, since bridges don't open non-anonymous
1116 connections to the bridge authority and don't allow unencrypted
1117 directory connections from clients, but we might as well make
1118 sure. Closes bug 5139.
1119 - Expose our view of whether we have gone dormant to the controller,
1120 via a new "GETINFO dormant" value. Torbutton and other controllers
1121 can use this to avoid doing periodic requests through Tor while
1122 it's dormant (bug 4718). Fixes bug 5954.
1123 - Tell GCC and Clang to check for any errors in format strings passed
1124 to the tor_v*(print|scan)f functions.
1125 - Update to the May 1 2012 Maxmind GeoLite Country database.
1127 o Minor bugfixes (already included in 0.2.2.36):
1128 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1129 Fixes bug 5346; bugfix on 0.0.8pre3.
1130 - Correct parsing of certain date types in parse_http_time().
1131 Without this patch, If-Modified-Since would behave
1132 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1133 Esteban Manchado Velázques.
1134 - Make our number-parsing functions always treat too-large values
1135 as an error, even when those values exceed the width of the
1136 underlying type. Previously, if the caller provided these
1137 functions with minima or maxima set to the extreme values of the
1138 underlying integer type, these functions would return those
1139 values on overflow rather than treating overflow as an error.
1140 Fixes part of bug 5786; bugfix on 0.0.9.
1141 - If we hit the error case where routerlist_insert() replaces an
1142 existing (old) server descriptor, make sure to remove that
1143 server descriptor from the old_routers list. Fix related to bug
1144 1776. Bugfix on 0.2.2.18-alpha.
1145 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1146 circuits. Fixes issue 5259.
1148 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
1149 - Prevent a null-pointer dereference when receiving a data cell
1150 for a nonexistent stream when the circuit in question has an
1151 empty deliver window. We don't believe this is triggerable,
1152 since we don't currently allow deliver windows to become empty,
1153 but the logic is tricky enough that it's better to make the code
1154 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
1155 - Fix a memory leak when trying to launch a DNS request when the
1156 network is disabled or the nameservers are unconfigurable. Fixes
1157 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
1158 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
1159 - Don't hold a Windows file handle open for every file mapping;
1160 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
1162 - Avoid O(n^2) performance characteristics when parsing a large
1163 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
1164 - Format more doubles with %f, not %lf. Patch from grarpamp to make
1165 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
1167 - Make our replacement implementation of strtok_r() compatible with
1168 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
1169 bugfix on 0.2.2.1-alpha.
1170 - Fix a NULL-pointer dereference on a badly formed
1171 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
1172 bugfix on 0.2.2.9-alpha.
1173 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1174 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1175 - Defensively refactor rend_mid_rendezvous() so that protocol
1176 violations and length checks happen in the beginning. Fixes
1178 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
1179 that IPv6 stuff will compile on MSVC, and compilation issues
1180 will be easier to track down. Fixes bug 5861.
1182 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
1183 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
1184 resource exhaustion, so that clients can adjust their load to
1185 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
1186 started using END_STREAM_REASON_RESOURCELIMIT.
1187 - Don't check for whether the address we're using for outbound
1188 connections has changed until after the outbound connection has
1189 completed. On Windows, getsockname() doesn't succeed until the
1190 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
1191 - If the configuration tries to set MyFamily on a bridge, refuse to
1192 do so, and warn about the security implications. Fixes bug 4657;
1193 bugfix on 0.2.0.3-alpha.
1194 - If the client fails to set a reasonable set of ciphersuites
1195 during its v2 handshake renegotiation, allow the renegotiation to
1196 continue nevertheless (i.e. send all the required certificates).
1197 Fixes bug 4591; bugfix on 0.2.0.20-rc.
1198 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
1199 option is set to 0 (which Vidalia version 0.2.16 now does when
1200 a SAVECONF attempt fails), perform other actions that SIGHUP
1201 usually causes (like reopening the logs). Fixes bug 5095; bugfix
1203 - If we fail to write a microdescriptor to the disk cache, do not
1204 continue replacing the old microdescriptor file. Fixes bug 2954;
1205 bugfix on 0.2.2.6-alpha.
1206 - Exit nodes don't need to fetch certificates for authorities that
1207 they don't recognize; only directory authorities, bridges,
1208 and caches need to do that. Fixes part of bug 2297; bugfix on
1210 - Correctly handle checking the permissions on the parent
1211 directory of a control socket in the root directory. Bug found
1212 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
1214 - When told to add a bridge with the same digest as a preexisting
1215 bridge but a different addr:port, change the addr:port as
1216 requested. Previously we would not notice the change. Fixes half
1217 of bug 5603; fix on 0.2.2.26-beta.
1218 - End AUTHCHALLENGE error messages (in the control protocol) with
1219 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
1221 o Minor bugfixes (on 0.2.3.x):
1222 - Turn an assertion (that the number of handshakes received as a
1223 server is not < 1) into a warning. Fixes bug 4873; bugfix on
1225 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
1226 we had reversed them when the answer was cached.) Fixes bug
1227 5723; bugfix on 0.2.3.1-alpha.
1228 - Work correctly on Linux systems with accept4 support advertised in
1229 their headers, but without accept4 support in the kernel. Fix
1230 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
1231 - When told to add a bridge with the same addr:port as a preexisting
1232 bridge but a different transport, change the transport as
1233 requested. Previously we would not notice the change. Fixes half
1234 of bug 5603; fix on 0.2.3.2-alpha.
1235 - Avoid a "double-reply" warning when replying to a SOCKS request
1236 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
1237 bugfix on 0.2.3.4-alpha.
1238 - Fix a bug where a bridge authority crashes if it has seen no
1239 directory requests when it's time to write statistics to disk.
1240 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
1242 - Don't try to open non-control listeners when DisableNetwork is set.
1243 Previously, we'd open all listeners, then immediately close them.
1244 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
1245 - Don't abort the managed proxy protocol if the managed proxy
1246 sends us an unrecognized line; ignore it instead. Fixes bug
1247 5910; bugfix on 0.2.3.9-alpha.
1248 - Fix a compile warning in crypto.c when compiling with clang 3.1.
1249 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
1250 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
1251 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
1252 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
1253 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
1254 - Resolve numerous small warnings and build issues with MSVC. Resolves
1257 o Documentation fixes:
1258 - Improve the manual's documentation for the NT Service command-line
1259 options. Addresses ticket 3964.
1260 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
1261 - Document the changes to the ORPort and DirPort options, and the
1262 fact that {OR/Dir}ListenAddress is now unnecessary (and
1263 therefore deprecated). Resolves ticket 5597.
1266 - Remove the torrc.bridge file: we don't use it for anything, and
1267 it had become badly desynchronized from torrc.sample. Resolves
1271 Changes in version 0.2.2.36 - 2012-05-24
1272 Tor 0.2.2.36 updates the addresses for two of the eight directory
1273 authorities, fixes some potential anonymity and security issues,
1274 and fixes several crash bugs.
1276 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
1277 known flaws, and nobody should be using them. You should upgrade. If
1278 you're using a Linux or BSD and its packages are obsolete, stop using
1279 those packages and upgrade anyway.
1281 o Directory authority changes:
1282 - Change IP address for maatuska (v3 directory authority).
1283 - Change IP address for ides (v3 directory authority), and rename
1287 - When building or running with any version of OpenSSL earlier
1288 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1289 versions have a bug (CVE-2011-4576) in which their block cipher
1290 padding includes uninitialized data, potentially leaking sensitive
1291 information to any peer with whom they make a SSLv3 connection. Tor
1292 does not use SSL v3 by default, but a hostile client or server
1293 could force an SSLv3 connection in order to gain information that
1294 they shouldn't have been able to get. The best solution here is to
1295 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1296 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1297 to make sure that the bug can't happen.
1298 - Never use a bridge or a controller-supplied node as an exit, even
1299 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1300 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1301 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1302 - Only build circuits if we have a sufficient threshold of the total
1303 descriptors that are marked in the consensus with the "Exit"
1304 flag. This mitigates an attack proposed by wanoskarnet, in which
1305 all of a client's bridges collude to restrict the exit nodes that
1306 the client knows about. Fixes bug 5343.
1307 - Provide controllers with a safer way to implement the cookie
1308 authentication mechanism. With the old method, if another locally
1309 running program could convince a controller that it was the Tor
1310 process, then that program could trick the controller into telling
1311 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1312 authentication method uses a challenge-response approach to prevent
1313 this attack. Fixes bug 5185; implements proposal 193.
1316 - Avoid logging uninitialized data when unable to decode a hidden
1317 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1318 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1319 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1321 - Fix builds when the path to sed, openssl, or sha1sum contains
1322 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1324 - Correct our replacements for the timeradd() and timersub() functions
1325 on platforms that lack them (for example, Windows). The timersub()
1326 function is used when expiring circuits, while timeradd() is
1327 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1328 bugfix on 0.2.2.24-alpha.
1329 - Fix the SOCKET_OK test that we use to tell when socket
1330 creation fails so that it works on Win64. Fixes part of bug 4533;
1331 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1334 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1335 Fixes bug 5346; bugfix on 0.0.8pre3.
1336 - Make our number-parsing functions always treat too-large values
1337 as an error, even when those values exceed the width of the
1338 underlying type. Previously, if the caller provided these
1339 functions with minima or maxima set to the extreme values of the
1340 underlying integer type, these functions would return those
1341 values on overflow rather than treating overflow as an error.
1342 Fixes part of bug 5786; bugfix on 0.0.9.
1343 - Older Linux kernels erroneously respond to strange nmap behavior
1344 by having accept() return successfully with a zero-length
1345 socket. When this happens, just close the connection. Previously,
1346 we would try harder to learn the remote address: but there was
1347 no such remote address to learn, and our method for trying to
1348 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1349 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1350 - Correct parsing of certain date types in parse_http_time().
1351 Without this patch, If-Modified-Since would behave
1352 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1353 Esteban Manchado Velázques.
1354 - Change the BridgePassword feature (part of the "bridge community"
1355 design, which is not yet implemented) to use a time-independent
1356 comparison. The old behavior might have allowed an adversary
1357 to use timing to guess the BridgePassword value. Fixes bug 5543;
1358 bugfix on 0.2.0.14-alpha.
1359 - Detect and reject certain misformed escape sequences in
1360 configuration values. Previously, these values would cause us
1361 to crash if received in a torrc file or over an authenticated
1362 control port. Bug found by Esteban Manchado Velázquez, and
1363 independently by Robert Connolly from Matta Consulting who further
1364 noted that it allows a post-authentication heap overflow. Patch
1365 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1366 bugfix on 0.2.0.16-alpha.
1367 - Fix a compile warning when using the --enable-openbsd-malloc
1368 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1369 - During configure, detect when we're building with clang version
1370 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1371 CFLAGS. clang doesn't support them yet.
1372 - When sending an HTTP/1.1 proxy request, include a Host header.
1373 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1374 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
1375 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
1376 - If we hit the error case where routerlist_insert() replaces an
1377 existing (old) server descriptor, make sure to remove that
1378 server descriptor from the old_routers list. Fix related to bug
1379 1776. Bugfix on 0.2.2.18-alpha.
1381 o Minor bugfixes (documentation and log messages):
1382 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1383 Fixes bug 4856; bugfix on Tor 0.0.6.
1384 - Update "ClientOnly" man page entry to explain that there isn't
1385 really any point to messing with it. Resolves ticket 5005.
1386 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1387 directory authority option (introduced in Tor 0.2.2.34).
1388 - Downgrade the "We're missing a certificate" message from notice
1389 to info: people kept mistaking it for a real problem, whereas it
1390 is seldom the problem even when we are failing to bootstrap. Fixes
1391 bug 5067; bugfix on 0.2.0.10-alpha.
1392 - Correctly spell "connect" in a log message on failure to create a
1393 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
1394 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1395 circuits. Fixes issue 5259.
1398 - Directory authorities now reject versions of Tor older than
1399 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1400 inclusive. These versions accounted for only a small fraction of
1401 the Tor network, and have numerous known security issues. Resolves
1403 - Update to the May 1 2012 Maxmind GeoLite Country database.
1406 - When sending or relaying a RELAY_EARLY cell, we used to convert
1407 it to a RELAY cell if the connection was using the v1 link
1408 protocol. This was a workaround for older versions of Tor, which
1409 didn't handle RELAY_EARLY cells properly. Now that all supported
1410 versions can handle RELAY_EARLY cells, and now that we're enforcing
1411 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1412 remove this workaround. Addresses bug 4786.
1415 Changes in version 0.2.3.15-alpha - 2012-04-30
1416 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
1417 the development branch build on Windows again.
1419 o Minor bugfixes (on 0.2.2.x and earlier):
1420 - Make sure that there are no unhandled pending TLS errors before
1421 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
1422 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
1423 Bugfix on 0.1.0.5-rc; fixes bug 4528.
1424 - Fix an assert that directory authorities could trigger on sighup
1425 during some configuration state transitions. We now don't treat
1426 it as a fatal error when the new descriptor we just generated in
1427 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1428 - After we pick a directory mirror, we would refuse to use it if
1429 it's in our ExcludeExitNodes list, resulting in mysterious failures
1430 to bootstrap for people who just wanted to avoid exiting from
1431 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
1432 - When building with --enable-static-tor on OpenBSD, do not
1433 erroneously attempt to link -lrt. Fixes bug 5103.
1435 o Minor bugfixes (on 0.2.3.x):
1436 - When Tor is built with kernel headers from a recent (last few
1437 years) Linux kernel, do not fail to run on older (pre-2.6.28
1438 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
1439 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
1441 - Fix compilation with miniupnpc version 1.6; patch from
1442 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
1443 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
1444 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
1445 - Fix compilation on platforms without unistd.h, or where environ
1446 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
1449 - Directory authorities are now a little more lenient at accepting
1450 older router descriptors, or newer router descriptors that don't
1451 make big changes. This should help ameliorate past and future
1452 issues where routers think they have uploaded valid descriptors,
1453 but the authorities don't think so. Fix for ticket 2479.
1454 - Make the code that clients use to detect an address change be
1455 IPv6-aware, so that it won't fill clients' logs with error
1456 messages when trying to get the IPv4 address of an IPv6
1457 connection. Implements ticket 5537.
1460 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
1461 authorities needed to use it for a while to keep the network working
1462 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
1463 that was six months ago. As of now, it should no longer be needed
1467 Changes in version 0.2.3.14-alpha - 2012-04-23
1468 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
1469 candidate. It also dramatically speeds up AES: fast relays should
1470 consider switching to the newer OpenSSL library.
1472 o Directory authority changes:
1473 - Change IP address for ides (v3 directory authority), and rename
1477 - Avoid logging uninitialized data when unable to decode a hidden
1478 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1479 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1480 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1482 - If authorities are unable to get a v2 consensus document from other
1483 directory authorities, they no longer fall back to fetching
1484 them from regular directory caches. Fixes bug 5635; bugfix on
1485 0.2.2.26-beta, where routers stopped downloading v2 consensus
1487 - When we start a Tor client with a normal consensus already cached,
1488 be willing to download a microdescriptor consensus. Fixes bug 4011;
1489 fix on 0.2.3.1-alpha.
1491 o Major features (performance):
1492 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
1493 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
1494 vectorized AES implementations as appropriate. These can be much,
1495 much faster than other AES implementations.
1497 o Minor bugfixes (0.2.2.x and earlier):
1498 - Don't launch more than 10 service-side introduction-point circuits
1499 for a hidden service in five minutes. Previously, we would consider
1500 launching more introduction-point circuits if at least one second
1501 had passed without any introduction-point circuits failing. Fixes
1502 bug 4607; bugfix on 0.0.7pre1.
1503 - Change the BridgePassword feature (part of the "bridge community"
1504 design, which is not yet implemented) to use a time-independent
1505 comparison. The old behavior might have allowed an adversary
1506 to use timing to guess the BridgePassword value. Fixes bug 5543;
1507 bugfix on 0.2.0.14-alpha.
1508 - Enforce correct return behavior of tor_vsscanf() when the '%%'
1509 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
1510 - When sending an HTTP/1.1 proxy request, include a Host header.
1511 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1512 - Don't log that we have "decided to publish new relay descriptor"
1513 unless we are actually publishing a descriptor. Fixes bug 3942;
1514 bugfix on 0.2.2.28-beta.
1516 o Minor bugfixes (0.2.3.x):
1517 - Fix a bug where a bridge authority crashes (on a failed assert)
1518 if it has seen no directory requests when it's time to write
1519 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
1520 - Fix bug stomping on ORPort option NoListen and ignoring option
1521 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
1522 - In the testsuite, provide a large enough buffer in the tor_sscanf
1523 unit test. Otherwise we'd overrun that buffer and crash during
1524 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
1526 - Make sure we create the keys directory if it doesn't exist and we're
1527 about to store the dynamic Diffie-Hellman parameters. Fixes bug
1528 5572; bugfix on 0.2.3.13-alpha.
1529 - Fix a small memory leak when trying to decode incorrect base16
1530 authenticator during SAFECOOKIE authentication. Found by
1531 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
1534 - Add more information to a log statement that might help track down
1535 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
1536 non-IP address" messages (or any Bug messages, for that matter!),
1537 please let us know about it.
1538 - Relays now understand an IPv6 address when they get one from a
1539 directory server. Resolves ticket 4875.
1540 - Resolve IPv6 addresses in bridge and entry statistics to country
1541 code "??" which means we at least count them. Resolves ticket 5053;
1542 improves on 0.2.3.9-alpha.
1543 - Update to the April 3 2012 Maxmind GeoLite Country database.
1544 - Begin a doc/state-contents.txt file to explain the contents of
1545 the Tor state file. Fixes bug 2987.
1547 o Default torrc changes:
1548 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1549 port on 9050 by default anyway, so this should not change anything
1551 - Stop mentioning the deprecated *ListenAddress options in
1552 torrc.sample. Fixes bug 5438.
1553 - Document unit of bandwidth related options in sample torrc.
1557 - The "torify" script no longer supports the "tsocks" socksifier
1558 tool, since tsocks doesn't support DNS and UDP right for Tor.
1559 Everyone should be using torsocks instead. Fixes bugs 3530 and
1560 5180. Based on a patch by "ugh".
1563 - Change the symmetric cipher interface so that creating and
1564 initializing a stream cipher are no longer separate functions.
1565 - Remove all internal support for unpadded RSA. We never used it, and
1566 it would be a bad idea to start.
1569 Changes in version 0.2.3.13-alpha - 2012-03-26
1570 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
1571 in managed pluggable transports, as well as providing other cleanups
1572 that get us closer to a release candidate.
1574 o Directory authority changes:
1575 - Change IP address for maatuska (v3 directory authority).
1578 - Provide controllers with a safer way to implement the cookie
1579 authentication mechanism. With the old method, if another locally
1580 running program could convince a controller that it was the Tor
1581 process, then that program could trick the controller into telling
1582 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1583 authentication method uses a challenge-response approach to prevent
1584 this attack. Fixes bug 5185, implements proposal 193.
1585 - Never use a bridge or a controller-supplied node as an exit, even
1586 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1587 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1588 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1589 - Only build circuits if we have a sufficient threshold of the total
1590 descriptors that are marked in the consensus with the "Exit"
1591 flag. This mitigates an attack proposed by wanoskarnet, in which
1592 all of a client's bridges collude to restrict the exit nodes that
1593 the client knows about. Fixes bug 5343.
1595 o Major bugfixes (on Tor 0.2.3.x):
1596 - Avoid an assert when managed proxies like obfsproxy are configured,
1597 and we receive HUP signals or setconf attempts too rapidly. This
1598 situation happens most commonly when Vidalia tries to attach to
1599 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
1600 bugfix on 0.2.3.6-alpha.
1601 - Fix a relay-side pluggable transports bug where managed proxies were
1602 unreachable from the Internet, because Tor asked them to bind on
1603 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
1604 - Stop discarding command-line arguments when TestingTorNetwork
1605 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
1606 0.2.3.9-alpha, where task 4552 added support for two layers of
1608 - Resume allowing the unit tests to run in gdb. This was accidentally
1609 made impossible when the DisableDebuggerAttachment option was
1610 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
1611 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
1612 0.2.3.11-alpha. Reported by Anthony G. Basile.
1614 o Minor bugfixes (on 0.2.2.x and earlier):
1615 - Ensure we don't cannibalize circuits that are longer than three hops
1616 already, so we don't end up making circuits with 5 or more
1617 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
1618 0.1.0.1-rc which introduced cannibalization.
1619 - Detect and reject certain misformed escape sequences in
1620 configuration values. Previously, these values would cause us
1621 to crash if received in a torrc file or over an authenticated
1622 control port. Bug found by Esteban Manchado Velázquez, and
1623 independently by Robert Connolly from Matta Consulting who further
1624 noted that it allows a post-authentication heap overflow. Patch
1625 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1626 bugfix on 0.2.0.16-alpha.
1627 - Fix a compile warning when using the --enable-openbsd-malloc
1628 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1629 - Directory caches no longer refuse to clean out descriptors because
1630 of missing v2 networkstatus documents, unless they're configured
1631 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
1632 0.2.2.26-beta. Patch by Daniel Bryg.
1633 - Update to the latest version of the tinytest unit testing framework.
1634 This includes a couple of bugfixes that can be relevant for
1635 running forked unit tests on Windows, and removes all reserved
1638 o Minor bugfixes (on 0.2.3.x):
1639 - On a failed pipe() call, don't leak file descriptors. Fixes bug
1640 4296; bugfix on 0.2.3.1-alpha.
1641 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
1642 until after we have received a CERTS cell. Fixes bug 4361; bugfix
1643 on 0.2.3.6-alpha. Patch by "frosty".
1644 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
1645 option, so that the IP stack doesn't decide to use it for IPv4
1646 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
1647 - Ensure that variables set in Tor's environment cannot override
1648 environment variables that Tor passes to a managed
1649 pluggable-transport proxy. Previously, Tor would pass every
1650 variable in its environment to managed proxies along with the new
1651 ones, in such a way that on many operating systems, the inherited
1652 environment variables would override those which Tor tried to
1653 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
1654 bugfix on 0.2.3.9-alpha for Windows.
1657 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1658 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1659 - Update to the March 6 2012 Maxmind GeoLite Country database.
1662 Changes in version 0.2.3.12-alpha - 2012-02-13
1663 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
1664 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
1665 when Tor is configured to use a pluggable transport like obfsproxy.
1668 - Fix builds when the path to sed, openssl, or sha1sum contains
1669 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1671 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1672 connections. This change should allow busy exit relays to stop
1673 running out of available sockets as quickly. Fixes bug 4950;
1674 bugfix on 0.2.2.26-beta.
1675 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
1676 would ask the bridge for microdescriptors, which are only supported
1677 in 0.2.3.x, and then fail to bootstrap when it didn't get the
1678 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
1679 - Properly set up obfsproxy's environment when in managed mode. The
1680 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
1681 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
1682 5076 and 5082; bugfix on 0.2.3.6-alpha.
1685 - Use the dead_strip option when building Tor on OS X. This reduces
1686 binary size by almost 19% when linking openssl and libevent
1687 statically, which we do for Tor Browser Bundle.
1688 - Fix broken URLs in the sample torrc file, and tell readers about
1689 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1690 PublishServerDescriptor options. Addresses bug 4652.
1691 - Update to the February 7 2012 Maxmind GeoLite Country database.
1694 - Downgrade the "We're missing a certificate" message from notice
1695 to info: people kept mistaking it for a real problem, whereas it
1696 is seldom the problem even when we are failing to bootstrap. Fixes
1697 bug 5067; bugfix on 0.2.0.10-alpha.
1698 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
1699 managed pluggable transport server proxy's environment.
1700 Previously, we would put it there, even though Tor doesn't
1701 implement an 'extended server port' yet, and even though Tor
1702 almost certainly isn't listening at that address. For now, we set
1703 it to an empty string to avoid crashing older obfsproxies. Bugfix
1705 - Log the heartbeat message every HeartbeatPeriod seconds, not every
1706 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
1707 0.2.3.1-alpha. Bug reported by Scott Bennett.
1708 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
1709 bugfix on 0.2.3.11-alpha.
1710 - Update "ClientOnly" man page entry to explain that there isn't
1711 really any point to messing with it. Resolves ticket 5005.
1712 - Use the correct CVE number for CVE-2011-4576 in our comments and
1713 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
1716 o Code simplifications and refactoring:
1717 - Use the _WIN32 macro throughout our code to detect Windows.
1718 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1722 Changes in version 0.2.3.11-alpha - 2012-01-22
1723 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
1724 the last step of the plan to limit maximum circuit length, includes
1725 a wide variety of hidden service performance and correctness fixes,
1726 works around an OpenSSL security flaw if your distro is too stubborn
1727 to upgrade, and fixes a bunch of smaller issues.
1730 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1731 part of "Proposal 110: Avoiding infinite length circuits" by
1732 refusing all circuit-extend requests that do not use a relay_early
1733 cell. This change helps Tor resist a class of denial-of-service
1734 attacks by limiting the maximum circuit length.
1735 - Adjust the number of introduction points that a hidden service
1736 will try to maintain based on how long its introduction points
1737 remain in use and how many introductions they handle. Fixes
1739 - Try to use system facilities for enumerating local interface
1740 addresses, before falling back to our old approach (which was
1741 binding a UDP socket, and calling getsockname() on it). That
1742 approach was scaring OS X users whose draconian firewall
1743 software warned about binding to UDP sockets, regardless of
1744 whether packets were sent. Now we try to use getifaddrs(),
1745 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1746 system supports. Resolves ticket 1827.
1748 o Major security workaround:
1749 - When building or running with any version of OpenSSL earlier
1750 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1751 versions have a bug (CVE-2011-4576) in which their block cipher
1752 padding includes uninitialized data, potentially leaking sensitive
1753 information to any peer with whom they make a SSLv3 connection. Tor
1754 does not use SSL v3 by default, but a hostile client or server
1755 could force an SSLv3 connection in order to gain information that
1756 they shouldn't have been able to get. The best solution here is to
1757 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1758 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1759 to make sure that the bug can't happen.
1762 - Fix the SOCKET_OK test that we use to tell when socket
1763 creation fails so that it works on Win64. Fixes part of bug 4533;
1764 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1765 - Correct our replacements for the timeradd() and timersub() functions
1766 on platforms that lack them (for example, Windows). The timersub()
1767 function is used when expiring circuits, while timeradd() is
1768 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1769 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
1770 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
1771 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
1772 bug at runtime, not compile time, because some distributions hack
1773 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
1774 on 0.2.3.9-alpha. Found by Pascal.
1776 o Minor features (controller):
1777 - Use absolute path names when reporting the torrc filename in the
1778 control protocol, so a controller can more easily find the torrc
1779 file. Resolves bug 1101.
1780 - Extend the control protocol to report flags that control a circuit's
1781 path selection in CIRC events and in replies to 'GETINFO
1782 circuit-status'. Implements part of ticket 2411.
1783 - Extend the control protocol to report the hidden service address
1784 and current state of a hidden-service-related circuit in CIRC
1785 events and in replies to 'GETINFO circuit-status'. Implements part
1787 - When reporting the path to the cookie file to the controller,
1788 give an absolute path. Resolves ticket 4881.
1789 - Allow controllers to request an event notification whenever a
1790 circuit is cannibalized or its purpose is changed. Implements
1791 part of ticket 3457.
1792 - Include the creation time of a circuit in CIRC and CIRC2
1793 control-port events and the list produced by the 'GETINFO
1794 circuit-status' control-port command.
1796 o Minor features (directory authorities):
1797 - Directory authorities now reject versions of Tor older than
1798 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1799 inclusive. These versions accounted for only a small fraction of
1800 the Tor network, and have numerous known security issues. Resolves
1802 - Authority operators can now vote for all relays in a given
1803 set of countries to be BadDir/BadExit/Invalid/Rejected.
1804 - Provide two consensus parameters (FastFlagMinThreshold and
1805 FastFlagMaxThreshold) to control the range of allowable bandwidths
1806 for the Fast directory flag. These allow authorities to run
1807 experiments on appropriate requirements for being a "Fast" node.
1808 The AuthDirFastGuarantee config value still applies. Implements
1810 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1811 directory authority option (introduced in Tor 0.2.2.34).
1813 o Minor features (other):
1814 - Don't disable the DirPort when we cannot exceed our AccountingMax
1815 limit during this interval because the effective bandwidthrate is
1816 low enough. This is useful in a situation where AccountMax is only
1817 used as an additional safeguard or to provide statistics.
1818 - Prepend an informative header to generated dynamic_dh_params files.
1819 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1820 EntryNodes will have no effect. Resolves issue 2571.
1821 - Log more useful messages when we fail to disable debugger
1823 - Log which authority we're missing votes from when we go to fetch
1824 them from the other auths.
1825 - Log (at debug level) whenever a circuit's purpose is changed.
1826 - Add missing documentation for the MaxClientCircuitsPending,
1827 UseMicrodescriptors, UserspaceIOCPBuffers, and
1828 _UseFilteringSSLBufferevents options, all introduced during
1830 - Update to the January 3 2012 Maxmind GeoLite Country database.
1832 o Minor bugfixes (hidden services):
1833 - Don't close hidden service client circuits which have almost
1834 finished connecting to their destination when they reach
1835 the normal circuit-build timeout. Previously, we would close
1836 introduction circuits which are waiting for an acknowledgement
1837 from the introduction point, and rendezvous circuits which have
1838 been specified in an INTRODUCE1 cell sent to a hidden service,
1839 after the normal CBT. Now, we mark them as 'timed out', and launch
1840 another rendezvous attempt in parallel. This behavior change can
1841 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1842 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1843 - Don't close hidden-service-side rendezvous circuits when they
1844 reach the normal circuit-build timeout. This behaviour change can
1845 be disabled using the new
1846 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1847 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1848 - Make sure we never mark the wrong rendezvous circuit as having
1849 had its introduction cell acknowleged by the introduction-point
1850 relay. Previously, when we received an INTRODUCE_ACK cell on a
1851 client-side hidden-service introduction circuit, we might have
1852 marked a rendezvous circuit other than the one we specified in
1853 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
1854 a warning message and interfered with the hidden service
1855 connection-establishment process. Fixes bug 4759; bugfix on
1856 0.2.3.3-alpha, when we added the stream-isolation feature which
1857 might cause Tor to open multiple rendezvous circuits for the same
1859 - Don't trigger an assertion failure when we mark a new client-side
1860 hidden-service introduction circuit for close during the process
1861 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
1864 o Minor bugfixes (log messages):
1865 - Correctly spell "connect" in a log message on failure to create a
1866 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
1868 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1869 Fixes bug 4856; bugfix on Tor 0.0.6.
1870 - Fix the log message describing how we work around discovering
1871 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1872 4837; bugfix on 0.2.2.9-alpha.
1873 - When logging about a disallowed .exit name, do not also call it
1874 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1876 o Minor bugfixes (build fixes):
1877 - During configure, detect when we're building with clang version
1878 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1879 CFLAGS. clang doesn't support them yet.
1880 - During configure, search for library containing cos function as
1881 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1882 against libm was hard-coded before. Fixes the first part of bug
1883 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1885 - Detect attempts to build Tor on (as yet hypothetical) versions
1886 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1887 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1888 - Preprocessor directives should not be put inside the arguments
1889 of a macro. This would break compilation with GCC releases prior
1890 to version 3.3. We would never recommend such an old GCC version,
1891 but it is apparently required for binary compatibility on some
1892 platforms (namely, certain builds of Haiku). Fixes the other part
1893 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
1896 o Minor bugfixes (other):
1897 - Older Linux kernels erroneously respond to strange nmap behavior
1898 by having accept() return successfully with a zero-length
1899 socket. When this happens, just close the connection. Previously,
1900 we would try harder to learn the remote address: but there was
1901 no such remote address to learn, and our method for trying to
1902 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1903 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1904 - Fix null-pointer access that could occur if TLS allocation failed.
1905 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
1906 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
1907 accidentally been reverted.
1908 - Fix our implementation of crypto_random_hostname() so it can't
1909 overflow on ridiculously large inputs. (No Tor version has ever
1910 provided this kind of bad inputs, but let's be correct in depth.)
1911 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1912 - Find more places in the code that should have been testing for
1913 invalid sockets using the SOCKET_OK macro. Required for a fix
1914 for bug 4533. Bugfix on 0.2.2.28-beta.
1915 - Fix an assertion failure when, while running with bufferevents, a
1916 connection finishes connecting after it is marked for close, but
1917 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
1918 - test_util_spawn_background_ok() hardcoded the expected value
1919 for ENOENT to 2. This isn't portable as error numbers are
1920 platform specific, and particularly the hurd has ENOENT at
1921 0x40000002. Construct expected string at runtime, using the correct
1922 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
1923 - Reject attempts to disable DisableDebuggerAttachment while Tor is
1924 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
1925 - Use an appropriate-width type for sockets in tor-fw-helper on
1926 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1929 - When sending or relaying a RELAY_EARLY cell, we used to convert
1930 it to a RELAY cell if the connection was using the v1 link
1931 protocol. This was a workaround for older versions of Tor, which
1932 didn't handle RELAY_EARLY cells properly. Now that all supported
1933 versions can handle RELAY_EARLY cells, and now that we're enforcing
1934 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1935 remove this workaround. Addresses bug 4786.
1937 o Code simplifications and refactoring:
1938 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1939 own homebrewed ssl_state_to_string() replacement. Patch from
1940 Emile Snyder. Fixes bug 4653.
1941 - Use macros to indicate OpenSSL versions, so we don't need to worry
1942 about accidental hexadecimal bit shifts.
1943 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1945 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1946 - Use the smartlist_add_asprintf() alias more consistently.
1947 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1948 invalid value, rather than just -1.
1949 - Rename a handful of old identifiers, mostly related to crypto
1950 structures and crypto functions. By convention, our "create an
1951 object" functions are called "type_new()", our "free an object"
1952 functions are called "type_free()", and our types indicate that
1953 they are types only with a final "_t". But a handful of older
1954 types and functions broke these rules, with function names like
1955 "type_create" or "subsystem_op_type", or with type names like
1959 Changes in version 0.2.3.10-alpha - 2011-12-16
1960 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1961 Tor's buffers code. Absolutely everybody should upgrade.
1963 The bug relied on an incorrect calculation when making data continuous
1964 in one of our IO buffers, if the first chunk of the buffer was
1965 misaligned by just the wrong amount. The miscalculation would allow an
1966 attacker to overflow a piece of heap-allocated memory. To mount this
1967 attack, the attacker would need to either open a SOCKS connection to
1968 Tor's SocksPort (usually restricted to localhost), or target a Tor
1969 instance configured to make its connections through a SOCKS proxy
1970 (which Tor does not do by default).
1972 Good security practice requires that all heap-overflow bugs should be
1973 presumed to be exploitable until proven otherwise, so we are treating
1974 this as a potential code execution attack. Please upgrade immediately!
1975 This bug does not affect bufferevents-based builds of Tor. Special
1976 thanks to "Vektor" for reporting this issue to us!
1978 This release also contains a few minor bugfixes for issues discovered
1982 - Fix a heap overflow bug that could occur when trying to pull
1983 data into the first chunk of a buffer, when that chunk had
1984 already had some data drained from it. Fixes CVE-2011-2778;
1985 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1988 - If we can't attach streams to a rendezvous circuit when we
1989 finish connecting to a hidden service, clear the rendezvous
1990 circuit's stream-isolation state and try to attach streams
1991 again. Previously, we cleared rendezvous circuits' isolation
1992 state either too early (if they were freshly built) or not at all
1993 (if they had been built earlier and were cannibalized). Bugfix on
1994 0.2.3.3-alpha; fixes bug 4655.
1995 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1996 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1997 - Fix an assertion failure when a relay with accounting enabled
1998 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
2001 - Update to the December 6 2011 Maxmind GeoLite Country database.
2004 Changes in version 0.2.2.35 - 2011-12-16
2005 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2006 buffers code. Absolutely everybody should upgrade.
2008 The bug relied on an incorrect calculation when making data continuous
2009 in one of our IO buffers, if the first chunk of the buffer was
2010 misaligned by just the wrong amount. The miscalculation would allow an
2011 attacker to overflow a piece of heap-allocated memory. To mount this
2012 attack, the attacker would need to either open a SOCKS connection to
2013 Tor's SocksPort (usually restricted to localhost), or target a Tor
2014 instance configured to make its connections through a SOCKS proxy
2015 (which Tor does not do by default).
2017 Good security practice requires that all heap-overflow bugs should be
2018 presumed to be exploitable until proven otherwise, so we are treating
2019 this as a potential code execution attack. Please upgrade immediately!
2020 This bug does not affect bufferevents-based builds of Tor. Special
2021 thanks to "Vektor" for reporting this issue to us!
2023 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2024 crash bugs for unusual configurations, and a long-term bug that
2025 would prevent Tor from starting on Windows machines with draconian
2028 With this release, we remind everyone that 0.2.0.x has reached its
2029 formal end-of-life. Those Tor versions have many known flaws, and
2030 nobody should be using them. You should upgrade -- ideally to the
2031 0.2.2.x series. If you're using a Linux or BSD and its packages are
2032 obsolete, stop using those packages and upgrade anyway.
2034 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2035 longer receive support after some time in early 2012.
2038 - Fix a heap overflow bug that could occur when trying to pull
2039 data into the first chunk of a buffer, when that chunk had
2040 already had some data drained from it. Fixes CVE-2011-2778;
2041 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2042 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2043 that it doesn't attempt to allocate a socketpair. This could cause
2044 some problems on Windows systems with overzealous firewalls. Fix for
2045 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2047 - If we mark an OR connection for close based on a cell we process,
2048 don't process any further cells on it. We already avoid further
2049 reads on marked-for-close connections, but now we also discard the
2050 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2051 which was the first version where we might mark a connection for
2052 close based on processing a cell on it.
2053 - Correctly sanity-check that we don't underflow on a memory
2054 allocation (and then assert) for hidden service introduction
2055 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2056 bugfix on 0.2.1.5-alpha.
2057 - Fix a memory leak when we check whether a hidden service
2058 descriptor has any usable introduction points left. Fixes bug
2059 4424. Bugfix on 0.2.2.25-alpha.
2060 - Don't crash when we're running as a relay and don't have a GeoIP
2061 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2062 we've had in the 0.2.3.x branch already.
2063 - When running as a client, do not print a misleading (and plain
2064 wrong) log message that we're collecting "directory request"
2065 statistics: clients don't collect statistics. Also don't create a
2066 useless (because empty) stats file in the stats/ directory. Fixes
2067 bug 4353; bugfix on 0.2.2.34.
2070 - Detect failure to initialize Libevent. This fix provides better
2071 detection for future instances of bug 4457.
2072 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2073 function. This was eating up hideously large amounts of time on some
2074 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2075 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2076 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2078 - Don't warn about unused log_mutex in log.c when building with
2079 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2080 0.1.0.6-rc which introduced --disable-threads.
2081 - When configuring, starting, or stopping an NT service, stop
2082 immediately after the service configuration attempt has succeeded
2083 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2084 - When sending a NETINFO cell, include the original address
2085 received for the other side, not its canonical address. Found
2086 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2087 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2088 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2089 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2090 occurred when a client tried to fetch a descriptor for a bridge
2091 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2092 - Backport fixes for a pair of compilation warnings on Windows.
2093 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
2094 - If we had ever tried to call tor_addr_to_str on an address of
2095 unknown type, we would have done a strdup on an uninitialized
2096 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2097 Reported by "troll_un".
2098 - Correctly detect and handle transient lookup failures from
2099 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2100 Reported by "troll_un".
2101 - Fix null-pointer access that could occur if TLS allocation failed.
2102 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2103 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2104 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2107 - Add two new config options for directory authorities:
2108 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2109 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2110 that is always sufficient to satisfy the bandwidth requirement for
2111 the Guard flag. Now it will be easier for researchers to simulate
2112 Tor networks with different values. Resolves ticket 4484.
2113 - When Tor ignores a hidden service specified in its configuration,
2114 include the hidden service's directory in the warning message.
2115 Previously, we would only tell the user that some hidden service
2116 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2117 - Update to the December 6 2011 Maxmind GeoLite Country database.
2119 o Packaging changes:
2120 - Make it easier to automate expert package builds on Windows,
2121 by removing an absolute path from makensis.exe command.
2124 Changes in version 0.2.1.32 - 2011-12-16
2125 Tor 0.2.1.32 backports important security and privacy fixes for
2126 oldstable. This release is intended only for package maintainers and
2127 others who cannot use the 0.2.2 stable series. All others should be
2128 using Tor 0.2.2.x or newer.
2130 The Tor 0.2.1.x series will reach formal end-of-life some time in
2131 early 2012; we will stop releasing patches for it then.
2133 o Major bugfixes (also included in 0.2.2.x):
2134 - Correctly sanity-check that we don't underflow on a memory
2135 allocation (and then assert) for hidden service introduction
2136 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2137 bugfix on 0.2.1.5-alpha.
2138 - Fix a heap overflow bug that could occur when trying to pull
2139 data into the first chunk of a buffer, when that chunk had
2140 already had some data drained from it. Fixes CVE-2011-2778;
2141 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2144 - Update to the December 6 2011 Maxmind GeoLite Country database.
2147 Changes in version 0.2.3.9-alpha - 2011-12-08
2148 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
2149 a "DisableNetwork" security feature that bundles can use to avoid
2150 touching the network until bridges are configured, moves forward on
2151 the pluggable transport design, fixes a flaw in the hidden service
2152 design that unnecessarily prevented clients with wrong clocks from
2153 reaching hidden services, and fixes a wide variety of other issues.
2156 - Clients can now connect to private bridges over IPv6. Bridges
2157 still need at least one IPv4 address in order to connect to
2158 other relays. Note that we don't yet handle the case where the
2159 user has two bridge lines for the same bridge (one IPv4, one
2160 IPv6). Implements parts of proposal 186.
2161 - New "DisableNetwork" config option to prevent Tor from launching any
2162 connections or accepting any connections except on a control port.
2163 Bundles and controllers can set this option before letting Tor talk
2164 to the rest of the network, for example to prevent any connections
2165 to a non-bridge address. Packages like Orbot can also use this
2166 option to instruct Tor to save power when the network is off.
2167 - Clients and bridges can now be configured to use a separate
2168 "transport" proxy. This approach makes the censorship arms race
2169 easier by allowing bridges to use protocol obfuscation plugins. It
2170 implements the "managed proxy" part of proposal 180 (ticket 3472).
2171 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
2172 implementation. It makes AES_CTR about 7% faster than our old one
2173 (which was about 10% faster than the one OpenSSL used to provide).
2174 Resolves ticket 4526.
2175 - Add a "tor2web mode" for clients that want to connect to hidden
2176 services non-anonymously (and possibly more quickly). As a safety
2177 measure to try to keep users from turning this on without knowing
2178 what they are doing, tor2web mode must be explicitly enabled at
2179 compile time, and a copy of Tor compiled to run in tor2web mode
2180 cannot be used as a normal Tor client. Implements feature 2553.
2181 - Add experimental support for running on Windows with IOCP and no
2182 kernel-space socket buffers. This feature is controlled by a new
2183 "UserspaceIOCPBuffers" config option (off by default), which has
2184 no effect unless Tor has been built with support for bufferevents,
2185 is running on Windows, and has enabled IOCP. This may, in the long
2186 run, help solve or mitigate bug 98.
2187 - Use a more secure consensus parameter voting algorithm. Now at
2188 least three directory authorities or a majority of them must
2189 vote on a given parameter before it will be included in the
2190 consensus. Implements proposal 178.
2193 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
2194 They used to check that the timestamp was within 30 minutes
2195 of their system clock, so they could cap the size of their
2196 replay-detection cache, but that approach unnecessarily refused
2197 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
2198 the v3 intro-point protocol (the first one which sent a timestamp
2199 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
2200 - Only use the EVP interface when AES acceleration is enabled,
2201 to avoid a 5-7% performance regression. Resolves issue 4525;
2202 bugfix on 0.2.3.8-alpha.
2204 o Privacy/anonymity features (bridge detection):
2205 - Make bridge SSL certificates a bit more stealthy by using random
2206 serial numbers, in the same fashion as OpenSSL when generating
2207 self-signed certificates. Implements ticket 4584.
2208 - Introduce a new config option "DynamicDHGroups", enabled by
2209 default, which provides each bridge with a unique prime DH modulus
2210 to be used during SSL handshakes. This option attempts to help
2211 against censors who might use the Apache DH modulus as a static
2212 identifier for bridges. Addresses ticket 4548.
2214 o Minor features (new/different config options):
2215 - New configuration option "DisableDebuggerAttachment" (on by default)
2216 to prevent basic debugging attachment attempts by other processes.
2217 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
2218 - Allow MapAddress directives to specify matches against super-domains,
2219 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
2220 Implements issue 933.
2221 - Slightly change behavior of "list" options (that is, config
2222 options that can appear more than once) when they appear both in
2223 torrc and on the command line. Previously, the command-line options
2224 would be appended to the ones from torrc. Now, the command-line
2225 options override the torrc options entirely. This new behavior
2226 allows the user to override list options (like exit policies and
2227 ports to listen on) from the command line, rather than simply
2228 appending to the list.
2229 - You can get the old (appending) command-line behavior for "list"
2230 options by prefixing the option name with a "+".
2231 - You can remove all the values for a "list" option from the command
2232 line without adding any new ones by prefixing the option name
2234 - Add experimental support for a "defaults" torrc file to be parsed
2235 before the regular torrc. Torrc options override the defaults file's
2236 options in the same way that the command line overrides the torrc.
2237 The SAVECONF controller command saves only those options which
2238 differ between the current configuration and the defaults file. HUP
2239 reloads both files. (Note: This is an experimental feature; its
2240 behavior will probably be refined in future 0.2.3.x-alpha versions
2241 to better meet packagers' needs.) Implements task 4552.
2244 - Try to make the introductory warning message that Tor prints on
2245 startup more useful for actually finding help and information.
2246 Resolves ticket 2474.
2247 - Running "make version" now displays the version of Tor that
2248 we're about to build. Idea from katmagic; resolves issue 4400.
2249 - Expire old or over-used hidden service introduction points.
2250 Required by fix for bug 3460.
2251 - Move the replay-detection cache for the RSA-encrypted parts of
2252 INTRODUCE2 cells to the introduction point data structures.
2253 Previously, we would use one replay-detection cache per hidden
2254 service. Required by fix for bug 3460.
2255 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
2256 public key replay-detection cache from 60 minutes to 5 minutes. This
2257 replay-detection cache is now used only to detect multiple
2258 INTRODUCE2 cells specifying the same rendezvous point, so we can
2259 avoid launching multiple simultaneous attempts to connect to it.
2261 o Minor bugfixes (on Tor 0.2.2.x and earlier):
2262 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2263 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2265 - Fix a minor formatting issue in one of tor-gencert's error messages.
2267 - Prevent a false positive from the check-spaces script, by disabling
2268 the "whitespace between function name and (" check for functions
2270 - Fix a log message suggesting that people contact a non-existent
2271 email address. Fixes bug 3448.
2272 - Fix null-pointer access that could occur if TLS allocation failed.
2273 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2274 - Report a real bootstrap problem to the controller on router
2275 identity mismatch. Previously we just said "foo", which probably
2276 made a lot of sense at the time. Fixes bug 4169; bugfix on
2278 - If we had ever tried to call tor_addr_to_str() on an address of
2279 unknown type, we would have done a strdup() on an uninitialized
2280 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2281 Reported by "troll_un".
2282 - Correctly detect and handle transient lookup failures from
2283 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2284 Reported by "troll_un".
2285 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2286 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2287 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
2288 bug 4532; found by "troll_un".
2290 o Minor bugfixes (on Tor 0.2.3.x):
2291 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
2293 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
2294 circuit for use as a hidden service client's rendezvous point.
2295 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
2296 with help from wanoskarnet.
2297 - Restore behavior of overriding SocksPort, ORPort, and similar
2298 options from the command line. Bugfix on 0.2.3.3-alpha.
2301 - Properly handle the case where the build-tree is not the same
2302 as the source tree when generating src/common/common_sha1.i,
2303 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
2304 bugfix on 0.2.0.1-alpha.
2306 o Code simplifications, cleanups, and refactorings:
2307 - Remove the pure attribute from all functions that used it
2308 previously. In many cases we assigned it incorrectly, because the
2309 functions might assert or call impure functions, and we don't have
2310 evidence that keeping the pure attribute is worthwhile. Implements
2311 changes suggested in ticket 4421.
2312 - Remove some dead code spotted by coverity. Fixes cid 432.
2313 Bugfix on 0.2.3.1-alpha, closes bug 4637.
2316 Changes in version 0.2.3.8-alpha - 2011-11-22
2317 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
2318 socketpair-related bug that has been bothering Windows users. It adds
2319 support to serve microdescriptors to controllers, so Vidalia's network
2320 map can resume listing relays (once Vidalia implements its side),
2321 and adds better support for hardware AES acceleration. Finally, it
2322 starts the process of adjusting the bandwidth cutoff for getting the
2323 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
2324 that tiny relays harm performance more than they help network capacity.
2327 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2328 that it doesn't attempt to allocate a socketpair. This could cause
2329 some problems on Windows systems with overzealous firewalls. Fix for
2330 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2332 - Correctly sanity-check that we don't underflow on a memory
2333 allocation (and then assert) for hidden service introduction
2334 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2335 bugfix on 0.2.1.5-alpha.
2336 - Remove the artificially low cutoff of 20KB to guarantee the Fast
2337 flag. In the past few years the average relay speed has picked
2338 up, and while the "top 7/8 of the network get the Fast flag" and
2339 "all relays with 20KB or more of capacity get the Fast flag" rules
2340 used to have the same result, now the top 7/8 of the network has
2341 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
2342 - Fix a rare assertion failure when checking whether a v0 hidden
2343 service descriptor has any usable introduction points left, and
2344 we don't have enough information to build a circuit to the first
2345 intro point named in the descriptor. The HS client code in
2346 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
2347 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
2348 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
2349 - Make bridge authorities not crash when they are asked for their own
2350 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
2351 - When running as a client, do not print a misleading (and plain
2352 wrong) log message that we're collecting "directory request"
2353 statistics: clients don't collect statistics. Also don't create a
2354 useless (because empty) stats file in the stats/ directory. Fixes
2355 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
2358 - Allow Tor controllers like Vidalia to obtain the microdescriptor
2359 for a relay by identity digest or nickname. Previously,
2360 microdescriptors were only available by their own digests, so a
2361 controller would have to ask for and parse the whole microdescriptor
2362 consensus in order to look up a single relay's microdesc. Fixes
2363 bug 3832; bugfix on 0.2.3.1-alpha.
2364 - Use OpenSSL's EVP interface for AES encryption, so that all AES
2365 operations can use hardware acceleration (if present). Resolves
2368 o Minor bugfixes (on 0.2.2.x and earlier):
2369 - Detect failure to initialize Libevent. This fix provides better
2370 detection for future instances of bug 4457.
2371 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2372 function. This was eating up hideously large amounts of time on some
2373 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2374 - Don't warn about unused log_mutex in log.c when building with
2375 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2376 0.1.0.6-rc which introduced --disable-threads.
2377 - Allow manual 'authenticate' commands to the controller interface
2378 from netcat (nc) as well as telnet. We were rejecting them because
2379 they didn't come with the expected whitespace at the end of the
2380 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
2381 - Fix some (not actually triggerable) buffer size checks in usage of
2382 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2384 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2385 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2386 - When configuring, starting, or stopping an NT service, stop
2387 immediately after the service configuration attempt has succeeded
2388 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2389 - When sending a NETINFO cell, include the original address
2390 received for the other side, not its canonical address. Found
2391 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2392 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
2393 can pick them up when the tests aren't disabled. Bugfix on
2394 0.2.2.4-alpha which introduced tinytest.
2395 - Fix a memory leak when we check whether a hidden service
2396 descriptor has any usable introduction points left. Fixes bug
2397 4424. Bugfix on 0.2.2.25-alpha.
2398 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2399 occurred when a client tried to fetch a descriptor for a bridge
2400 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2402 o Minor bugfixes (on 0.2.3.x):
2403 - Make util unit tests build correctly with MSVC. Bugfix on
2404 0.2.3.3-alpha. Patch by Gisle Vanem.
2405 - Successfully detect AUTH_CHALLENGE cells with no recognized
2406 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
2408 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
2409 it should still send a NETINFO cell to allow the connection to
2410 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
2412 - Log less loudly when we get an invalid authentication certificate
2413 from a source other than a directory authority: it's not unusual
2414 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
2416 - Tolerate servers with more clock skew in their authentication
2417 certificates than previously. Fixes bug 4371; bugfix on
2419 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
2420 on 0.2.3.4-alpha and 0.2.3.6-alpha.
2423 - Add two new config options for directory authorities:
2424 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2425 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2426 that is always sufficient to satisfy the bandwidth requirement for
2427 the Guard flag. Now it will be easier for researchers to simulate
2428 Tor networks with different values. Resolves ticket 4484.
2429 - When Tor ignores a hidden service specified in its configuration,
2430 include the hidden service's directory in the warning message.
2431 Previously, we would only tell the user that some hidden service
2432 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2433 - When we fail to initialize Libevent, retry with IOCP disabled so we
2434 don't need to turn on multi-threading support in Libevent, which in
2435 turn requires a working socketpair(). This is a workaround for bug
2436 4457, which affects Libevent versions from 2.0.1-alpha through
2438 - Detect when we try to build on a platform that doesn't define
2439 AF_UNSPEC to 0. We don't work there, so refuse to compile.
2440 - Update to the November 1 2011 Maxmind GeoLite Country database.
2442 o Packaging changes:
2443 - Make it easier to automate expert package builds on Windows,
2444 by removing an absolute path from makensis.exe command.
2446 o Code simplifications and refactoring:
2447 - Remove some redundant #include directives throughout the code.
2448 Patch from Andrea Gelmini.
2449 - Unconditionally use OpenSSL's AES implementation instead of our
2450 old built-in one. OpenSSL's AES has been better for a while, and
2451 relatively few servers should still be on any version of OpenSSL
2452 that doesn't have good optimized assembly AES.
2453 - Use the name "CERTS" consistently to refer to the new cell type;
2454 we were calling it CERT in some places and CERTS in others.
2457 - Numerous new unit tests for functions in util.c and address.c by
2459 - The long-disabled benchmark tests are now split into their own
2460 ./src/test/bench binary.
2461 - The benchmark tests can now use more accurate timers than
2462 gettimeofday() when such timers are available.
2465 Changes in version 0.2.3.7-alpha - 2011-10-30
2466 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
2467 the new v3 handshake. It also resolves yet another bridge address
2471 - If we mark an OR connection for close based on a cell we process,
2472 don't process any further cells on it. We already avoid further
2473 reads on marked-for-close connections, but now we also discard the
2474 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2475 which was the first version where we might mark a connection for
2476 close based on processing a cell on it.
2477 - Fix a double-free bug that would occur when we received an invalid
2478 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
2479 bugfix on 0.2.3.6-alpha.
2480 - Bridges no longer include their address in NETINFO cells on outgoing
2481 OR connections, to allow them to blend in better with clients.
2482 Removes another avenue for enumerating bridges. Reported by
2483 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
2484 cells were introduced.
2487 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
2488 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2491 Changes in version 0.2.3.6-alpha - 2011-10-26
2492 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
2493 anonymity vulnerability where an attacker can deanonymize Tor
2494 users. Everybody should upgrade.
2496 This release also features support for a new v3 connection handshake
2497 protocol, and fixes to make hidden service connections more robust.
2500 - Implement a new handshake protocol (v3) for authenticating Tors to
2501 each other over TLS. It should be more resistant to fingerprinting
2502 than previous protocols, and should require less TLS hacking for
2503 future Tor implementations. Implements proposal 176.
2504 - Allow variable-length padding cells to disguise the length of
2505 Tor's TLS records. Implements part of proposal 184.
2507 o Privacy/anonymity fixes (clients):
2508 - Clients and bridges no longer send TLS certificate chains on
2509 outgoing OR connections. Previously, each client or bridge would
2510 use the same cert chain for all outgoing OR connections until
2511 its IP address changes, which allowed any relay that the client
2512 or bridge contacted to determine which entry guards it is using.
2513 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2514 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2515 no longer considers that connection as suitable for satisfying a
2516 circuit EXTEND request. Now relays can protect clients from the
2517 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2518 - Directory authorities no longer assign the Guard flag to relays
2519 that haven't upgraded to the above "refuse EXTEND requests
2520 to client connections" fix. Now directory authorities can
2521 protect clients from the CVE-2011-2768 issue even if neither
2522 the clients nor the relays have upgraded yet. There's a new
2523 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2524 to let us transition smoothly, else tomorrow there would be no
2527 o Major bugfixes (hidden services):
2528 - Improve hidden service robustness: when an attempt to connect to
2529 a hidden service ends, be willing to refetch its hidden service
2530 descriptors from each of the HSDir relays responsible for them
2531 immediately. Previously, we would not consider refetching the
2532 service's descriptors from each HSDir for 15 minutes after the last
2533 fetch, which was inconvenient if the hidden service was not running
2534 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
2535 - When one of a hidden service's introduction points appears to be
2536 unreachable, stop trying it. Previously, we would keep trying
2537 to build circuits to the introduction point until we lost the
2538 descriptor, usually because the user gave up and restarted Tor.
2539 Partly fixes bug 3825.
2540 - Don't launch a useless circuit after failing to use one of a
2541 hidden service's introduction points. Previously, we would
2542 launch a new introduction circuit, but not set the hidden service
2543 which that circuit was intended to connect to, so it would never
2544 actually be used. A different piece of code would then create a
2545 new introduction circuit correctly. Bug reported by katmagic and
2546 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2548 o Major bugfixes (other):
2549 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2550 that they initiated. Relays could distinguish incoming bridge
2551 connections from client connections, creating another avenue for
2552 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2553 Found by "frosty_un".
2554 - Don't update the AccountingSoftLimitHitAt state file entry whenever
2555 tor gets started. This prevents a wrong average bandwidth
2556 estimate, which would cause relays to always start a new accounting
2557 interval at the earliest possible moment. Fixes bug 2003; bugfix
2558 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
2559 immensely in tracking this bug down.
2560 - Fix a crash bug when changing node restrictions while a DNS lookup
2561 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2564 o Minor bugfixes (on 0.2.2.x and earlier):
2565 - When a hidden service turns an extra service-side introduction
2566 circuit into a general-purpose circuit, free the rend_data and
2567 intro_key fields first, so we won't leak memory if the circuit
2568 is cannibalized for use as another service-side introduction
2569 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2570 - Rephrase the log message emitted if the TestSocks check is
2571 successful. Patch from Fabian Keil; fixes bug 4094.
2572 - Bridges now skip DNS self-tests, to act a little more stealthily.
2573 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2574 bridges. Patch by "warms0x".
2575 - Remove a confusing dollar sign from the example fingerprint in the
2576 man page, and also make the example fingerprint a valid one. Fixes
2577 bug 4309; bugfix on 0.2.1.3-alpha.
2578 - Fix internal bug-checking logic that was supposed to catch
2579 failures in digest generation so that it will fail more robustly
2580 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2581 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2582 - Report any failure in init_keys() calls launched because our
2583 IP address has changed. Spotted by Coverity Scan. Bugfix on
2584 0.1.1.4-alpha; fixes CID 484.
2586 o Minor bugfixes (on 0.2.3.x):
2587 - Fix a bug in configure.in that kept it from building a configure
2588 script with autoconf versions earlier than 2.61. Fixes bug 2430;
2589 bugfix on 0.2.3.1-alpha.
2590 - Don't warn users that they are exposing a client port to the
2591 Internet if they have specified an RFC1918 address. Previously,
2592 we would warn if the user had specified any non-loopback
2593 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
2594 - Fix memory leaks in the failing cases of the new SocksPort and
2595 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
2596 fixes coverity CIDs 485, 486, and 487.
2599 - When a hidden service's introduction point times out, consider
2600 trying it again during the next attempt to connect to the
2601 HS. Previously, we would not try it again unless a newly fetched
2602 descriptor contained it. Required by fixes for bugs 1297 and 3825.
2603 - The next version of Windows will be called Windows 8, and it has
2604 a major version of 6, minor version of 2. Correctly identify that
2605 version instead of calling it "Very recent version". Resolves
2606 ticket 4153; reported by funkstar.
2607 - The Bridge Authority now writes statistics on how many bridge
2608 descriptors it gave out in total, and how many unique descriptors
2609 it gave out. It also lists how often the most and least commonly
2610 fetched descriptors were given out, as well as the median and
2611 25th/75th percentile. Implements tickets 4200 and 4294.
2612 - Update to the October 4 2011 Maxmind GeoLite Country database.
2614 o Code simplifications and refactoring:
2615 - Remove some old code to remember statistics about which descriptors
2616 we've served as a directory mirror. The feature wasn't used and
2617 is outdated now that microdescriptors are around.
2618 - Rename Tor functions that turn strings into addresses, so that
2619 "parse" indicates that no hostname resolution occurs, and
2620 "lookup" indicates that hostname resolution may occur. This
2621 should help prevent mistakes in the future. Fixes bug 3512.
2624 Changes in version 0.2.2.34 - 2011-10-26
2625 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2626 can deanonymize Tor users. Everybody should upgrade.
2628 The attack relies on four components: 1) Clients reuse their TLS cert
2629 when talking to different relays, so relays can recognize a user by
2630 the identity key in her cert. 2) An attacker who knows the client's
2631 identity key can probe each guard relay to see if that identity key
2632 is connected to that guard relay right now. 3) A variety of active
2633 attacks in the literature (starting from "Low-Cost Traffic Analysis
2634 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2635 discover the guard relays that a Tor user visiting the website is using.
2636 4) Clients typically pick three guards at random, so the set of guards
2637 for a given user could well be a unique fingerprint for her. This
2638 release fixes components #1 and #2, which is enough to block the attack;
2639 the other two remain as open research problems. Special thanks to
2640 "frosty_un" for reporting the issue to us!
2642 Clients should upgrade so they are no longer recognizable by the TLS
2643 certs they present. Relays should upgrade so they no longer allow a
2644 remote attacker to probe them to test whether unpatched clients are
2645 currently connected to them.
2647 This release also fixes several vulnerabilities that allow an attacker
2648 to enumerate bridge relays. Some bridge enumeration attacks still
2649 remain; see for example proposal 188.
2651 o Privacy/anonymity fixes (clients):
2652 - Clients and bridges no longer send TLS certificate chains on
2653 outgoing OR connections. Previously, each client or bridge would
2654 use the same cert chain for all outgoing OR connections until
2655 its IP address changes, which allowed any relay that the client
2656 or bridge contacted to determine which entry guards it is using.
2657 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2658 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2659 no longer considers that connection as suitable for satisfying a
2660 circuit EXTEND request. Now relays can protect clients from the
2661 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2662 - Directory authorities no longer assign the Guard flag to relays
2663 that haven't upgraded to the above "refuse EXTEND requests
2664 to client connections" fix. Now directory authorities can
2665 protect clients from the CVE-2011-2768 issue even if neither
2666 the clients nor the relays have upgraded yet. There's a new
2667 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2668 to let us transition smoothly, else tomorrow there would be no
2671 o Privacy/anonymity fixes (bridge enumeration):
2672 - Bridge relays now do their directory fetches inside Tor TLS
2673 connections, like all the other clients do, rather than connecting
2674 directly to the DirPort like public relays do. Removes another
2675 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2676 - Bridges relays now build circuits for themselves in a more similar
2677 way to how clients build them. Removes another avenue for
2678 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2679 when bridges were introduced.
2680 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2681 that they initiated. Relays could distinguish incoming bridge
2682 connections from client connections, creating another avenue for
2683 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2684 Found by "frosty_un".
2687 - Fix a crash bug when changing node restrictions while a DNS lookup
2688 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2690 - Don't launch a useless circuit after failing to use one of a
2691 hidden service's introduction points. Previously, we would
2692 launch a new introduction circuit, but not set the hidden service
2693 which that circuit was intended to connect to, so it would never
2694 actually be used. A different piece of code would then create a
2695 new introduction circuit correctly. Bug reported by katmagic and
2696 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2699 - Change an integer overflow check in the OpenBSD_Malloc code so
2700 that GCC is less likely to eliminate it as impossible. Patch
2701 from Mansour Moufid. Fixes bug 4059.
2702 - When a hidden service turns an extra service-side introduction
2703 circuit into a general-purpose circuit, free the rend_data and
2704 intro_key fields first, so we won't leak memory if the circuit
2705 is cannibalized for use as another service-side introduction
2706 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2707 - Bridges now skip DNS self-tests, to act a little more stealthily.
2708 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2709 bridges. Patch by "warms0x".
2710 - Fix internal bug-checking logic that was supposed to catch
2711 failures in digest generation so that it will fail more robustly
2712 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2713 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2714 - Report any failure in init_keys() calls launched because our
2715 IP address has changed. Spotted by Coverity Scan. Bugfix on
2716 0.1.1.4-alpha; fixes CID 484.
2718 o Minor bugfixes (log messages and documentation):
2719 - Remove a confusing dollar sign from the example fingerprint in the
2720 man page, and also make the example fingerprint a valid one. Fixes
2721 bug 4309; bugfix on 0.2.1.3-alpha.
2722 - The next version of Windows will be called Windows 8, and it has
2723 a major version of 6, minor version of 2. Correctly identify that
2724 version instead of calling it "Very recent version". Resolves
2725 ticket 4153; reported by funkstar.
2726 - Downgrade log messages about circuit timeout calibration from
2727 "notice" to "info": they don't require or suggest any human
2728 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2729 bugfix on 0.2.2.14-alpha.
2732 - Turn on directory request statistics by default and include them in
2733 extra-info descriptors. Don't break if we have no GeoIP database.
2734 Backported from 0.2.3.1-alpha; implements ticket 3951.
2735 - Update to the October 4 2011 Maxmind GeoLite Country database.
2738 Changes in version 0.2.1.31 - 2011-10-26
2739 Tor 0.2.1.31 backports important security and privacy fixes for
2740 oldstable. This release is intended only for package maintainers and
2741 others who cannot use the 0.2.2 stable series. All others should be
2742 using Tor 0.2.2.x or newer.
2744 o Security fixes (also included in 0.2.2.x):
2745 - Replace all potentially sensitive memory comparison operations
2746 with versions whose runtime does not depend on the data being
2747 compared. This will help resist a class of attacks where an
2748 adversary can use variations in timing information to learn
2749 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2750 implementation by Robert Ransom based partially on code by DJB.)
2751 - Fix an assert in parsing router descriptors containing IPv6
2752 addresses. This one took down the directory authorities when
2753 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2755 o Privacy/anonymity fixes (also included in 0.2.2.x):
2756 - Clients and bridges no longer send TLS certificate chains on
2757 outgoing OR connections. Previously, each client or bridge would
2758 use the same cert chain for all outgoing OR connections until
2759 its IP address changes, which allowed any relay that the client
2760 or bridge contacted to determine which entry guards it is using.
2761 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2762 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2763 no longer considers that connection as suitable for satisfying a
2764 circuit EXTEND request. Now relays can protect clients from the
2765 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2766 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2767 that they initiated. Relays could distinguish incoming bridge
2768 connections from client connections, creating another avenue for
2769 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2770 Found by "frosty_un".
2771 - When receiving a hidden service descriptor, check that it is for
2772 the hidden service we wanted. Previously, Tor would store any
2773 hidden service descriptors that a directory gave it, whether it
2774 wanted them or not. This wouldn't have let an attacker impersonate
2775 a hidden service, but it did let directories pre-seed a client
2776 with descriptors that it didn't want. Bugfix on 0.0.6.
2777 - Avoid linkability based on cached hidden service descriptors: forget
2778 all hidden service descriptors cached as a client when processing a
2779 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2780 - Make the bridge directory authority refuse to answer directory
2781 requests for "all" descriptors. It used to include bridge
2782 descriptors in its answer, which was a major information leak.
2783 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2784 - Don't attach new streams to old rendezvous circuits after SIGNAL
2785 NEWNYM. Previously, we would keep using an existing rendezvous
2786 circuit if it remained open (i.e. if it were kept open by a
2787 long-lived stream, or if a new stream were attached to it before
2788 Tor could notice that it was old and no longer in use). Bugfix on
2789 0.1.1.15-rc; fixes bug 3375.
2791 o Minor bugfixes (also included in 0.2.2.x):
2792 - When we restart our relay, we might get a successful connection
2793 from the outside before we've started our reachability tests,
2794 triggering a warning: "ORPort found reachable, but I have no
2795 routerinfo yet. Failing to inform controller of success." This
2796 bug was harmless unless Tor is running under a controller
2797 like Vidalia, in which case the controller would never get a
2798 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2800 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2801 enabled. Fixes bug 1526.
2802 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2803 anything since 0.2.1.16-rc.
2804 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2805 None of the cases where we did this before were wrong, but by making
2806 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2807 - Fix a rare crash bug that could occur when a client was configured
2808 with a large number of bridges. Fixes bug 2629; bugfix on
2809 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2810 - Correct the warning displayed when a rendezvous descriptor exceeds
2811 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2813 - Fix an uncommon assertion failure when running with DNSPort under
2814 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2815 - When warning about missing zlib development packages during compile,
2816 give the correct package names. Bugfix on 0.2.0.1-alpha.
2817 - Require that introduction point keys and onion keys have public
2818 exponent 65537. Bugfix on 0.2.0.10-alpha.
2819 - Do not crash when our configuration file becomes unreadable, for
2820 example due to a permissions change, between when we start up
2821 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2823 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2825 - Always NUL-terminate the sun_path field of a sockaddr_un before
2826 passing it to the kernel. (Not a security issue: kernels are
2827 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2828 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2829 - Don't stack-allocate the list of supplementary GIDs when we're
2830 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2831 could take up to 256K, which is way too much stack. Found by
2832 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2834 o Minor bugfixes (only in 0.2.1.x):
2835 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2836 rely on them. Bugfix on 0.2.1.30.
2837 - Use git revisions instead of svn revisions when generating our
2838 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2840 o Minor features (also included in 0.2.2.x):
2841 - Adjust the expiration time on our SSL session certificates to
2842 better match SSL certs seen in the wild. Resolves ticket 4014.
2843 - Allow nameservers with IPv6 address. Resolves bug 2574.
2844 - Update to the October 4 2011 Maxmind GeoLite Country database.
2847 Changes in version 0.2.3.5-alpha - 2011-09-28
2848 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
2849 bridge relays; fixes an assertion error that many users started hitting
2850 today; and adds the ability to refill token buckets more often than
2851 once per second, allowing significant performance improvements.
2854 - Bridge relays now do their directory fetches inside Tor TLS
2855 connections, like all the other clients do, rather than connecting
2856 directly to the DirPort like public relays do. Removes another
2857 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2858 - Bridges relays now build circuits for themselves in a more similar
2859 way to how clients build them. Removes another avenue for
2860 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2861 when bridges were introduced.
2864 - Fix an "Assertion md->held_by_node == 1 failed" error that could
2865 occur when the same microdescriptor was referenced by two node_t
2866 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
2868 o Major features (networking):
2869 - Add a new TokenBucketRefillInterval option to refill token buckets
2870 more frequently than once per second. This should improve network
2871 performance, alleviate queueing problems, and make traffic less
2872 bursty. Implements proposal 183; closes ticket 3630. Design by
2873 Florian Tschorsch and Björn Scheuermann; implementation by
2877 - Change an integer overflow check in the OpenBSD_Malloc code so
2878 that GCC is less likely to eliminate it as impossible. Patch
2879 from Mansour Moufid. Fixes bug 4059.
2881 o Minor bugfixes (usability):
2882 - Downgrade log messages about circuit timeout calibration from
2883 "notice" to "info": they don't require or suggest any human
2884 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2885 bugfix on 0.2.2.14-alpha.
2887 o Minor features (diagnostics):
2888 - When the system call to create a listener socket fails, log the
2889 error message explaining why. This may help diagnose bug 4027.
2892 Changes in version 0.2.3.4-alpha - 2011-09-13
2893 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
2894 tweak to Tor's TLS handshake that makes relays and bridges that run
2895 this new version reachable from Iran again. It also fixes a few new
2896 bugs in 0.2.3.x, and teaches relays to recognize when they're not
2897 listed in the network consensus and republish.
2899 o Major bugfixes (also part of 0.2.2.33):
2900 - Avoid an assertion failure when reloading a configuration with
2901 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2902 3923; bugfix on 0.2.2.25-alpha.
2904 o Minor features (security, also part of 0.2.2.33):
2905 - Check for replays of the public-key encrypted portion of an
2906 INTRODUCE1 cell, in addition to the current check for replays of
2907 the g^x value. This prevents a possible class of active attacks
2908 by an attacker who controls both an introduction point and a
2909 rendezvous point, and who uses the malleability of AES-CTR to
2910 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2911 that these attacks is infeasible (requiring the attacker to send
2912 on the order of zettabytes of altered cells in a short interval),
2913 but we'd rather block them off in case there are any classes of
2914 this attack that we missed. Reported by Willem Pinckaers.
2916 o Minor features (also part of 0.2.2.33):
2917 - Adjust the expiration time on our SSL session certificates to
2918 better match SSL certs seen in the wild. Resolves ticket 4014.
2919 - Change the default required uptime for a relay to be accepted as
2920 a HSDir (hidden service directory) from 24 hours to 25 hours.
2921 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2922 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2923 authorities to abstain from voting on assignment of the HSDir
2924 consensus flag. Related to bug 2649.
2925 - Update to the September 6 2011 Maxmind GeoLite Country database.
2927 o Minor bugfixes (also part of 0.2.2.33):
2928 - Demote the 'replay detected' log message emitted when a hidden
2929 service receives the same Diffie-Hellman public key in two different
2930 INTRODUCE2 cells to info level. A normal Tor client can cause that
2931 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2932 fixes part of bug 2442.
2933 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2934 level. There is nothing that a hidden service's operator can do
2935 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2937 - Clarify a log message specifying the characters permitted in
2938 HiddenServiceAuthorizeClient client names. Previously, the log
2939 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2940 given the impression that every ASCII character between "+" and "_"
2941 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2943 o Build fixes (also part of 0.2.2.33):
2944 - Clean up some code issues that prevented Tor from building on older
2945 BSDs. Fixes bug 3894; reported by "grarpamp".
2946 - Search for a platform-specific version of "ar" when cross-compiling.
2947 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2950 - Fix a bug where the SocksPort option (for example) would get
2951 ignored and replaced by the default if a SocksListenAddress
2952 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2956 - Relays now try regenerating and uploading their descriptor more
2957 frequently if they are not listed in the consensus, or if the
2958 version of their descriptor listed in the consensus is too
2959 old. This fix should prevent situations where a server declines
2960 to re-publish itself because it has done so too recently, even
2961 though the authorities decided not to list its recent-enough
2962 descriptor. Fix for bug 3327.
2965 - Relays now include a reason for regenerating their descriptors
2966 in an HTTP header when uploading to the authorities. This will
2967 make it easier to debug descriptor-upload issues in the future.
2968 - When starting as root and then changing our UID via the User
2969 control option, and we have a ControlSocket configured, make sure
2970 that the ControlSocket is owned by the same account that Tor will
2971 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2974 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2975 utility function used in the control-port code). This shouldn't
2976 ever happen unless Tor is completely out of memory, but if it did
2977 happen and Tor somehow recovered from it, Tor could have sent a log
2978 message to a control port in the middle of a reply to a controller
2979 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2980 - Make 'FetchUselessDescriptors' cause all descriptor types and
2981 all consensus types (including microdescriptors) to get fetched.
2982 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2985 - Make a new "entry connection" struct as an internal subtype of "edge
2986 connection", to simplify the code and make exit connections smaller.
2989 Changes in version 0.2.2.33 - 2011-09-13
2990 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2991 TLS handshake that makes relays and bridges that run this new version
2992 reachable from Iran again.
2995 - Avoid an assertion failure when reloading a configuration with
2996 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2997 3923; bugfix on 0.2.2.25-alpha.
2999 o Minor features (security):
3000 - Check for replays of the public-key encrypted portion of an
3001 INTRODUCE1 cell, in addition to the current check for replays of
3002 the g^x value. This prevents a possible class of active attacks
3003 by an attacker who controls both an introduction point and a
3004 rendezvous point, and who uses the malleability of AES-CTR to
3005 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3006 that these attacks are infeasible (requiring the attacker to send
3007 on the order of zettabytes of altered cells in a short interval),
3008 but we'd rather block them off in case there are any classes of
3009 this attack that we missed. Reported by Willem Pinckaers.
3012 - Adjust the expiration time on our SSL session certificates to
3013 better match SSL certs seen in the wild. Resolves ticket 4014.
3014 - Change the default required uptime for a relay to be accepted as
3015 a HSDir (hidden service directory) from 24 hours to 25 hours.
3016 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3017 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3018 authorities to abstain from voting on assignment of the HSDir
3019 consensus flag. Related to bug 2649.
3020 - Update to the September 6 2011 Maxmind GeoLite Country database.
3022 o Minor bugfixes (documentation and log messages):
3023 - Correct the man page to explain that HashedControlPassword and
3024 CookieAuthentication can both be set, in which case either method
3025 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3026 when we decided to allow these config options to both be set. Issue
3028 - Demote the 'replay detected' log message emitted when a hidden
3029 service receives the same Diffie-Hellman public key in two different
3030 INTRODUCE2 cells to info level. A normal Tor client can cause that
3031 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3032 fixes part of bug 2442.
3033 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3034 level. There is nothing that a hidden service's operator can do
3035 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3037 - Clarify a log message specifying the characters permitted in
3038 HiddenServiceAuthorizeClient client names. Previously, the log
3039 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3040 given the impression that every ASCII character between "+" and "_"
3041 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3044 - Provide a substitute implementation of lround() for MSVC, which
3045 apparently lacks it. Patch from Gisle Vanem.
3046 - Clean up some code issues that prevented Tor from building on older
3047 BSDs. Fixes bug 3894; reported by "grarpamp".
3048 - Search for a platform-specific version of "ar" when cross-compiling.
3049 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3052 Changes in version 0.2.3.3-alpha - 2011-09-01
3053 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
3054 security, and provides client-side support for the microdescriptor
3055 and optimistic data features introduced earlier in the 0.2.3.x
3056 series. It also includes numerous critical bugfixes in the (optional)
3057 bufferevent-based networking backend.
3059 o Major features (stream isolation):
3060 - You can now configure Tor so that streams from different
3061 applications are isolated on different circuits, to prevent an
3062 attacker who sees your streams as they leave an exit node from
3063 linking your sessions to one another. To do this, choose some way
3064 to distinguish the applications: have them connect to different
3065 SocksPorts, or have one of them use SOCKS4 while the other uses
3066 SOCKS5, or have them pass different authentication strings to the
3067 SOCKS proxy. Then, use the new SocksPort syntax to configure the
3068 degree of isolation you need. This implements Proposal 171.
3069 - There's a new syntax for specifying multiple client ports (such as
3070 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
3071 multiple *Port entries with full addr:port syntax on each.
3072 The old *ListenAddress format is still supported, but you can't
3073 mix it with the new *Port syntax.
3075 o Major features (other):
3076 - Enable microdescriptor fetching by default for clients. This allows
3077 clients to download a much smaller amount of directory information.
3078 To disable it (and go back to the old-style consensus and
3079 descriptors), set "UseMicrodescriptors 0" in your torrc file.
3080 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
3081 "PortForwarding" config option), now supports Windows.
3082 - When using an exit relay running 0.2.3.x, clients can now
3083 "optimistically" send data before the exit relay reports that
3084 the stream has opened. This saves a round trip when starting
3085 connections where the client speaks first (such as web browsing).
3086 This behavior is controlled by a consensus parameter (currently
3087 disabled). To turn it on or off manually, use the "OptimisticData"
3088 torrc option. Implements proposal 181; code by Ian Goldberg.
3090 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
3091 - When using IOCP on Windows, we need to enable Libevent windows
3093 - The IOCP backend now works even when the user has not specified
3094 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
3095 Fixes part of bug 3752.
3096 - Correctly record the bytes we've read and written when using
3097 bufferevents, so that we can include them in our bandwidth history
3098 and advertised bandwidth. Fixes bug 3803.
3099 - Apply rate-limiting only at the bottom of a chain of filtering
3100 bufferevents. This prevents us from filling up internal read
3101 buffers and violating rate-limits when filtering bufferevents
3102 are enabled. Fixes part of bug 3804.
3103 - Add high-watermarks to the output buffers for filtered
3104 bufferevents. This prevents us from filling up internal write
3105 buffers and wasting CPU cycles when filtering bufferevents are
3106 enabled. Fixes part of bug 3804.
3107 - Correctly notice when data has been written from a bufferevent
3108 without flushing it completely. Fixes bug 3805.
3109 - Fix a bug where server-side tunneled bufferevent-based directory
3110 streams would get closed prematurely. Fixes bug 3814.
3111 - Fix a use-after-free error with per-connection rate-limiting
3112 buckets. Fixes bug 3888.
3114 o Major bugfixes (also part of 0.2.2.31-rc):
3115 - If we're configured to write our ControlPorts to disk, only write
3116 them after switching UID and creating the data directory. This way,
3117 we don't fail when starting up with a nonexistent DataDirectory
3118 and a ControlPortWriteToFile setting based on that directory. Fixes
3119 bug 3747; bugfix on Tor 0.2.2.26-beta.
3122 - Added a new CONF_CHANGED event so that controllers can be notified
3123 of any configuration changes made by other controllers, or by the
3124 user. Implements ticket 1692.
3125 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
3126 leak when using bufferevents, and lets Libevent worry about how to
3127 best copy data out of a buffer.
3128 - Replace files in stats/ rather than appending to them. Now that we
3129 include statistics in extra-info descriptors, it makes no sense to
3130 keep old statistics forever. Implements ticket 2930.
3132 o Minor features (build compatibility):
3133 - Limited, experimental support for building with nmake and MSVC.
3134 - Provide a substitute implementation of lround() for MSVC, which
3135 apparently lacks it. Patch from Gisle Vanem.
3137 o Minor features (also part of 0.2.2.31-rc):
3138 - Update to the August 2 2011 Maxmind GeoLite Country database.
3140 o Minor bugfixes (on 0.2.3.x-alpha):
3141 - Fix a spurious warning when parsing SOCKS requests with
3142 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
3143 - Get rid of a harmless warning that could happen on relays running
3144 with bufferevents. The warning was caused by someone doing an http
3145 request to a relay's orport. Also don't warn for a few related
3146 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
3148 o Minor bugfixes (on 2.2.x and earlier):
3149 - Correct the man page to explain that HashedControlPassword and
3150 CookieAuthentication can both be set, in which case either method
3151 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3152 when we decided to allow these config options to both be set. Issue
3154 - The "--quiet" and "--hush" options now apply not only to Tor's
3155 behavior before logs are configured, but also to Tor's behavior in
3156 the absense of configured logs. Fixes bug 3550; bugfix on
3159 o Minor bugfixes (also part of 0.2.2.31-rc):
3160 - Write several files in text mode, on OSes that distinguish text
3161 mode from binary mode (namely, Windows). These files are:
3162 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3163 that collect those statistics; 'client_keys' and 'hostname' for
3164 hidden services that use authentication; and (in the tor-gencert
3165 utility) newly generated identity and signing keys. Previously,
3166 we wouldn't specify text mode or binary mode, leading to an
3167 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3168 the DirRecordUsageByCountry option which would have triggered
3169 the assertion failure was added), although this assertion failure
3170 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3171 - Selectively disable deprecation warnings on OS X because Lion
3172 started deprecating the shipped copy of openssl. Fixes bug 3643.
3173 - Remove an extra pair of quotation marks around the error
3174 message in control-port STATUS_GENERAL BUG events. Bugfix on
3175 0.1.2.6-alpha; fixes bug 3732.
3176 - When unable to format an address as a string, report its value
3177 as "???" rather than reusing the last formatted address. Bugfix
3180 o Code simplifications and refactoring:
3181 - Rewrite the listener-selection logic so that parsing which ports
3182 we want to listen on is now separate from binding to the ports
3186 - Building Tor with bufferevent support now requires Libevent
3187 2.0.13-stable or later. Previous versions of Libevent had bugs in
3188 SSL-related bufferevents and related issues that would make Tor
3189 work badly with bufferevents. Requiring 2.0.13-stable also allows
3190 Tor with bufferevents to take advantage of Libevent APIs
3191 introduced after 2.0.8-rc.
3194 Changes in version 0.2.2.32 - 2011-08-27
3195 The Tor 0.2.2 release series is dedicated to the memory of Andreas
3196 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
3197 a founder of the PETS community, a leader in our field, a mentor,
3198 and a friend. He left us with these words: "I had the possibility
3199 to contribute to this world that is not as it should be. I hope I
3200 could help in some areas to make the world a better place, and that
3201 I could also encourage other people to be engaged in improving the
3202 world. Please, stay engaged. This world needs you, your love, your
3203 initiative -- now I cannot be part of that anymore."
3205 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
3206 ready. More than two years in the making, this release features improved
3207 client performance and hidden service reliability, better compatibility
3208 for Android, correct behavior for bridges that listen on more than
3209 one address, more extensible and flexible directory object handling,
3210 better reporting of network statistics, improved code security, and
3211 many many other features and bugfixes.
3214 Changes in version 0.2.2.31-rc - 2011-08-17
3215 Tor 0.2.2.31-rc is the second and hopefully final release candidate
3216 for the Tor 0.2.2.x series.
3219 - Remove an extra pair of quotation marks around the error
3220 message in control-port STATUS_GENERAL BUG events. Bugfix on
3221 0.1.2.6-alpha; fixes bug 3732.
3222 - If we're configured to write our ControlPorts to disk, only write
3223 them after switching UID and creating the data directory. This way,
3224 we don't fail when starting up with a nonexistent DataDirectory
3225 and a ControlPortWriteToFile setting based on that directory. Fixes
3226 bug 3747; bugfix on Tor 0.2.2.26-beta.
3229 - Update to the August 2 2011 Maxmind GeoLite Country database.
3232 - Allow GETINFO fingerprint to return a fingerprint even when
3233 we have not yet built a router descriptor. Fixes bug 3577;
3234 bugfix on 0.2.0.1-alpha.
3235 - Write several files in text mode, on OSes that distinguish text
3236 mode from binary mode (namely, Windows). These files are:
3237 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3238 that collect those statistics; 'client_keys' and 'hostname' for
3239 hidden services that use authentication; and (in the tor-gencert
3240 utility) newly generated identity and signing keys. Previously,
3241 we wouldn't specify text mode or binary mode, leading to an
3242 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3243 the DirRecordUsageByCountry option which would have triggered
3244 the assertion failure was added), although this assertion failure
3245 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3246 - Selectively disable deprecation warnings on OS X because Lion
3247 started deprecating the shipped copy of openssl. Fixes bug 3643.
3248 - When unable to format an address as a string, report its value
3249 as "???" rather than reusing the last formatted address. Bugfix
3253 Changes in version 0.2.3.2-alpha - 2011-07-18
3254 Tor 0.2.3.2-alpha introduces two new experimental features:
3255 microdescriptors and pluggable transports. It also continues cleaning
3256 up a variety of recently introduced features.
3259 - Clients can now use microdescriptors instead of regular descriptors
3260 to build circuits. Microdescriptors are authority-generated
3261 summaries of regular descriptors' contents, designed to change
3262 very rarely (see proposal 158 for details). This feature is
3263 designed to save bandwidth, especially for clients on slow internet
3264 connections. It's off by default for now, since nearly no caches
3265 support it, but it will be on-by-default for clients in a future
3266 version. You can use the UseMicrodescriptors option to turn it on.
3267 - Tor clients using bridges can now be configured to use a separate
3268 'transport' proxy for each bridge. This approach helps to resist
3269 censorship by allowing bridges to use protocol obfuscation
3270 plugins. It implements part of proposal 180. Implements ticket 2841.
3271 - While we're trying to bootstrap, record how many TLS connections
3272 fail in each state, and report which states saw the most failures
3273 in response to any bootstrap failures. This feature may speed up
3274 diagnosis of censorship events. Implements ticket 3116.
3276 o Major bugfixes (on 0.2.3.1-alpha):
3277 - When configuring a large set of nodes in EntryNodes (as with
3278 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
3279 random subset to be guards, and choose them in random
3280 order. Fixes bug 2798.
3281 - Tor could crash when remembering a consensus in a non-used consensus
3282 flavor without having a current consensus set. Fixes bug 3361.
3283 - Comparing an unknown address to a microdescriptor's shortened exit
3284 policy would always give a "rejected" result. Fixes bug 3599.
3285 - Using microdescriptors as a client no longer prevents Tor from
3286 uploading and downloading hidden service descriptors. Fixes
3290 - Allow nameservers with IPv6 address. Resolves bug 2574.
3291 - Accept attempts to include a password authenticator in the
3292 handshake, as supported by SOCKS5. This handles SOCKS clients that
3293 don't know how to omit a password when authenticating. Resolves
3295 - When configuring a large set of nodes in EntryNodes, and there are
3296 enough of them listed as Guard so that we don't need to consider
3297 the non-guard entries, prefer the ones listed with the Guard flag.
3298 - Check for and recover from inconsistency in the microdescriptor
3299 cache. This will make it harder for us to accidentally free a
3300 microdescriptor without removing it from the appropriate data
3301 structures. Fixes issue 3135; issue noted by "wanoskarnet".
3302 - Log SSL state transitions at log level DEBUG, log domain
3303 HANDSHAKE. This can be useful for debugging censorship events.
3304 Implements ticket 3264.
3305 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
3306 implements ticket 3439.
3308 o Minor bugfixes (on 0.2.3.1-alpha):
3309 - Do not free all general-purpose regular descriptors just
3310 because microdescriptor use is enabled. Fixes bug 3113.
3311 - Correctly link libevent_openssl when --enable-static-libevent
3312 is passed to configure. Fixes bug 3118.
3313 - Bridges should not complain during their heartbeat log messages that
3314 they are unlisted in the consensus: that's more or less the point
3315 of being a bridge. Fixes bug 3183.
3316 - Report a SIGNAL event to controllers when acting on a delayed
3317 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
3318 event to the controller if we acted on a SIGNAL NEWNYM command
3319 immediately, and otherwise not report a SIGNAL event for the
3320 command at all. Fixes bug 3349.
3321 - Fix a crash when handling the SIGNAL controller command or
3322 reporting ERR-level status events with bufferevents enabled. Found
3323 by Robert Ransom. Fixes bug 3367.
3324 - Always ship the tor-fw-helper manpage in our release tarballs.
3325 Fixes bug 3389. Reported by Stephen Walker.
3326 - Fix a class of double-mark-for-close bugs when bufferevents
3327 are enabled. Fixes bug 3403.
3328 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
3329 - Add SIGNAL to the list returned by the 'GETINFO events/names'
3330 control-port command. Fixes part of bug 3465.
3331 - Prevent using negative indices during unit test runs when read_all()
3332 fails. Spotted by coverity.
3333 - Fix a rare memory leak when checking the nodelist without it being
3334 present. Found by coverity.
3335 - Only try to download a microdescriptor-flavored consensus from
3336 a directory cache that provides them.
3338 o Minor bugfixes (on 0.2.2.x and earlier):
3339 - Assert that hidden-service-related operations are not performed
3340 using single-hop circuits. Previously, Tor would assert that
3341 client-side streams are not attached to single-hop circuits,
3342 but not that other sensitive operations on the client and service
3343 side are not performed using single-hop circuits. Fixes bug 3332;
3345 - Don't publish a new relay descriptor when we reload our onion key,
3346 unless the onion key has actually changed. Fixes bug 3263 and
3347 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
3348 - Allow GETINFO fingerprint to return a fingerprint even when
3349 we have not yet built a router descriptor. Fixes bug 3577;
3350 bugfix on 0.2.0.1-alpha.
3351 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
3352 on 0.2.2.4-alpha; fixes bug 3427.
3354 o Code simplification and refactoring:
3355 - Use tor_sscanf() in place of scanf() in more places through the
3356 code. This makes us a little more locale-independent, and
3357 should help shut up code-analysis tools that can't tell
3358 a safe sscanf string from a dangerous one.
3359 - Use tt_assert(), not tor_assert(), for checking for test failures.
3360 This makes the unit tests more able to go on in the event that
3362 - Split connection_about_to_close() into separate functions for each
3366 - On Windows, we now define the _WIN32_WINNT macros only if they
3367 are not already defined. This lets the person building Tor decide,
3368 if they want, to require a later version of Windows.
3371 Changes in version 0.2.2.30-rc - 2011-07-07
3372 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
3373 series. It fixes a few smaller bugs, but generally appears stable.
3374 Please test it and let us know whether it is!
3377 - Send a SUCCEEDED stream event to the controller when a reverse
3378 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
3379 discovered by katmagic.
3380 - Always NUL-terminate the sun_path field of a sockaddr_un before
3381 passing it to the kernel. (Not a security issue: kernels are
3382 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3383 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3384 - Don't stack-allocate the list of supplementary GIDs when we're
3385 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3386 could take up to 256K, which is way too much stack. Found by
3387 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3388 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
3389 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
3390 fixes part of bug 3465.
3391 - Fix a memory leak when receiving a descriptor for a hidden
3392 service we didn't ask for. Found by Coverity; CID #30. Bugfix
3396 - Update to the July 1 2011 Maxmind GeoLite Country database.
3399 Changes in version 0.2.2.29-beta - 2011-06-20
3400 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
3401 have bridge lines in their torrc but don't want to use them; gets
3402 us closer to having the control socket feature working on Debian;
3403 and fixes a variety of smaller bugs.
3406 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
3407 When we changed the default behavior to "use bridges if any
3408 are listed in the torrc", we surprised users who had bridges
3409 in their torrc files but who didn't actually want to use them.
3410 Partial resolution for bug 3354.
3413 - Don't attach new streams to old rendezvous circuits after SIGNAL
3414 NEWNYM. Previously, we would keep using an existing rendezvous
3415 circuit if it remained open (i.e. if it were kept open by a
3416 long-lived stream, or if a new stream were attached to it before
3417 Tor could notice that it was old and no longer in use). Bugfix on
3418 0.1.1.15-rc; fixes bug 3375.
3421 - Fix a bug when using ControlSocketsGroupWritable with User. The
3422 directory's group would be checked against the current group, not
3423 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
3424 bugfix on 0.2.2.26-beta.
3425 - Make connection_printf_to_buf()'s behaviour sane. Its callers
3426 expect it to emit a CRLF iff the format string ends with CRLF;
3427 it actually emitted a CRLF iff (a) the format string ended with
3428 CRLF or (b) the resulting string was over 1023 characters long or
3429 (c) the format string did not end with CRLF *and* the resulting
3430 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
3431 fixes part of bug 3407.
3432 - Make send_control_event_impl()'s behaviour sane. Its callers
3433 expect it to always emit a CRLF at the end of the string; it
3434 might have emitted extra control characters as well. Bugfix on
3435 0.1.1.9-alpha; fixes another part of bug 3407.
3436 - Make crypto_rand_int() check the value of its input correctly.
3437 Previously, it accepted values up to UINT_MAX, but could return a
3438 negative number if given a value above INT_MAX+1. Found by George
3439 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
3440 - Avoid a segfault when reading a malformed circuit build state
3441 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
3443 - When asked about a DNS record type we don't support via a
3444 client DNSPort, reply with NOTIMPL rather than an empty
3445 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
3446 - Fix a rare memory leak during stats writing. Found by coverity.
3449 - Update to the June 1 2011 Maxmind GeoLite Country database.
3451 o Code simplifications and refactoring:
3452 - Remove some dead code as indicated by coverity.
3453 - Remove a few dead assignments during router parsing. Found by
3455 - Add some forgotten return value checks during unit tests. Found
3457 - Don't use 1-bit wide signed bit fields. Found by coverity.
3460 Changes in version 0.2.2.28-beta - 2011-06-04
3461 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
3462 fixed a big bug in whether relays stay in the consensus consistently,
3463 we moved closer to handling bridges and hidden services correctly,
3464 and we started the process of better handling the dreaded "my Vidalia
3465 died, and now my Tor demands a password when I try to reconnect to it"
3469 - Don't decide to make a new descriptor when receiving a HUP signal.
3470 This bug has caused a lot of 0.2.2.x relays to disappear from the
3471 consensus periodically. Fixes the most common case of triggering
3472 bug 1810; bugfix on 0.2.2.7-alpha.
3473 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
3474 - Don't try to build descriptors if "ORPort auto" is set and we
3475 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
3477 - Resolve a crash that occurred when setting BridgeRelay to 1 with
3478 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
3479 - Apply circuit timeouts to opened hidden-service-related circuits
3480 based on the correct start time. Previously, we would apply the
3481 circuit build timeout based on time since the circuit's creation;
3482 it was supposed to be applied based on time since the circuit
3483 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
3484 - Use the same circuit timeout for client-side introduction
3485 circuits as for other four-hop circuits, rather than the timeout
3486 for single-hop directory-fetch circuits; the shorter timeout may
3487 have been appropriate with the static circuit build timeout in
3488 0.2.1.x and earlier, but caused many hidden service access attempts
3489 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
3490 on 0.2.2.2-alpha; fixes another part of bug 1297.
3491 - In ticket 2511 we fixed a case where you could use an unconfigured
3492 bridge if you had configured it as a bridge the last time you ran
3493 Tor. Now fix another edge case: if you had configured it as a bridge
3494 but then switched to a different bridge via the controller, you
3495 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
3499 - Add an __OwningControllerProcess configuration option and a
3500 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
3501 that when it exits, Tor will shut down. Implements feature 3049.
3502 - If "UseBridges 1" is set and no bridges are configured, Tor will
3503 now refuse to build any circuits until some bridges are set.
3504 If "UseBridges auto" is set, Tor will use bridges if they are
3505 configured and we are not running as a server, but otherwise will
3506 make circuits as usual. The new default is "auto". Patch by anonym,
3507 so the Tails LiveCD can stop automatically revealing you as a Tor
3511 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3512 - Remove a trailing asterisk from "exit-policy/default" in the
3513 output of the control port command "GETINFO info/names". Bugfix
3515 - Use a wide type to hold sockets when built for 64-bit Windows builds.
3517 - Warn when the user configures two HiddenServiceDir lines that point
3518 to the same directory. Bugfix on 0.0.6 (the version introducing
3519 HiddenServiceDir); fixes bug 3289.
3520 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
3521 part of bug 2748; bugfix on 0.2.0.10-alpha.
3522 - Log malformed requests for rendezvous descriptors as protocol
3523 warnings, not warnings. Also, use a more informative log message
3524 in case someone sees it at log level warning without prior
3525 info-level messages. Fixes the other part of bug 2748; bugfix
3527 - Clear the table recording the time of the last request for each
3528 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
3529 Previously, we would clear our HS descriptor cache on SIGNAL
3530 NEWNYM, but if we had previously retrieved a descriptor (or tried
3531 to) from every directory responsible for it, we would refuse to
3532 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
3534 - Fix a log message that said "bits" while displaying a value in
3535 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
3537 - When checking for 1024-bit keys, check for 1024 bits, not 128
3538 bytes. This allows Tor to correctly discard keys of length 1017
3539 through 1023. Bugfix on 0.0.9pre5.
3542 - Relays now log the reason for publishing a new relay descriptor,
3543 so we have a better chance of hunting down instances of bug 1810.
3544 Resolves ticket 3252.
3545 - Revise most log messages that refer to nodes by nickname to
3546 instead use the "$key=nickname at address" format. This should be
3547 more useful, especially since nicknames are less and less likely
3548 to be unique. Resolves ticket 3045.
3549 - Log (at info level) when purging pieces of hidden-service-client
3550 state because of SIGNAL NEWNYM.
3553 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3554 anything since 0.2.1.16-rc.
3557 Changes in version 0.2.2.27-beta - 2011-05-18
3558 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
3559 release, and also adds a few more general bugfixes.
3562 - Fix a crash bug when changing bridges in a running Tor process.
3563 Fixes bug 3213; bugfix on 0.2.2.26-beta.
3564 - When the controller configures a new bridge, don't wait 10 to 60
3565 seconds before trying to fetch its descriptor. Bugfix on
3566 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3569 - Require that onion keys have exponent 65537 in microdescriptors too.
3570 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
3571 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
3572 Changed the limit to 512 characters by removing base64 newlines.
3573 Fixes bug 2752. Fix by Michael Yakubovich.
3574 - When a client starts or stops using bridges, never use a circuit
3575 that was built before the configuration change. This behavior could
3576 put at risk a user who uses bridges to ensure that her traffic
3577 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3581 Changes in version 0.2.2.26-beta - 2011-05-17
3582 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
3583 also introduces a new "socksport auto" approach that should make it
3584 easier to run multiple Tors on the same system, and does a lot of
3585 cleanup to get us closer to a release candidate.
3587 o Security/privacy fixes:
3588 - Replace all potentially sensitive memory comparison operations
3589 with versions whose runtime does not depend on the data being
3590 compared. This will help resist a class of attacks where an
3591 adversary can use variations in timing information to learn
3592 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3593 implementation by Robert Ransom based partially on code by DJB.)
3594 - When receiving a hidden service descriptor, check that it is for
3595 the hidden service we wanted. Previously, Tor would store any
3596 hidden service descriptors that a directory gave it, whether it
3597 wanted them or not. This wouldn't have let an attacker impersonate
3598 a hidden service, but it did let directories pre-seed a client
3599 with descriptors that it didn't want. Bugfix on 0.0.6.
3600 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3601 DNS cache entries, and virtual address mappings: that's what
3602 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3605 - The options SocksPort, ControlPort, and so on now all accept a
3606 value "auto" that opens a socket on an OS-selected port. A
3607 new ControlPortWriteToFile option tells Tor to write its
3608 actual control port or ports to a chosen file. If the option
3609 ControlPortFileGroupReadable is set, the file is created as
3610 group-readable. Now users can run two Tor clients on the same
3611 system without needing to manually mess with parameters. Resolves
3612 part of ticket 3076.
3613 - Set SO_REUSEADDR on all sockets, not just listeners. This should
3614 help busy exit nodes avoid running out of useable ports just
3615 because all the ports have been used in the near past. Resolves
3619 - New "GETINFO net/listeners/(type)" controller command to return
3620 a list of addresses and ports that are bound for listeners for a
3621 given connection type. This is useful when the user has configured
3622 "SocksPort auto" and the controller needs to know which port got
3623 chosen. Resolves another part of ticket 3076.
3624 - Add a new ControlSocketsGroupWritable configuration option: when
3625 it is turned on, ControlSockets are group-writeable by the default
3626 group of the current user. Patch by Jérémy Bobbio; implements
3628 - Tor now refuses to create a ControlSocket in a directory that is
3629 world-readable (or group-readable if ControlSocketsGroupWritable
3630 is 0). This is necessary because some operating systems do not
3631 enforce permissions on an AF_UNIX sockets. Permissions on the
3632 directory holding the socket, however, seems to work everywhere.
3633 - Rate-limit a warning about failures to download v2 networkstatus
3634 documents. Resolves part of bug 1352.
3635 - Backport code from 0.2.3.x that allows directory authorities to
3636 clean their microdescriptor caches. Needed to resolve bug 2230.
3637 - When an HTTPS proxy reports "403 Forbidden", we now explain
3638 what it means rather than calling it an unexpected status code.
3639 Closes bug 2503. Patch from Michael Yakubovich.
3640 - Update to the May 1 2011 Maxmind GeoLite Country database.
3643 - Authorities now clean their microdesc cache periodically and when
3644 reading from disk initially, not only when adding new descriptors.
3645 This prevents a bug where we could lose microdescriptors. Bugfix
3646 on 0.2.2.6-alpha. Fixes bug 2230.
3647 - Do not crash when our configuration file becomes unreadable, for
3648 example due to a permissions change, between when we start up
3649 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3651 - Avoid a bug that would keep us from replacing a microdescriptor
3652 cache on Windows. (We would try to replace the file while still
3653 holding it open. That's fine on Unix, but Windows doesn't let us
3654 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
3655 - Add missing explanations for the authority-related torrc options
3656 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
3657 man page. Resolves issue 2379.
3658 - As an authority, do not upload our own vote or signature set to
3659 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
3660 it would get flagged as a duplicate. Resolves bug 3026.
3661 - Accept hidden service descriptors if we think we might be a hidden
3662 service directory, regardless of what our consensus says. This
3663 helps robustness, since clients and hidden services can sometimes
3664 have a more up-to-date view of the network consensus than we do,
3665 and if they think that the directory authorities list us a HSDir,
3666 we might actually be one. Related to bug 2732; bugfix on
3668 - When a controller changes TrackHostExits, remove mappings for
3669 hosts that should no longer have their exits tracked. Bugfix on
3671 - When a controller changes VirtualAddrNetwork, remove any mappings
3672 for hosts that were automapped to the old network. Bugfix on
3674 - When a controller changes one of the AutomapHosts* options, remove
3675 any mappings for hosts that should no longer be automapped. Bugfix
3677 - Do not reset the bridge descriptor download status every time we
3678 re-parse our configuration or get a configuration change. Fixes
3679 bug 3019; bugfix on 0.2.0.3-alpha.
3681 o Minor bugfixes (code cleanup):
3682 - When loading the microdesc journal, remember its current size.
3683 In 0.2.2, this helps prevent the microdesc journal from growing
3684 without limit on authorities (who are the only ones to use it in
3685 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3686 Fix posted by "cypherpunks."
3687 - The microdesc journal is supposed to get rebuilt only if it is
3688 at least _half_ the length of the store, not _twice_ the length
3689 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3690 - Fix a potential null-pointer dereference while computing a
3691 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3693 - Avoid a possible null-pointer dereference when rebuilding the mdesc
3694 cache without actually having any descriptors to cache. Bugfix on
3695 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
3696 - If we fail to compute the identity digest of a v3 legacy keypair,
3697 warn, and don't use a buffer-full of junk instead. Bugfix on
3698 0.2.1.1-alpha; fixes bug 3106.
3699 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3700 where if the function had ever in the future been used to check
3701 for the presence of a too-large number, it would have given an
3702 incorrect result. (Fortunately, we only used it for 16-bit
3703 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3704 - Require that introduction point keys and onion handshake keys
3705 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3709 - Caches no longer download and serve v2 networkstatus documents
3710 unless FetchV2Networkstatus flag is set: these documents haven't
3711 haven't been used by clients or relays since 0.2.0.x. Resolves
3715 Changes in version 0.2.3.1-alpha - 2011-05-05
3716 Tor 0.2.3.1-alpha adds some new experimental features, including support
3717 for an improved network IO backend, IOCP networking on Windows,
3718 microdescriptor caching, "fast-start" support for streams, and automatic
3719 home router configuration. There are also numerous internal improvements
3720 to try to make the code easier for developers to work with.
3722 This is the first alpha release in a new series, so expect there to be
3723 bugs. Users who would rather test out a more stable branch should
3724 stay with 0.2.2.x for now.
3727 - Tor can now optionally build with the "bufferevents" buffered IO
3728 backend provided by Libevent 2. To use this feature, make sure you
3729 have the latest possible version of Libevent, and pass the
3730 --enable-bufferevents flag to configure when building Tor from
3731 source. This feature will make our networking code more flexible,
3732 let us stack layers on each other, and let us use more efficient
3733 zero-copy transports where available.
3734 - As an experimental feature, Tor can use IOCP for networking on Windows.
3735 Once this code is tuned and optimized, it promises much better
3736 performance than the select-based backend we've used in the past. To
3737 try this feature, you must build Tor with Libevent 2, configure Tor
3738 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
3739 your torrc. There are known bugs here: only try this if you can help
3740 debug it as it breaks.
3741 - The EntryNodes option can now include country codes like {de} or IP
3742 addresses or network masks. Previously we had disallowed these options
3743 because we didn't have an efficient way to keep the list up to
3744 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
3745 - Exit nodes now accept and queue data on not-yet-connected streams.
3746 Previously, the client wasn't allowed to send data until the stream was
3747 connected, which slowed down all connections. This change will enable
3748 clients to perform a "fast-start" on streams and send data without
3749 having to wait for a confirmation that the stream has opened. (Patch
3750 from Ian Goldberg; implements the server side of Proposal 174.)
3751 - Tor now has initial support for automatic port mapping on the many
3752 home routers that support NAT-PMP or UPnP. (Not yet supported on
3753 Windows). To build the support code, you'll need to have libnatpnp
3754 library and/or the libminiupnpc library, and you'll need to enable the
3755 feature specifically by passing "--enable-upnp" and/or
3756 "--enable-natpnp" to configure. To turn it on, use the new
3757 PortForwarding option.
3758 - Caches now download, cache, and serve multiple "flavors" of the
3759 consensus, including a flavor that describes microdescriptors.
3760 - Caches now download, cache, and serve microdescriptors -- small
3761 summaries of router descriptors that are authenticated by all of the
3762 directory authorities. Once enough caches are running this code,
3763 clients will be able to save significant amounts of directory bandwidth
3764 by downloading microdescriptors instead of router descriptors.
3767 - Make logging resolution configurable with a new LogTimeGranularity
3768 option, and change the default from 1 millisecond to 1 second.
3769 Implements enhancement 1668.
3770 - We log which torrc file we're using on startup. Implements ticket
3772 - Ordinarily, Tor does not count traffic from private addresses (like
3773 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
3774 There is now a new option, CountPrivateBandwidth, to disable this
3775 behavior. Patch from Daniel Cagara.
3776 - New --enable-static-tor configure option for building Tor as
3777 statically as possible. Idea, general hackery and thoughts from
3778 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3780 - If you set the NumCPUs option to 0, Tor will now try to detect how
3781 many CPUs you have. This is the new default behavior.
3782 - Turn on directory request statistics by default and include them in
3783 extra-info descriptors. Don't break if we have no GeoIP database.
3784 - Relays that set "ConnDirectionStatistics 1" write statistics on the
3785 bidirectional use of connections to disk every 24 hours.
3786 - Add a GeoIP file digest to the extra-info descriptor. Implements
3788 - The NodeFamily option -- which let you declare that you want to
3789 consider nodes to be part of a family whether they list themselves
3790 that way or not -- now allows IP address ranges and country codes.
3791 - Add a new 'Heartbeat' log message type to periodically log a message
3792 describing Tor's status at level Notice. This feature is meant for
3793 operators who log at notice, and want to make sure that their Tor
3794 server is still working. Implementation by George Kadianakis.
3796 o Minor bugfixes (on 0.2.2.25-alpha):
3797 - When loading the microdesc journal, remember its current size.
3798 In 0.2.2, this helps prevent the microdesc journal from growing
3799 without limit on authorities (who are the only ones to use it in
3800 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3801 Fix posted by "cypherpunks."
3802 - The microdesc journal is supposed to get rebuilt only if it is
3803 at least _half_ the length of the store, not _twice_ the length
3804 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3805 - If as an authority we fail to compute the identity digest of a v3
3806 legacy keypair, warn, and don't use a buffer-full of junk instead.
3807 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
3808 - Authorities now clean their microdesc cache periodically and when
3809 reading from disk initially, not only when adding new descriptors.
3810 This prevents a bug where we could lose microdescriptors. Bugfix
3813 o Minor features (controller):
3814 - Add a new SIGNAL event to the controller interface so that
3815 controllers can be notified when Tor handles a signal. Resolves
3816 issue 1955. Patch by John Brooks.
3817 - Add a new GETINFO option to get total bytes read and written. Patch
3818 from pipe, revised by atagar. Resolves ticket 2345.
3819 - Implement some GETINFO controller fields to provide information about
3820 the Tor process's pid, euid, username, and resource limits.
3823 - Our build system requires automake 1.6 or later to create the
3824 Makefile.in files. Previously, you could have used 1.4.
3825 This only affects developers and people building Tor from git;
3826 people who build Tor from the source distribution without changing
3827 the Makefile.am files should be fine.
3828 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
3829 so on. This is more robust against some of the failure modes
3830 associated with running the autotools pieces on their own.
3832 o Minor packaging issues:
3833 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
3834 already created. Patch from Andreas Stieger. Fixes bug 2573.
3836 o Code simplifications and refactoring:
3837 - A major revision to our internal node-selecting and listing logic.
3838 Tor already had at least two major ways to look at the question of
3839 "which Tor servers do we know about": a list of router descriptors,
3840 and a list of entries in the current consensus. With
3841 microdescriptors, we're adding a third. Having so many systems
3842 without an abstraction layer over them was hurting the codebase.
3843 Now, we have a new "node_t" abstraction that presents a consistent
3844 interface to a client's view of a Tor node, and holds (nearly) all
3845 of the mutable state formerly in routerinfo_t and routerstatus_t.
3846 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3847 no longer link against Libevent: they never used it, but
3848 our library structure used to force them to link it.
3851 - Remove some old code to work around even older versions of Tor that
3852 used forked processes to handle DNS requests. Such versions of Tor
3853 are no longer in use as servers.
3855 o Documentation fixes:
3856 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3857 - Add missing documentation for the authority-related torrc options
3858 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
3862 Changes in version 0.2.2.25-alpha - 2011-04-29
3863 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
3864 robust, routers no longer overreport their bandwidth, Win7 should crash
3865 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
3866 now prevents hidden service-related activity from being linkable. It
3867 provides more information to Vidalia so you can see if your bridge is
3868 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
3869 StrictNodes configuration options to make them more reliable, more
3870 understandable, and more regularly applied. If you use those options,
3871 please see the revised documentation for them in the manual page.
3874 - Relays were publishing grossly inflated bandwidth values because
3875 they were writing their state files wrong--now they write the
3876 correct value. Also, resume reading bandwidth history from the
3877 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
3878 - Improve hidden service robustness: When we find that we have
3879 extended a hidden service's introduction circuit to a relay not
3880 listed as an introduction point in the HS descriptor we currently
3881 have, retry with an introduction point from the current
3882 descriptor. Previously we would just give up. Fixes bugs 1024 and
3883 1930; bugfix on 0.2.0.10-alpha.
3884 - Clients now stop trying to use an exit node associated with a given
3885 destination by TrackHostExits if they fail to reach that exit node.
3886 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3887 - Fix crash bug on platforms where gmtime and localtime can return
3888 NULL. Windows 7 users were running into this one. Fixes part of bug
3889 2077. Bugfix on all versions of Tor. Found by boboper.
3891 o Security and stability fixes:
3892 - Don't double-free a parsable, but invalid, microdescriptor, even if
3893 it is followed in the blob we're parsing by an unparsable
3894 microdescriptor. Fixes an issue reported in a comment on bug 2954.
3895 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
3896 - If the Nickname configuration option isn't given, Tor would pick a
3897 nickname based on the local hostname as the nickname for a relay.
3898 Because nicknames are not very important in today's Tor and the
3899 "Unnamed" nickname has been implemented, this is now problematic
3900 behavior: It leaks information about the hostname without being
3901 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3902 introduced the Unnamed nickname. Reported by tagnaq.
3903 - Fix an uncommon assertion failure when running with DNSPort under
3904 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3905 - Avoid linkability based on cached hidden service descriptors: forget
3906 all hidden service descriptors cached as a client when processing a
3907 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3910 - Export GeoIP information on bridge usage to controllers even if we
3911 have not yet been running for 24 hours. Now Vidalia bridge operators
3912 can get more accurate and immediate feedback about their
3913 contributions to the network.
3915 o Major features and bugfixes (node selection):
3916 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3917 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
3918 options. Previously, we had been ambiguous in describing what
3919 counted as an "exit" node, and what operations exactly "StrictNodes
3920 0" would permit. This created confusion when people saw nodes built
3921 through unexpected circuits, and made it hard to tell real bugs from
3922 surprises. Now the intended behavior is:
3923 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3924 a node that delivers user traffic outside the Tor network.
3925 . "Entry", in the context of EntryNodes, means a node used as the
3926 first hop of a multihop circuit. It doesn't include direct
3927 connections to directory servers.
3928 . "ExcludeNodes" applies to all nodes.
3929 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3930 StrictNodes is set, Tor should avoid all nodes listed in
3931 ExcludeNodes, even when it will make user requests fail. When
3932 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3933 whenever it can, except when it must use an excluded node to
3934 perform self-tests, connect to a hidden service, provide a
3935 hidden service, fulfill a .exit request, upload directory
3936 information, or fetch directory information.
3937 Collectively, the changes to implement the behavior fix bug 1090.
3938 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3939 a node is listed in both, it's treated as excluded.
3940 - ExcludeNodes now applies to directory nodes -- as a preference if
3941 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3942 Don't exclude all the directory authorities and set StrictNodes to 1
3943 unless you really want your Tor to break.
3944 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3945 - ExcludeExitNodes now overrides .exit requests.
3946 - We don't use bridges listed in ExcludeNodes.
3947 - When StrictNodes is 1:
3948 . We now apply ExcludeNodes to hidden service introduction points
3949 and to rendezvous points selected by hidden service users. This
3950 can make your hidden service less reliable: use it with caution!
3951 . If we have used ExcludeNodes on ourself, do not try relay
3952 reachability self-tests.
3953 . If we have excluded all the directory authorities, we will not
3954 even try to upload our descriptor if we're a relay.
3955 . Do not honor .exit requests to an excluded node.
3956 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3957 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3958 - When the set of permitted nodes changes, we now remove any mappings
3959 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3961 - We never cannibalize a circuit that had excluded nodes on it, even
3962 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3963 - Revert a change where we would be laxer about attaching streams to
3964 circuits than when building the circuits. This was meant to prevent
3965 a set of bugs where streams were never attachable, but our improved
3966 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3967 - Keep track of how many times we launch a new circuit to handle a
3968 given stream. Too many launches could indicate an inconsistency
3969 between our "launch a circuit to handle this stream" logic and our
3970 "attach this stream to one of the available circuits" logic.
3971 - Improve log messages related to excluded nodes.
3974 - Fix a spurious warning when moving from a short month to a long
3975 month on relays with month-based BandwidthAccounting. Bugfix on
3976 0.2.2.17-alpha; fixes bug 3020.
3977 - When a client finds that an origin circuit has run out of 16-bit
3978 stream IDs, we now mark it as unusable for new streams. Previously,
3979 we would try to close the entire circuit. Bugfix on 0.0.6.
3980 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3981 Bugfix on 0.2.2.24-alpha.
3982 - Be more careful about reporting the correct error from a failed
3983 connect() system call. Under some circumstances, it was possible to
3984 look at an incorrect value for errno when sending the end reason.
3985 Bugfix on 0.1.0.1-rc.
3986 - Correctly handle an "impossible" overflow cases in connection byte
3987 counting, where we write or read more than 4GB on an edge connection
3988 in a single second. Bugfix on 0.1.2.8-beta.
3989 - Correct the warning displayed when a rendezvous descriptor exceeds
3990 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3992 - Clients and hidden services now use HSDir-flagged relays for hidden
3993 service descriptor downloads and uploads even if the relays have no
3994 DirPort set and the client has disabled TunnelDirConns. This will
3995 eventually allow us to give the HSDir flag to relays with no
3996 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3997 - Downgrade "no current certificates known for authority" message from
3998 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3999 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
4000 2917. Bugfix on 0.1.1.1-alpha.
4001 - Only limit the lengths of single HS descriptors, even when multiple
4002 HS descriptors are published to an HSDir relay in a single POST
4003 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4004 - Write the current time into the LastWritten line in our state file,
4005 rather than the time from the previous write attempt. Also, stop
4006 trying to use a time of -1 in our log statements. Fixes bug 3039;
4007 bugfix on 0.2.2.14-alpha.
4008 - Be more consistent in our treatment of file system paths. "~" should
4009 get expanded to the user's home directory in the Log config option.
4010 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4011 feature for the -f and --DataDirectory options.
4014 - Make sure every relay writes a state file at least every 12 hours.
4015 Previously, a relay could go for weeks without writing its state
4016 file, and on a crash could lose its bandwidth history, capacity
4017 estimates, client country statistics, and so on. Addresses bug 3012.
4018 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
4019 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
4020 clients are already deprecated because of security bugs.
4021 - Don't allow v0 hidden service authorities to act as clients.
4022 Required by fix for bug 3000.
4023 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
4024 by fix for bug 3000.
4025 - Ensure that no empty [dirreq-](read|write)-history lines are added
4026 to an extrainfo document. Implements ticket 2497.
4028 o Code simplification and refactoring:
4029 - Remove workaround code to handle directory responses from servers
4030 that had bug 539 (they would send HTTP status 503 responses _and_
4031 send a body too). Since only server versions before
4032 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
4033 keep the workaround in place.
4034 - Remove the old 'fuzzy time' logic. It was supposed to be used for
4035 handling calculations where we have a known amount of clock skew and
4036 an allowed amount of unknown skew. But we only used it in three
4037 places, and we never adjusted the known/unknown skew values. This is
4038 still something we might want to do someday, but if we do, we'll
4039 want to do it differently.
4040 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4041 None of the cases where we did this before were wrong, but by making
4042 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4043 - Use GetTempDir to find the proper temporary directory location on
4044 Windows when generating temporary files for the unit tests. Patch by
4048 Changes in version 0.2.2.24-alpha - 2011-04-08
4049 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
4050 prevented Tor clients from effectively using "multihomed" bridges,
4051 that is, bridges that listen on multiple ports or IP addresses so users
4052 can continue to use some of their addresses even if others get blocked.
4055 - Fix a bug where bridge users who configure the non-canonical
4056 address of a bridge automatically switch to its canonical
4057 address. If a bridge listens at more than one address, it should be
4058 able to advertise those addresses independently and any non-blocked
4059 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
4061 - If you configured Tor to use bridge A, and then quit and
4062 configured Tor to use bridge B instead, it would happily continue
4063 to use bridge A if it's still reachable. While this behavior is
4064 a feature if your goal is connectivity, in some scenarios it's a
4065 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
4066 - Directory authorities now use data collected from their own
4067 uptime observations when choosing whether to assign the HSDir flag
4068 to relays, instead of trusting the uptime value the relay reports in
4069 its descriptor. This change helps prevent an attack where a small
4070 set of nodes with frequently-changing identity keys can blackhole
4071 a hidden service. (Only authorities need upgrade; others will be
4072 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
4075 - When we restart our relay, we might get a successful connection
4076 from the outside before we've started our reachability tests,
4077 triggering a warning: "ORPort found reachable, but I have no
4078 routerinfo yet. Failing to inform controller of success." This
4079 bug was harmless unless Tor is running under a controller
4080 like Vidalia, in which case the controller would never get a
4081 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4083 - Make directory authorities more accurate at recording when
4084 relays that have failed several reachability tests became
4085 unreachable, so we can provide more accuracy at assigning Stable,
4086 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4087 - Fix an issue that prevented static linking of libevent on
4088 some platforms (notably Linux). Fixes bug 2698; bugfix on
4089 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
4090 the --with-static-libevent configure option).
4091 - We now ask the other side of a stream (the client or the exit)
4092 for more data on that stream when the amount of queued data on
4093 that stream dips low enough. Previously, we wouldn't ask the
4094 other side for more data until either it sent us more data (which
4095 it wasn't supposed to do if it had exhausted its window!) or we
4096 had completely flushed all our queued data. This flow control fix
4097 should improve throughput. Fixes bug 2756; bugfix on the earliest
4098 released versions of Tor (svn commit r152).
4099 - Avoid a double-mark-for-free warning when failing to attach a
4100 transparent proxy connection. (We thought we had fixed this in
4101 0.2.2.23-alpha, but it turns out our fix was checking the wrong
4102 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
4103 bug) and 0.2.2.23-alpha (the incorrect fix).
4104 - When warning about missing zlib development packages during compile,
4105 give the correct package names. Bugfix on 0.2.0.1-alpha.
4108 - Directory authorities now log the source of a rejected POSTed v3
4110 - Make compilation with clang possible when using
4111 --enable-gcc-warnings by removing two warning options that clang
4112 hasn't implemented yet and by fixing a few warnings. Implements
4114 - When expiring circuits, use microsecond timers rather than
4115 one-second timers. This can avoid an unpleasant situation where a
4116 circuit is launched near the end of one second and expired right
4117 near the beginning of the next, and prevent fluctuations in circuit
4119 - Use computed circuit-build timeouts to decide when to launch
4120 parallel introduction circuits for hidden services. (Previously,
4121 we would retry after 15 seconds.)
4122 - Update to the April 1 2011 Maxmind GeoLite Country database.
4125 - Create the /var/run/tor directory on startup on OpenSUSE if it is
4126 not already created. Patch from Andreas Stieger. Fixes bug 2573.
4128 o Documentation changes:
4129 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
4130 - Resolve all doxygen warnings except those for missing documentation.
4132 - Add doxygen documentation for more functions, fields, and types.
4135 Changes in version 0.2.2.23-alpha - 2011-03-08
4136 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
4137 they restart they don't lose their bandwidth capacity estimate. This
4138 release also fixes a diverse set of user-facing bugs, ranging from
4139 relays overrunning their rate limiting to clients falsely warning about
4140 clock skew to bridge descriptor leaks by our bridge directory authority.
4143 - Stop sending a CLOCK_SKEW controller status event whenever
4144 we fetch directory information from a relay that has a wrong clock.
4145 Instead, only inform the controller when it's a trusted authority
4146 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4147 the rest of bug 1074.
4148 - Fix an assert in parsing router descriptors containing IPv6
4149 addresses. This one took down the directory authorities when
4150 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4151 - Make the bridge directory authority refuse to answer directory
4152 requests for "all" descriptors. It used to include bridge
4153 descriptors in its answer, which was a major information leak.
4154 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4155 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4156 Tor would ignore their RelayBandwidthBurst setting,
4157 potentially using more bandwidth than expected. Bugfix on
4158 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4159 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4160 hidserv" in her torrc. The 'hidserv' argument never controlled
4161 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4164 - Relays now save observed peak bandwidth throughput rates to their
4165 state file (along with total usage, which was already saved)
4166 so that they can determine their correct estimated bandwidth on
4167 restart. Resolves bug 1863, where Tor relays would reset their
4168 estimated bandwidth to 0 after restarting.
4169 - Directory authorities now take changes in router IP address and
4170 ORPort into account when determining router stability. Previously,
4171 if a router changed its IP or ORPort, the authorities would not
4172 treat it as having any downtime for the purposes of stability
4173 calculation, whereas clients would experience downtime since the
4174 change could take a while to propagate to them. Resolves issue 1035.
4175 - Enable Address Space Layout Randomization (ASLR) and Data Execution
4176 Prevention (DEP) by default on Windows to make it harder for
4177 attackers to exploit vulnerabilities. Patch from John Brooks.
4179 o Minor bugfixes (on 0.2.1.x and earlier):
4180 - Fix a rare crash bug that could occur when a client was configured
4181 with a large number of bridges. Fixes bug 2629; bugfix on
4182 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4183 - Avoid a double mark-for-free warning when failing to attach a
4184 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
4186 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
4187 found by "cypherpunks". This bug was introduced before the first
4188 Tor release, in svn commit r110.
4189 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
4190 don't mention them in the manpage. Fixes bug 2450; issue
4191 spotted by keb and G-Lo.
4192 - Fix a bug in bandwidth history state parsing that could have been
4193 triggered if a future version of Tor ever changed the timing
4194 granularity at which bandwidth history is measured. Bugfix on
4196 - When a relay decides that its DNS is too broken for it to serve
4197 as an exit server, it advertised itself as a non-exit, but
4198 continued to act as an exit. This could create accidental
4199 partitioning opportunities for users. Instead, if a relay is
4200 going to advertise reject *:* as its exit policy, it should
4201 really act with exit policy "reject *:*". Fixes bug 2366.
4202 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
4203 - In the special case where you configure a public exit relay as your
4204 bridge, Tor would be willing to use that exit relay as the last
4205 hop in your circuit as well. Now we fail that circuit instead.
4206 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4207 - Fix a bug with our locking implementation on Windows that couldn't
4208 correctly detect when a file was already locked. Fixes bug 2504,
4209 bugfix on 0.2.1.6-alpha.
4210 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
4211 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
4213 - Set target port in get_interface_address6() correctly. Bugfix
4214 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
4215 - Directory authorities are now more robust to hops back in time
4216 when calculating router stability. Previously, if a run of uptime
4217 or downtime appeared to be negative, the calculation could give
4218 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
4220 - Fix an assert that got triggered when using the TestingTorNetwork
4221 configuration option and then issuing a GETINFO config-text control
4222 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
4224 o Minor bugfixes (on 0.2.2.x):
4225 - Clients should not weight BadExit nodes as Exits in their node
4226 selection. Similarly, directory authorities should not count BadExit
4227 bandwidth as Exit bandwidth when computing bandwidth-weights.
4228 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
4229 - Correctly clear our dir_read/dir_write history when there is an
4230 error parsing any bw history value from the state file. Bugfix on
4232 - Resolve a bug in verifying signatures of directory objects
4233 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
4234 Fixes bug 2409. Found by "piebeer".
4235 - Bridge authorities no longer crash on SIGHUP when they try to
4236 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
4240 - Log less aggressively about circuit timeout changes, and improve
4241 some other circuit timeout messages. Resolves bug 2004.
4242 - Log a little more clearly about the times at which we're no longer
4243 accepting new connections. Resolves bug 2181.
4244 - Reject attempts at the client side to open connections to private
4245 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
4246 a randomly chosen exit node. Attempts to do so are always
4247 ill-defined, generally prevented by exit policies, and usually
4248 in error. This will also help to detect loops in transparent
4249 proxy configurations. You can disable this feature by setting
4250 "ClientRejectInternalAddresses 0" in your torrc.
4251 - Always treat failure to allocate an RSA key as an unrecoverable
4253 - Update to the March 1 2011 Maxmind GeoLite Country database.
4255 o Minor features (log subsystem):
4256 - Add documentation for configuring logging at different severities in
4257 different log domains. We've had this feature since 0.2.1.1-alpha,
4258 but for some reason it never made it into the manpage. Fixes
4260 - Make it simpler to specify "All log domains except for A and B".
4261 Previously you needed to say "[*,~A,~B]". Now you can just say
4263 - Add a "LogMessageDomains 1" option to include the domains of log
4264 messages along with the messages. Without this, there's no way
4265 to use log domains without reading the source or doing a lot
4268 o Packaging changes:
4269 - Stop shipping the Tor specs files and development proposal documents
4270 in the tarball. They are now in a separate git repository at
4271 git://git.torproject.org/torspec.git
4274 Changes in version 0.2.1.30 - 2011-02-23
4275 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
4276 change is a slight tweak to Tor's TLS handshake that makes relays
4277 and bridges that run this new version reachable from Iran again.
4278 We don't expect this tweak will win the arms race long-term, but it
4279 buys us time until we roll out a better solution.
4282 - Stop sending a CLOCK_SKEW controller status event whenever
4283 we fetch directory information from a relay that has a wrong clock.
4284 Instead, only inform the controller when it's a trusted authority
4285 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4286 the rest of bug 1074.
4287 - Fix a bounds-checking error that could allow an attacker to
4288 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4290 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4291 Tor would ignore their RelayBandwidthBurst setting,
4292 potentially using more bandwidth than expected. Bugfix on
4293 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4294 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4295 hidserv" in her torrc. The 'hidserv' argument never controlled
4296 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4299 - Adjust our TLS Diffie-Hellman parameters to match those used by
4301 - Update to the February 1 2011 Maxmind GeoLite Country database.
4304 - Check for and reject overly long directory certificates and
4305 directory tokens before they have a chance to hit any assertions.
4306 Bugfix on 0.2.1.28. Found by "doorss".
4307 - Bring the logic that gathers routerinfos and assesses the
4308 acceptability of circuits into line. This prevents a Tor OP from
4309 getting locked in a cycle of choosing its local OR as an exit for a
4310 path (due to a .exit request) and then rejecting the circuit because
4311 its OR is not listed yet. It also prevents Tor clients from using an
4312 OR running in the same instance as an exit (due to a .exit request)
4313 if the OR does not meet the same requirements expected of an OR
4314 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4316 o Packaging changes:
4317 - Stop shipping the Tor specs files and development proposal documents
4318 in the tarball. They are now in a separate git repository at
4319 git://git.torproject.org/torspec.git
4320 - Do not include Git version tags as though they are SVN tags when
4321 generating a tarball from inside a repository that has switched
4322 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4325 Changes in version 0.2.2.22-alpha - 2011-01-25
4326 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
4327 main other change is a slight tweak to Tor's TLS handshake that makes
4328 relays and bridges that run this new version reachable from Iran again.
4329 We don't expect this tweak will win the arms race long-term, but it
4330 will buy us a bit more time until we roll out a better solution.
4333 - Fix a bounds-checking error that could allow an attacker to
4334 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4336 - Don't assert when changing from bridge to relay or vice versa
4337 via the controller. The assert happened because we didn't properly
4338 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
4339 bug 2433. Reported by bastik.
4342 - Adjust our TLS Diffie-Hellman parameters to match those used by
4344 - Provide a log message stating which geoip file we're parsing
4345 instead of just stating that we're parsing the geoip file.
4346 Implements ticket 2432.
4349 - Check for and reject overly long directory certificates and
4350 directory tokens before they have a chance to hit any assertions.
4351 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
4354 Changes in version 0.2.2.21-alpha - 2011-01-15
4355 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
4356 continues our recent code security audit work. The main fix resolves
4357 a remote heap overflow vulnerability that can allow remote code
4358 execution (CVE-2011-0427). Other fixes address a variety of assert
4359 and crash bugs, most of which we think are hard to exploit remotely.
4361 o Major bugfixes (security), also included in 0.2.1.29:
4362 - Fix a heap overflow bug where an adversary could cause heap
4363 corruption. This bug probably allows remote code execution
4364 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4366 - Prevent a denial-of-service attack by disallowing any
4367 zlib-compressed data whose compression factor is implausibly
4368 high. Fixes part of bug 2324; reported by "doorss".
4369 - Zero out a few more keys in memory before freeing them. Fixes
4370 bug 2384 and part of bug 2385. These key instances found by
4371 "cypherpunks", based on Andrew Case's report about being able
4372 to find sensitive data in Tor's memory space if you have enough
4373 permissions. Bugfix on 0.0.2pre9.
4375 o Major bugfixes (crashes), also included in 0.2.1.29:
4376 - Prevent calls to Libevent from inside Libevent log handlers.
4377 This had potential to cause a nasty set of crashes, especially
4378 if running Libevent with debug logging enabled, and running
4379 Tor with a controller watching for low-severity log messages.
4380 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4381 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4382 underflow errors there too. Fixes the other part of bug 2324.
4383 - Fix a bug where we would assert if we ever had a
4384 cached-descriptors.new file (or another file read directly into
4385 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4386 on 0.2.1.25. Found by doorss.
4387 - Fix some potential asserts and parsing issues with grossly
4388 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4391 o Minor bugfixes (other), also included in 0.2.1.29:
4392 - Fix a bug with handling misformed replies to reverse DNS lookup
4393 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4394 bug reported by doorss.
4395 - Fix compilation on mingw when a pthreads compatibility library
4396 has been installed. (We don't want to use it, so we shouldn't
4397 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4398 - Fix a bug where we would declare that we had run out of virtual
4399 addresses when the address space was only half-exhausted. Bugfix
4401 - Correctly handle the case where AutomapHostsOnResolve is set but
4402 no virtual addresses are available. Fixes bug 2328; bugfix on
4403 0.1.2.1-alpha. Bug found by doorss.
4404 - Correctly handle wrapping around when we run out of virtual
4405 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
4407 o Minor features, also included in 0.2.1.29:
4408 - Update to the January 1 2011 Maxmind GeoLite Country database.
4409 - Introduce output size checks on all of our decryption functions.
4411 o Build changes, also included in 0.2.1.29:
4412 - Tor does not build packages correctly with Automake 1.6 and earlier;
4413 added a check to Makefile.am to make sure that we're building with
4414 Automake 1.7 or later.
4415 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4416 because we built it with a too-old version of automake. Thus that
4417 release broke ./configure --enable-openbsd-malloc, which is popular
4418 among really fast exit relays on Linux.
4420 o Major bugfixes, new in 0.2.2.21-alpha:
4421 - Prevent crash/heap corruption when the cbtnummodes consensus
4422 parameter is set to 0 or large values. Fixes bug 2317; bugfix
4425 o Major features, new in 0.2.2.21-alpha:
4426 - Introduce minimum/maximum values that clients will believe
4427 from the consensus. Now we'll have a better chance to avoid crashes
4428 or worse when a consensus param has a weird value.
4430 o Minor features, new in 0.2.2.21-alpha:
4431 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
4432 used on bridges, and it makes bridge scanning somewhat easier.
4433 - If writing the state file to disk fails, wait up to an hour before
4434 retrying again, rather than trying again each second. Fixes bug
4435 2346; bugfix on Tor 0.1.1.3-alpha.
4436 - Make Libevent log messages get delivered to controllers later,
4437 and not from inside the Libevent log handler. This prevents unsafe
4438 reentrant Libevent calls while still letting the log messages
4440 - Detect platforms that brokenly use a signed size_t, and refuse to
4441 build there. Found and analyzed by doorss and rransom.
4442 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
4445 o Minor bugfixes, new in 0.2.2.21-alpha:
4446 - Handle SOCKS messages longer than 128 bytes long correctly, rather
4447 than waiting forever for them to finish. Fixes bug 2330; bugfix
4448 on 0.2.0.16-alpha. Found by doorss.
4449 - Add assertions to check for overflow in arguments to
4450 base32_encode() and base32_decode(); fix a signed-unsigned
4451 comparison there too. These bugs are not actually reachable in Tor,
4452 but it's good to prevent future errors too. Found by doorss.
4453 - Correctly detect failures to create DNS requests when using Libevent
4454 versions before v2. (Before Libevent 2, we used our own evdns
4455 implementation. Its return values for Libevent's evdns_resolve_*()
4456 functions are not consistent with those from Libevent.) Fixes bug
4457 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
4459 o Documentation, new in 0.2.2.21-alpha:
4460 - Document the default socks host and port (127.0.0.1:9050) for
4464 Changes in version 0.2.1.29 - 2011-01-15
4465 Tor 0.2.1.29 continues our recent code security audit work. The main
4466 fix resolves a remote heap overflow vulnerability that can allow remote
4467 code execution. Other fixes address a variety of assert and crash bugs,
4468 most of which we think are hard to exploit remotely.
4470 o Major bugfixes (security):
4471 - Fix a heap overflow bug where an adversary could cause heap
4472 corruption. This bug probably allows remote code execution
4473 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4475 - Prevent a denial-of-service attack by disallowing any
4476 zlib-compressed data whose compression factor is implausibly
4477 high. Fixes part of bug 2324; reported by "doorss".
4478 - Zero out a few more keys in memory before freeing them. Fixes
4479 bug 2384 and part of bug 2385. These key instances found by
4480 "cypherpunks", based on Andrew Case's report about being able
4481 to find sensitive data in Tor's memory space if you have enough
4482 permissions. Bugfix on 0.0.2pre9.
4484 o Major bugfixes (crashes):
4485 - Prevent calls to Libevent from inside Libevent log handlers.
4486 This had potential to cause a nasty set of crashes, especially
4487 if running Libevent with debug logging enabled, and running
4488 Tor with a controller watching for low-severity log messages.
4489 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4490 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4491 underflow errors there too. Fixes the other part of bug 2324.
4492 - Fix a bug where we would assert if we ever had a
4493 cached-descriptors.new file (or another file read directly into
4494 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4495 on 0.2.1.25. Found by doorss.
4496 - Fix some potential asserts and parsing issues with grossly
4497 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4500 o Minor bugfixes (other):
4501 - Fix a bug with handling misformed replies to reverse DNS lookup
4502 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4503 bug reported by doorss.
4504 - Fix compilation on mingw when a pthreads compatibility library
4505 has been installed. (We don't want to use it, so we shouldn't
4506 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4507 - Fix a bug where we would declare that we had run out of virtual
4508 addresses when the address space was only half-exhausted. Bugfix
4510 - Correctly handle the case where AutomapHostsOnResolve is set but
4511 no virtual addresses are available. Fixes bug 2328; bugfix on
4512 0.1.2.1-alpha. Bug found by doorss.
4513 - Correctly handle wrapping around to when we run out of virtual
4514 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
4515 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4516 because we built it with a too-old version of automake. Thus that
4517 release broke ./configure --enable-openbsd-malloc, which is popular
4518 among really fast exit relays on Linux.
4521 - Update to the January 1 2011 Maxmind GeoLite Country database.
4522 - Introduce output size checks on all of our decryption functions.
4525 - Tor does not build packages correctly with Automake 1.6 and earlier;
4526 added a check to Makefile.am to make sure that we're building with
4527 Automake 1.7 or later.
4530 Changes in version 0.2.2.20-alpha - 2010-12-17
4531 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
4532 exploitable bugs. We also fix a variety of other significant bugs,
4533 change the IP address for one of our directory authorities, and update
4534 the minimum version that Tor relays must run to join the network.
4537 - Fix a remotely exploitable bug that could be used to crash instances
4538 of Tor remotely by overflowing on the heap. Remote-code execution
4539 hasn't been confirmed, but can't be ruled out. Everyone should
4540 upgrade. Bugfix on the 0.1.1 series and later.
4541 - Fix a bug that could break accounting on 64-bit systems with large
4542 time_t values, making them hibernate for impossibly long intervals.
4543 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
4544 - Fix a logic error in directory_fetches_from_authorities() that
4545 would cause all _non_-exits refusing single-hop-like circuits
4546 to fetch from authorities, when we wanted to have _exits_ fetch
4547 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
4549 - Fix a stream fairness bug that would cause newer streams on a given
4550 circuit to get preference when reading bytes from the origin or
4551 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
4552 introduced before the first Tor release, in svn revision r152.
4554 o Directory authority changes:
4555 - Change IP address and ports for gabelmoo (v3 directory authority).
4558 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
4559 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
4560 - Fix an off-by-one error in calculating some controller command
4561 argument lengths. Fortunately, this mistake is harmless since
4562 the controller code does redundant NUL termination too. Found by
4563 boboper. Bugfix on 0.1.1.1-alpha.
4564 - Do not dereference NULL if a bridge fails to build its
4565 extra-info descriptor. Found by an anonymous commenter on
4566 Trac. Bugfix on 0.2.2.19-alpha.
4569 - Update to the December 1 2010 Maxmind GeoLite Country database.
4570 - Directory authorities now reject relays running any versions of
4571 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
4572 known bugs that keep RELAY_EARLY cells from working on rendezvous
4573 circuits. Followup to fix for bug 2081.
4574 - Directory authorities now reject relays running any version of Tor
4575 older than 0.2.0.26-rc. That version is the earliest that fetches
4576 current directory information correctly. Fixes bug 2156.
4577 - Report only the top 10 ports in exit-port stats in order not to
4578 exceed the maximum extra-info descriptor length of 50 KB. Implements
4582 Changes in version 0.2.1.28 - 2010-12-17
4583 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4584 exploitable bugs. We also took this opportunity to change the IP address
4585 for one of our directory authorities, and to update the geoip database
4589 - Fix a remotely exploitable bug that could be used to crash instances
4590 of Tor remotely by overflowing on the heap. Remote-code execution
4591 hasn't been confirmed, but can't be ruled out. Everyone should
4592 upgrade. Bugfix on the 0.1.1 series and later.
4594 o Directory authority changes:
4595 - Change IP address and ports for gabelmoo (v3 directory authority).
4598 - Update to the December 1 2010 Maxmind GeoLite Country database.
4601 Changes in version 0.2.1.27 - 2010-11-23
4602 Yet another OpenSSL security patch broke its compatibility with Tor:
4603 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4604 also took this opportunity to fix several crash bugs, integrate a new
4605 directory authority, and update the bundled GeoIP database.
4608 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4609 No longer set the tlsext_host_name extension on server SSL objects;
4610 but continue to set it on client SSL objects. Our goal in setting
4611 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4612 bugfix on 0.2.1.1-alpha.
4613 - Do not log messages to the controller while shrinking buffer
4614 freelists. Doing so would sometimes make the controller connection
4615 try to allocate a buffer chunk, which would mess up the internals
4616 of the freelist and cause an assertion failure. Fixes bug 1125;
4617 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4618 - Learn our external IP address when we're a relay or bridge, even if
4619 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4620 where we introduced bridge relays that don't need to publish to
4621 be useful. Fixes bug 2050.
4622 - Do even more to reject (and not just ignore) annotations on
4623 router descriptors received anywhere but from the cache. Previously
4624 we would ignore such annotations at first, but cache them to disk
4625 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4626 - When you're using bridges and your network goes away and your
4627 bridges get marked as down, recover when you attempt a new socks
4628 connection (if the network is back), rather than waiting up to an
4629 hour to try fetching new descriptors for your bridges. Bugfix on
4630 0.2.0.3-alpha; fixes bug 1981.
4633 - Move to the November 2010 Maxmind GeoLite country db (rather
4634 than the June 2009 ip-to-country GeoIP db) for our statistics that
4635 count how many users relays are seeing from each country. Now we'll
4636 have more accurate data, especially for many African countries.
4638 o New directory authorities:
4639 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4643 - Fix an assertion failure that could occur in directory caches or
4644 bridge users when using a very short voting interval on a testing
4645 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4647 - Enforce multiplicity rules when parsing annotations. Bugfix on
4648 0.2.0.8-alpha. Found by piebeer.
4649 - Allow handshaking OR connections to take a full KeepalivePeriod
4650 seconds to handshake. Previously, we would close them after
4651 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4652 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4654 - When building with --enable-gcc-warnings on OpenBSD, disable
4655 warnings in system headers. This makes --enable-gcc-warnings
4656 pass on OpenBSD 4.8.
4659 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4660 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4661 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4662 Servers can start sending this code when enough clients recognize
4663 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4664 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4665 Patch from mingw-san.
4668 - Remove the old debian/ directory from the main Tor distribution.
4669 The official Tor-for-debian git repository lives at the URL
4670 https://git.torproject.org/debian/tor.git
4671 - Stop shipping the old doc/website/ directory in the tarball. We
4672 changed the website format in late 2010, and what we shipped in
4673 0.2.1.26 really wasn't that useful anyway.
4676 Changes in version 0.2.2.19-alpha - 2010-11-22
4677 Yet another OpenSSL security patch broke its compatibility with Tor:
4678 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
4681 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4682 No longer set the tlsext_host_name extension on server SSL objects;
4683 but continue to set it on client SSL objects. Our goal in setting
4684 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4685 bugfix on 0.2.1.1-alpha.
4688 - Try harder not to exceed the maximum length of 50 KB when writing
4689 statistics to extra-info descriptors. This bug was triggered by very
4690 fast relays reporting exit-port, entry, and dirreq statistics.
4691 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
4692 - Publish a router descriptor even if generating an extra-info
4693 descriptor fails. Previously we would not publish a router
4694 descriptor without an extra-info descriptor; this can cause fast
4695 exit relays collecting exit-port statistics to drop from the
4696 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4699 Changes in version 0.2.2.18-alpha - 2010-11-16
4700 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
4701 us lately, makes unpublished bridge relays able to detect their IP
4702 address, and fixes a wide variety of other bugs to get us much closer
4703 to a stable release.
4706 - Do even more to reject (and not just ignore) annotations on
4707 router descriptors received anywhere but from the cache. Previously
4708 we would ignore such annotations at first, but cache them to disk
4709 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4710 - Do not log messages to the controller while shrinking buffer
4711 freelists. Doing so would sometimes make the controller connection
4712 try to allocate a buffer chunk, which would mess up the internals
4713 of the freelist and cause an assertion failure. Fixes bug 1125;
4714 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4715 - Learn our external IP address when we're a relay or bridge, even if
4716 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4717 where we introduced bridge relays that don't need to publish to
4718 be useful. Fixes bug 2050.
4719 - Maintain separate TLS contexts and certificates for incoming and
4720 outgoing connections in bridge relays. Previously we would use the
4721 same TLS contexts and certs for incoming and outgoing connections.
4722 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4723 - Maintain separate identity keys for incoming and outgoing TLS
4724 contexts in bridge relays. Previously we would use the same
4725 identity keys for incoming and outgoing TLS contexts. Bugfix on
4726 0.2.0.3-alpha; addresses the other half of bug 988.
4727 - Avoid an assertion failure when we as an authority receive a
4728 duplicate upload of a router descriptor that we already have,
4729 but which we previously considered an obsolete descriptor.
4730 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
4731 - Avoid a crash bug triggered by looking at a dangling pointer while
4732 setting the network status consensus. Found by Robert Ransom.
4733 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
4734 - Fix a logic error where servers that _didn't_ act as exits would
4735 try to keep their server lists more aggressively up to date than
4736 exits, when it was supposed to be the other way around. Bugfix
4739 o Minor bugfixes (on Tor 0.2.1.x and earlier):
4740 - When we're trying to guess whether we know our IP address as
4741 a relay, we would log various ways that we failed to guess
4742 our address, but never log that we ended up guessing it
4743 successfully. Now add a log line to help confused and anxious
4744 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4745 - Bring the logic that gathers routerinfos and assesses the
4746 acceptability of circuits into line. This prevents a Tor OP from
4747 getting locked in a cycle of choosing its local OR as an exit for a
4748 path (due to a .exit request) and then rejecting the circuit because
4749 its OR is not listed yet. It also prevents Tor clients from using an
4750 OR running in the same instance as an exit (due to a .exit request)
4751 if the OR does not meet the same requirements expected of an OR
4752 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4753 - Correctly describe errors that occur when generating a TLS object.
4754 Previously we would attribute them to a failure while generating a
4755 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4757 - Enforce multiplicity rules when parsing annotations. Bugfix on
4758 0.2.0.8-alpha. Found by piebeer.
4759 - Fix warnings that newer versions of autoconf produced during
4760 ./autogen.sh. These warnings appear to be harmless in our case,
4761 but they were extremely verbose. Fixes bug 2020.
4763 o Minor bugfixes (on Tor 0.2.2.x):
4764 - Enable protection of small arrays whenever we build with gcc
4765 hardening features, not only when also building with warnings
4766 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
4769 - Make hidden services work better in private Tor networks by not
4770 requiring any uptime to join the hidden service descriptor
4771 DHT. Implements ticket 2088.
4772 - Rate-limit the "your application is giving Tor only an IP address"
4773 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4774 - When AllowSingleHopExits is set, print a warning to explain to the
4775 relay operator why most clients are avoiding her relay.
4776 - Update to the November 1 2010 Maxmind GeoLite Country database.
4778 o Code simplifications and refactoring:
4779 - When we fixed bug 1038 we had to put in a restriction not to send
4780 RELAY_EARLY cells on rend circuits. This was necessary as long
4781 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
4782 active. Now remove this obsolete check. Resolves bug 2081.
4783 - Some options used different conventions for uppercasing of acronyms
4784 when comparing manpage and source. Fix those in favor of the
4785 manpage, as it makes sense to capitalize acronyms.
4786 - Remove the torrc.complete file. It hasn't been kept up to date
4787 and users will have better luck checking out the manpage.
4788 - Remove the obsolete "NoPublish" option; it has been flagged
4789 as obsolete and has produced a warning since 0.1.1.18-rc.
4790 - Remove everything related to building the expert bundle for OS X.
4791 It has confused many users, doesn't work right on OS X 10.6,
4792 and is hard to get rid of once installed. Resolves bug 1274.
4795 Changes in version 0.2.2.17-alpha - 2010-09-30
4796 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
4797 to use one-hop circuits (which can put the exit relays at higher risk,
4798 plus unbalance the network); fixes a big bug in bandwidth accounting
4799 for relays that want to limit their monthly bandwidth use; fixes a
4800 big pile of bugs in how clients tolerate temporary network failure;
4801 and makes our adaptive circuit build timeout feature (which improves
4802 client performance if your network is fast while not breaking things
4803 if your network is slow) better handle bad networks.
4806 - Exit relays now try harder to block exit attempts from unknown
4807 relays, to make it harder for people to use them as one-hop proxies
4808 a la tortunnel. Controlled by the refuseunknownexits consensus
4809 parameter (currently enabled), or you can override it on your
4810 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
4812 o Major bugfixes (0.2.1.x and earlier):
4813 - Fix a bug in bandwidth accounting that could make us use twice
4814 the intended bandwidth when our interval start changes due to
4815 daylight saving time. Now we tolerate skew in stored vs computed
4816 interval starts: if the start of the period changes by no more than
4817 50% of the period's duration, we remember bytes that we transferred
4818 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4819 - Always search the Windows system directory for system DLLs, and
4820 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4821 - When you're using bridges and your network goes away and your
4822 bridges get marked as down, recover when you attempt a new socks
4823 connection (if the network is back), rather than waiting up to an
4824 hour to try fetching new descriptors for your bridges. Bugfix on
4825 0.2.0.3-alpha; fixes bug 1981.
4827 o Major bugfixes (on 0.2.2.x):
4828 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
4830 - Fix a segfault that could happen when operating a bridge relay with
4831 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
4832 - The consensus bandwidth-weights (used by clients to choose fast
4833 relays) entered an unexpected edge case in September where
4834 Exits were much scarcer than Guards, resulting in bad weight
4835 recommendations. Now we compute them using new constraints that
4836 should succeed in all cases. Also alter directory authorities to
4837 not include the bandwidth-weights line if they fail to produce
4838 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
4839 - When weighting bridges during path selection, we used to trust
4840 the bandwidths they provided in their descriptor, only capping them
4841 at 10MB/s. This turned out to be problematic for two reasons:
4842 Bridges could claim to handle a lot more traffic then they
4843 actually would, thus making more clients pick them and have a
4844 pretty effective DoS attack. The other issue is that new bridges
4845 that might not have a good estimate for their bw capacity yet
4846 would not get used at all unless no other bridges are available
4847 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
4849 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
4850 - Ignore cannibalized circuits when recording circuit build times.
4851 This should provide for a minor performance improvement for hidden
4852 service users using 0.2.2.14-alpha, and should remove two spurious
4853 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
4854 - Simplify the logic that causes us to decide if the network is
4855 unavailable for purposes of recording circuit build times. If we
4856 receive no cells whatsoever for the entire duration of a circuit's
4857 full measured lifetime, the network is probably down. Also ignore
4858 one-hop directory fetching circuit timeouts when calculating our
4859 circuit build times. These changes should hopefully reduce the
4860 cases where we see ridiculous circuit build timeouts for people
4861 with spotty wireless connections. Fixes part of bug 1772; bugfix
4863 - Prevent the circuit build timeout from becoming larger than
4864 the maximum build time we have ever seen. Also, prevent the time
4865 period for measurement circuits from becoming larger than twice that
4866 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
4869 - When we run out of directory information such that we can't build
4870 circuits, but then get enough that we can build circuits, log when
4871 we actually construct a circuit, so the user has a better chance of
4872 knowing what's going on. Fixes bug 1362.
4873 - Be more generous with how much bandwidth we'd use up (with
4874 accounting enabled) before entering "soft hibernation". Previously,
4875 we'd refuse new connections and circuits once we'd used up 95% of
4876 our allotment. Now, we use up 95% of our allotment, AND make sure
4877 that we have no more than 500MB (or 3 hours of expected traffic,
4878 whichever is lower) remaining before we enter soft hibernation.
4879 - If we've configured EntryNodes and our network goes away and/or all
4880 our entrynodes get marked down, optimistically retry them all when
4881 a new socks application request appears. Fixes bug 1882.
4882 - Add some more defensive programming for architectures that can't
4883 handle unaligned integer accesses. We don't know of any actual bugs
4884 right now, but that's the best time to fix them. Fixes bug 1943.
4885 - Support line continuations in the torrc config file. If a line
4886 ends with a single backslash character, the newline is ignored, and
4887 the configuration value is treated as continuing on the next line.
4890 o Minor bugfixes (on 0.2.1.x and earlier):
4891 - For bandwidth accounting, calculate our expected bandwidth rate
4892 based on the time during which we were active and not in
4893 soft-hibernation during the last interval. Previously, we were
4894 also considering the time spent in soft-hibernation. If this
4895 was a long time, we would wind up underestimating our bandwidth
4896 by a lot, and skewing our wakeup time towards the start of the
4897 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4899 o Minor bugfixes (on 0.2.2.x):
4900 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
4901 which were disabled by the circuit build timeout changes in
4902 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
4903 - Make sure we don't warn about missing bandwidth weights when
4904 choosing bridges or other relays not in the consensus. Bugfix on
4905 0.2.2.10-alpha; fixes bug 1805.
4906 - In our logs, do not double-report signatures from unrecognized
4907 authorities both as "from unknown authority" and "not
4908 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
4911 Changes in version 0.2.2.16-alpha - 2010-09-17
4912 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
4913 evident at exit relays), and also continues to resolve all the little
4914 bugs that have been filling up trac lately.
4916 o Major bugfixes (stream-level fairness):
4917 - When receiving a circuit-level SENDME for a blocked circuit, try
4918 to package cells fairly from all the streams that had previously
4919 been blocked on that circuit. Previously, we had started with the
4920 oldest stream, and allowed each stream to potentially exhaust
4921 the circuit's package window. This gave older streams on any
4922 given circuit priority over newer ones. Fixes bug 1937. Detected
4923 originally by Camilo Viecco. This bug was introduced before the
4924 first Tor release, in svn commit r152: it is the new winner of
4925 the longest-lived bug prize.
4926 - When the exit relay got a circuit-level sendme cell, it started
4927 reading on the exit streams, even if had 500 cells queued in the
4928 circuit queue already, so the circuit queue just grew and grew in
4929 some cases. We fix this by not re-enabling reading on receipt of a
4930 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4931 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4933 - Newly created streams were allowed to read cells onto circuits,
4934 even if the circuit's cell queue was blocked and waiting to drain.
4935 This created potential unfairness, as older streams would be
4936 blocked, but newer streams would gladly fill the queue completely.
4937 We add code to detect this situation and prevent any stream from
4938 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4942 - Update to the September 1 2010 Maxmind GeoLite Country database.
4943 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4944 not. This would lead to a cookie that is still not group readable.
4945 Closes bug 1843. Suggested by katmagic.
4946 - When logging a rate-limited warning, we now mention how many messages
4947 got suppressed since the last warning.
4948 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4949 do individual connection-level rate limiting of clients. The torrc
4950 config options with the same names trump the consensus params, if
4951 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4952 consensus params which were broken from 0.2.2.7-alpha through
4953 0.2.2.14-alpha. Closes bug 1947.
4954 - When a router changes IP address or port, authorities now launch
4955 a new reachability test for it. Implements ticket 1899.
4956 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4957 2 no signature, 4 required" messages about consensus signatures
4958 easier to read, and make sure they get logged at the same severity
4959 as the messages explaining which keys are which. Fixes bug 1290.
4960 - Don't warn when we have a consensus that we can't verify because
4961 of missing certificates, unless those certificates are ones
4962 that we have been trying and failing to download. Fixes bug 1145.
4963 - If you configure your bridge with a known identity fingerprint,
4964 and the bridge authority is unreachable (as it is in at least
4965 one country now), fall back to directly requesting the descriptor
4966 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4968 - When building with --enable-gcc-warnings on OpenBSD, disable
4969 warnings in system headers. This makes --enable-gcc-warnings
4970 pass on OpenBSD 4.8.
4972 o Minor bugfixes (on 0.2.1.x and earlier):
4973 - Authorities will now attempt to download consensuses if their
4974 own efforts to make a live consensus have failed. This change
4975 means authorities that restart will fetch a valid consensus, and
4976 it means authorities that didn't agree with the current consensus
4977 will still fetch and serve it if it has enough signatures. Bugfix
4978 on 0.2.0.9-alpha; fixes bug 1300.
4979 - Ensure DNS requests launched by "RESOLVE" commands from the
4980 controller respect the __LeaveStreamsUnattached setconf options. The
4981 same goes for requests launched via DNSPort or transparent
4982 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4983 - Allow handshaking OR connections to take a full KeepalivePeriod
4984 seconds to handshake. Previously, we would close them after
4985 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4986 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4988 - Rate-limit "Failed to hand off onionskin" warnings.
4989 - Never relay a cell for a circuit we have already destroyed.
4990 Between marking a circuit as closeable and finally closing it,
4991 it may have been possible for a few queued cells to get relayed,
4992 even though they would have been immediately dropped by the next
4993 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4994 - Never queue a cell for a circuit that's already been marked
4996 - Never vote for a server as "Running" if we have a descriptor for
4997 it claiming to be hibernating, and that descriptor was published
4998 more recently than our last contact with the server. Bugfix on
4999 0.2.0.3-alpha; fixes bug 911.
5000 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
5003 o Minor bugfixes (on 0.2.2.x):
5004 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
5005 down if a directory fetch fails and you've configured either
5006 bridges or EntryNodes. The intent was to mark the relay as down
5007 _unless_ you're using bridges or EntryNodes, since if you are
5008 then you could quickly run out of entry points.
5009 - Fix the Windows directory-listing code. A bug introduced in
5010 0.2.2.14-alpha could make Windows directory servers forget to load
5011 some of their cached v2 networkstatus files.
5012 - Really allow clients to use relays as bridges. Fixes bug 1776;
5013 bugfix on 0.2.2.15-alpha.
5014 - Demote a warn to info that happens when the CellStatistics option
5015 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
5016 Reported by Moritz Bartl.
5017 - On Windows, build correctly either with or without Unicode support.
5018 This is necessary so that Tor can support fringe platforms like
5019 Windows 98 (which has no Unicode), or Windows CE (which has no
5020 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
5023 - Add a unit test for cross-platform directory-listing code.
5026 Changes in version 0.2.2.15-alpha - 2010-08-18
5027 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
5028 fixes a variety of other bugs that were preventing performance
5029 experiments from moving forward, fixes several bothersome memory leaks,
5030 and generally closes a lot of smaller bugs that have been filling up
5034 - Stop assigning the HSDir flag to relays that disable their
5035 DirPort (and thus will refuse to answer directory requests). This
5036 fix should dramatically improve the reachability of hidden services:
5037 hidden services and hidden service clients pick six HSDir relays
5038 to store and retrieve the hidden service descriptor, and currently
5039 about half of the HSDir relays will refuse to work. Bugfix on
5040 0.2.0.10-alpha; fixes part of bug 1693.
5041 - The PerConnBWRate and Burst config options, along with the
5042 bwconnrate and bwconnburst consensus params, initialized each conn's
5043 token bucket values only when the connection is established. Now we
5044 update them if the config options change, and update them every time
5045 we get a new consensus. Otherwise we can encounter an ugly edge
5046 case where we initialize an OR conn to client-level bandwidth,
5047 but then later the relay joins the consensus and we leave it
5048 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
5049 - Fix a regression that caused Tor to rebind its ports if it receives
5050 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
5053 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
5054 should give us approximately 40-50% more Guard-flagged nodes,
5055 improving the anonymity the Tor network can provide and also
5056 decreasing the dropoff in throughput that relays experience when
5057 they first get the Guard flag.
5058 - Allow enabling or disabling the *Statistics config options while
5062 - Update to the August 1 2010 Maxmind GeoLite Country database.
5063 - Have the controller interface give a more useful message than
5064 "Internal Error" in response to failed GETINFO requests.
5065 - Warn when the same option is provided more than once in a torrc
5066 file, on the command line, or in a single SETCONF statement, and
5067 the option is one that only accepts a single line. Closes bug 1384.
5068 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5069 Patch from mingw-san.
5070 - Add support for the country code "{??}" in torrc options like
5071 ExcludeNodes, to indicate all routers of unknown country. Closes
5073 - Relays report the number of bytes spent on answering directory
5074 requests in extra-info descriptors similar to {read,write}-history.
5075 Implements enhancement 1790.
5077 o Minor bugfixes (on 0.2.1.x and earlier):
5078 - Complain if PublishServerDescriptor is given multiple arguments that
5079 include 0 or 1. This configuration will be rejected in the future.
5080 Bugfix on 0.2.0.1-alpha; closes bug 1107.
5081 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
5082 Bugfix on 0.2.0.13-alpha; closes bug 928.
5083 - Change "Application request when we're believed to be offline."
5084 notice to "Application request when we haven't used client
5085 functionality lately.", to clarify that it's not an error. Bugfix
5086 on 0.0.9.3; fixes bug 1222.
5087 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
5088 would return "551 Internal error" rather than "552 Unrecognized key
5089 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
5090 - Users can't configure a regular relay to be their bridge. It didn't
5091 work because when Tor fetched the bridge descriptor, it found
5092 that it already had it, and didn't realize that the purpose of the
5093 descriptor had changed. Now we replace routers with a purpose other
5094 than bridge with bridge descriptors when fetching them. Bugfix on
5095 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
5096 refetch the descriptor with router purpose 'general', disabling
5098 - Fix a rare bug in rend_fn unit tests: we would fail a test when
5099 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
5100 on 0.2.0.10-alpha; fixes bug 1808.
5101 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5102 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5103 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5104 Servers can start sending this code when enough clients recognize
5105 it. Also update the spec to reflect this new reason. Bugfix on
5106 0.1.0.1-rc; fixes part of bug 1793.
5107 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
5108 when we switch from being a public relay to a bridge. Otherwise
5109 there will still be clients that see the relay in their consensus,
5110 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
5112 - Instead of giving an assertion failure on an internal mismatch
5113 on estimated freelist size, just log a BUG warning and try later.
5114 Mitigates but does not fix bug 1125.
5115 - Fix an assertion failure that could occur in caches or bridge users
5116 when using a very short voting interval on a testing network.
5117 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
5119 o Minor bugfixes (on 0.2.2.x):
5120 - Alter directory authorities to always consider Exit-flagged nodes
5121 as potential Guard nodes in their votes. The actual decision to
5122 use Exits as Guards is done in the consensus bandwidth weights.
5123 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
5124 - When the controller is reporting the purpose of circuits that
5125 didn't finish building before the circuit build timeout, it was
5126 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
5127 - Our libevent version parsing code couldn't handle versions like
5128 1.4.14b-stable and incorrectly warned the user about using an
5129 old and broken version of libevent. Treat 1.4.14b-stable like
5130 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
5132 - Don't use substitution references like $(VAR:MOD) when
5133 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
5134 '$(:x)' to 'x' rather than the empty string. This bites us in
5135 doc/ when configured with --disable-asciidoc. Bugfix on
5136 0.2.2.9-alpha; fixes bug 1773.
5137 - Remove a spurious hidden service server-side log notice about
5138 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
5140 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
5142 - Correctly report written bytes on linked connections. Found while
5143 implementing 1790. Bugfix on 0.2.2.4-alpha.
5144 - Fix three memory leaks: one in circuit_build_times_parse_state(),
5145 one in dirvote_add_signatures_to_pending_consensus(), and one every
5146 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
5147 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
5149 o Code simplifications and refactoring:
5150 - Take a first step towards making or.h smaller by splitting out
5151 function definitions for all source files in src/or/. Leave
5152 structures and defines in or.h for now.
5153 - Remove a bunch of unused function declarations as well as a block of
5154 #if 0'd code from the unit tests. Closes bug 1824.
5155 - New unit tests for exit-port history statistics; refactored exit
5156 statistics code to be more easily tested.
5157 - Remove the old debian/ directory from the main Tor distribution.
5158 The official Tor-for-debian git repository lives at the URL
5159 https://git.torproject.org/debian/tor.git
5162 Changes in version 0.2.2.14-alpha - 2010-07-12
5163 Tor 0.2.2.14-alpha greatly improves client-side handling of
5164 circuit build timeouts, which are used to estimate speed and improve
5165 performance. We also move to a much better GeoIP database, port Tor to
5166 Windows CE, introduce new compile flags that improve code security,
5167 add an eighth v3 directory authority, and address a lot of more
5171 - Tor directory authorities no longer crash when started with a
5172 cached-microdesc-consensus file in their data directory. Bugfix
5173 on 0.2.2.6-alpha; fixes bug 1532.
5174 - Treat an unset $HOME like an empty $HOME rather than triggering an
5175 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
5176 - Ignore negative and large circuit build timeout values that can
5177 happen during a suspend or hibernate. These values caused various
5178 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
5179 - Alter calculation of Pareto distribution parameter 'Xm' for
5180 Circuit Build Timeout learning to use the weighted average of the
5181 top N=3 modes (because we have three entry guards). Considering
5182 multiple modes should improve the timeout calculation in some cases,
5183 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
5185 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
5186 right censored distribution model. This approach improves over the
5187 synthetic timeout generation approach that was producing insanely
5188 high timeout values. Now we calculate build timeouts using truncated
5189 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
5190 - Do not close circuits that are under construction when they reach
5191 the circuit build timeout. Instead, leave them building (but do not
5192 use them) for up until the time corresponding to the 95th percentile
5193 on the Pareto CDF or 60 seconds, whichever is greater. This is done
5194 to provide better data for the new Pareto model. This percentile
5195 can be controlled by the consensus.
5198 - Move to the June 2010 Maxmind GeoLite country db (rather than the
5199 June 2009 ip-to-country GeoIP db) for our statistics that count
5200 how many users relays are seeing from each country. Now we have
5201 more accurate data for many African countries.
5202 - Port Tor to build and run correctly on Windows CE systems, using
5203 the wcecompat library. Contributed by Valerio Lupi.
5204 - New "--enable-gcc-hardening" ./configure flag (off by default)
5205 to turn on gcc compile time hardening options. It ensures
5206 that signed ints have defined behavior (-fwrapv), enables
5207 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
5208 with canaries (-fstack-protector-all), turns on ASLR protection if
5209 supported by the kernel (-fPIE, -pie), and adds additional security
5210 related warnings. Verified to work on Mac OS X and Debian Lenny.
5211 - New "--enable-linker-hardening" ./configure flag (off by default)
5212 to turn on ELF specific hardening features (relro, now). This does
5213 not work with Mac OS X or any other non-ELF binary format.
5215 o New directory authorities:
5216 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5220 - New config option "WarnUnsafeSocks 0" disables the warning that
5221 occurs whenever Tor receives a socks handshake using a version of
5222 the socks protocol that can only provide an IP address (rather
5223 than a hostname). Setups that do DNS locally over Tor are fine,
5224 and we shouldn't spam the logs in that case.
5225 - Convert the HACKING file to asciidoc, and add a few new sections
5226 to it, explaining how we use Git, how we make changelogs, and
5227 what should go in a patch.
5228 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
5229 event, to give information on the current rate of circuit timeouts
5230 over our stored history.
5231 - Add ability to disable circuit build time learning via consensus
5232 parameter and via a LearnCircuitBuildTimeout config option. Also
5233 automatically disable circuit build time calculation if we are
5234 either a AuthoritativeDirectory, or if we fail to write our state
5235 file. Fixes bug 1296.
5236 - More gracefully handle corrupt state files, removing asserts
5237 in favor of saving a backup and resetting state.
5238 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
5242 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5244 - When a2x fails, mention that the user could disable manpages instead
5245 of trying to fix their asciidoc installation.
5246 - Where available, use Libevent 2.0's periodic timers so that our
5247 once-per-second cleanup code gets called even more closely to
5248 once per second than it would otherwise. Fixes bug 943.
5249 - If you run a bridge that listens on multiple IP addresses, and
5250 some user configures a bridge address that uses a different IP
5251 address than your bridge writes in its router descriptor, and the
5252 user doesn't specify an identity key, their Tor would discard the
5253 descriptor because "it isn't one of our configured bridges", and
5254 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
5255 Bugfix on 0.2.0.3-alpha.
5256 - If OpenSSL fails to make a duplicate of a private or public key, log
5257 an error message and try to exit cleanly. May help with debugging
5258 if bug 1209 ever remanifests.
5259 - Save a couple bytes in memory allocation every time we escape
5260 certain characters in a string. Patch from Florian Zumbiehl.
5261 - Make it explicit that we don't cannibalize one-hop circuits. This
5262 happens in the wild, but doesn't turn out to be a problem because
5263 we fortunately don't use those circuits. Many thanks to outofwords
5264 for the initial analysis and to swissknife who confirmed that
5265 two-hop circuits are actually created.
5266 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
5267 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
5268 - Eliminate a case where a circuit build time warning was displayed
5269 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
5272 Changes in version 0.2.1.26 - 2010-05-02
5273 Tor 0.2.1.26 addresses the recent connection and memory overload
5274 problems we've been seeing on relays, especially relays with their
5275 DirPort open. If your relay has been crashing, or you turned it off
5276 because it used too many resources, give this release a try.
5278 This release also fixes yet another instance of broken OpenSSL libraries
5279 that was causing some relays to drop out of the consensus.
5282 - Teach relays to defend themselves from connection overload. Relays
5283 now close idle circuits early if it looks like they were intended
5284 for directory fetches. Relays are also more aggressive about closing
5285 TLS connections that have no circuits on them. Such circuits are
5286 unlikely to be re-used, and tens of thousands of them were piling
5287 up at the fast relays, causing the relays to run out of sockets
5288 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5289 their directory fetches over TLS).
5290 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5291 that claim to be earlier than 0.9.8m, but which have in reality
5292 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5293 behavior. Possible fix for some cases of bug 1346.
5294 - Directory mirrors were fetching relay descriptors only from v2
5295 directory authorities, rather than v3 authorities like they should.
5296 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5297 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5300 - Finally get rid of the deprecated and now harmful notion of "clique
5301 mode", where directory authorities maintain TLS connections to
5305 - In the util/threads test, no longer free the test_mutex before all
5306 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5307 - The master thread could starve the worker threads quite badly on
5308 certain systems, causing them to run only partially in the allowed
5309 window. This resulted in test failures. Now the master thread sleeps
5310 occasionally for a few microseconds while the two worker-threads
5311 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5314 Changes in version 0.2.2.13-alpha - 2010-04-24
5315 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
5316 problems we've been seeing on relays, especially relays with their
5317 DirPort open. If your relay has been crashing, or you turned it off
5318 because it used too many resources, give this release a try.
5321 - Teach relays to defend themselves from connection overload. Relays
5322 now close idle circuits early if it looks like they were intended
5323 for directory fetches. Relays are also more aggressive about closing
5324 TLS connections that have no circuits on them. Such circuits are
5325 unlikely to be re-used, and tens of thousands of them were piling
5326 up at the fast relays, causing the relays to run out of sockets
5327 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5328 their directory fetches over TLS).
5331 - Finally get rid of the deprecated and now harmful notion of "clique
5332 mode", where directory authorities maintain TLS connections to
5334 - Directory authorities now do an immediate reachability check as soon
5335 as they hear about a new relay. This change should slightly reduce
5336 the time between setting up a relay and getting listed as running
5337 in the consensus. It should also improve the time between setting
5338 up a bridge and seeing use by bridge users.
5339 - Directory authorities no longer launch a TLS connection to every
5340 relay as they startup. Now that we have 2k+ descriptors cached,
5341 the resulting network hiccup is becoming a burden. Besides,
5342 authorities already avoid voting about Running for the first half
5343 hour of their uptime.
5346 Changes in version 0.2.2.12-alpha - 2010-04-20
5347 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
5348 handle and vote on descriptors. It was causing relays to drop out of
5352 - Many relays have been falling out of the consensus lately because
5353 not enough authorities know about their descriptor for them to get
5354 a majority of votes. When we deprecated the v2 directory protocol,
5355 we got rid of the only way that v3 authorities can hear from each
5356 other about other descriptors. Now authorities examine every v3
5357 vote for new descriptors, and fetch them from that authority. Bugfix
5359 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
5360 and a warning in or.h related to bandwidth_weight_rule_t that
5361 prevented clean compile on OS X. Fixes bug 1363; bugfix on
5363 - Fix a segfault on relays when DirReqStatistics is enabled
5364 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
5368 - Demote a confusing TLS warning that relay operators might get when
5369 someone tries to talk to their OrPort. It is neither the operator's
5370 fault nor can they do anything about it. Fixes bug 1364; bugfix
5374 Changes in version 0.2.2.11-alpha - 2010-04-15
5375 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
5376 libraries that was causing some relays to drop out of the consensus.
5379 - Directory mirrors were fetching relay descriptors only from v2
5380 directory authorities, rather than v3 authorities like they should.
5381 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5382 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5383 - Fix a parsing error that made every possible value of
5384 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
5385 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
5386 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
5387 about the option without breaking older ones.
5388 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5389 that claim to be earlier than 0.9.8m, but which have in reality
5390 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5391 behavior. Possible fix for some cases of bug 1346.
5394 - Experiment with a more aggressive approach to preventing clients
5395 from making one-hop exit streams. Exit relays who want to try it
5396 out can set "RefuseUnknownExits 1" in their torrc, and then look
5397 for "Attempt by %s to open a stream" log messages. Let us know
5399 - Add support for statically linking zlib by specifying
5400 --enable-static-zlib, to go with our support for statically linking
5401 openssl and libevent. Resolves bug 1358.
5404 - Fix a segfault that happens whenever a Tor client that is using
5405 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
5407 - When we cleaned up the contrib/tor-exit-notice.html file, we left
5408 out the first line. Fixes bug 1295.
5409 - When building the manpage from a tarball, we required asciidoc, but
5410 the asciidoc -> roff/html conversion was already done for the
5411 tarball. Make 'make' complain only when we need asciidoc (either
5412 because we're compiling directly from git, or because we altered
5413 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
5414 - When none of the directory authorities vote on any params, Tor
5415 segfaulted when trying to make the consensus from the votes. We
5416 didn't trigger the bug in practice, because authorities do include
5417 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
5420 - In the util/threads test, no longer free the test_mutex before all
5421 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5422 - The master thread could starve the worker threads quite badly on
5423 certain systems, causing them to run only partially in the allowed
5424 window. This resulted in test failures. Now the master thread sleeps
5425 occasionally for a few microseconds while the two worker-threads
5426 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5429 Changes in version 0.2.2.10-alpha - 2010-03-07
5430 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
5431 could prevent relays from guessing their IP address correctly. It also
5432 starts the groundwork for another client-side performance boost, since
5433 currently we're not making efficient use of relays that have both the
5434 Guard flag and the Exit flag.
5437 - Fix a regression from our patch for bug 1244 that caused relays
5438 to guess their IP address incorrectly if they didn't set Address
5439 in their torrc and/or their address fails to resolve. Bugfix on
5440 0.2.2.9-alpha; fixes bug 1269.
5442 o Major features (performance):
5443 - Directory authorities now compute consensus weightings that instruct
5444 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
5445 and no flag. Clients that use these weightings will distribute
5446 network load more evenly across these different relay types. The
5447 weightings are in the consensus so we can change them globally in
5448 the future. Extra thanks to "outofwords" for finding some nasty
5449 security bugs in the first implementation of this feature.
5451 o Minor features (performance):
5452 - Always perform router selections using weighted relay bandwidth,
5453 even if we don't need a high capacity circuit at the time. Non-fast
5454 circuits now only differ from fast ones in that they can use relays
5455 not marked with the Fast flag. This "feature" could turn out to
5456 be a horrible bug; we should investigate more before it goes into
5460 - Allow disabling building of the manpages. Skipping the manpage
5461 speeds up the build considerably.
5463 o Minor bugfixes (on 0.2.2.x):
5464 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
5465 Bugfix on 0.2.2.9-alpha.
5466 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
5467 config option. Bugfix on 0.2.2.7-alpha.
5468 - Ship the asciidoc-helper file in the tarball, so that people can
5469 build from source if they want to, and touching the .1.txt files
5470 doesn't break the build. Bugfix on 0.2.2.9-alpha.
5472 o Minor bugfixes (on 0.2.1.x or earlier):
5473 - Fix a dereference-then-NULL-check sequence when publishing
5474 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5476 - Fix another dereference-then-NULL-check sequence. Bugfix on
5477 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5478 - Make sure we treat potentially not NUL-terminated strings correctly.
5479 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5481 o Code simplifications and refactoring:
5482 - Fix some urls in the exit notice file and make it XHTML1.1 strict
5483 compliant. Based on a patch from Christian Kujau.
5484 - Don't use sed in asciidoc-helper anymore.
5485 - Make the build process fail if asciidoc cannot be found and
5486 building with asciidoc isn't disabled.
5489 Changes in version 0.2.2.9-alpha - 2010-02-22
5490 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
5491 location of a directory authority, and cleans up a bunch of small bugs.
5493 o Directory authority changes:
5494 - Change IP address for dannenberg (v3 directory authority), and
5495 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5496 service directory authority) from the list.
5499 - Make Tor work again on the latest OS X: when deciding whether to
5500 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5501 version at run-time, not compile time. We need to do this because
5502 Apple doesn't update its dev-tools headers when it updates its
5503 libraries in a security patch.
5504 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5505 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5506 a memory leak when requesting a hidden service descriptor we've
5507 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5509 - Authorities could be tricked into giving out the Exit flag to relays
5510 that didn't allow exiting to any ports. This bug could screw
5511 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
5512 1238. Bug discovered by Martin Kowalczyk.
5513 - When freeing a session key, zero it out completely. We only zeroed
5514 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5515 patched by ekir. Fixes bug 1254.
5518 - Fix static compilation by listing the openssl libraries in the right
5519 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
5520 - Resume handling .exit hostnames in a special way: originally we
5521 stripped the .exit part and used the requested exit relay. In
5522 0.2.2.1-alpha we stopped treating them in any special way, meaning
5523 if you use a .exit address then Tor will pass it on to the exit
5524 relay. Now we reject the .exit stream outright, since that behavior
5525 might be more expected by the user. Found and diagnosed by Scott
5526 Bennett and Downie on or-talk.
5527 - Don't spam the controller with events when we have no file
5528 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
5529 for log messages was already solved from bug 748.)
5530 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
5532 - Make the DNSPort option work with libevent 2.x. Don't alter the
5533 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
5534 - Emit a GUARD DROPPED controller event for a case we missed.
5535 - Make more fields in the controller protocol case-insensitive, since
5536 control-spec.txt said they were.
5537 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5538 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5539 - Fix a spec conformance issue: the network-status-version token
5540 must be the first token in a v3 consensus or vote. Discovered by
5541 parakeep. Bugfix on 0.2.0.3-alpha.
5543 o Code simplifications and refactoring:
5544 - Generate our manpage and HTML documentation using Asciidoc. This
5545 change should make it easier to maintain the documentation, and
5547 - Remove the --enable-iphone option. According to reports from Marco
5548 Bonetti, Tor builds fine without any special tweaking on recent
5549 iPhone SDK versions.
5550 - Removed some unnecessary files from the source distribution. The
5551 AUTHORS file has now been merged into the people page on the
5552 website. The roadmaps and design doc can now be found in the
5553 projects directory in svn.
5554 - Enabled various circuit build timeout constants to be controlled
5555 by consensus parameters. Also set better defaults for these
5556 parameters based on experimentation on broadband and simulated
5560 - The 'EXTENDCIRCUIT' control port command can now be used with
5561 a circ id of 0 and no path. This feature will cause Tor to build
5562 a new 'fast' general purpose circuit using its own path selection
5564 - Added a BUILDTIMEOUT_SET controller event to describe changes
5565 to the circuit build timeout.
5566 - Future-proof the controller protocol a bit by ignoring keyword
5567 arguments we do not recognize.
5568 - Expand homedirs passed to tor-checkkey. This should silence a
5569 coverity complaint about passing a user-supplied string into
5570 open() without checking it.
5573 Changes in version 0.2.1.25 - 2010-03-16
5574 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
5575 prevent relays from guessing their IP address correctly. It also fixes
5576 several minor potential security bugs.
5579 - Fix a regression from our patch for bug 1244 that caused relays
5580 to guess their IP address incorrectly if they didn't set Address
5581 in their torrc and/or their address fails to resolve. Bugfix on
5582 0.2.1.23; fixes bug 1269.
5583 - When freeing a session key, zero it out completely. We only zeroed
5584 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5585 patched by ekir. Fixes bug 1254.
5588 - Fix a dereference-then-NULL-check sequence when publishing
5589 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5591 - Fix another dereference-then-NULL-check sequence. Bugfix on
5592 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5593 - Make sure we treat potentially not NUL-terminated strings correctly.
5594 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5598 Changes in version 0.2.1.24 - 2010-02-21
5599 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
5603 - Work correctly out-of-the-box with even more vendor-patched versions
5604 of OpenSSL. In particular, make it so Debian and OS X don't need
5605 customized patches to run/build.
5608 Changes in version 0.2.1.23 - 2010-02-13
5609 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
5610 again on the latest OS X, and updates the location of a directory
5613 o Major bugfixes (performance):
5614 - We were selecting our guards uniformly at random, and then weighting
5615 which of our guards we'd use uniformly at random. This imbalance
5616 meant that Tor clients were severely limited on throughput (and
5617 probably latency too) by the first hop in their circuit. Now we
5618 select guards weighted by currently advertised bandwidth. We also
5619 automatically discard guards picked using the old algorithm. Fixes
5620 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5623 - Make Tor work again on the latest OS X: when deciding whether to
5624 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5625 version at run-time, not compile time. We need to do this because
5626 Apple doesn't update its dev-tools headers when it updates its
5627 libraries in a security patch.
5628 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5629 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5630 a memory leak when requesting a hidden service descriptor we've
5631 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5634 o Directory authority changes:
5635 - Change IP address for dannenberg (v3 directory authority), and
5636 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5637 service directory authority) from the list.
5640 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5641 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5644 - Avoid a mad rush at the beginning of each month when each client
5645 rotates half of its guards. Instead we spread the rotation out
5646 throughout the month, but we still avoid leaving a precise timestamp
5647 in the state file about when we first picked the guard. Improves
5648 over the behavior introduced in 0.1.2.17.
5651 Changes in version 0.2.2.8-alpha - 2010-01-26
5652 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
5653 causing bridge relays to disappear. If you're running a bridge,
5657 - Fix a memory corruption bug on bridges that occured during the
5658 inclusion of stats data in extra-info descriptors. Also fix the
5659 interface for geoip_get_bridge_stats* to prevent similar bugs in
5660 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
5661 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
5664 - Ignore OutboundBindAddress when connecting to localhost.
5665 Connections to localhost need to come _from_ localhost, or else
5666 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
5670 Changes in version 0.2.2.7-alpha - 2010-01-19
5671 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
5672 as laying the groundwork for further relay-side performance fixes. It
5673 also starts cleaning up client behavior with respect to the EntryNodes,
5674 ExitNodes, and StrictNodes config options.
5676 This release also rotates two directory authority keys, due to a
5677 security breach of some of the Torproject servers.
5679 o Directory authority changes:
5680 - Rotate keys (both v3 identity and relay identity) for moria1
5683 o Major features (performance):
5684 - We were selecting our guards uniformly at random, and then weighting
5685 which of our guards we'd use uniformly at random. This imbalance
5686 meant that Tor clients were severely limited on throughput (and
5687 probably latency too) by the first hop in their circuit. Now we
5688 select guards weighted by currently advertised bandwidth. We also
5689 automatically discard guards picked using the old algorithm. Fixes
5690 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5691 - When choosing which cells to relay first, relays can now favor
5692 circuits that have been quiet recently, to provide lower latency
5693 for low-volume circuits. By default, relays enable or disable this
5694 feature based on a setting in the consensus. You can override
5695 this default by using the new "CircuitPriorityHalflife" config
5696 option. Design and code by Ian Goldberg, Can Tang, and Chris
5698 - Add separate per-conn write limiting to go with the per-conn read
5699 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
5700 but never per-conn write limits.
5701 - New consensus params "bwconnrate" and "bwconnburst" to let us
5702 rate-limit client connections as they enter the network. It's
5703 controlled in the consensus so we can turn it on and off for
5704 experiments. It's starting out off. Based on proposal 163.
5706 o Major features (relay selection options):
5707 - Switch to a StrictNodes config option, rather than the previous
5708 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
5709 "StrictExcludeNodes" option.
5710 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
5711 change during a config reload, mark and discard all our origin
5712 circuits. This fix should address edge cases where we change the
5713 config options and but then choose a circuit that we created before
5715 - If EntryNodes or ExitNodes are set, be more willing to use an
5716 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
5718 - Make EntryNodes config option much more aggressive even when
5719 StrictNodes is not set. Before it would prepend your requested
5720 entrynodes to your list of guard nodes, but feel free to use others
5721 after that. Now it chooses only from your EntryNodes if any of
5722 those are available, and only falls back to others if a) they're
5723 all down and b) StrictNodes is not set.
5724 - Now we refresh your entry guards from EntryNodes at each consensus
5725 fetch -- rather than just at startup and then they slowly rot as
5726 the network changes.
5729 - Stop bridge directory authorities from answering dbg-stability.txt
5730 directory queries, which would let people fetch a list of all
5731 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5734 - Log a notice when we get a new control connection. Now it's easier
5735 for security-conscious users to recognize when a local application
5736 is knocking on their controller door. Suggested by bug 1196.
5737 - New config option "CircuitStreamTimeout" to override our internal
5738 timeout schedule for how many seconds until we detach a stream from
5739 a circuit and try a new circuit. If your network is particularly
5740 slow, you might want to set this to a number like 60.
5741 - New controller command "getinfo config-text". It returns the
5742 contents that Tor would write if you send it a SAVECONF command,
5743 so the controller can write the file to disk itself.
5744 - New options for SafeLogging to allow scrubbing only log messages
5745 generated while acting as a relay.
5746 - Ship the bridges spec file in the tarball too.
5747 - Avoid a mad rush at the beginning of each month when each client
5748 rotates half of its guards. Instead we spread the rotation out
5749 throughout the month, but we still avoid leaving a precise timestamp
5750 in the state file about when we first picked the guard. Improves
5751 over the behavior introduced in 0.1.2.17.
5753 o Minor bugfixes (compiling):
5754 - Fix compilation on OS X 10.3, which has a stub mlockall() but
5755 hides it. Bugfix on 0.2.2.6-alpha.
5756 - Fix compilation on Solaris by removing support for the
5757 DisableAllSwap config option. Solaris doesn't have an rlimit for
5758 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
5761 o Minor bugfixes (crashes):
5762 - Do not segfault when writing buffer stats when we haven't observed
5763 a single circuit to report about. Found by Fabian Lanze. Bugfix on
5765 - If we're in the pathological case where there's no exit bandwidth
5766 but there is non-exit bandwidth, or no guard bandwidth but there
5767 is non-guard bandwidth, don't crash during path selection. Bugfix
5769 - Fix an impossible-to-actually-trigger buffer overflow in relay
5770 descriptor generation. Bugfix on 0.1.0.15.
5772 o Minor bugfixes (privacy):
5773 - Fix an instance where a Tor directory mirror might accidentally
5774 log the IP address of a misbehaving Tor client. Bugfix on
5776 - Don't list Windows capabilities in relay descriptors. We never made
5777 use of them, and maybe it's a bad idea to publish them. Bugfix
5780 o Minor bugfixes (other):
5781 - Resolve an edge case in path weighting that could make us misweight
5782 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
5783 - Fix statistics on client numbers by country as seen by bridges that
5784 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
5785 intervals instead of variable 12-to-48-hour intervals.
5786 - After we free an internal connection structure, overwrite it
5787 with a different memory value than we use for overwriting a freed
5788 internal circuit structure. Should help with debugging. Suggested
5790 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5794 - Remove the HSAuthorityRecordStats option that version 0 hidden
5795 service authorities could have used to track statistics of overall
5796 hidden service usage.
5799 Changes in version 0.2.1.22 - 2010-01-19
5800 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5801 authorities -- it would tell you its whole history of bridge descriptors
5802 if you make the right directory request. This stable update also
5803 rotates two of the seven v3 directory authority keys and locations.
5805 o Directory authority changes:
5806 - Rotate keys (both v3 identity and relay identity) for moria1
5810 - Stop bridge directory authorities from answering dbg-stability.txt
5811 directory queries, which would let people fetch a list of all
5812 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5815 Changes in version 0.2.1.21 - 2009-12-21
5816 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5817 library. If you use Tor on Linux / Unix and you're getting SSL
5818 renegotiation errors, upgrading should help. We also recommend an
5819 upgrade if you're an exit relay.
5822 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5823 handshake from working unless we explicitly tell OpenSSL that we
5824 are using SSL renegotiation safely. We are, of course, but OpenSSL
5825 0.9.8l won't work unless we say we are.
5826 - Avoid crashing if the client is trying to upload many bytes and the
5827 circuit gets torn down at the same time, or if the flip side
5828 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5831 - Do not refuse to learn about authority certs and v2 networkstatus
5832 documents that are older than the latest consensus. This bug might
5833 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5834 Spotted and fixed by xmux.
5835 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5836 trigger platform-specific option misparsing case found by Coverity
5838 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5839 trigger assert. Fixes bug 1173.
5842 Changes in version 0.2.2.6-alpha - 2009-11-19
5843 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
5844 support for the new lower-footprint "microdescriptor" directory design,
5845 future-proofing our consensus format against new hash functions or
5846 other changes, and an Android port. It also makes Tor compatible with
5847 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
5850 - Directory authorities can now create, vote on, and serve multiple
5851 parallel formats of directory data as part of their voting process.
5852 Partially implements Proposal 162: "Publish the consensus in
5854 - Directory authorities can now agree on and publish small summaries
5855 of router information that clients can use in place of regular
5856 server descriptors. This transition will eventually allow clients
5857 to use far less bandwidth for downloading information about the
5858 network. Begins the implementation of Proposal 158: "Clients
5859 download consensus + microdescriptors".
5860 - The directory voting system is now extensible to use multiple hash
5861 algorithms for signatures and resource selection. Newer formats
5862 are signed with SHA256, with a possibility for moving to a better
5863 hash algorithm in the future.
5864 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5865 current and future memory pages via mlockall(). On supported
5866 platforms (modern Linux and probably BSD but not Windows or OS X),
5867 this should effectively disable any and all attempts to page out
5868 memory. This option requires that you start your Tor as root --
5869 if you use DisableAllSwap, please consider using the User option
5870 to properly reduce the privileges of your Tor.
5871 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5872 to help Tor build correctly for Android phones.
5875 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5876 handshake from working unless we explicitly tell OpenSSL that we
5877 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
5878 won't work unless we say we are.
5881 - Fix a crash bug when trying to initialize the evdns module in
5882 Libevent 2. Bugfix on 0.2.1.16-rc.
5883 - Stop logging at severity 'warn' when some other Tor client tries
5884 to establish a circuit with us using weak DH keys. It's a protocol
5885 violation, but that doesn't mean ordinary users need to hear about
5886 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5887 - Do not refuse to learn about authority certs and v2 networkstatus
5888 documents that are older than the latest consensus. This bug might
5889 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5890 Spotted and fixed by xmux.
5891 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5892 - If all authorities restart at once right before a consensus vote,
5893 nobody will vote about "Running", and clients will get a consensus
5894 with no usable relays. Instead, authorities refuse to build a
5895 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5896 - If your relay can't keep up with the number of incoming create
5897 cells, it would log one warning per failure into your logs. Limit
5898 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5899 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5900 on 0.2.0.3-alpha; fixes bug 1113.
5901 - Fix a memory leak on directory authorities during voting that was
5902 introduced in 0.2.2.1-alpha. Found via valgrind.
5905 Changes in version 0.2.1.20 - 2009-10-15
5906 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5907 services at once, prepares for more performance improvements, and
5908 fixes a bunch of smaller bugs.
5910 The Windows and OS X bundles also include a more recent Vidalia,
5911 and switch from Privoxy to Polipo.
5913 The OS X installers are now drag and drop. It's best to un-install
5914 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5915 you want to upgrade, you'll need to update the paths for Tor and Polipo
5916 in the Vidalia Settings window.
5919 - Send circuit or stream sendme cells when our window has decreased
5920 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5921 by Karsten when testing the "reduce circuit window" performance
5922 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5923 before the release of Tor 0.0.0. This is the new winner of the
5925 - Fix a remotely triggerable memory leak when a consensus document
5926 contains more than one signature from the same voter. Bugfix on
5928 - Avoid segfault in rare cases when finishing an introduction circuit
5929 as a client and finding out that we don't have an introduction key
5930 for it. Fixes bug 1073. Reported by Aaron Swartz.
5933 - Tor now reads the "circwindow" parameter out of the consensus,
5934 and uses that value for its circuit package window rather than the
5935 default of 1000 cells. Begins the implementation of proposal 168.
5937 o New directory authorities:
5938 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5940 - Move moria1 and tonga to alternate IP addresses.
5943 - Fix a signed/unsigned compile warning in 0.2.1.19.
5944 - Fix possible segmentation fault on directory authorities. Bugfix on
5946 - Fix an extremely rare infinite recursion bug that could occur if
5947 we tried to log a message after shutting down the log subsystem.
5948 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5949 - Fix an obscure bug where hidden services on 64-bit big-endian
5950 systems might mis-read the timestamp in v3 introduce cells, and
5951 refuse to connect back to the client. Discovered by "rotor".
5952 Bugfix on 0.2.1.6-alpha.
5953 - We were triggering a CLOCK_SKEW controller status event whenever
5954 we connect via the v2 connection protocol to any relay that has
5955 a wrong clock. Instead, we should only inform the controller when
5956 it's a trusted authority that claims our clock is wrong. Bugfix
5957 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5958 - We were telling the controller about CHECKING_REACHABILITY and
5959 REACHABILITY_FAILED status events whenever we launch a testing
5960 circuit or notice that one has failed. Instead, only tell the
5961 controller when we want to inform the user of overall success or
5962 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5964 - Don't warn when we're using a circuit that ends with a node
5965 excluded in ExcludeExitNodes, but the circuit is not used to access
5966 the outside world. This should help fix bug 1090. Bugfix on
5968 - Work around a small memory leak in some versions of OpenSSL that
5969 stopped the memory used by the hostname TLS extension from being
5973 - Add a "getinfo status/accepted-server-descriptor" controller
5974 command, which is the recommended way for controllers to learn
5975 whether our server descriptor has been successfully received by at
5976 least on directory authority. Un-recommend good-server-descriptor
5977 getinfo and status events until we have a better design for them.
5980 Changes in version 0.2.2.5-alpha - 2009-10-11
5981 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5984 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5986 o Directory authorities:
5987 - Temporarily (just for this release) move dizum to an alternate
5991 Changes in version 0.2.2.4-alpha - 2009-10-10
5992 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5993 introduces a new unit test framework, shifts directry authority
5994 addresses around to reduce the impact from recent blocking events,
5995 and fixes a few smaller bugs.
5998 - Fix several more asserts in the circuit_build_times code, for
5999 example one that causes Tor to fail to start once we have
6000 accumulated 5000 build times in the state file. Bugfixes on
6001 0.2.2.2-alpha; fixes bug 1108.
6003 o New directory authorities:
6004 - Move moria1 and Tonga to alternate IP addresses.
6007 - Log SSL state transitions at debug level during handshake, and
6008 include SSL states in error messages. This may help debug future
6009 SSL handshake issues.
6010 - Add a new "Handshake" log domain for activities that happen
6011 during the TLS handshake.
6012 - Revert to the "June 3 2009" ip-to-country file. The September one
6013 seems to have removed most US IP addresses.
6014 - Directory authorities now reject Tor relays with versions less than
6015 0.1.2.14. This step cuts out four relays from the current network,
6016 none of which are very big.
6019 - Fix a couple of smaller issues with gathering statistics. Bugfixes
6021 - Fix two memory leaks in the error case of
6022 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
6023 - Don't count one-hop circuits when we're estimating how long it
6024 takes circuits to build on average. Otherwise we'll set our circuit
6025 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
6026 - Directory authorities no longer change their opinion of, or vote on,
6027 whether a router is Running, unless they have themselves been
6028 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
6031 o Code simplifications and refactoring:
6032 - Revise our unit tests to use the "tinytest" framework, so we
6033 can run tests in their own processes, have smarter setup/teardown
6034 code, and so on. The unit test code has moved to its own
6035 subdirectory, and has been split into multiple modules.
6038 Changes in version 0.2.2.3-alpha - 2009-09-23
6039 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
6042 - Fix an overzealous assert in our new circuit build timeout code.
6043 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
6046 - If the networkstatus consensus tells us that we should use a
6047 negative circuit package window, ignore it. Otherwise we'll
6048 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
6051 Changes in version 0.2.2.2-alpha - 2009-09-21
6052 Tor 0.2.2.2-alpha introduces our latest performance improvement for
6053 clients: Tor tracks the average time it takes to build a circuit, and
6054 avoids using circuits that take too long to build. For fast connections,
6055 this feature can cut your expected latency in half. For slow or flaky
6056 connections, it could ruin your Tor experience. Let us know if it does!
6059 - Tor now tracks how long it takes to build client-side circuits
6060 over time, and adapts its timeout to local network performance.
6061 Since a circuit that takes a long time to build will also provide
6062 bad performance, we get significant latency improvements by
6063 discarding the slowest 20% of circuits. Specifically, Tor creates
6064 circuits more aggressively than usual until it has enough data
6065 points for a good timeout estimate. Implements proposal 151.
6066 We are especially looking for reports (good and bad) from users with
6067 both EDGE and broadband connections that can move from broadband
6068 to EDGE and find out if the build-time data in the .tor/state gets
6069 reset without loss of Tor usability. You should also see a notice
6070 log message telling you that Tor has reset its timeout.
6071 - Directory authorities can now vote on arbitary integer values as
6072 part of the consensus process. This is designed to help set
6073 network-wide parameters. Implements proposal 167.
6074 - Tor now reads the "circwindow" parameter out of the consensus,
6075 and uses that value for its circuit package window rather than the
6076 default of 1000 cells. Begins the implementation of proposal 168.
6079 - Fix a remotely triggerable memory leak when a consensus document
6080 contains more than one signature from the same voter. Bugfix on
6084 - Fix an extremely rare infinite recursion bug that could occur if
6085 we tried to log a message after shutting down the log subsystem.
6086 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6087 - Fix parsing for memory or time units given without a space between
6088 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
6089 - A networkstatus vote must contain exactly one signature. Spec
6090 conformance issue. Bugfix on 0.2.0.3-alpha.
6091 - Fix an obscure bug where hidden services on 64-bit big-endian
6092 systems might mis-read the timestamp in v3 introduce cells, and
6093 refuse to connect back to the client. Discovered by "rotor".
6094 Bugfix on 0.2.1.6-alpha.
6095 - We were triggering a CLOCK_SKEW controller status event whenever
6096 we connect via the v2 connection protocol to any relay that has
6097 a wrong clock. Instead, we should only inform the controller when
6098 it's a trusted authority that claims our clock is wrong. Bugfix
6099 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6100 - We were telling the controller about CHECKING_REACHABILITY and
6101 REACHABILITY_FAILED status events whenever we launch a testing
6102 circuit or notice that one has failed. Instead, only tell the
6103 controller when we want to inform the user of overall success or
6104 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6106 - Don't warn when we're using a circuit that ends with a node
6107 excluded in ExcludeExitNodes, but the circuit is not used to access
6108 the outside world. This should help fix bug 1090, but more problems
6109 remain. Bugfix on 0.2.1.6-alpha.
6110 - Work around a small memory leak in some versions of OpenSSL that
6111 stopped the memory used by the hostname TLS extension from being
6113 - Make our 'torify' script more portable; if we have only one of
6114 'torsocks' or 'tsocks' installed, don't complain to the user;
6115 and explain our warning about tsocks better.
6118 - Add a "getinfo status/accepted-server-descriptor" controller
6119 command, which is the recommended way for controllers to learn
6120 whether our server descriptor has been successfully received by at
6121 least on directory authority. Un-recommend good-server-descriptor
6122 getinfo and status events until we have a better design for them.
6123 - Update to the "September 4 2009" ip-to-country file.
6126 Changes in version 0.2.2.1-alpha - 2009-08-26
6127 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
6128 Tor clients to bootstrap on networks where only port 80 is reachable,
6129 makes it more straightforward to support hardware crypto accelerators,
6130 and starts the groundwork for gathering stats safely at relays.
6133 - Start the process of disabling ".exit" address notation, since it
6134 can be used for a variety of esoteric application-level attacks
6135 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
6138 o New directory authorities:
6139 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6143 - New AccelName and AccelDir options add support for dynamic OpenSSL
6144 hardware crypto acceleration engines.
6145 - Tor now supports tunneling all of its outgoing connections over
6146 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
6147 configuration options. Code by Christopher Davis.
6150 - Send circuit or stream sendme cells when our window has decreased
6151 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6152 by Karsten when testing the "reduce circuit window" performance
6153 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6154 before the release of Tor 0.0.0. This is the new winner of the
6157 o New options for gathering stats safely:
6158 - Directory mirrors that set "DirReqStatistics 1" write statistics
6159 about directory requests to disk every 24 hours. As compared to the
6160 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
6161 1) stats are written to disk exactly every 24 hours; 2) estimated
6162 shares of v2 and v3 requests are determined as mean values, not at
6163 the end of a measurement period; 3) unresolved requests are listed
6164 with country code '??'; 4) directories also measure download times.
6165 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
6166 number of exit streams and transferred bytes per port to disk every
6168 - Relays that set "CellStatistics 1" write statistics on how long
6169 cells spend in their circuit queues to disk every 24 hours.
6170 - Entry nodes that set "EntryStatistics 1" write statistics on the
6171 rough number and origins of connecting clients to disk every 24
6173 - Relays that write any of the above statistics to disk and set
6174 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
6175 their extra-info documents.
6178 - New --digests command-line switch to output the digests of the
6179 source files Tor was built with.
6180 - The "torify" script now uses torsocks where available.
6181 - The memarea code now uses a sentinel value at the end of each area
6182 to make sure nothing writes beyond the end of an area. This might
6183 help debug some conceivable causes of bug 930.
6184 - Time and memory units in the configuration file can now be set to
6185 fractional units. For example, "2.5 GB" is now a valid value for
6187 - Certain Tor clients (such as those behind check.torproject.org) may
6188 want to fetch the consensus in an extra early manner. To enable this
6189 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
6190 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
6191 as only certain clients who must have this information sooner should
6193 - Instead of adding the svn revision to the Tor version string, report
6194 the git commit (when we're building from a git checkout).
6197 - If any of the v3 certs we download are unparseable, we should
6198 actually notice the failure so we don't retry indefinitely. Bugfix
6199 on 0.2.0.x; reported by "rotator".
6200 - If the cached cert file is unparseable, warn but don't exit.
6201 - Fix possible segmentation fault on directory authorities. Bugfix on
6203 - When Tor fails to parse a descriptor of any kind, dump it to disk.
6204 Might help diagnosing bug 1051.
6206 o Deprecated and removed features:
6207 - The controller no longer accepts the old obsolete "addr-mappings/"
6208 or "unregistered-servers-" GETINFO values.
6209 - Hidden services no longer publish version 0 descriptors, and clients
6210 do not request or use version 0 descriptors. However, the old hidden
6211 service authorities still accept and serve version 0 descriptors
6212 when contacted by older hidden services/clients.
6213 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
6214 always on; using them is necessary for correct forward-compatible
6216 - Remove support for .noconnect style addresses. Nobody was using
6217 them, and they provided another avenue for detecting Tor users
6218 via application-level web tricks.
6220 o Packaging changes:
6221 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
6222 installer bundles. See
6223 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
6224 for details of what's new in Vidalia 0.2.3.
6225 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
6226 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
6227 configuration file, rather than the old Privoxy.
6228 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
6229 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
6230 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
6231 better compatibility with OS X 10.6, aka Snow Leopard.
6232 - OS X Vidalia Bundle: The multi-package installer is now replaced
6233 by a simple drag and drop to the /Applications folder. This change
6234 occurred with the upgrade to Vidalia 0.2.3.
6237 Changes in version 0.2.1.19 - 2009-07-28
6238 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
6239 services on Tor 0.2.1.3-alpha through 0.2.1.18.
6242 - Make accessing hidden services on 0.2.1.x work right again.
6243 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
6244 part of patch provided by "optimist".
6247 - When a relay/bridge is writing out its identity key fingerprint to
6248 the "fingerprint" file and to its logs, write it without spaces. Now
6249 it will look like the fingerprints in our bridges documentation,
6250 and confuse fewer users.
6253 - Relays no longer publish a new server descriptor if they change
6254 their MaxAdvertisedBandwidth config option but it doesn't end up
6255 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
6256 fixes bug 1026. Patch from Sebastian.
6257 - Avoid leaking memory every time we get a create cell but we have
6258 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
6259 fixes bug 1034. Reported by BarkerJr.
6262 Changes in version 0.2.1.18 - 2009-07-24
6263 Tor 0.2.1.18 lays the foundations for performance improvements,
6264 adds status events to help users diagnose bootstrap problems, adds
6265 optional authentication/authorization for hidden services, fixes a
6266 variety of potential anonymity problems, and includes a huge pile of
6267 other features and bug fixes.
6270 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
6273 Changes in version 0.2.1.17-rc - 2009-07-07
6274 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
6275 candidate for the 0.2.1.x series. It lays the groundwork for further
6276 client performance improvements, and also fixes a big bug with directory
6277 authorities that were causing them to assign Guard and Stable flags
6280 The Windows bundles also finally include the geoip database that we
6281 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
6282 should actually install Torbutton rather than giving you a cryptic
6283 failure message (oops).
6286 - Clients now use the bandwidth values in the consensus, rather than
6287 the bandwidth values in each relay descriptor. This approach opens
6288 the door to more accurate bandwidth estimates once the directory
6289 authorities start doing active measurements. Implements more of
6293 - When Tor clients restart after 1-5 days, they discard all their
6294 cached descriptors as too old, but they still use the cached
6295 consensus document. This approach is good for robustness, but
6296 bad for performance: since they don't know any bandwidths, they
6297 end up choosing at random rather than weighting their choice by
6298 speed. Fixed by the above feature of putting bandwidths in the
6299 consensus. Bugfix on 0.2.0.x.
6300 - Directory authorities were neglecting to mark relays down in their
6301 internal histories if the relays fall off the routerlist without
6302 ever being found unreachable. So there were relays in the histories
6303 that haven't been seen for eight months, and are listed as being
6304 up for eight months. This wreaked havoc on the "median wfu"
6305 and "median mtbf" calculations, in turn making Guard and Stable
6306 flags very wrong, hurting network performance. Fixes bugs 696 and
6307 969. Bugfix on 0.2.0.6-alpha.
6310 - Serve the DirPortFrontPage page even when we have been approaching
6311 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
6312 - The control port would close the connection before flushing long
6313 replies, such as the network consensus, if a QUIT command was issued
6314 before the reply had completed. Now, the control port flushes all
6315 pending replies before closing the connection. Also fixed a spurious
6316 warning when a QUIT command is issued after a malformed or rejected
6317 AUTHENTICATE command, but before the connection was closed. Patch
6318 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
6319 - When we can't find an intro key for a v2 hidden service descriptor,
6320 fall back to the v0 hidden service descriptor and log a bug message.
6321 Workaround for bug 1024.
6322 - Fix a log message that did not respect the SafeLogging option.
6326 - If we're a relay and we change our IP address, be more verbose
6327 about the reason that made us change. Should help track down
6328 further bugs for relays on dynamic IP addresses.
6331 Changes in version 0.2.0.35 - 2009-06-24
6333 - Avoid crashing in the presence of certain malformed descriptors.
6334 Found by lark, and by automated fuzzing.
6335 - Fix an edge case where a malicious exit relay could convince a
6336 controller that the client's DNS question resolves to an internal IP
6337 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6340 - Finally fix the bug where dynamic-IP relays disappear when their
6341 IP address changes: directory mirrors were mistakenly telling
6342 them their old address if they asked via begin_dir, so they
6343 never got an accurate answer about their new address, so they
6344 just vanished after a day. For belt-and-suspenders, relays that
6345 don't set Address in their config now avoid using begin_dir for
6346 all direct connections. Should fix bugs 827, 883, and 900.
6347 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6348 that would occur on some exit nodes when DNS failures and timeouts
6349 occurred in certain patterns. Fix for bug 957.
6352 - When starting with a cache over a few days old, do not leak
6353 memory for the obsolete router descriptors in it. Bugfix on
6354 0.2.0.33; fixes bug 672.
6355 - Hidden service clients didn't use a cached service descriptor that
6356 was older than 15 minutes, but wouldn't fetch a new one either,
6357 because there was already one in the cache. Now, fetch a v2
6358 descriptor unless the same descriptor was added to the cache within
6359 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6362 Changes in version 0.2.1.16-rc - 2009-06-20
6363 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
6364 a bunch of minor bugs.
6367 - Fix an edge case where a malicious exit relay could convince a
6368 controller that the client's DNS question resolves to an internal IP
6369 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6371 o Major performance improvements (on 0.2.0.x):
6372 - Disable and refactor some debugging checks that forced a linear scan
6373 over the whole server-side DNS cache. These accounted for over 50%
6374 of CPU time on a relatively busy exit node's gprof profile. Found
6376 - Disable some debugging checks that appeared in exit node profile
6380 - Update to the "June 3 2009" ip-to-country file.
6381 - Do not have tor-resolve automatically refuse all .onion addresses;
6382 if AutomapHostsOnResolve is set in your torrc, this will work fine.
6384 o Minor bugfixes (on 0.2.0.x):
6385 - Log correct error messages for DNS-related network errors on
6387 - Fix a race condition that could cause crashes or memory corruption
6388 when running as a server with a controller listening for log
6390 - Avoid crashing when we have a policy specified in a DirPolicy or
6391 SocksPolicy or ReachableAddresses option with ports set on it,
6392 and we re-load the policy. May fix bug 996.
6393 - Hidden service clients didn't use a cached service descriptor that
6394 was older than 15 minutes, but wouldn't fetch a new one either,
6395 because there was already one in the cache. Now, fetch a v2
6396 descriptor unless the same descriptor was added to the cache within
6397 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6399 o Minor bugfixes (on 0.2.1.x):
6400 - Don't warn users about low port and hibernation mix when they
6401 provide a *ListenAddress directive to fix that. Bugfix on
6403 - When switching back and forth between bridge mode, do not start
6404 gathering GeoIP data until two hours have passed.
6405 - Do not complain that the user has requested an excluded node as
6406 an exit when the node is not really an exit. This could happen
6407 because the circuit was for testing, or an introduction point.
6411 Changes in version 0.2.1.15-rc - 2009-05-25
6412 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
6413 series. It fixes a major bug on fast exit relays, as well as a variety
6416 o Major bugfixes (on 0.2.0.x):
6417 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6418 that would occur on some exit nodes when DNS failures and timeouts
6419 occurred in certain patterns. Fix for bug 957.
6421 o Minor bugfixes (on 0.2.0.x):
6422 - Actually return -1 in the error case for read_bandwidth_usage().
6423 Harmless bug, since we currently don't care about the return value
6424 anywhere. Bugfix on 0.2.0.9-alpha.
6425 - Provide a more useful log message if bug 977 (related to buffer
6426 freelists) ever reappears, and do not crash right away.
6427 - Fix an assertion failure on 64-bit platforms when we allocated
6428 memory right up to the end of a memarea, then realigned the memory
6429 one step beyond the end. Fixes a possible cause of bug 930.
6430 - Protect the count of open sockets with a mutex, so we can't
6431 corrupt it when two threads are closing or opening sockets at once.
6432 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
6433 - Don't allow a bridge to publish its router descriptor to a
6434 non-bridge directory authority. Fixes part of bug 932.
6435 - When we change to or from being a bridge, reset our counts of
6436 client usage by country. Fixes bug 932.
6437 - Fix a bug that made stream bandwidth get misreported to the
6439 - Stop using malloc_usable_size() to use more area than we had
6440 actually allocated: it was safe, but made valgrind really unhappy.
6441 - Fix a memory leak when v3 directory authorities load their keys
6442 and cert from disk. Bugfix on 0.2.0.1-alpha.
6444 o Minor bugfixes (on 0.2.1.x):
6445 - Fix use of freed memory when deciding to mark a non-addable
6446 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
6449 Changes in version 0.2.1.14-rc - 2009-04-12
6450 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
6451 series. It begins fixing some major performance problems, and also
6452 finally addresses the bug that was causing relays on dynamic IP
6453 addresses to fall out of the directory.
6456 - Clients replace entry guards that were chosen more than a few months
6457 ago. This change should significantly improve client performance,
6458 especially once more people upgrade, since relays that have been
6459 a guard for a long time are currently overloaded.
6461 o Major bugfixes (on 0.2.0):
6462 - Finally fix the bug where dynamic-IP relays disappear when their
6463 IP address changes: directory mirrors were mistakenly telling
6464 them their old address if they asked via begin_dir, so they
6465 never got an accurate answer about their new address, so they
6466 just vanished after a day. For belt-and-suspenders, relays that
6467 don't set Address in their config now avoid using begin_dir for
6468 all direct connections. Should fix bugs 827, 883, and 900.
6469 - Relays were falling out of the networkstatus consensus for
6470 part of a day if they changed their local config but the
6471 authorities discarded their new descriptor as "not sufficiently
6472 different". Now directory authorities accept a descriptor as changed
6473 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
6475 - Avoid crashing in the presence of certain malformed descriptors.
6476 Found by lark, and by automated fuzzing.
6479 - When generating circuit events with verbose nicknames for
6480 controllers, try harder to look up nicknames for routers on a
6481 circuit. (Previously, we would look in the router descriptors we had
6482 for nicknames, but not in the consensus.) Partial fix for bug 941.
6483 - If the bridge config line doesn't specify a port, assume 443.
6484 This makes bridge lines a bit smaller and easier for users to
6486 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
6487 bytes (aka 20KB/s), to match our documentation. Also update
6488 directory authorities so they always assign the Fast flag to relays
6489 with 20KB/s of capacity. Now people running relays won't suddenly
6490 find themselves not seeing any use, if the network gets faster
6492 - Update to the "April 3 2009" ip-to-country file.
6495 - Avoid trying to print raw memory to the logs when we decide to
6496 give up on downloading a given relay descriptor. Bugfix on
6498 - In tor-resolve, when the Tor client to use is specified by
6499 <hostname>:<port>, actually use the specified port rather than
6500 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
6501 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
6502 - When starting with a cache over a few days old, do not leak
6503 memory for the obsolete router descriptors in it. Bugfix on
6505 - Avoid double-free on list of successfully uploaded hidden
6506 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
6507 - Change memarea_strndup() implementation to work even when
6508 duplicating a string at the end of a page. This bug was
6509 harmless for now, but could have meant crashes later. Fix by
6510 lark. Bugfix on 0.2.1.1-alpha.
6511 - Limit uploaded directory documents to be 16M rather than 500K.
6512 The directory authorities were refusing v3 consensus votes from
6513 other authorities, since the votes are now 504K. Fixes bug 959;
6514 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
6515 - Directory authorities should never send a 503 "busy" response to
6516 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
6520 Changes in version 0.2.1.13-alpha - 2009-03-09
6521 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
6522 cleanups. We're finally getting close to a release candidate.
6525 - Correctly update the list of which countries we exclude as
6526 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
6527 lark. Bugfix on 0.2.1.6-alpha.
6529 o Minor bugfixes (on 0.2.0.x and earlier):
6530 - Automatically detect MacOSX versions earlier than 10.4.0, and
6531 disable kqueue from inside Tor when running with these versions.
6532 We previously did this from the startup script, but that was no
6533 help to people who didn't use the startup script. Resolves bug 863.
6534 - When we had picked an exit node for a connection, but marked it as
6535 "optional", and it turned out we had no onion key for the exit,
6536 stop wanting that exit and try again. This situation may not
6537 be possible now, but will probably become feasible with proposal
6538 158. Spotted by rovv. Fixes another case of bug 752.
6539 - Clients no longer cache certificates for authorities they do not
6540 recognize. Bugfix on 0.2.0.9-alpha.
6541 - When we can't transmit a DNS request due to a network error, retry
6542 it after a while, and eventually transmit a failing response to
6543 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
6544 - If the controller claimed responsibility for a stream, but that
6545 stream never finished making its connection, it would live
6546 forever in circuit_wait state. Now we close it after SocksTimeout
6547 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
6548 - Drop begin cells to a hidden service if they come from the middle
6549 of a circuit. Patch from lark.
6550 - When we erroneously receive two EXTEND cells for the same circuit
6551 ID on the same connection, drop the second. Patch from lark.
6552 - Fix a crash that occurs on exit nodes when a nameserver request
6553 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
6554 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
6556 - Do not assume that a stack-allocated character array will be
6557 64-bit aligned on platforms that demand that uint64_t access is
6558 aligned. Possible fix for bug 604.
6559 - Parse dates and IPv4 addresses in a locale- and libc-independent
6560 manner, to avoid platform-dependent behavior on malformed input.
6561 - Build correctly when configured to build outside the main source
6562 path. Patch from Michael Gold.
6563 - We were already rejecting relay begin cells with destination port
6564 of 0. Now also reject extend cells with destination port or address
6565 of 0. Suggested by lark.
6567 o Minor bugfixes (on 0.2.1.x):
6568 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
6569 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
6570 - If we're an exit node, scrub the IP address to which we are exiting
6571 in the logs. Bugfix on 0.2.1.8-alpha.
6574 - On Linux, use the prctl call to re-enable core dumps when the user
6576 - New controller event NEWCONSENSUS that lists the networkstatus
6577 lines for every recommended relay. Now controllers like Torflow
6578 can keep up-to-date on which relays they should be using.
6579 - Update to the "February 26 2009" ip-to-country file.
6582 Changes in version 0.2.0.34 - 2009-02-08
6583 Tor 0.2.0.34 features several more security-related fixes. You should
6584 upgrade, especially if you run an exit relay (remote crash) or a
6585 directory authority (remote infinite loop), or you're on an older
6586 (pre-XP) or not-recently-patched Windows (remote exploit).
6588 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
6589 have many known flaws, and nobody should be using them. You should
6590 upgrade. If you're using a Linux or BSD and its packages are obsolete,
6591 stop using those packages and upgrade anyway.
6594 - Fix an infinite-loop bug on handling corrupt votes under certain
6595 circumstances. Bugfix on 0.2.0.8-alpha.
6596 - Fix a temporary DoS vulnerability that could be performed by
6597 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6598 - Avoid a potential crash on exit nodes when processing malformed
6599 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
6600 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6601 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6604 - Fix compilation on systems where time_t is a 64-bit integer.
6605 Patch from Matthias Drochner.
6606 - Don't consider expiring already-closed client connections. Fixes
6607 bug 893. Bugfix on 0.0.2pre20.
6610 Changes in version 0.2.1.12-alpha - 2009-02-08
6611 Tor 0.2.1.12-alpha features several more security-related fixes. You
6612 should upgrade, especially if you run an exit relay (remote crash) or
6613 a directory authority (remote infinite loop), or you're on an older
6614 (pre-XP) or not-recently-patched Windows (remote exploit). It also
6615 includes a big pile of minor bugfixes and cleanups.
6618 - Fix an infinite-loop bug on handling corrupt votes under certain
6619 circumstances. Bugfix on 0.2.0.8-alpha.
6620 - Fix a temporary DoS vulnerability that could be performed by
6621 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6622 - Avoid a potential crash on exit nodes when processing malformed
6623 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
6626 - Let controllers actually ask for the "clients_seen" event for
6627 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
6628 reported by Matt Edman.
6629 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
6631 - Fix a bug in address parsing that was preventing bridges or hidden
6632 service targets from being at IPv6 addresses.
6633 - Solve a bug that kept hardware crypto acceleration from getting
6634 enabled when accounting was turned on. Fixes bug 907. Bugfix on
6636 - Remove a bash-ism from configure.in to build properly on non-Linux
6637 platforms. Bugfix on 0.2.1.1-alpha.
6638 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
6639 headers. Bugfix on 0.2.0.10-alpha.
6640 - Don't consider expiring already-closed client connections. Fixes
6641 bug 893. Bugfix on 0.0.2pre20.
6642 - Fix another interesting corner-case of bug 891 spotted by rovv:
6643 Previously, if two hosts had different amounts of clock drift, and
6644 one of them created a new connection with just the wrong timing,
6645 the other might decide to deprecate the new connection erroneously.
6646 Bugfix on 0.1.1.13-alpha.
6647 - Resolve a very rare crash bug that could occur when the user forced
6648 a nameserver reconfiguration during the middle of a nameserver
6649 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
6650 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
6651 Bugfix on 0.2.1.7-alpha.
6652 - If we're using bridges and our network goes away, be more willing
6653 to forgive our bridges and try again when we get an application
6654 request. Bugfix on 0.2.0.x.
6657 - Support platforms where time_t is 64 bits long. (Congratulations,
6658 NetBSD!) Patch from Matthias Drochner.
6659 - Add a 'getinfo status/clients-seen' controller command, in case
6660 controllers want to hear clients_seen events but connect late.
6663 - Disable GCC's strict alias optimization by default, to avoid the
6664 likelihood of its introducing subtle bugs whenever our code violates
6665 the letter of C99's alias rules.
6668 Changes in version 0.2.0.33 - 2009-01-21
6669 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
6670 useful to users. It also finally fixes a bug where a relay or client
6671 that's been off for many days would take a long time to bootstrap.
6673 This update also fixes an important security-related bug reported by
6674 Ilja van Sprundel. You should upgrade. (We'll send out more details
6675 about the bug once people have had some time to upgrade.)
6678 - Fix a heap-corruption bug that may be remotely triggerable on
6679 some platforms. Reported by Ilja van Sprundel.
6682 - When a stream at an exit relay is in state "resolving" or
6683 "connecting" and it receives an "end" relay cell, the exit relay
6684 would silently ignore the end cell and not close the stream. If
6685 the client never closes the circuit, then the exit relay never
6686 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6688 - When sending CREATED cells back for a given circuit, use a 64-bit
6689 connection ID to find the right connection, rather than an addr:port
6690 combination. Now that we can have multiple OR connections between
6691 the same ORs, it is no longer possible to use addr:port to uniquely
6692 identify a connection.
6693 - Bridge relays that had DirPort set to 0 would stop fetching
6694 descriptors shortly after startup, and then briefly resume
6695 after a new bandwidth test and/or after publishing a new bridge
6696 descriptor. Bridge users that try to bootstrap from them would
6697 get a recent networkstatus but would get descriptors from up to
6698 18 hours earlier, meaning most of the descriptors were obsolete
6699 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6700 - Prevent bridge relays from serving their 'extrainfo' document
6701 to anybody who asks, now that extrainfo docs include potentially
6702 sensitive aggregated client geoip summaries. Bugfix on
6704 - If the cached networkstatus consensus is more than five days old,
6705 discard it rather than trying to use it. In theory it could be
6706 useful because it lists alternate directory mirrors, but in practice
6707 it just means we spend many minutes trying directory mirrors that
6708 are long gone from the network. Also discard router descriptors as
6709 we load them if they are more than five days old, since the onion
6710 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6713 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6714 could make gcc generate non-functional binary search code. Bugfix
6716 - Build correctly on platforms without socklen_t.
6717 - Compile without warnings on solaris.
6718 - Avoid potential crash on internal error during signature collection.
6719 Fixes bug 864. Patch from rovv.
6720 - Correct handling of possible malformed authority signing key
6721 certificates with internal signature types. Fixes bug 880.
6722 Bugfix on 0.2.0.3-alpha.
6723 - Fix a hard-to-trigger resource leak when logging credential status.
6725 - When we can't initialize DNS because the network is down, do not
6726 automatically stop Tor from starting. Instead, we retry failed
6727 dns_init() every 10 minutes, and change the exit policy to reject
6728 *:* until one succeeds. Fixes bug 691.
6729 - Use 64 bits instead of 32 bits for connection identifiers used with
6730 the controller protocol, to greatly reduce risk of identifier reuse.
6731 - When we're choosing an exit node for a circuit, and we have
6732 no pending streams, choose a good general exit rather than one that
6733 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6734 - Fix another case of assuming, when a specific exit is requested,
6735 that we know more than the user about what hosts it allows.
6736 Fixes one case of bug 752. Patch from rovv.
6737 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6738 seconds. Warn the user if lower values are given in the
6739 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6740 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6741 user if lower values are given in the configuration. Bugfix on
6742 0.1.1.17-rc. Patch by Sebastian.
6743 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6744 the cache because we already had a v0 descriptor with the same ID.
6745 Bugfix on 0.2.0.18-alpha.
6746 - Fix a race condition when freeing keys shared between main thread
6747 and CPU workers that could result in a memory leak. Bugfix on
6748 0.1.0.1-rc. Fixes bug 889.
6749 - Send a valid END cell back when a client tries to connect to a
6750 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6751 840. Patch from rovv.
6752 - Check which hops rendezvous stream cells are associated with to
6753 prevent possible guess-the-streamid injection attacks from
6754 intermediate hops. Fixes another case of bug 446. Based on patch
6756 - If a broken client asks a non-exit router to connect somewhere,
6757 do not even do the DNS lookup before rejecting the connection.
6758 Fixes another case of bug 619. Patch from rovv.
6759 - When a relay gets a create cell it can't decrypt (e.g. because it's
6760 using the wrong onion key), we were dropping it and letting the
6761 client time out. Now actually answer with a destroy cell. Fixes
6762 bug 904. Bugfix on 0.0.2pre8.
6764 o Minor bugfixes (hidden services):
6765 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6766 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6769 - Report the case where all signatures in a detached set are rejected
6770 differently than the case where there is an error handling the
6772 - When we realize that another process has modified our cached
6773 descriptors, print out a more useful error message rather than
6774 triggering an assertion. Fixes bug 885. Patch from Karsten.
6775 - Implement the 0x20 hack to better resist DNS poisoning: set the
6776 case on outgoing DNS requests randomly, and reject responses that do
6777 not match the case correctly. This logic can be disabled with the
6778 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6779 of servers that do not reliably preserve case in replies. See
6780 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6782 - Check DNS replies for more matching fields to better resist DNS
6784 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6785 compress cells, which are basically all encrypted, compressed, or
6789 Changes in version 0.2.1.11-alpha - 2009-01-20
6790 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
6791 week it will take a long time to bootstrap again" bug. It also fixes
6792 an important security-related bug reported by Ilja van Sprundel. You
6793 should upgrade. (We'll send out more details about the bug once people
6794 have had some time to upgrade.)
6797 - Fix a heap-corruption bug that may be remotely triggerable on
6798 some platforms. Reported by Ilja van Sprundel.
6801 - Discard router descriptors as we load them if they are more than
6802 five days old. Otherwise if Tor is off for a long time and then
6803 starts with cached descriptors, it will try to use the onion
6804 keys in those obsolete descriptors when building circuits. Bugfix
6805 on 0.2.0.x. Fixes bug 887.
6808 - Try to make sure that the version of Libevent we're running with
6809 is binary-compatible with the one we built with. May address bug
6811 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
6812 for bug 905. Bugfix on 0.2.1.7-alpha.
6813 - Add a new --enable-local-appdata configuration switch to change
6814 the default location of the datadir on win32 from APPDATA to
6815 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6816 entirely. Patch from coderman.
6819 - Make outbound DNS packets respect the OutboundBindAddress setting.
6820 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
6821 - When our circuit fails at the first hop (e.g. we get a destroy
6822 cell back), avoid using that OR connection anymore, and also
6823 tell all the one-hop directory requests waiting for it that they
6824 should fail. Bugfix on 0.2.1.3-alpha.
6825 - In the torify(1) manpage, mention that tsocks will leak your
6829 Changes in version 0.2.1.10-alpha - 2009-01-06
6830 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
6831 would make the bridge relay not so useful if it had DirPort set to 0,
6832 and one that could let an attacker learn a little bit of information
6833 about the bridge's users), and a bug that would cause your Tor relay
6834 to ignore a circuit create request it can't decrypt (rather than reply
6835 with an error). It also fixes a wide variety of other bugs.
6838 - If the cached networkstatus consensus is more than five days old,
6839 discard it rather than trying to use it. In theory it could
6840 be useful because it lists alternate directory mirrors, but in
6841 practice it just means we spend many minutes trying directory
6842 mirrors that are long gone from the network. Helps bug 887 a bit;
6844 - Bridge relays that had DirPort set to 0 would stop fetching
6845 descriptors shortly after startup, and then briefly resume
6846 after a new bandwidth test and/or after publishing a new bridge
6847 descriptor. Bridge users that try to bootstrap from them would
6848 get a recent networkstatus but would get descriptors from up to
6849 18 hours earlier, meaning most of the descriptors were obsolete
6850 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6851 - Prevent bridge relays from serving their 'extrainfo' document
6852 to anybody who asks, now that extrainfo docs include potentially
6853 sensitive aggregated client geoip summaries. Bugfix on
6857 - New controller event "clients_seen" to report a geoip-based summary
6858 of which countries we've seen clients from recently. Now controllers
6859 like Vidalia can show bridge operators that they're actually making
6861 - Build correctly against versions of OpenSSL 0.9.8 or later built
6862 without support for deprecated functions.
6863 - Update to the "December 19 2008" ip-to-country file.
6865 o Minor bugfixes (on 0.2.0.x):
6866 - Authorities now vote for the Stable flag for any router whose
6867 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6868 - Do not remove routers as too old if we do not have any consensus
6869 document. Bugfix on 0.2.0.7-alpha.
6870 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6871 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6872 - When an exit relay resolves a stream address to a local IP address,
6873 do not just keep retrying that same exit relay over and
6874 over. Instead, just close the stream. Addresses bug 872. Bugfix
6875 on 0.2.0.32. Patch from rovv.
6876 - If a hidden service sends us an END cell, do not consider
6877 retrying the connection; just close it. Patch from rovv.
6878 - When we made bridge authorities stop serving bridge descriptors over
6879 unencrypted links, we also broke DirPort reachability testing for
6880 bridges. So bridges with a non-zero DirPort were printing spurious
6881 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6882 - When a relay gets a create cell it can't decrypt (e.g. because it's
6883 using the wrong onion key), we were dropping it and letting the
6884 client time out. Now actually answer with a destroy cell. Fixes
6885 bug 904. Bugfix on 0.0.2pre8.
6886 - Squeeze 2-5% out of client performance (according to oprofile) by
6887 improving the implementation of some policy-manipulation functions.
6889 o Minor bugfixes (on 0.2.1.x):
6890 - Make get_interface_address() function work properly again; stop
6891 guessing the wrong parts of our address as our address.
6892 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
6893 send on that circuit. Otherwise we might violate the proposal-110
6894 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
6896 - When we're sending non-EXTEND cells to the first hop in a circuit,
6897 for example to use an encrypted directory connection, we don't need
6898 to use RELAY_EARLY cells: the first hop knows what kind of cell
6899 it is, and nobody else can even see the cell type. Conserving
6900 RELAY_EARLY cells makes it easier to cannibalize circuits like
6902 - Stop logging nameserver addresses in reverse order.
6903 - If we are retrying a directory download slowly over and over, do
6904 not automatically give up after the 254th failure. Bugfix on
6906 - Resume reporting accurate "stream end" reasons to the local control
6907 port. They were lost in the changes for Proposal 148. Bugfix on
6910 o Deprecated and removed features:
6911 - The old "tor --version --version" command, which would print out
6912 the subversion "Id" of most of the source files, is now removed. It
6913 turned out to be less useful than we'd expected, and harder to
6916 o Code simplifications and refactoring:
6917 - Change our header file guard macros to be less likely to conflict
6918 with system headers. Adam Langley noticed that we were conflicting
6919 with log.h on Android.
6920 - Tool-assisted documentation cleanup. Nearly every function or
6921 static variable in Tor should have its own documentation now.
6924 Changes in version 0.2.1.9-alpha - 2008-12-25
6925 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
6927 o New directory authorities:
6928 - gabelmoo (the authority run by Karsten Loesing) now has a new
6932 - Never use a connection with a mismatched address to extend a
6933 circuit, unless that connection is canonical. A canonical
6934 connection is one whose address is authenticated by the router's
6935 identity key, either in a NETINFO cell or in a router descriptor.
6936 - Avoid a possible memory corruption bug when receiving hidden service
6937 descriptors. Bugfix on 0.2.1.6-alpha.
6940 - Fix a logic error that would automatically reject all but the first
6941 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
6942 part of bug 813/868. Bug spotted by coderman.
6943 - When a stream at an exit relay is in state "resolving" or
6944 "connecting" and it receives an "end" relay cell, the exit relay
6945 would silently ignore the end cell and not close the stream. If
6946 the client never closes the circuit, then the exit relay never
6947 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
6949 - When we can't initialize DNS because the network is down, do not
6950 automatically stop Tor from starting. Instead, retry failed
6951 dns_init() every 10 minutes, and change the exit policy to reject
6952 *:* until one succeeds. Fixes bug 691.
6955 - Give a better error message when an overzealous init script says
6956 "sudo -u username tor --user username". Makes Bug 882 easier for
6958 - When a directory authority gives us a new guess for our IP address,
6959 log which authority we used. Hopefully this will help us debug
6960 the recent complaints about bad IP address guesses.
6961 - Detect svn revision properly when we're using git-svn.
6962 - Try not to open more than one descriptor-downloading connection
6963 to an authority at once. This should reduce load on directory
6964 authorities. Fixes bug 366.
6965 - Add cross-certification to newly generated certificates, so that
6966 a signing key is enough information to look up a certificate.
6967 Partial implementation of proposal 157.
6968 - Start serving certificates by <identity digest, signing key digest>
6969 pairs. Partial implementation of proposal 157.
6970 - Clients now never report any stream end reason except 'MISC'.
6971 Implements proposal 148.
6972 - On platforms with a maximum syslog string length, truncate syslog
6973 messages to that length ourselves, rather than relying on the
6974 system to do it for us.
6975 - Optimize out calls to time(NULL) that occur for every IO operation,
6976 or for every cell. On systems where time() is a slow syscall,
6977 this fix will be slightly helpful.
6978 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6979 - When we download a descriptor that we then immediately (as
6980 a directory authority) reject, do not retry downloading it right
6981 away. Should save some bandwidth on authorities. Fix for bug
6982 888. Patch by Sebastian Hahn.
6983 - When a download gets us zero good descriptors, do not notify
6984 Tor that new directory information has arrived.
6985 - Avoid some nasty corner cases in the logic for marking connections
6986 as too old or obsolete or noncanonical for circuits. Partial
6989 o Minor features (controller):
6990 - New CONSENSUS_ARRIVED event to note when a new consensus has
6991 been fetched and validated.
6992 - When we realize that another process has modified our cached
6993 descriptors file, print out a more useful error message rather
6994 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6995 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6996 controllers to prevent SIGHUP from reloading the
6997 configuration. Fixes bug 856.
7000 - Resume using the correct "REASON=" stream when telling the
7001 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
7002 - When a canonical connection appears later in our internal list
7003 than a noncanonical one for a given OR ID, always use the
7004 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
7006 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7007 seconds. Warn the user if lower values are given in the
7008 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7009 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7010 user if lower values are given in the configuration. Bugfix on
7011 0.1.1.17-rc. Patch by Sebastian.
7012 - Fix a race condition when freeing keys shared between main thread
7013 and CPU workers that could result in a memory leak. Bugfix on
7014 0.1.0.1-rc. Fixes bug 889.
7016 o Minor bugfixes (hidden services):
7017 - Do not throw away existing introduction points on SIGHUP (bugfix on
7018 0.0.6pre1); also, do not stall hidden services because we're
7019 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
7020 by John Brooks. Patch by Karsten. Fixes bug 874.
7021 - Fix a memory leak when we decline to add a v2 rendezvous
7022 descriptor to the cache because we already had a v0 descriptor
7023 with the same ID. Bugfix on 0.2.0.18-alpha.
7025 o Deprecated and removed features:
7026 - RedirectExits has been removed. It was deprecated since
7028 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
7029 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
7030 - Cell pools are now always enabled; --disable-cell-pools is ignored.
7032 o Code simplifications and refactoring:
7033 - Rename the confusing or_is_obsolete field to the more appropriate
7034 is_bad_for_new_circs, and move it to or_connection_t where it
7036 - Move edge-only flags from connection_t to edge_connection_t: not
7037 only is this better coding, but on machines of plausible alignment,
7038 it should save 4-8 bytes per connection_t. "Every little bit helps."
7039 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
7040 for consistency; keep old option working for backward compatibility.
7041 - Simplify the code for finding connections to use for a circuit.
7044 Changes in version 0.2.1.8-alpha - 2008-12-08
7045 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
7046 builds better on unusual platforms like Solaris and old OS X, and
7047 fixes a variety of other issues.
7050 - New DirPortFrontPage option that takes an html file and publishes
7051 it as "/" on the DirPort. Now relay operators can provide a
7052 disclaimer without needing to set up a separate webserver. There's
7053 a sample disclaimer in contrib/tor-exit-notice.html.
7056 - When the client is choosing entry guards, now it selects at most
7057 one guard from a given relay family. Otherwise we could end up with
7058 all of our entry points into the network run by the same operator.
7059 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
7062 - Fix a DOS opportunity during the voting signature collection process
7063 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7064 - Fix a possible segfault when establishing an exit connection. Bugfix
7068 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
7070 - Made Tor a little less aggressive about deleting expired
7071 certificates. Partial fix for bug 854.
7072 - Stop doing unaligned memory access that generated bus errors on
7073 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
7074 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
7075 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
7076 - Make USR2 log-level switch take effect immediately. Bugfix on
7078 - If one win32 nameserver fails to get added, continue adding the
7079 rest, and don't automatically fail.
7080 - Use fcntl() for locking when flock() is not available. Should fix
7081 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
7082 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7083 could make gcc generate non-functional binary search code. Bugfix
7085 - Build correctly on platforms without socklen_t.
7086 - Avoid potential crash on internal error during signature collection.
7087 Fixes bug 864. Patch from rovv.
7088 - Do not use C's stdio library for writing to log files. This will
7089 improve logging performance by a minute amount, and will stop
7090 leaking fds when our disk is full. Fixes bug 861.
7091 - Stop erroneous use of O_APPEND in cases where we did not in fact
7092 want to re-seek to the end of a file before every last write().
7093 - Correct handling of possible malformed authority signing key
7094 certificates with internal signature types. Fixes bug 880. Bugfix
7096 - Fix a hard-to-trigger resource leak when logging credential status.
7100 - Directory mirrors no longer fetch the v1 directory or
7101 running-routers files. They are obsolete, and nobody asks for them
7102 anymore. This is the first step to making v1 authorities obsolete.
7104 o Minor features (controller):
7105 - Return circuit purposes in response to GETINFO circuit-status. Fixes
7109 Changes in version 0.2.0.32 - 2008-11-20
7110 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
7111 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7112 a smaller security flaw that might allow an attacker to access local
7113 services, further improves hidden service performance, and fixes a
7114 variety of other issues.
7117 - The "User" and "Group" config options did not clear the
7118 supplementary group entries for the Tor process. The "User" option
7119 is now more robust, and we now set the groups to the specified
7120 user's primary group. The "Group" option is now ignored. For more
7121 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7122 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7123 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
7124 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7125 consistently obeyed: if an exit relay refuses a stream because its
7126 exit policy doesn't allow it, we would remember what IP address
7127 the relay said the destination address resolves to, even if it's
7128 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7131 - Fix a DOS opportunity during the voting signature collection process
7132 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7134 o Major bugfixes (hidden services):
7135 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7136 we were failing the whole hidden service request when the v0
7137 descriptor fetch fails, even if the v2 fetch is still pending and
7138 might succeed. Similarly, if the last v2 fetch fails, we were
7139 failing the whole hidden service request even if a v0 fetch is
7140 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7141 - When extending a circuit to a hidden service directory to upload a
7142 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7143 requests failed, because the router descriptor has not been
7144 downloaded yet. In these cases, do not attempt to upload the
7145 rendezvous descriptor, but wait until the router descriptor is
7146 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
7147 descriptor from a hidden service directory for which the router
7148 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
7152 - Fix several infrequent memory leaks spotted by Coverity.
7153 - When testing for libevent functions, set the LDFLAGS variable
7154 correctly. Found by Riastradh.
7155 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7156 bootstrapping with tunneled directory connections. Bugfix on
7157 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7158 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7159 and we know that server B rejects most-but-not all connections to
7160 port 80, we would previously reject the connection. Now, we assume
7161 the user knows what they were asking for. Fixes bug 752. Bugfix
7162 on 0.0.9rc5. Diagnosed by BarkerJr.
7163 - If we overrun our per-second write limits a little, count this as
7164 having used up our write allocation for the second, and choke
7165 outgoing directory writes. Previously, we had only counted this when
7166 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
7167 Bugfix on 0.2.0.x (??).
7168 - Remove the old v2 directory authority 'lefkada' from the default
7169 list. It has been gone for many months.
7170 - Stop doing unaligned memory access that generated bus errors on
7171 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
7172 - Make USR2 log-level switch take effect immediately. Bugfix on
7175 o Minor bugfixes (controller):
7176 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
7177 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
7180 Changes in version 0.2.1.7-alpha - 2008-11-08
7181 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
7182 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7183 a smaller security flaw that might allow an attacker to access local
7184 services, adds better defense against DNS poisoning attacks on exit
7185 relays, further improves hidden service performance, and fixes a
7186 variety of other issues.
7189 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7190 consistently obeyed: if an exit relay refuses a stream because its
7191 exit policy doesn't allow it, we would remember what IP address
7192 the relay said the destination address resolves to, even if it's
7193 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7194 - The "User" and "Group" config options did not clear the
7195 supplementary group entries for the Tor process. The "User" option
7196 is now more robust, and we now set the groups to the specified
7197 user's primary group. The "Group" option is now ignored. For more
7198 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7199 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7200 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
7201 - Do not use or believe expired v3 authority certificates. Patch
7202 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
7205 - Now NodeFamily and MyFamily config options allow spaces in
7206 identity fingerprints, so it's easier to paste them in.
7207 Suggested by Lucky Green.
7208 - Implement the 0x20 hack to better resist DNS poisoning: set the
7209 case on outgoing DNS requests randomly, and reject responses that do
7210 not match the case correctly. This logic can be disabled with the
7211 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
7212 of servers that do not reliably preserve case in replies. See
7213 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7215 - Preserve case in replies to DNSPort requests in order to support
7216 the 0x20 hack for resisting DNS poisoning attacks.
7218 o Hidden service performance improvements:
7219 - When the client launches an introduction circuit, retry with a
7220 new circuit after 30 seconds rather than 60 seconds.
7221 - Launch a second client-side introduction circuit in parallel
7222 after a delay of 15 seconds (based on work by Christian Wilms).
7223 - Hidden services start out building five intro circuits rather
7224 than three, and when the first three finish they publish a service
7225 descriptor using those. Now we publish our service descriptor much
7226 faster after restart.
7229 - Minor fix in the warning messages when you're having problems
7230 bootstrapping; also, be more forgiving of bootstrap problems when
7231 we're still making incremental progress on a given bootstrap phase.
7232 - When we're choosing an exit node for a circuit, and we have
7233 no pending streams, choose a good general exit rather than one that
7234 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7235 - Send a valid END cell back when a client tries to connect to a
7236 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7237 840. Patch from rovv.
7238 - If a broken client asks a non-exit router to connect somewhere,
7239 do not even do the DNS lookup before rejecting the connection.
7240 Fixes another case of bug 619. Patch from rovv.
7241 - Fix another case of assuming, when a specific exit is requested,
7242 that we know more than the user about what hosts it allows.
7243 Fixes another case of bug 752. Patch from rovv.
7244 - Check which hops rendezvous stream cells are associated with to
7245 prevent possible guess-the-streamid injection attacks from
7246 intermediate hops. Fixes another case of bug 446. Based on patch
7248 - Avoid using a negative right-shift when comparing 32-bit
7249 addresses. Possible fix for bug 845 and bug 811.
7250 - Make the assert_circuit_ok() function work correctly on circuits that
7251 have already been marked for close.
7252 - Fix read-off-the-end-of-string error in unit tests when decoding
7253 introduction points.
7254 - Fix uninitialized size field for memory area allocation: may improve
7255 memory performance during directory parsing.
7256 - Treat duplicate certificate fetches as failures, so that we do
7257 not try to re-fetch an expired certificate over and over and over.
7258 - Do not say we're fetching a certificate when we'll in fact skip it
7259 because of a pending download.
7262 Changes in version 0.2.1.6-alpha - 2008-09-30
7263 Tor 0.2.1.6-alpha further improves performance and robustness of
7264 hidden services, starts work on supporting per-country relay selection,
7265 and fixes a variety of smaller issues.
7268 - Implement proposal 121: make it possible to build hidden services
7269 that only certain clients are allowed to connect to. This is
7270 enforced at several points, so that unauthorized clients are unable
7271 to send INTRODUCE cells to the service, or even (depending on the
7272 type of authentication) to learn introduction points. This feature
7273 raises the bar for certain kinds of active attacks against hidden
7274 services. Code by Karsten Loesing.
7275 - Relays now store and serve v2 hidden service descriptors by default,
7276 i.e., the new default value for HidServDirectoryV2 is 1. This is
7277 the last step in proposal 114, which aims to make hidden service
7278 lookups more reliable.
7279 - Start work to allow node restrictions to include country codes. The
7280 syntax to exclude nodes in a country with country code XX is
7281 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
7282 refinement to decide what config options should take priority if
7283 you ask to both use a particular node and exclude it.
7284 - Allow ExitNodes list to include IP ranges and country codes, just
7285 like the Exclude*Nodes lists. Patch from Robert Hogan.
7288 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
7289 Tor to fail to start if you had it configured to use a bridge
7290 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
7291 - When extending a circuit to a hidden service directory to upload a
7292 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7293 requests failed, because the router descriptor had not been
7294 downloaded yet. In these cases, we now wait until the router
7295 descriptor is downloaded, and then retry. Likewise, clients
7296 now skip over a hidden service directory if they don't yet have
7297 its router descriptor, rather than futilely requesting it and
7298 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
7300 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7301 we were failing the whole hidden service request when the v0
7302 descriptor fetch fails, even if the v2 fetch is still pending and
7303 might succeed. Similarly, if the last v2 fetch fails, we were
7304 failing the whole hidden service request even if a v0 fetch is
7305 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7306 - DNS replies need to have names matching their requests, but
7307 these names should be in the questions section, not necessarily
7308 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
7311 - Update to the "September 1 2008" ip-to-country file.
7312 - Allow ports 465 and 587 in the default exit policy again. We had
7313 rejected them in 0.1.0.15, because back in 2005 they were commonly
7314 misconfigured and ended up as spam targets. We hear they are better
7315 locked down these days.
7316 - Use a lockfile to make sure that two Tor processes are not
7317 simultaneously running with the same datadir.
7318 - Serve the latest v3 networkstatus consensus via the control
7319 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
7320 - Better logging about stability/reliability calculations on directory
7322 - Drop the requirement to have an open dir port for storing and
7323 serving v2 hidden service descriptors.
7324 - Directory authorities now serve a /tor/dbg-stability.txt URL to
7325 help debug WFU and MTBF calculations.
7326 - Implement most of Proposal 152: allow specialized servers to permit
7327 single-hop circuits, and clients to use those servers to build
7328 single-hop circuits when using a specialized controller. Patch
7329 from Josh Albrecht. Resolves feature request 768.
7330 - Add a -p option to tor-resolve for specifying the SOCKS port: some
7331 people find host:port too confusing.
7332 - Make TrackHostExit mappings expire a while after their last use, not
7333 after their creation. Patch from Robert Hogan.
7334 - Provide circuit purposes along with circuit events to the controller.
7337 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
7339 - Fixed some memory leaks -- some quite frequent, some almost
7340 impossible to trigger -- based on results from Coverity.
7341 - When testing for libevent functions, set the LDFLAGS variable
7342 correctly. Found by Riastradh.
7343 - Fix an assertion bug in parsing policy-related options; possible fix
7345 - Catch and report a few more bootstrapping failure cases when Tor
7346 fails to establish a TCP connection. Cleanup on 0.2.1.x.
7347 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7348 bootstrapping with tunneled directory connections. Bugfix on
7349 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7350 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7351 and we know that server B rejects most-but-not all connections to
7352 port 80, we would previously reject the connection. Now, we assume
7353 the user knows what they were asking for. Fixes bug 752. Bugfix
7354 on 0.0.9rc5. Diagnosed by BarkerJr.
7355 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
7356 service directories if they have no advertised dir port. Bugfix
7358 - If we overrun our per-second write limits a little, count this as
7359 having used up our write allocation for the second, and choke
7360 outgoing directory writes. Previously, we had only counted this when
7361 we had met our limits precisely. Fixes bug 824. Patch by rovv.
7362 Bugfix on 0.2.0.x (??).
7363 - Avoid a "0 divided by 0" calculation when calculating router uptime
7364 at directory authorities. Bugfix on 0.2.0.8-alpha.
7365 - Make DNS resolved controller events into "CLOSED", not
7366 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
7368 - Fix a bug where an unreachable relay would establish enough
7369 reachability testing circuits to do a bandwidth test -- if
7370 we already have a connection to the middle hop of the testing
7371 circuit, then it could establish the last hop by using the existing
7372 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
7373 circuits no longer use entry guards in 0.2.1.3-alpha.
7374 - If we have correct permissions on $datadir, we complain to stdout
7375 and fail to start. But dangerous permissions on
7376 $datadir/cached-status/ would cause us to open a log and complain
7377 there. Now complain to stdout and fail to start in both cases. Fixes
7378 bug 820, reported by seeess.
7379 - Remove the old v2 directory authority 'lefkada' from the default
7380 list. It has been gone for many months.
7382 o Code simplifications and refactoring:
7383 - Revise the connection_new functions so that a more typesafe variant
7384 exists. This will work better with Coverity, and let us find any
7385 actual mistakes we're making here.
7386 - Refactor unit testing logic so that dmalloc can be used sensibly
7387 with unit tests to check for memory leaks.
7388 - Move all hidden-service related fields from connection and circuit
7389 structure to substructures: this way they won't eat so much memory.
7392 Changes in version 0.2.0.31 - 2008-09-03
7393 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
7394 a big bug we're seeing where in rare cases traffic from one Tor stream
7395 gets mixed into another stream, and fixes a variety of smaller issues.
7398 - Make sure that two circuits can never exist on the same connection
7399 with the same circuit ID, even if one is marked for close. This
7400 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
7401 - Relays now reject risky extend cells: if the extend cell includes
7402 a digest of all zeroes, or asks to extend back to the relay that
7403 sent the extend cell, tear down the circuit. Ideas suggested
7405 - If not enough of our entry guards are available so we add a new
7406 one, we might use the new one even if it overlapped with the
7407 current circuit's exit relay (or its family). Anonymity bugfix
7408 pointed out by rovv.
7411 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7412 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7413 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7414 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7415 - Pick size of default geoip filename string correctly on windows.
7416 Fixes bug 806. Bugfix on 0.2.0.30.
7417 - Make the autoconf script accept the obsolete --with-ssl-dir
7418 option as an alias for the actually-working --with-openssl-dir
7419 option. Fix the help documentation to recommend --with-openssl-dir.
7420 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7421 - When using the TransPort option on OpenBSD, and using the User
7422 option to change UID and drop privileges, make sure to open
7423 /dev/pf before dropping privileges. Fixes bug 782. Patch from
7424 Christopher Davis. Bugfix on 0.1.2.1-alpha.
7425 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7426 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7427 on the client side when connecting to a hidden service. Bugfix
7428 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7429 - When closing an application-side connection because its circuit is
7430 getting torn down, generate the stream event correctly. Bugfix on
7431 0.1.2.x. Anonymous patch.
7434 Changes in version 0.2.1.5-alpha - 2008-08-31
7435 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
7436 in a lot of the infrastructure for adding authorization to hidden
7437 services, lays the groundwork for having clients read their load
7438 balancing information out of the networkstatus consensus rather than
7439 the individual router descriptors, addresses two potential anonymity
7440 issues, and fixes a variety of smaller issues.
7443 - Convert many internal address representations to optionally hold
7445 - Generate and accept IPv6 addresses in many protocol elements.
7446 - Make resolver code handle nameservers located at ipv6 addresses.
7447 - Begin implementation of proposal 121 ("Client authorization for
7448 hidden services"): configure hidden services with client
7449 authorization, publish descriptors for them, and configure
7450 authorization data for hidden services at clients. The next
7451 step is to actually access hidden services that perform client
7453 - More progress toward proposal 141: Network status consensus
7454 documents and votes now contain bandwidth information for each
7455 router and a summary of that router's exit policy. Eventually this
7456 will be used by clients so that they do not have to download every
7457 known descriptor before building circuits.
7459 o Major bugfixes (on 0.2.0.x and before):
7460 - When sending CREATED cells back for a given circuit, use a 64-bit
7461 connection ID to find the right connection, rather than an addr:port
7462 combination. Now that we can have multiple OR connections between
7463 the same ORs, it is no longer possible to use addr:port to uniquely
7464 identify a connection.
7465 - Relays now reject risky extend cells: if the extend cell includes
7466 a digest of all zeroes, or asks to extend back to the relay that
7467 sent the extend cell, tear down the circuit. Ideas suggested
7469 - If not enough of our entry guards are available so we add a new
7470 one, we might use the new one even if it overlapped with the
7471 current circuit's exit relay (or its family). Anonymity bugfix
7472 pointed out by rovv.
7475 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7476 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7477 - When using the TransPort option on OpenBSD, and using the User
7478 option to change UID and drop privileges, make sure to open /dev/pf
7479 before dropping privileges. Fixes bug 782. Patch from Christopher
7480 Davis. Bugfix on 0.1.2.1-alpha.
7481 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7482 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7483 - Add a missing safe_str() call for a debug log message.
7484 - Use 64 bits instead of 32 bits for connection identifiers used with
7485 the controller protocol, to greatly reduce risk of identifier reuse.
7486 - Make the autoconf script accept the obsolete --with-ssl-dir
7487 option as an alias for the actually-working --with-openssl-dir
7488 option. Fix the help documentation to recommend --with-openssl-dir.
7489 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7492 - Rate-limit too-many-sockets messages: when they happen, they happen
7493 a lot. Resolves bug 748.
7494 - Resist DNS poisoning a little better by making sure that names in
7495 answer sections match.
7496 - Print the SOCKS5 error message string as well as the error code
7497 when a tor-resolve request fails. Patch from Jacob.
7500 Changes in version 0.2.1.4-alpha - 2008-08-04
7501 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
7504 - The address part of exit policies was not correctly written
7505 to router descriptors. This generated router descriptors that failed
7506 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
7508 - Tor triggered a false assert when extending a circuit to a relay
7509 but we already have a connection open to that relay. Noticed by
7510 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
7513 - Fix a hidden service logging bug: in some edge cases, the router
7514 descriptor of a previously picked introduction point becomes
7515 obsolete and we need to give up on it rather than continually
7516 complaining that it has become obsolete. Observed by xiando. Bugfix
7520 - Take out the TestVia config option, since it was a workaround for
7521 a bug that was fixed in Tor 0.1.1.21.
7524 Changes in version 0.2.1.3-alpha - 2008-08-03
7525 Tor 0.2.1.3-alpha implements most of the pieces to prevent
7526 infinite-length circuit attacks (see proposal 110); fixes a bug that
7527 might cause exit relays to corrupt streams they send back; allows
7528 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
7529 ExcludeExitNodes config options; and fixes a big pile of bugs.
7531 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
7532 - Send a bootstrap problem "warn" event on the first problem if the
7533 reason is NO_ROUTE (that is, our network is down).
7536 - Implement most of proposal 110: The first K cells to be sent
7537 along a circuit are marked as special "early" cells; only K "early"
7538 cells will be allowed. Once this code is universal, we can block
7539 certain kinds of DOS attack by requiring that EXTEND commands must
7540 be sent using an "early" cell.
7543 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7544 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7545 on the client side when connecting to a hidden service. Bugfix
7546 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7547 - Ensure that two circuits can never exist on the same connection
7548 with the same circuit ID, even if one is marked for close. This
7549 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
7552 - When relays do their initial bandwidth measurement, don't limit
7553 to just our entry guards for the test circuits. Otherwise we tend
7554 to have multiple test circuits going through a single entry guard,
7555 which makes our bandwidth test less accurate. Fixes part of bug 654;
7556 patch contributed by Josh Albrecht.
7557 - Add an ExcludeExitNodes option so users can list a set of nodes
7558 that should be be excluded from the exit node position, but
7559 allowed elsewhere. Implements proposal 151.
7560 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
7561 ExcludeNodes and ExcludeExitNodes lists.
7562 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
7563 be more efficient. Formerly it was quadratic in the number of
7564 servers; now it should be linear. Fixes bug 509.
7565 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
7566 and n_conn_id_digest fields into a separate structure that's
7567 only needed when the circuit has not yet attached to an n_conn.
7570 - Change the contrib/tor.logrotate script so it makes the new
7571 logs as "_tor:_tor" rather than the default, which is generally
7572 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
7573 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7574 warnings (occasionally), but it can also cause the compiler to
7575 eliminate error-checking code. Suggested by Peter Gutmann.
7576 - When a hidden service is giving up on an introduction point candidate
7577 that was not included in the last published rendezvous descriptor,
7578 don't reschedule publication of the next descriptor. Fixes bug 763.
7580 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
7581 HiddenServiceExcludeNodes as obsolete: they never worked properly,
7582 and nobody claims to be using them. Fixes bug 754. Bugfix on
7583 0.1.0.1-rc. Patch from Christian Wilms.
7584 - Fix a small alignment and memory-wasting bug on buffer chunks.
7587 o Minor bugfixes (controller):
7588 - When closing an application-side connection because its circuit
7589 is getting torn down, generate the stream event correctly.
7590 Bugfix on 0.1.2.x. Anonymous patch.
7593 - Remove all backward-compatibility code to support relays running
7594 versions of Tor so old that they no longer work at all on the
7598 Changes in version 0.2.0.30 - 2008-07-15
7600 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7601 warnings (occasionally), but it can also cause the compiler to
7602 eliminate error-checking code. Suggested by Peter Gutmann.
7605 Changes in version 0.2.0.29-rc - 2008-07-08
7606 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
7607 hidden-service performance bugs, and fixes a bunch of smaller bugs.
7610 - If you have more than one bridge but don't know their keys,
7611 you would only launch a request for the descriptor of the first one
7612 on your list. (Tor considered launching requests for the others, but
7613 found that it already had a connection on the way for $0000...0000
7614 so it didn't open another.) Bugfix on 0.2.0.x.
7615 - If you have more than one bridge but don't know their keys, and the
7616 connection to one of the bridges failed, you would cancel all
7617 pending bridge connections. (After all, they all have the same
7618 digest.) Bugfix on 0.2.0.x.
7619 - When a hidden service was trying to establish an introduction point,
7620 and Tor had built circuits preemptively for such purposes, we
7621 were ignoring all the preemptive circuits and launching a new one
7622 instead. Bugfix on 0.2.0.14-alpha.
7623 - When a hidden service was trying to establish an introduction point,
7624 and Tor *did* manage to reuse one of the preemptively built
7625 circuits, it didn't correctly remember which one it used,
7626 so it asked for another one soon after, until there were no
7627 more preemptive circuits, at which point it launched one from
7628 scratch. Bugfix on 0.0.9.x.
7629 - Make directory servers include the X-Your-Address-Is: http header in
7630 their responses even for begin_dir conns. Now clients who only
7631 ever use begin_dir connections still have a way to learn their IP
7632 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
7635 - Fix a macro/CPP interaction that was confusing some compilers:
7636 some GCCs don't like #if/#endif pairs inside macro arguments.
7638 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
7639 Fixes bug 704; fix from Steven Murdoch.
7640 - When opening /dev/null in finish_daemonize(), do not pass the
7641 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
7642 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
7643 - Correctly detect transparent proxy support on Linux hosts that
7644 require in.h to be included before netfilter_ipv4.h. Patch
7646 - Disallow session resumption attempts during the renegotiation
7647 stage of the v2 handshake protocol. Clients should never be trying
7648 session resumption at this point, but apparently some did, in
7649 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
7650 found by Geoff Goodell.
7653 Changes in version 0.2.1.2-alpha - 2008-06-20
7654 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
7655 make it easier to set up your own private Tor network; fixes several
7656 big bugs with using more than one bridge relay; fixes a big bug with
7657 offering hidden services quickly after Tor starts; and uses a better
7658 API for reporting potential bootstrapping problems to the controller.
7661 - New TestingTorNetwork config option to allow adjustment of
7662 previously constant values that, while reasonable, could slow
7663 bootstrapping. Implements proposal 135. Patch from Karsten.
7666 - If you have more than one bridge but don't know their digests,
7667 you would only learn a request for the descriptor of the first one
7668 on your list. (Tor considered launching requests for the others, but
7669 found that it already had a connection on the way for $0000...0000
7670 so it didn't open another.) Bugfix on 0.2.0.x.
7671 - If you have more than one bridge but don't know their digests,
7672 and the connection to one of the bridges failed, you would cancel
7673 all pending bridge connections. (After all, they all have the
7674 same digest.) Bugfix on 0.2.0.x.
7675 - When establishing a hidden service, introduction points that
7676 originate from cannibalized circuits are completely ignored and not
7677 included in rendezvous service descriptors. This might be another
7678 reason for delay in making a hidden service available. Bugfix
7679 from long ago (0.0.9.x?)
7682 - Allow OpenSSL to use dynamic locks if it wants.
7683 - When building a consensus, do not include routers that are down.
7684 This will cut down 30% to 40% on consensus size. Implements
7686 - In directory authorities' approved-routers files, allow
7687 fingerprints with or without space.
7688 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
7689 controller can query our current bootstrap state in case it attaches
7690 partway through and wants to catch up.
7691 - Send an initial "Starting" bootstrap status event, so we have a
7692 state to start out in.
7695 - Asking for a conditional consensus at .../consensus/<fingerprints>
7696 would crash a dirserver if it did not already have a
7697 consensus. Bugfix on 0.2.1.1-alpha.
7698 - Clean up some macro/CPP interactions: some GCC versions don't like
7699 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
7702 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
7703 - Directory authorities shouldn't complain about bootstrapping
7704 problems just because they do a lot of reachability testing and
7705 some of the connection attempts fail.
7706 - Start sending "count" and "recommendation" key/value pairs in
7707 bootstrap problem status events, so the controller can hear about
7708 problems even before Tor decides they're worth reporting for sure.
7709 - If you're using bridges, generate "bootstrap problem" warnings
7710 as soon as you run out of working bridges, rather than waiting
7711 for ten failures -- which will never happen if you have less than
7713 - If we close our OR connection because there's been a circuit
7714 pending on it for too long, we were telling our bootstrap status
7715 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
7718 Changes in version 0.2.1.1-alpha - 2008-06-13
7719 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
7720 were making the Tor process bloat especially on Linux; makes our TLS
7721 handshake blend in better; sends "bootstrap phase" status events to
7722 the controller, so it can keep the user informed of progress (and
7723 problems) fetching directory information and establishing circuits;
7724 and adds a variety of smaller features.
7727 - More work on making our TLS handshake blend in: modify the list
7728 of ciphers advertised by OpenSSL in client mode to even more
7729 closely resemble a common web browser. We cheat a little so that
7730 we can advertise ciphers that the locally installed OpenSSL doesn't
7732 - Start sending "bootstrap phase" status events to the controller,
7733 so it can keep the user informed of progress fetching directory
7734 information and establishing circuits. Also inform the controller
7735 if we think we're stuck at a particular bootstrap phase. Implements
7737 - Resume using OpenSSL's RAND_poll() for better (and more portable)
7738 cross-platform entropy collection again. We used to use it, then
7739 stopped using it because of a bug that could crash systems that
7740 called RAND_poll when they had a lot of fds open. It looks like the
7741 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
7742 at startup, and to call RAND_poll() when we reseed later only if
7743 we have a non-buggy OpenSSL version.
7746 - When we choose to abandon a new entry guard because we think our
7747 older ones might be better, close any circuits pending on that
7748 new entry guard connection. This fix should make us recover much
7749 faster when our network is down and then comes back. Bugfix on
7750 0.1.2.8-beta; found by lodger.
7752 o Memory fixes and improvements:
7753 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
7754 to avoid unused RAM in buffer chunks and memory pools.
7755 - Speed up parsing and cut down on memory fragmentation by using
7756 stack-style allocations for parsing directory objects. Previously,
7757 this accounted for over 40% of allocations from within Tor's code
7758 on a typical directory cache.
7759 - Use a Bloom filter rather than a digest-based set to track which
7760 descriptors we need to keep around when we're cleaning out old
7761 router descriptors. This speeds up the computation significantly,
7762 and may reduce fragmentation.
7763 - Reduce the default smartlist size from 32 to 16; it turns out that
7764 most smartlists hold around 8-12 elements tops.
7765 - Make dumpstats() log the fullness and size of openssl-internal
7767 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
7768 patch to their OpenSSL, turn it on to save memory on servers. This
7769 patch will (with any luck) get included in a mainline distribution
7771 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7772 compress cells, which are basically all encrypted, compressed,
7776 - Stop reloading the router list from disk for no reason when we
7777 run out of reachable directory mirrors. Once upon a time reloading
7778 it would set the 'is_running' flag back to 1 for them. It hasn't
7779 done that for a long time.
7780 - In very rare situations new hidden service descriptors were
7781 published earlier than 30 seconds after the last change to the
7782 service. (We currently think that a hidden service descriptor
7783 that's been stable for 30 seconds is worth publishing.)
7786 - Allow separate log levels to be configured for different logging
7787 domains. For example, this allows one to log all notices, warnings,
7788 or errors, plus all memory management messages of level debug or
7789 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7790 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7791 and stop using a warning that had become unfixably verbose under
7793 - New --hush command-line option similar to --quiet. While --quiet
7794 disables all logging to the console on startup, --hush limits the
7795 output to messages of warning and error severity.
7796 - Servers support a new URL scheme for consensus downloads that
7797 allows the client to specify which authorities are trusted.
7798 The server then only sends the consensus if the client will trust
7799 it. Otherwise a 404 error is sent back. Clients use this
7800 new scheme when the server supports it (meaning it's running
7801 0.2.1.1-alpha or later). Implements proposal 134.
7802 - New configure/torrc options (--enable-geoip-stats,
7803 DirRecordUsageByCountry) to record how many IPs we've served
7804 directory info to in each country code, how many status documents
7805 total we've sent to each country code, and what share of the total
7806 directory requests we should expect to see.
7807 - Use the TLS1 hostname extension to more closely resemble browser
7809 - Lots of new unit tests.
7810 - Add a macro to implement the common pattern of iterating through
7811 two parallel lists in lockstep.
7814 Changes in version 0.2.0.28-rc - 2008-06-13
7815 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
7816 performance bug, and fixes a bunch of smaller bugs.
7819 - Fix a bug where, when we were choosing the 'end stream reason' to
7820 put in our relay end cell that we send to the exit relay, Tor
7821 clients on Windows were sometimes sending the wrong 'reason'. The
7822 anonymity problem is that exit relays may be able to guess whether
7823 the client is running Windows, thus helping partition the anonymity
7824 set. Down the road we should stop sending reasons to exit relays,
7825 or otherwise prevent future versions of this bug.
7828 - While setting up a hidden service, some valid introduction circuits
7829 were overlooked and abandoned. This might be the reason for
7830 the long delay in making a hidden service available. Bugfix on
7834 - Update to the "June 9 2008" ip-to-country file.
7835 - Run 'make test' as part of 'make dist', so we stop releasing so
7836 many development snapshots that fail their unit tests.
7839 - When we're checking if we have enough dir info for each relay
7840 to begin establishing circuits, make sure that we actually have
7841 the descriptor listed in the consensus, not just any descriptor.
7843 - Bridge relays no longer print "xx=0" in their extrainfo document
7844 for every single country code in the geoip db. Bugfix on
7846 - Only warn when we fail to load the geoip file if we were planning to
7847 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
7848 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7849 Tor won't realize it should publish a new relay descriptor. Fixes
7850 bug 688, reported by mfr. Bugfix on 0.1.2.x.
7851 - When we haven't had any application requests lately, don't bother
7852 logging that we have expired a bunch of descriptors. Bugfix
7854 - Make relay cells written on a connection count as non-padding when
7855 tracking how long a connection has been in use. Bugfix on
7856 0.2.0.1-alpha. Spotted by lodger.
7857 - Fix unit tests in 0.2.0.27-rc.
7858 - Fix compile on Windows.
7861 Changes in version 0.2.0.27-rc - 2008-06-03
7862 Tor 0.2.0.27-rc adds a few features we left out of the earlier
7863 release candidates. In particular, we now include an IP-to-country
7864 GeoIP database, so controllers can easily look up what country a
7865 given relay is in, and so bridge relays can give us some sanitized
7866 summaries about which countries are making use of bridges. (See proposal
7867 126-geoip-fetching.txt for details.)
7870 - Include an IP-to-country GeoIP file in the tarball, so bridge
7871 relays can report sanitized summaries of the usage they're seeing.
7874 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7875 Robert Hogan. Fixes the first part of bug 681.
7876 - Make bridge authorities never serve extrainfo docs.
7877 - Add support to detect Libevent versions in the 1.4.x series
7879 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
7880 - Include a new contrib/tor-exit-notice.html file that exit relay
7881 operators can put on their website to help reduce abuse queries.
7884 - When tunneling an encrypted directory connection, and its first
7885 circuit fails, do not leave it unattached and ask the controller
7886 to deal. Fixes the second part of bug 681.
7887 - Make bridge authorities correctly expire old extrainfo documents
7891 Changes in version 0.2.0.26-rc - 2008-05-13
7892 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
7893 in Debian's OpenSSL packages. All users running any 0.2.0.x version
7894 should upgrade, whether they're running Debian or not.
7896 o Major security fixes:
7897 - Use new V3 directory authority keys on the tor26, gabelmoo, and
7898 moria1 V3 directory authorities. The old keys were generated with
7899 a vulnerable version of Debian's OpenSSL package, and must be
7900 considered compromised. Other authorities' keys were not generated
7901 with an affected version of OpenSSL.
7904 - List authority signatures as "unrecognized" based on DirServer
7905 lines, not on cert cache. Bugfix on 0.2.0.x.
7908 - Add a new V3AuthUseLegacyKey option to make it easier for
7909 authorities to change their identity keys if they have to.
7912 Changes in version 0.2.0.25-rc - 2008-04-23
7913 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
7916 - Remember to initialize threading before initializing logging.
7917 Otherwise, many BSD-family implementations will crash hard on
7918 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
7921 - Authorities correctly free policies on bad servers on
7922 exit. Fixes bug 672. Bugfix on 0.2.0.x.
7925 Changes in version 0.2.0.24-rc - 2008-04-22
7926 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
7927 v3 directory authority, makes relays with dynamic IP addresses and no
7928 DirPort notice more quickly when their IP address changes, fixes a few
7929 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
7931 o New directory authorities:
7932 - Take lefkada out of the list of v3 directory authorities, since
7933 it has been down for months.
7934 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
7938 - Detect address changes more quickly on non-directory mirror
7939 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
7941 o Minor features (security):
7942 - Reject requests for reverse-dns lookup of names that are in
7943 a private address space. Patch from lodger.
7944 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
7947 o Minor bugfixes (crashes):
7948 - Avoid a rare assert that can trigger when Tor doesn't have much
7949 directory information yet and it tries to fetch a v2 hidden
7950 service descriptor. Fixes bug 651, reported by nwf.
7951 - Initialize log mutex before initializing dmalloc. Otherwise,
7952 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7953 - Use recursive pthread mutexes in order to avoid deadlock when
7954 logging debug-level messages to a controller. Bug spotted by nwf,
7955 bugfix on 0.2.0.16-alpha.
7957 o Minor bugfixes (resource management):
7958 - Keep address policies from leaking memory: start their refcount
7959 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7960 - Free authority certificates on exit, so they don't look like memory
7961 leaks. Bugfix on 0.2.0.19-alpha.
7962 - Free static hashtables for policy maps and for TLS connections on
7963 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7964 - Avoid allocating extra space when computing consensuses on 64-bit
7965 platforms. Bug spotted by aakova.
7967 o Minor bugfixes (misc):
7968 - Do not read the configuration file when we've only been told to
7969 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7970 based on patch from Sebastian Hahn.
7971 - Exit relays that are used as a client can now reach themselves
7972 using the .exit notation, rather than just launching an infinite
7973 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7974 - When attempting to open a logfile fails, tell us why.
7975 - Fix a dumb bug that was preventing us from knowing that we should
7976 preemptively build circuits to handle expected directory requests.
7977 Fixes bug 660. Bugfix on 0.1.2.x.
7978 - Warn less verbosely about clock skew from netinfo cells from
7979 untrusted sources. Fixes bug 663.
7980 - Make controller stream events for DNS requests more consistent,
7981 by adding "new stream" events for DNS requests, and removing
7982 spurious "stream closed" events" for cached reverse resolves.
7983 Patch from mwenge. Fixes bug 646.
7984 - Correctly notify one-hop connections when a circuit build has
7985 failed. Possible fix for bug 669. Found by lodger.
7988 Changes in version 0.2.0.23-rc - 2008-03-24
7989 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7990 makes bootstrapping faster if the first directory mirror you contact
7991 is down. The bundles also include the new Vidalia 0.1.2 release.
7994 - When a tunneled directory request is made to a directory server
7995 that's down, notice after 30 seconds rather than 120 seconds. Also,
7996 fail any begindir streams that are pending on it, so they can
7997 retry elsewhere. This was causing multi-minute delays on bootstrap.
8000 Changes in version 0.2.0.22-rc - 2008-03-18
8001 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
8002 enables encrypted directory connections by default for non-relays, fixes
8003 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
8004 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
8007 - Enable encrypted directory connections by default for non-relays,
8008 so censor tools that block Tor directory connections based on their
8009 plaintext patterns will no longer work. This means Tor works in
8010 certain censored countries by default again.
8013 - Make sure servers always request certificates from clients during
8014 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
8015 - Do not enter a CPU-eating loop when a connection is closed in
8016 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
8017 diagnosed by lodger; bugfix on 0.2.0.20-rc.
8018 - Fix assertion failure that could occur when a blocked circuit
8019 became unblocked, and it had pending client DNS requests. Bugfix
8020 on 0.2.0.1-alpha. Fixes bug 632.
8022 o Minor bugfixes (on 0.1.2.x):
8023 - Generate "STATUS_SERVER" events rather than misspelled
8024 "STATUS_SEVER" events. Caught by mwenge.
8025 - When counting the number of bytes written on a TLS connection,
8026 look at the BIO actually used for writing to the network, not
8027 at the BIO used (sometimes) to buffer data for the network.
8028 Looking at different BIOs could result in write counts on the
8029 order of ULONG_MAX. Fixes bug 614.
8030 - On Windows, correctly detect errors when listing the contents of
8031 a directory. Fix from lodger.
8033 o Minor bugfixes (on 0.2.0.x):
8034 - Downgrade "sslv3 alert handshake failure" message to INFO.
8035 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
8036 left BandwidthRate and BandwidthBurst at the default, we would be
8037 silently limited by those defaults. Now raise them to match the
8038 RelayBandwidth* values.
8039 - Fix the SVK version detection logic to work correctly on a branch.
8040 - Make --enable-openbsd-malloc work correctly on Linux with alpha
8041 CPUs. Fixes bug 625.
8042 - Logging functions now check that the passed severity is sane.
8043 - Use proper log levels in the testsuite call of
8044 get_interface_address6().
8045 - When using a nonstandard malloc, do not use the platform values for
8046 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
8047 - Make the openbsd malloc code use 8k pages on alpha CPUs and
8049 - Detect mismatched page sizes when using --enable-openbsd-malloc.
8050 - Avoid double-marked-for-close warning when certain kinds of invalid
8051 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
8052 for bug 617. Bugfix on 0.2.0.1-alpha.
8053 - Make sure that the "NULL-means-reject *:*" convention is followed by
8054 all the policy manipulation functions, avoiding some possible crash
8055 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
8056 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
8057 actually works, and doesn't warn about every single reverse lookup.
8058 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
8061 - Only log guard node status when guard node status has changed.
8062 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
8063 make "INFO" 75% less verbose.
8066 Changes in version 0.2.0.21-rc - 2008-03-02
8067 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
8068 makes Tor work well with Vidalia again, fixes a rare assert bug,
8069 and fixes a pair of more minor bugs. The bundles also include Vidalia
8070 0.1.0 and Torbutton 1.1.16.
8073 - The control port should declare that it requires password auth
8074 when HashedControlSessionPassword is set too. Patch from Matt Edman;
8075 bugfix on 0.2.0.20-rc. Fixes bug 615.
8076 - Downgrade assert in connection_buckets_decrement() to a log message.
8077 This may help us solve bug 614, and in any case will make its
8078 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
8079 - We were sometimes miscounting the number of bytes read from the
8080 network, causing our rate limiting to not be followed exactly.
8081 Bugfix on 0.2.0.16-alpha. Reported by lodger.
8084 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
8085 OpenSSL versions should have been working fine. Diagnosis and patch
8086 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
8087 Bugfix on 0.2.0.20-rc.
8090 Changes in version 0.2.0.20-rc - 2008-02-24
8091 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
8092 makes more progress towards normalizing Tor's TLS handshake, makes
8093 hidden services work better again, helps relays bootstrap if they don't
8094 know their IP address, adds optional support for linking in openbsd's
8095 allocator or tcmalloc, allows really fast relays to scale past 15000
8096 sockets, and fixes a bunch of minor bugs reported by Veracode.
8099 - Enable the revised TLS handshake based on the one designed by
8100 Steven Murdoch in proposal 124, as revised in proposal 130. It
8101 includes version negotiation for OR connections as described in
8102 proposal 105. The new handshake is meant to be harder for censors
8103 to fingerprint, and it adds the ability to detect certain kinds of
8104 man-in-the-middle traffic analysis attacks. The version negotiation
8105 feature will allow us to improve Tor's link protocol more safely
8107 - Choose which bridge to use proportional to its advertised bandwidth,
8108 rather than uniformly at random. This should speed up Tor for
8109 bridge users. Also do this for people who set StrictEntryNodes.
8110 - When a TrackHostExits-chosen exit fails too many times in a row,
8111 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
8114 - Resolved problems with (re-)fetching hidden service descriptors.
8115 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
8117 - If we only ever used Tor for hidden service lookups or posts, we
8118 would stop building circuits and start refusing connections after
8119 24 hours, since we falsely believed that Tor was dormant. Reported
8120 by nwf; bugfix on 0.1.2.x.
8121 - Servers that don't know their own IP address should go to the
8122 authorities for their first directory fetch, even if their DirPort
8123 is off or if they don't know they're reachable yet. This will help
8124 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
8125 - When counting the number of open sockets, count not only the number
8126 of sockets we have received from the socket() call, but also
8127 the number we've gotten from accept() and socketpair(). This bug
8128 made us fail to count all sockets that we were using for incoming
8129 connections. Bugfix on 0.2.0.x.
8130 - Fix code used to find strings within buffers, when those strings
8131 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
8132 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
8133 - Add a new __HashedControlSessionPassword option for controllers
8134 to use for one-off session password hashes that shouldn't get
8135 saved to disk by SAVECONF --- Vidalia users were accumulating a
8136 pile of HashedControlPassword lines in their torrc files, one for
8137 each time they had restarted Tor and then clicked Save. Make Tor
8138 automatically convert "HashedControlPassword" to this new option but
8139 only when it's given on the command line. Partial fix for bug 586.
8141 o Minor features (performance):
8142 - Tune parameters for cell pool allocation to minimize amount of
8144 - Add OpenBSD malloc code from phk as an optional malloc
8145 replacement on Linux: some glibc libraries do very poorly
8146 with Tor's memory allocation patterns. Pass
8147 --enable-openbsd-malloc to get the replacement malloc code.
8148 - Add a --with-tcmalloc option to the configure script to link
8149 against tcmalloc (if present). Does not yet search for
8150 non-system include paths.
8151 - Stop imposing an arbitrary maximum on the number of file descriptors
8152 used for busy servers. Bug reported by Olaf Selke; patch from
8155 o Minor features (other):
8156 - When SafeLogging is disabled, log addresses along with all TLS
8158 - When building with --enable-gcc-warnings, check for whether Apple's
8159 warning "-Wshorten-64-to-32" is available.
8160 - Add a --passphrase-fd argument to the tor-gencert command for
8163 o Minor bugfixes (memory leaks and code problems):
8164 - We were leaking a file descriptor if Tor started with a zero-length
8165 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
8166 - Detect size overflow in zlib code. Reported by Justin Ferguson and
8168 - We were comparing the raw BridgePassword entry with a base64'ed
8169 version of it, when handling a "/tor/networkstatus-bridges"
8170 directory request. Now compare correctly. Noticed by Veracode.
8171 - Recover from bad tracked-since value in MTBF-history file.
8173 - Alter the code that tries to recover from unhandled write
8174 errors, to not try to flush onto a socket that's given us
8175 unhandled errors. Bugfix on 0.1.2.x.
8176 - Make Unix controlsockets work correctly on OpenBSD. Patch from
8177 tup. Bugfix on 0.2.0.3-alpha.
8179 o Minor bugfixes (other):
8180 - If we have an extra-info document for our server, always make
8181 it available on the control port, even if we haven't gotten
8182 a copy of it from an authority yet. Patch from mwenge.
8183 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
8184 - Directory mirrors no longer include a guess at the client's IP
8185 address if the connection appears to be coming from the same /24
8186 network; it was producing too many wrong guesses.
8187 - Make the new hidden service code respect the SafeLogging setting.
8188 Bugfix on 0.2.0.x. Patch from Karsten.
8189 - When starting as an authority, do not overwrite all certificates
8190 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
8191 - If we're trying to flush the last bytes on a connection (for
8192 example, when answering a directory request), reset the
8193 time-to-give-up timeout every time we manage to write something
8194 on the socket. Bugfix on 0.1.2.x.
8195 - Change the behavior of "getinfo status/good-server-descriptor"
8196 so it doesn't return failure when any authority disappears.
8197 - Even though the man page said that "TrackHostExits ." should
8198 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
8199 - Report TLS "zero return" case as a "clean close" and "IO error"
8200 as a "close". Stop calling closes "unexpected closes": existing
8201 Tors don't use SSL_close(), so having a connection close without
8202 the TLS shutdown handshake is hardly unexpected.
8203 - Send NAMESERVER_STATUS messages for a single failed nameserver
8206 o Code simplifications and refactoring:
8207 - Remove the tor_strpartition function: its logic was confused,
8208 and it was only used for one thing that could be implemented far
8212 Changes in version 0.2.0.19-alpha - 2008-02-09
8213 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
8214 handshake, makes path selection for relays more secure and IP address
8215 guessing more robust, and generally fixes a lot of bugs in preparation
8216 for calling the 0.2.0 branch stable.
8219 - Do not include recognizeable strings in the commonname part of
8220 Tor's x509 certificates.
8223 - If we're a relay, avoid picking ourselves as an introduction point,
8224 a rendezvous point, or as the final hop for internal circuits. Bug
8225 reported by taranis and lodger. Bugfix on 0.1.2.x.
8226 - Patch from "Andrew S. Lists" to catch when we contact a directory
8227 mirror at IP address X and he says we look like we're coming from
8228 IP address X. Bugfix on 0.1.2.x.
8230 o Minor features (security):
8231 - Be more paranoid about overwriting sensitive memory on free(),
8232 as a defensive programming tactic to ensure forward secrecy.
8234 o Minor features (directory authority):
8235 - Actually validate the options passed to AuthDirReject,
8236 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
8237 - Reject router descriptors with out-of-range bandwidthcapacity or
8238 bandwidthburst values.
8240 o Minor features (controller):
8241 - Reject controller commands over 1MB in length. This keeps rogue
8242 processes from running us out of memory.
8244 o Minor features (misc):
8245 - Give more descriptive well-formedness errors for out-of-range
8246 hidden service descriptor/protocol versions.
8247 - Make memory debugging information describe more about history
8248 of cell allocation, so we can help reduce our memory use.
8250 o Deprecated features (controller):
8251 - The status/version/num-versioning and status/version/num-concurring
8252 GETINFO options are no longer useful in the v3 directory protocol:
8253 treat them as deprecated, and warn when they're used.
8256 - When our consensus networkstatus has been expired for a while, stop
8257 being willing to build circuits using it. Fixes bug 401. Bugfix
8259 - Directory caches now fetch certificates from all authorities
8260 listed in a networkstatus consensus, even when they do not
8261 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
8262 - When connecting to a bridge without specifying its key, insert
8263 the connection into the identity-to-connection map as soon as
8264 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
8265 - Detect versions of OS X where malloc_good_size() is present in the
8266 library but never actually declared. Resolves bug 587. Bugfix
8268 - Stop incorrectly truncating zlib responses to directory authority
8269 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
8270 - Stop recommending that every server operator send mail to tor-ops.
8271 Resolves bug 597. Bugfix on 0.1.2.x.
8272 - Don't trigger an assert if we start a directory authority with a
8273 private IP address (like 127.0.0.1).
8274 - Avoid possible failures when generating a directory with routers
8275 with over-long versions strings, or too many flags set. Bugfix
8277 - If an attempt to launch a DNS resolve request over the control
8278 port fails because we have overrun the limit on the number of
8279 connections, tell the controller that the request has failed.
8280 - Avoid using too little bandwidth when our clock skips a few
8281 seconds. Bugfix on 0.1.2.x.
8282 - Fix shell error when warning about missing packages in configure
8283 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
8284 - Do not become confused when receiving a spurious VERSIONS-like
8285 cell from a confused v1 client. Bugfix on 0.2.0.x.
8286 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
8287 introduction points for a hidden service have failed. Patch from
8288 Karsten Loesing. Bugfix on 0.2.0.x.
8290 o Code simplifications and refactoring:
8291 - Remove some needless generality from cpuworker code, for improved
8293 - Stop overloading the circuit_t.onionskin field for both "onionskin
8294 from a CREATE cell that we are waiting for a cpuworker to be
8295 assigned" and "onionskin from an EXTEND cell that we are going to
8296 send to an OR as soon as we are connected". Might help with bug 600.
8297 - Add an in-place version of aes_crypt() so that we can avoid doing a
8298 needless memcpy() call on each cell payload.
8301 Changes in version 0.2.0.18-alpha - 2008-01-25
8302 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
8303 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
8304 that can warn or reject connections to ports generally associated with
8305 vulnerable-plaintext protocols.
8307 o New directory authorities:
8308 - Set up dannenberg (run by CCC) as the sixth v3 directory
8312 - Fix a major memory leak when attempting to use the v2 TLS
8313 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
8314 - We accidentally enabled the under-development v2 TLS handshake
8315 code, which was causing log entries like "TLS error while
8316 renegotiating handshake". Disable it again. Resolves bug 590.
8317 - We were computing the wrong Content-Length: header for directory
8318 responses that need to be compressed on the fly, causing clients
8319 asking for those items to always fail. Bugfix on 0.2.0.x; partially
8323 - Avoid going directly to the directory authorities even if you're a
8324 relay, if you haven't found yourself reachable yet or if you've
8325 decided not to advertise your dirport yet. Addresses bug 556.
8326 - If we've gone 12 hours since our last bandwidth check, and we
8327 estimate we have less than 50KB bandwidth capacity but we could
8328 handle more, do another bandwidth test.
8329 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
8330 Tor can warn and/or refuse connections to ports commonly used with
8331 vulnerable-plaintext protocols. Currently we warn on ports 23,
8332 109, 110, and 143, but we don't reject any.
8335 - When we setconf ClientOnly to 1, close any current OR and Dir
8336 listeners. Reported by mwenge.
8337 - When we get a consensus that's been signed by more people than
8338 we expect, don't log about it; it's not a big deal. Reported
8342 - Don't answer "/tor/networkstatus-bridges" directory requests if
8343 the request isn't encrypted.
8344 - Make "ClientOnly 1" config option disable directory ports too.
8345 - Patches from Karsten Loesing to make v2 hidden services more
8346 robust: work even when there aren't enough HSDir relays available;
8347 retry when a v2 rend desc fetch fails; but don't retry if we
8348 already have a usable v0 rend desc.
8351 Changes in version 0.2.0.17-alpha - 2008-01-17
8352 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
8355 - Make the tor-gencert man page get included correctly in the tarball.
8358 Changes in version 0.2.0.16-alpha - 2008-01-17
8359 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
8360 Loesing, and generally cleans up a lot of features and minor bugs.
8362 o New directory authorities:
8363 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
8366 o Major performance improvements:
8367 - Switch our old ring buffer implementation for one more like that
8368 used by free Unix kernels. The wasted space in a buffer with 1mb
8369 of data will now be more like 8k than 1mb. The new implementation
8370 also avoids realloc();realloc(); patterns that can contribute to
8371 memory fragmentation.
8374 - Configuration files now accept C-style strings as values. This
8375 helps encode characters not allowed in the current configuration
8376 file format, such as newline or #. Addresses bug 557.
8377 - Although we fixed bug 539 (where servers would send HTTP status 503
8378 responses _and_ send a body too), there are still servers out
8379 there that haven't upgraded. Therefore, make clients parse such
8380 bodies when they receive them.
8381 - When we're not serving v2 directory information, there is no reason
8382 to actually keep any around. Remove the obsolete files and directory
8383 on startup if they are very old and we aren't going to serve them.
8385 o Minor performance improvements:
8386 - Reference-count and share copies of address policy entries; only 5%
8387 of them were actually distinct.
8388 - Never walk through the list of logs if we know that no log is
8389 interested in a given message.
8392 - When an authority has not signed a consensus, do not try to
8393 download a nonexistent "certificate with key 00000000". Bugfix
8394 on 0.2.0.x. Fixes bug 569.
8395 - Fix a rare assert error when we're closing one of our threads:
8396 use a mutex to protect the list of logs, so we never write to the
8397 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
8398 bug 575, which is kind of the revenge of bug 222.
8399 - Patch from Karsten Loesing to complain less at both the client
8400 and the relay when a relay used to have the HSDir flag but doesn't
8401 anymore, and we try to upload a hidden service descriptor.
8402 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
8404 - Do not try to download missing certificates until we have tried
8405 to check our fallback consensus. Fixes bug 583.
8406 - Make bridges round reported GeoIP stats info up to the nearest
8407 estimate, not down. Now we can distinguish between "0 people from
8408 this country" and "1 person from this country".
8409 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
8410 - Avoid possible segfault if key generation fails in
8411 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
8412 - Avoid segfault in the case where a badly behaved v2 versioning
8413 directory sends a signed networkstatus with missing client-versions.
8415 - Avoid segfaults on certain complex invocations of
8416 router_get_by_hexdigest(). Bugfix on 0.1.2.
8417 - Correct bad index on array access in parse_http_time(). Bugfix
8419 - Fix possible bug in vote generation when server versions are present
8420 but client versions are not.
8421 - Fix rare bug on REDIRECTSTREAM control command when called with no
8422 port set: it could erroneously report an error when none had
8424 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
8425 compressing large objects and find ourselves with more than 4k
8426 left over. Bugfix on 0.2.0.
8427 - Fix a small memory leak when setting up a hidden service.
8428 - Fix a few memory leaks that could in theory happen under bizarre
8430 - Fix an assert if we post a general-purpose descriptor via the
8431 control port but that descriptor isn't mentioned in our current
8432 network consensus. Bug reported by Jon McLachlan; bugfix on
8435 o Minor features (controller):
8436 - Get NS events working again. Patch from tup.
8437 - The GETCONF command now escapes and quotes configuration values
8438 that don't otherwise fit into the torrc file.
8439 - The SETCONF command now handles quoted values correctly.
8441 o Minor features (directory authorities):
8442 - New configuration options to override default maximum number of
8443 servers allowed on a single IP address. This is important for
8444 running a test network on a single host.
8445 - Actually implement the -s option to tor-gencert.
8446 - Add a manual page for tor-gencert.
8448 o Minor features (bridges):
8449 - Bridge authorities no longer serve bridge descriptors over
8450 unencrypted connections.
8452 o Minor features (other):
8453 - Add hidden services and DNSPorts to the list of things that make
8454 Tor accept that it has running ports. Change starting Tor with no
8455 ports from a fatal error to a warning; we might change it back if
8456 this turns out to confuse anybody. Fixes bug 579.
8459 Changes in version 0.1.2.19 - 2008-01-17
8460 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
8461 exit policy a little bit more conservative so it's safer to run an
8462 exit relay on a home system, and fixes a variety of smaller issues.
8465 - Exit policies now reject connections that are addressed to a
8466 relay's public (external) IP address too, unless
8467 ExitPolicyRejectPrivate is turned off. We do this because too
8468 many relays are running nearby to services that trust them based
8472 - When the clock jumps forward a lot, do not allow the bandwidth
8473 buckets to become negative. Fixes bug 544.
8474 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8475 on every successful resolve. Reported by Mike Perry.
8476 - Purge old entries from the "rephist" database and the hidden
8477 service descriptor database even when DirPort is zero.
8478 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8479 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8480 crashing or mis-answering these requests.
8481 - When we decide to send a 503 response to a request for servers, do
8482 not then also send the server descriptors: this defeats the whole
8483 purpose. Fixes bug 539.
8486 - Changing the ExitPolicyRejectPrivate setting should cause us to
8487 rebuild our server descriptor.
8488 - Fix handling of hex nicknames when answering controller requests for
8489 networkstatus by name, or when deciding whether to warn about
8490 unknown routers in a config option. (Patch from mwenge.)
8491 - Fix a couple of hard-to-trigger autoconf problems that could result
8492 in really weird results on platforms whose sys/types.h files define
8493 nonstandard integer types.
8494 - Don't try to create the datadir when running --verify-config or
8495 --hash-password. Resolves bug 540.
8496 - If we were having problems getting a particular descriptor from the
8497 directory caches, and then we learned about a new descriptor for
8498 that router, we weren't resetting our failure count. Reported
8500 - Although we fixed bug 539 (where servers would send HTTP status 503
8501 responses _and_ send a body too), there are still servers out there
8502 that haven't upgraded. Therefore, make clients parse such bodies
8503 when they receive them.
8504 - Run correctly on systems where rlim_t is larger than unsigned long.
8505 This includes some 64-bit systems.
8506 - Run correctly on platforms (like some versions of OS X 10.5) where
8507 the real limit for number of open files is OPEN_FILES, not rlim_max
8508 from getrlimit(RLIMIT_NOFILES).
8509 - Avoid a spurious free on base64 failure.
8510 - Avoid segfaults on certain complex invocations of
8511 router_get_by_hexdigest().
8512 - Fix rare bug on REDIRECTSTREAM control command when called with no
8513 port set: it could erroneously report an error when none had
8517 Changes in version 0.2.0.15-alpha - 2007-12-25
8518 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
8519 features added in 0.2.0.13-alpha.
8522 - Fix several remotely triggerable asserts based on DirPort requests
8523 for a v2 or v3 networkstatus object before we were prepared. This
8524 was particularly bad for 0.2.0.13 and later bridge relays, who
8525 would never have a v2 networkstatus and would thus always crash
8526 when used. Bugfixes on 0.2.0.x.
8527 - Estimate the v3 networkstatus size more accurately, rather than
8528 estimating it at zero bytes and giving it artificially high priority
8529 compared to other directory requests. Bugfix on 0.2.0.x.
8532 - Fix configure.in logic for cross-compilation.
8533 - When we load a bridge descriptor from the cache, and it was
8534 previously unreachable, mark it as retriable so we won't just
8535 ignore it. Also, try fetching a new copy immediately. Bugfixes
8537 - The bridge GeoIP stats were counting other relays, for example
8538 self-reachability and authority-reachability tests.
8541 - Support compilation to target iPhone; patch from cjacker huang.
8542 To build for iPhone, pass the --enable-iphone option to configure.
8545 Changes in version 0.2.0.14-alpha - 2007-12-23
8547 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
8548 without a datadirectory from a previous Tor install. Reported
8550 - Fix a crash when we fetch a descriptor that turns out to be
8551 unexpected (it used to be in our networkstatus when we started
8552 fetching it, but it isn't in our current networkstatus), and we
8553 aren't using bridges. Bugfix on 0.2.0.x.
8554 - Fix a crash when accessing hidden services: it would work the first
8555 time you use a given introduction point for your service, but
8556 on subsequent requests we'd be using garbage memory. Fixed by
8557 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
8558 - Fix a crash when we load a bridge descriptor from disk but we don't
8559 currently have a Bridge line for it in our torrc. Bugfix on
8563 - If bridge authorities set BridgePassword, they will serve a
8564 snapshot of known bridge routerstatuses from their DirPort to
8565 anybody who knows that password. Unset by default.
8568 - Make the unit tests build again.
8569 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
8570 - Make PublishServerDescriptor default to 1, so the default doesn't
8571 have to change as we invent new directory protocol versions.
8572 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
8573 be included unless sys/time.h is already included. Fixes
8574 bug 553. Bugfix on 0.2.0.x.
8575 - If we receive a general-purpose descriptor and then receive an
8576 identical bridge-purpose descriptor soon after, don't discard
8577 the next one as a duplicate.
8580 - If BridgeRelay is set to 1, then the default for
8581 PublishServerDescriptor is now "bridge" rather than "v2,v3".
8582 - If the user sets RelayBandwidthRate but doesn't set
8583 RelayBandwidthBurst, then make them equal rather than erroring out.
8586 Changes in version 0.2.0.13-alpha - 2007-12-21
8587 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
8588 Goodell, fixes many more bugs, and adds a lot of infrastructure for
8591 o New directory authorities:
8592 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
8596 - Only update guard status (usable / not usable) once we have
8597 enough directory information. This was causing us to always pick
8598 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
8599 causing us to discard all our guards on startup if we hadn't been
8600 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
8601 - Purge old entries from the "rephist" database and the hidden
8602 service descriptor databases even when DirPort is zero. Bugfix
8604 - We were ignoring our RelayBandwidthRate for the first 30 seconds
8605 after opening a circuit -- even a relayed circuit. Bugfix on
8607 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8608 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8609 crashing or mis-answering these types of requests.
8610 - Relays were publishing their server descriptor to v1 and v2
8611 directory authorities, but they didn't try publishing to v3-only
8612 authorities. Fix this; and also stop publishing to v1 authorities.
8614 - When we were reading router descriptors from cache, we were ignoring
8615 the annotations -- so for example we were reading in bridge-purpose
8616 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
8617 - When we decided to send a 503 response to a request for servers, we
8618 were then also sending the server descriptors: this defeats the
8619 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
8622 - Bridge relays now behave like clients with respect to time
8623 intervals for downloading new consensus documents -- otherwise they
8624 stand out. Bridge users now wait until the end of the interval,
8625 so their bridge relay will be sure to have a new consensus document.
8626 - Three new config options (AlternateDirAuthority,
8627 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
8628 user selectively replace the default directory authorities by type,
8629 rather than the all-or-nothing replacement that DirServer offers.
8630 - Tor can now be configured to read a GeoIP file from disk in one
8631 of two formats. This can be used by controllers to map IP addresses
8632 to countries. Eventually, it may support exit-by-country.
8633 - When possible, bridge relays remember which countries users
8634 are coming from, and report aggregate information in their
8635 extra-info documents, so that the bridge authorities can learn
8636 where Tor is blocked.
8637 - Bridge directory authorities now do reachability testing on the
8638 bridges they know. They provide router status summaries to the
8639 controller via "getinfo ns/purpose/bridge", and also dump summaries
8640 to a file periodically.
8641 - Stop fetching directory info so aggressively if your DirPort is
8642 on but your ORPort is off; stop fetching v2 dir info entirely.
8643 You can override these choices with the new FetchDirInfoEarly
8647 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
8648 consensus documents when there are too many relays at a single
8649 IP address. Now clear it in v2 network status documents too, and
8650 also clear it in routerinfo_t when the relay is no longer listed
8651 in the relevant networkstatus document.
8652 - Don't crash if we get an unexpected value for the
8653 PublishServerDescriptor config option. Reported by Matt Edman;
8654 bugfix on 0.2.0.9-alpha.
8655 - Our new v2 hidden service descriptor format allows descriptors
8656 that have no introduction points. But Tor crashed when we tried
8657 to build a descriptor with no intro points (and it would have
8658 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
8660 - Fix building with dmalloc 5.5.2 with glibc.
8661 - Reject uploaded descriptors and extrainfo documents if they're
8662 huge. Otherwise we'll cache them all over the network and it'll
8663 clog everything up. Reported by Aljosha Judmayer.
8664 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
8665 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
8666 - When the DANGEROUS_VERSION controller status event told us we're
8667 running an obsolete version, it used the string "OLD" to describe
8668 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
8669 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
8670 - If we can't expand our list of entry guards (e.g. because we're
8671 using bridges or we have StrictEntryNodes set), don't mark relays
8672 down when they fail a directory request. Otherwise we're too quick
8673 to mark all our entry points down. Bugfix on 0.1.2.x.
8674 - Fix handling of hex nicknames when answering controller requests for
8675 networkstatus by name, or when deciding whether to warn about unknown
8676 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
8677 - Fix a couple of hard-to-trigger autoconf problems that could result
8678 in really weird results on platforms whose sys/types.h files define
8679 nonstandard integer types. Bugfix on 0.1.2.x.
8680 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
8681 - Don't crash on name lookup when we have no current consensus. Fixes
8682 bug 538; bugfix on 0.2.0.x.
8683 - Only Tors that want to mirror the v2 directory info should
8684 create the "cached-status" directory in their datadir. (All Tors
8685 used to create it.) Bugfix on 0.2.0.9-alpha.
8686 - Directory authorities should only automatically download Extra Info
8687 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
8690 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
8691 consumers. (We already do this on HUP.)
8692 - Authorities and caches fetch the v2 networkstatus documents
8693 less often, now that v3 is encouraged.
8694 - Add a new config option BridgeRelay that specifies you want to
8695 be a bridge relay. Right now the only difference is that it makes
8696 you answer begin_dir requests, and it makes you cache dir info,
8697 even if your DirPort isn't on.
8698 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
8699 ask about source, timestamp of arrival, purpose, etc. We need
8700 something like this to help Vidalia not do GeoIP lookups on bridge
8702 - Allow multiple HashedControlPassword config lines, to support
8703 multiple controller passwords.
8704 - Authorities now decide whether they're authoritative for a given
8705 router based on the router's purpose.
8706 - New config options AuthDirBadDir and AuthDirListBadDirs for
8707 authorities to mark certain relays as "bad directories" in the
8708 networkstatus documents. Also supports the "!baddir" directive in
8709 the approved-routers file.
8712 Changes in version 0.2.0.12-alpha - 2007-11-16
8713 This twelfth development snapshot fixes some more build problems as
8714 well as a few minor bugs.
8717 - Make it build on OpenBSD again. Patch from tup.
8718 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
8719 package-building for Red Hat, OS X, etc.
8721 o Minor bugfixes (on 0.1.2.x):
8722 - Changing the ExitPolicyRejectPrivate setting should cause us to
8723 rebuild our server descriptor.
8725 o Minor bugfixes (on 0.2.0.x):
8726 - When we're lacking a consensus, don't try to perform rendezvous
8727 operations. Reported by Karsten Loesing.
8728 - Fix a small memory leak whenever we decide against using a
8729 newly picked entry guard. Reported by Mike Perry.
8730 - When authorities detected more than two relays running on the same
8731 IP address, they were clearing all the status flags but forgetting
8732 to clear the "hsdir" flag. So clients were being told that a
8733 given relay was the right choice for a v2 hsdir lookup, yet they
8734 never had its descriptor because it was marked as 'not running'
8736 - If we're trying to fetch a bridge descriptor and there's no way
8737 the bridge authority could help us (for example, we don't know
8738 a digest, or there is no bridge authority), don't be so eager to
8739 fall back to asking the bridge authority.
8740 - If we're using bridges or have strictentrynodes set, and our
8741 chosen exit is in the same family as all our bridges/entry guards,
8742 then be flexible about families.
8745 - When we negotiate a v2 link-layer connection (not yet implemented),
8746 accept RELAY_EARLY cells and turn them into RELAY cells if we've
8747 negotiated a v1 connection for their next step. Initial code for
8751 Changes in version 0.2.0.11-alpha - 2007-11-12
8752 This eleventh development snapshot fixes some build problems with
8753 the previous snapshot. It also includes a more secure-by-default exit
8754 policy for relays, fixes an enormous memory leak for exit relays, and
8755 fixes another bug where servers were falling out of the directory list.
8758 - Exit policies now reject connections that are addressed to a
8759 relay's public (external) IP address too, unless
8760 ExitPolicyRejectPrivate is turned off. We do this because too
8761 many relays are running nearby to services that trust them based
8762 on network address. Bugfix on 0.1.2.x.
8765 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8766 on every successful resolve. Reported by Mike Perry; bugfix
8768 - On authorities, never downgrade to old router descriptors simply
8769 because they're listed in the consensus. This created a catch-22
8770 where we wouldn't list a new descriptor because there was an
8771 old one in the consensus, and we couldn't get the new one in the
8772 consensus because we wouldn't list it. Possible fix for bug 548.
8773 Also, this might cause bug 543 to appear on authorities; if so,
8774 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
8776 o Packaging fixes on 0.2.0.10-alpha:
8777 - We were including instructions about what to do with the
8778 src/config/fallback-consensus file, but we weren't actually
8779 including it in the tarball. Disable all of that for now.
8782 - Allow people to say PreferTunnelledDirConns rather than
8783 PreferTunneledDirConns, for those alternate-spellers out there.
8786 - Don't reevaluate all the information from our consensus document
8787 just because we've downloaded a v2 networkstatus that we intend
8788 to cache. Fixes bug 545; bugfix on 0.2.0.x.
8791 Changes in version 0.2.0.10-alpha - 2007-11-10
8792 This tenth development snapshot adds a third v3 directory authority
8793 run by Mike Perry, adds most of Karsten Loesing's new hidden service
8794 descriptor format, fixes a bad crash bug and new bridge bugs introduced
8795 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
8796 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
8797 addresses many more minor issues.
8799 o New directory authorities:
8800 - Set up ides (run by Mike Perry) as the third v3 directory authority.
8803 - Allow tunnelled directory connections to ask for an encrypted
8804 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8805 connection independently. Now we can make anonymized begin_dir
8806 connections for (e.g.) more secure hidden service posting and
8808 - More progress on proposal 114: code from Karsten Loesing to
8809 implement new hidden service descriptor format.
8810 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8811 accommodate the growing number of servers that use the default
8812 and are reaching it.
8813 - Directory authorities use a new formula for selecting which nodes
8814 to advertise as Guards: they must be in the top 7/8 in terms of
8815 how long we have known about them, and above the median of those
8816 nodes in terms of weighted fractional uptime.
8817 - Make "not enough dir info yet" warnings describe *why* Tor feels
8818 it doesn't have enough directory info yet.
8821 - Stop servers from crashing if they set a Family option (or
8822 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
8824 - Make bridge users work again -- the move to v3 directories in
8825 0.2.0.9-alpha had introduced a number of bugs that made bridges
8826 no longer work for clients.
8827 - When the clock jumps forward a lot, do not allow the bandwidth
8828 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
8830 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
8831 - When the consensus lists a router descriptor that we previously were
8832 mirroring, but that we considered non-canonical, reload the
8833 descriptor as canonical. This fixes bug 543 where Tor servers
8834 would start complaining after a few days that they don't have
8835 enough directory information to build a circuit.
8836 - Consider replacing the current consensus when certificates arrive
8837 that make the pending consensus valid. Previously, we were only
8838 considering replacement when the new certs _didn't_ help.
8839 - Fix an assert error on startup if we didn't already have the
8840 consensus and certs cached in our datadirectory: we were caching
8841 the consensus in consensus_waiting_for_certs but then free'ing it
8843 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
8844 Request) if we need more v3 certs but we've already got pending
8845 requests for all of them.
8846 - Correctly back off from failing certificate downloads. Fixes
8848 - Authorities don't vote on the Running flag if they have been running
8849 for less than 30 minutes themselves. Fixes bug 547, where a newly
8850 started authority would vote that everyone was down.
8853 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8854 it, it had no AES, and it hasn't seen any security patches since
8858 - Clients now hold circuitless TLS connections open for 1.5 times
8859 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8860 rebuild a new circuit over them within that timeframe. Previously,
8861 they held them open only for KeepalivePeriod (5 minutes).
8862 - Use "If-Modified-Since" to avoid retrieving consensus
8863 networkstatuses that we already have.
8864 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8865 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8866 we start knowing some directory caches.
8867 - When we receive a consensus from the future, warn about skew.
8868 - Improve skew reporting: try to give the user a better log message
8869 about how skewed they are, and how much this matters.
8870 - When we have a certificate for an authority, believe that
8871 certificate's claims about the authority's IP address.
8872 - New --quiet command-line option to suppress the default console log.
8873 Good in combination with --hash-password.
8874 - Authorities send back an X-Descriptor-Not-New header in response to
8875 an accepted-but-discarded descriptor upload. Partially implements
8877 - Make the log message for "tls error. breaking." more useful.
8878 - Better log messages about certificate downloads, to attempt to
8879 track down the second incarnation of bug 546.
8881 o Minor features (bridges):
8882 - If bridge users set UpdateBridgesFromAuthority, but the digest
8883 they ask for is a 404 from the bridge authority, they now fall
8884 back to trying the bridge directly.
8885 - Bridges now use begin_dir to publish their server descriptor to
8886 the bridge authority, even when they haven't set TunnelDirConns.
8888 o Minor features (controller):
8889 - When reporting clock skew, and we know that the clock is _at least
8890 as skewed_ as some value, but we don't know the actual value,
8891 report the value as a "minimum skew."
8894 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8895 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8899 - Refuse to start if both ORPort and UseBridges are set. Bugfix
8900 on 0.2.0.x, suggested by Matt Edman.
8901 - Don't stop fetching descriptors when FetchUselessDescriptors is
8902 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
8903 reported by tup and ioerror.
8904 - Better log message on vote from unknown authority.
8905 - Don't log "Launching 0 request for 0 router" message.
8907 o Minor bugfixes (memory leaks):
8908 - Stop leaking memory every time we parse a v3 certificate. Bugfix
8910 - Stop leaking memory every time we load a v3 certificate. Bugfix
8911 on 0.2.0.1-alpha. Fixes bug 536.
8912 - Stop leaking a cached networkstatus on exit. Bugfix on
8914 - Stop leaking voter information every time we free a consensus.
8915 Bugfix on 0.2.0.3-alpha.
8916 - Stop leaking signed data every time we check a voter signature.
8917 Bugfix on 0.2.0.3-alpha.
8918 - Stop leaking a signature every time we fail to parse a consensus or
8919 a vote. Bugfix on 0.2.0.3-alpha.
8920 - Stop leaking v2_download_status_map on shutdown. Bugfix on
8922 - Stop leaking conn->nickname every time we make a connection to a
8923 Tor relay without knowing its expected identity digest (e.g. when
8924 using bridges). Bugfix on 0.2.0.3-alpha.
8926 - Minor bugfixes (portability):
8927 - Run correctly on platforms where rlim_t is larger than unsigned
8928 long, and/or where the real limit for number of open files is
8929 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
8930 particular, these may be needed for OS X 10.5.
8933 Changes in version 0.1.2.18 - 2007-10-28
8934 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8935 hidden service introduction that were causing huge delays, and a big
8936 bug that was causing some servers to disappear from the network status
8937 lists for a few hours each day.
8939 o Major bugfixes (crashes):
8940 - If a connection is shut down abruptly because of something that
8941 happened inside connection_flushed_some(), do not call
8942 connection_finished_flushing(). Should fix bug 451:
8943 "connection_stop_writing: Assertion conn->write_event failed"
8944 Bugfix on 0.1.2.7-alpha.
8945 - Fix possible segfaults in functions called from
8946 rend_process_relay_cell().
8948 o Major bugfixes (hidden services):
8949 - Hidden services were choosing introduction points uniquely by
8950 hexdigest, but when constructing the hidden service descriptor
8951 they merely wrote the (potentially ambiguous) nickname.
8952 - Clients now use the v2 intro format for hidden service
8953 connections: they specify their chosen rendezvous point by identity
8954 digest rather than by (potentially ambiguous) nickname. These
8955 changes could speed up hidden service connections dramatically.
8957 o Major bugfixes (other):
8958 - Stop publishing a new server descriptor just because we get a
8959 HUP signal. This led (in a roundabout way) to some servers getting
8960 dropped from the networkstatus lists for a few hours each day.
8961 - When looking for a circuit to cannibalize, consider family as well
8962 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8963 circuit cannibalization).
8964 - When a router wasn't listed in a new networkstatus, we were leaving
8965 the flags for that router alone -- meaning it remained Named,
8966 Running, etc -- even though absence from the networkstatus means
8967 that it shouldn't be considered to exist at all anymore. Now we
8968 clear all the flags for routers that fall out of the networkstatus
8969 consensus. Fixes bug 529.
8972 - Don't try to access (or alter) the state file when running
8973 --list-fingerprint or --verify-config or --hash-password. Resolves
8975 - When generating information telling us how to extend to a given
8976 router, do not try to include the nickname if it is
8977 absent. Resolves bug 467.
8978 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8979 a way to trigger this remotely.)
8980 - When sending a status event to the controller telling it that an
8981 OR address is reachable, set the port correctly. (Previously we
8982 were reporting the dir port.)
8983 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8984 command. Bugfix on 0.1.2.17.
8985 - When loading bandwidth history, do not believe any information in
8986 the future. Fixes bug 434.
8987 - When loading entry guard information, do not believe any information
8989 - When we have our clock set far in the future and generate an
8990 onion key, then re-set our clock to be correct, we should not stop
8991 the onion key from getting rotated.
8992 - On some platforms, accept() can return a broken address. Detect
8993 this more quietly, and deal accordingly. Fixes bug 483.
8994 - It's not actually an error to find a non-pending entry in the DNS
8995 cache when canceling a pending resolve. Don't log unless stuff
8996 is fishy. Resolves bug 463.
8997 - Don't reset trusted dir server list when we set a configuration
8998 option. Patch from Robert Hogan.
8999 - Don't try to create the datadir when running --verify-config or
9000 --hash-password. Resolves bug 540.
9003 Changes in version 0.2.0.9-alpha - 2007-10-24
9004 This ninth development snapshot switches clients to the new v3 directory
9005 system; allows servers to be listed in the network status even when they
9006 have the same nickname as a registered server; and fixes many other
9007 bugs including a big one that was causing some servers to disappear
9008 from the network status lists for a few hours each day.
9010 o Major features (directory system):
9011 - Clients now download v3 consensus networkstatus documents instead
9012 of v2 networkstatus documents. Clients and caches now base their
9013 opinions about routers on these consensus documents. Clients only
9014 download router descriptors listed in the consensus.
9015 - Authorities now list servers who have the same nickname as
9016 a different named server, but list them with a new flag,
9017 "Unnamed". Now we can list servers that happen to pick the same
9018 nickname as a server that registered two years ago and then
9019 disappeared. Partially implements proposal 122.
9020 - If the consensus lists a router as "Unnamed", the name is assigned
9021 to a different router: do not identify the router by that name.
9022 Partially implements proposal 122.
9023 - Authorities can now come to a consensus on which method to use to
9024 compute the consensus. This gives us forward compatibility.
9027 - Stop publishing a new server descriptor just because we HUP or
9028 when we find our DirPort to be reachable but won't actually publish
9029 it. New descriptors without any real changes are dropped by the
9030 authorities, and can screw up our "publish every 18 hours" schedule.
9032 - When a router wasn't listed in a new networkstatus, we were leaving
9033 the flags for that router alone -- meaning it remained Named,
9034 Running, etc -- even though absence from the networkstatus means
9035 that it shouldn't be considered to exist at all anymore. Now we
9036 clear all the flags for routers that fall out of the networkstatus
9037 consensus. Fixes bug 529; bugfix on 0.1.2.x.
9038 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
9039 extrainfo documents and then discard them immediately for not
9040 matching the latest router. Bugfix on 0.2.0.1-alpha.
9042 o Minor features (v3 directory protocol):
9043 - Allow tor-gencert to generate a new certificate without replacing
9045 - Allow certificates to include an address.
9046 - When we change our directory-cache settings, reschedule all voting
9047 and download operations.
9048 - Reattempt certificate downloads immediately on failure, as long as
9049 we haven't failed a threshold number of times yet.
9050 - Delay retrying consensus downloads while we're downloading
9051 certificates to verify the one we just got. Also, count getting a
9052 consensus that we already have (or one that isn't valid) as a failure,
9053 and count failing to get the certificates after 20 minutes as a
9055 - Build circuits and download descriptors even if our consensus is a
9056 little expired. (This feature will go away once authorities are
9059 o Minor features (router descriptor cache):
9060 - If we find a cached-routers file that's been sitting around for more
9061 than 28 days unmodified, then most likely it's a leftover from
9062 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
9064 - When we (as a cache) download a descriptor because it was listed
9065 in a consensus, remember when the consensus was supposed to expire,
9066 and don't expire the descriptor until then.
9068 o Minor features (performance):
9069 - Call routerlist_remove_old_routers() much less often. This should
9070 speed startup, especially on directory caches.
9071 - Don't try to launch new descriptor downloads quite so often when we
9072 already have enough directory information to build circuits.
9073 - Base64 decoding was actually showing up on our profile when parsing
9074 the initial descriptor file; switch to an in-process all-at-once
9075 implementation that's about 3.5x times faster than calling out to
9078 o Minor features (compilation):
9079 - Detect non-ASCII platforms (if any still exist) and refuse to
9080 build there: some of our code assumes that 'A' is 65 and so on.
9082 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
9083 - Make the "next period" votes into "current period" votes immediately
9084 after publishing the consensus; avoid a heisenbug that made them
9085 stick around indefinitely.
9086 - When we discard a vote as a duplicate, do not report this as
9088 - Treat missing v3 keys or certificates as an error when running as a
9089 v3 directory authority.
9090 - When we're configured to be a v3 authority, but we're only listed
9091 as a non-v3 authority in our DirServer line for ourself, correct
9093 - If an authority doesn't have a qualified hostname, just put
9094 its address in the vote. This fixes the problem where we referred to
9095 "moria on moria:9031."
9096 - Distinguish between detached signatures for the wrong period, and
9097 detached signatures for a divergent vote.
9098 - Fix a small memory leak when computing a consensus.
9099 - When there's no concensus, we were forming a vote every 30
9100 minutes, but writing the "valid-after" line in our vote based
9101 on our configured V3AuthVotingInterval: so unless the intervals
9102 matched up, we immediately rejected our own vote because it didn't
9103 start at the voting interval that caused us to construct a vote.
9105 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
9106 - Delete unverified-consensus when the real consensus is set.
9107 - Consider retrying a consensus networkstatus fetch immediately
9108 after one fails: don't wait 60 seconds to notice.
9109 - When fetching a consensus as a cache, wait until a newer consensus
9110 should exist before trying to replace the current one.
9111 - Use a more forgiving schedule for retrying failed consensus
9112 downloads than for other types.
9114 o Minor bugfixes (other directory issues):
9115 - Correct the implementation of "download votes by digest." Bugfix on
9117 - Authorities no longer send back "400 you're unreachable please fix
9118 it" errors to Tor servers that aren't online all the time. We're
9119 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
9121 o Minor bugfixes (controller):
9122 - Don't reset trusted dir server list when we set a configuration
9123 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
9124 - Respond to INT and TERM SIGNAL commands before we execute the
9125 signal, in case the signal shuts us down. We had a patch in
9126 0.1.2.1-alpha that tried to do this by queueing the response on
9127 the connection's buffer before shutting down, but that really
9128 isn't the same thing at all. Bug located by Matt Edman.
9130 o Minor bugfixes (misc):
9131 - Correctly check for bad options to the "PublishServerDescriptor"
9132 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
9133 - Stop leaking memory on failing case of base32_decode, and make
9134 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
9135 - Don't try to download extrainfo documents when we're trying to
9136 fetch enough directory info to build a circuit: having enough
9137 info should get priority. Bugfix on 0.2.0.x.
9138 - Don't complain that "your server has not managed to confirm that its
9139 ports are reachable" if we haven't been able to build any circuits
9140 yet. Bug found by spending four hours without a v3 consensus. Bugfix
9142 - Detect the reason for failing to mmap a descriptor file we just
9143 wrote, and give a more useful log message. Fixes bug 533. Bugfix
9146 o Code simplifications and refactoring:
9147 - Remove support for the old bw_accounting file: we've been storing
9148 bandwidth accounting information in the state file since
9149 0.1.2.5-alpha. This may result in bandwidth accounting errors
9150 if you try to upgrade from 0.1.1.x or earlier, or if you try to
9151 downgrade to 0.1.1.x or earlier.
9152 - New convenience code to locate a file within the DataDirectory.
9153 - Move non-authority functionality out of dirvote.c.
9154 - Refactor the arguments for router_pick_{directory_|trusteddir}server
9155 so that they all take the same named flags.
9158 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
9159 Unix users an easy way to script their Tor process (e.g. by
9160 adjusting bandwidth based on the time of the day).
9163 Changes in version 0.2.0.8-alpha - 2007-10-12
9164 This eighth development snapshot fixes a crash bug that's been bothering
9165 us since February 2007, lets bridge authorities store a list of bridge
9166 descriptors they've seen, gets v3 directory voting closer to working,
9167 starts caching v3 directory consensus documents on directory mirrors,
9168 and fixes a variety of smaller issues including some minor memory leaks.
9170 o Major features (router descriptor cache):
9171 - Store routers in a file called cached-descriptors instead of in
9172 cached-routers. Initialize cached-descriptors from cached-routers
9173 if the old format is around. The new format allows us to store
9174 annotations along with descriptors.
9175 - Use annotations to record the time we received each descriptor, its
9176 source, and its purpose.
9177 - Disable the SETROUTERPURPOSE controller command: it is now
9179 - Controllers should now specify cache=no or cache=yes when using
9180 the +POSTDESCRIPTOR command.
9181 - Bridge authorities now write bridge descriptors to disk, meaning
9182 we can export them to other programs and begin distributing them
9185 o Major features (directory authorities):
9186 - When a v3 authority is missing votes or signatures, it now tries
9188 - Directory authorities track weighted fractional uptime as well as
9189 weighted mean-time-between failures. WFU is suitable for deciding
9190 whether a node is "usually up", while MTBF is suitable for deciding
9191 whether a node is "likely to stay up." We need both, because
9192 "usually up" is a good requirement for guards, while "likely to
9193 stay up" is a good requirement for long-lived connections.
9195 o Major features (v3 directory system):
9196 - Caches now download v3 network status documents as needed,
9197 and download the descriptors listed in them.
9198 - All hosts now attempt to download and keep fresh v3 authority
9199 certificates, and re-attempt after failures.
9200 - More internal-consistency checks for vote parsing.
9202 o Major bugfixes (crashes):
9203 - If a connection is shut down abruptly because of something that
9204 happened inside connection_flushed_some(), do not call
9205 connection_finished_flushing(). Should fix bug 451. Bugfix on
9208 o Major bugfixes (performance):
9209 - Fix really bad O(n^2) performance when parsing a long list of
9210 routers: Instead of searching the entire list for an "extra-info "
9211 string which usually wasn't there, once for every routerinfo
9212 we read, just scan lines forward until we find one we like.
9214 - When we add data to a write buffer in response to the data on that
9215 write buffer getting low because of a flush, do not consider the
9216 newly added data as a candidate for immediate flushing, but rather
9217 make it wait until the next round of writing. Otherwise, we flush
9218 and refill recursively, and a single greedy TLS connection can
9219 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
9221 o Minor features (v3 authority system):
9222 - Add more ways for tools to download the votes that lead to the
9224 - Send a 503 when low on bandwidth and a vote, consensus, or
9225 certificate is requested.
9226 - If-modified-since is now implemented properly for all kinds of
9227 certificate requests.
9229 o Minor bugfixes (network statuses):
9230 - Tweak the implementation of proposal 109 slightly: allow at most
9231 two Tor servers on the same IP address, except if it's the location
9232 of a directory authority, in which case allow five. Bugfix on
9235 o Minor bugfixes (controller):
9236 - When sending a status event to the controller telling it that an
9237 OR address is reachable, set the port correctly. (Previously we
9238 were reporting the dir port.) Bugfix on 0.1.2.x.
9240 o Minor bugfixes (v3 directory system):
9241 - Fix logic to look up a cert by its signing key digest. Bugfix on
9243 - Only change the reply to a vote to "OK" if it's not already
9244 set. This gets rid of annoying "400 OK" log messages, which may
9245 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
9246 - When we get a valid consensus, recompute the voting schedule.
9247 - Base the valid-after time of a vote on the consensus voting
9248 schedule, not on our preferred schedule.
9249 - Make the return values and messages from signature uploads and
9250 downloads more sensible.
9251 - Fix a memory leak when serving votes and consensus documents, and
9252 another when serving certificates.
9254 o Minor bugfixes (performance):
9255 - Use a slightly simpler string hashing algorithm (copying Python's
9256 instead of Java's) and optimize our digest hashing algorithm to take
9257 advantage of 64-bit platforms and to remove some possibly-costly
9259 - Fix a minor memory leak whenever we parse guards from our state
9260 file. Bugfix on 0.2.0.7-alpha.
9261 - Fix a minor memory leak whenever we write out a file. Bugfix on
9263 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9264 command. Bugfix on 0.2.0.5-alpha.
9266 o Minor bugfixes (portability):
9267 - On some platforms, accept() can return a broken address. Detect
9268 this more quietly, and deal accordingly. Fixes bug 483.
9269 - Stop calling tor_strlower() on uninitialized memory in some cases.
9270 Bugfix in 0.2.0.7-alpha.
9272 o Minor bugfixes (usability):
9273 - Treat some 403 responses from directory servers as INFO rather than
9274 WARN-severity events.
9275 - It's not actually an error to find a non-pending entry in the DNS
9276 cache when canceling a pending resolve. Don't log unless stuff is
9277 fishy. Resolves bug 463.
9279 o Minor bugfixes (anonymity):
9280 - Never report that we've used more bandwidth than we're willing to
9281 relay: it leaks how much non-relay traffic we're using. Resolves
9283 - When looking for a circuit to cannibalize, consider family as well
9284 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9285 circuit cannibalization).
9287 o Code simplifications and refactoring:
9288 - Make a bunch of functions static. Remove some dead code.
9289 - Pull out about a third of the really big routerlist.c; put it in a
9290 new module, networkstatus.c.
9291 - Merge the extra fields in local_routerstatus_t back into
9292 routerstatus_t: we used to need one routerstatus_t for each
9293 authority's opinion, plus a local_routerstatus_t for the locally
9294 computed consensus opinion. To save space, we put the locally
9295 modified fields into local_routerstatus_t, and only the common
9296 stuff into routerstatus_t. But once v3 directories are in use,
9297 clients and caches will no longer need to hold authority opinions;
9298 thus, the rationale for keeping the types separate is now gone.
9299 - Make the code used to reschedule and reattempt downloads more
9301 - Turn all 'Are we a directory server/mirror?' logic into a call to
9303 - Remove the code to generate the oldest (v1) directory format.
9304 The code has been disabled since 0.2.0.5-alpha.
9307 Changes in version 0.2.0.7-alpha - 2007-09-21
9308 This seventh development snapshot makes bridges work again, makes bridge
9309 authorities work for the first time, fixes two huge performance flaws
9310 in hidden services, and fixes a variety of minor issues.
9312 o New directory authorities:
9313 - Set up moria1 and tor26 as the first v3 directory authorities. See
9314 doc/spec/dir-spec.txt for details on the new directory design.
9316 o Major bugfixes (crashes):
9317 - Fix possible segfaults in functions called from
9318 rend_process_relay_cell(). Bugfix on 0.1.2.x.
9320 o Major bugfixes (bridges):
9321 - Fix a bug that made servers send a "404 Not found" in response to
9322 attempts to fetch their server descriptor. This caused Tor servers
9323 to take many minutes to establish reachability for their DirPort,
9324 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
9325 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
9326 users configure that and specify a bridge with an identity
9327 fingerprint, now they will lookup the bridge descriptor at the
9328 default bridge authority via a one-hop tunnel, but once circuits
9329 are established they will switch to a three-hop tunnel for later
9330 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
9332 o Major bugfixes (hidden services):
9333 - Hidden services were choosing introduction points uniquely by
9334 hexdigest, but when constructing the hidden service descriptor
9335 they merely wrote the (potentially ambiguous) nickname.
9336 - Clients now use the v2 intro format for hidden service
9337 connections: they specify their chosen rendezvous point by identity
9338 digest rather than by (potentially ambiguous) nickname. Both
9339 are bugfixes on 0.1.2.x, and they could speed up hidden service
9340 connections dramatically. Thanks to Karsten Loesing.
9342 o Minor features (security):
9343 - As a client, do not believe any server that tells us that an
9344 address maps to an internal address space.
9345 - Make it possible to enable HashedControlPassword and
9346 CookieAuthentication at the same time.
9348 o Minor features (guard nodes):
9349 - Tag every guard node in our state file with the version that
9350 we believe added it, or with our own version if we add it. This way,
9351 if a user temporarily runs an old version of Tor and then switches
9352 back to a new one, she doesn't automatically lose her guards.
9354 o Minor features (speed):
9355 - When implementing AES counter mode, update only the portions of the
9356 counter buffer that need to change, and don't keep separate
9357 network-order and host-order counters when they are the same (i.e.,
9358 on big-endian hosts.)
9360 o Minor features (controller):
9361 - Accept LF instead of CRLF on controller, since some software has a
9362 hard time generating real Internet newlines.
9363 - Add GETINFO values for the server status events
9364 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
9368 - Routers no longer include bandwidth-history lines in their
9369 descriptors; this information is already available in extra-info
9370 documents, and including it in router descriptors took up 60%
9371 (!) of compressed router descriptor downloads. Completes
9372 implementation of proposal 104.
9373 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
9374 and TorControl.py, as they use the old v0 controller protocol,
9375 and are obsoleted by TorFlow anyway.
9376 - Drop support for v1 rendezvous descriptors, since we never used
9377 them anyway, and the code has probably rotted by now. Based on
9378 patch from Karsten Loesing.
9379 - On OSX, stop warning the user that kqueue support in libevent is
9380 "experimental", since it seems to have worked fine for ages.
9383 - When generating information telling us how to extend to a given
9384 router, do not try to include the nickname if it is absent. Fixes
9385 bug 467. Bugfix on 0.2.0.3-alpha.
9386 - Fix a user-triggerable (but not remotely-triggerable) segfault
9387 in expand_filename(). Bugfix on 0.1.2.x.
9388 - Fix a memory leak when freeing incomplete requests from DNSPort.
9389 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
9390 - Don't try to access (or alter) the state file when running
9391 --list-fingerprint or --verify-config or --hash-password. (Resolves
9392 bug 499.) Bugfix on 0.1.2.x.
9393 - Servers used to decline to publish their DirPort if their
9394 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
9395 were below a threshold. Now they only look at BandwidthRate and
9396 RelayBandwidthRate. Bugfix on 0.1.2.x.
9397 - Remove an optimization in the AES counter-mode code that assumed
9398 that the counter never exceeded 2^68. When the counter can be set
9399 arbitrarily as an IV (as it is by Karsten's new hidden services
9400 code), this assumption no longer holds. Bugfix on 0.1.2.x.
9401 - Resume listing "AUTHORITY" flag for authorities in network status.
9402 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
9404 o Code simplifications and refactoring:
9405 - Revamp file-writing logic so we don't need to have the entire
9406 contents of a file in memory at once before we write to disk. Tor,
9408 - Turn "descriptor store" into a full-fledged type.
9409 - Move all NT services code into a separate source file.
9410 - Unify all code that computes medians, percentile elements, etc.
9411 - Get rid of a needless malloc when parsing address policies.
9414 Changes in version 0.1.2.17 - 2007-08-30
9415 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
9416 X bundles. Vidalia 0.0.14 makes authentication required for the
9417 ControlPort in the default configuration, which addresses important
9418 security risks. Everybody who uses Vidalia (or another controller)
9421 In addition, this Tor update fixes major load balancing problems with
9422 path selection, which should speed things up a lot once many people
9425 o Major bugfixes (security):
9426 - We removed support for the old (v0) control protocol. It has been
9427 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
9428 become more of a headache than it's worth.
9430 o Major bugfixes (load balancing):
9431 - When choosing nodes for non-guard positions, weight guards
9432 proportionally less, since they already have enough load. Patch
9434 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9435 will allow fast Tor servers to get more attention.
9436 - When we're upgrading from an old Tor version, forget our current
9437 guards and pick new ones according to the new weightings. These
9438 three load balancing patches could raise effective network capacity
9439 by a factor of four. Thanks to Mike Perry for measurements.
9441 o Major bugfixes (stream expiration):
9442 - Expire not-yet-successful application streams in all cases if
9443 they've been around longer than SocksTimeout. Right now there are
9444 some cases where the stream will live forever, demanding a new
9445 circuit every 15 seconds. Fixes bug 454; reported by lodger.
9447 o Minor features (controller):
9448 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9449 is valid before any authentication has been received. It tells
9450 a controller what kind of authentication is expected, and what
9451 protocol is spoken. Implements proposal 119.
9453 o Minor bugfixes (performance):
9454 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
9455 greatly speeding up loading cached-routers from disk on startup.
9456 - Disable sentinel-based debugging for buffer code: we squashed all
9457 the bugs that this was supposed to detect a long time ago, and now
9458 its only effect is to change our buffer sizes from nice powers of
9459 two (which platform mallocs tend to like) to values slightly over
9460 powers of two (which make some platform mallocs sad).
9462 o Minor bugfixes (misc):
9463 - If exit bandwidth ever exceeds one third of total bandwidth, then
9464 use the correct formula to weight exit nodes when choosing paths.
9465 Based on patch from Mike Perry.
9466 - Choose perfectly fairly among routers when choosing by bandwidth and
9467 weighting by fraction of bandwidth provided by exits. Previously, we
9468 would choose with only approximate fairness, and correct ourselves
9469 if we ran off the end of the list.
9470 - If we require CookieAuthentication but we fail to write the
9471 cookie file, we would warn but not exit, and end up in a state
9472 where no controller could authenticate. Now we exit.
9473 - If we require CookieAuthentication, stop generating a new cookie
9474 every time we change any piece of our config.
9475 - Refuse to start with certain directory authority keys, and
9476 encourage people using them to stop.
9477 - Terminate multi-line control events properly. Original patch
9479 - Fix a minor memory leak when we fail to find enough suitable
9480 servers to choose a circuit.
9481 - Stop leaking part of the descriptor when we run into a particularly
9482 unparseable piece of it.
9485 Changes in version 0.2.0.6-alpha - 2007-08-26
9486 This sixth development snapshot features a new Vidalia version in the
9487 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
9488 the ControlPort in the default configuration, which addresses important
9491 In addition, this snapshot fixes major load balancing problems
9492 with path selection, which should speed things up a lot once many
9493 people have upgraded. The directory authorities also use a new
9494 mean-time-between-failure approach to tracking which servers are stable,
9495 rather than just looking at the most recent uptime.
9497 o New directory authorities:
9498 - Set up Tonga as the default bridge directory authority.
9501 - Directory authorities now track servers by weighted
9502 mean-times-between-failures. When we have 4 or more days of data,
9503 use measured MTBF rather than declared uptime to decide whether
9504 to call a router Stable. Implements proposal 108.
9506 o Major bugfixes (load balancing):
9507 - When choosing nodes for non-guard positions, weight guards
9508 proportionally less, since they already have enough load. Patch
9510 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9511 will allow fast Tor servers to get more attention.
9512 - When we're upgrading from an old Tor version, forget our current
9513 guards and pick new ones according to the new weightings. These
9514 three load balancing patches could raise effective network capacity
9515 by a factor of four. Thanks to Mike Perry for measurements.
9517 o Major bugfixes (descriptor parsing):
9518 - Handle unexpected whitespace better in malformed descriptors. Bug
9519 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
9522 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
9523 GETINFO for Torstat to use until it can switch to using extrainfos.
9524 - Optionally (if built with -DEXPORTMALLINFO) export the output
9525 of mallinfo via http, as tor/mallinfo.txt. Only accessible
9529 - Do not intermix bridge routers with controller-added
9530 routers. (Bugfix on 0.2.0.x)
9531 - Do not fail with an assert when accept() returns an unexpected
9532 address family. Addresses but does not wholly fix bug 483. (Bugfix
9534 - Let directory authorities startup even when they can't generate
9535 a descriptor immediately, e.g. because they don't know their
9537 - Stop putting the authentication cookie in a file called "0"
9538 in your working directory if you don't specify anything for the
9539 new CookieAuthFile option. Reported by Matt Edman.
9540 - Make it possible to read the PROTOCOLINFO response in a way that
9541 conforms to our control-spec. Reported by Matt Edman.
9542 - Fix a minor memory leak when we fail to find enough suitable
9543 servers to choose a circuit. Bugfix on 0.1.2.x.
9544 - Stop leaking part of the descriptor when we run into a particularly
9545 unparseable piece of it. Bugfix on 0.1.2.x.
9546 - Unmap the extrainfo cache file on exit.
9549 Changes in version 0.2.0.5-alpha - 2007-08-19
9550 This fifth development snapshot fixes compilation on Windows again;
9551 fixes an obnoxious client-side bug that slowed things down and put
9552 extra load on the network; gets us closer to using the v3 directory
9553 voting scheme; makes it easier for Tor controllers to use cookie-based
9554 authentication; and fixes a variety of other bugs.
9557 - Version 1 directories are no longer generated in full. Instead,
9558 authorities generate and serve "stub" v1 directories that list
9559 no servers. This will stop Tor versions 0.1.0.x and earlier from
9560 working, but (for security reasons) nobody should be running those
9563 o Major bugfixes (compilation, 0.2.0.x):
9564 - Try to fix Win32 compilation again: improve checking for IPv6 types.
9565 - Try to fix MSVC compilation: build correctly on platforms that do
9566 not define s6_addr16 or s6_addr32.
9567 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
9570 o Major bugfixes (stream expiration):
9571 - Expire not-yet-successful application streams in all cases if
9572 they've been around longer than SocksTimeout. Right now there are
9573 some cases where the stream will live forever, demanding a new
9574 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
9577 o Minor features (directory servers):
9578 - When somebody requests a list of statuses or servers, and we have
9579 none of those, return a 404 rather than an empty 200.
9581 o Minor features (directory voting):
9582 - Store v3 consensus status consensuses on disk, and reload them
9585 o Minor features (security):
9586 - Warn about unsafe ControlPort configurations.
9587 - Refuse to start with certain directory authority keys, and
9588 encourage people using them to stop.
9590 o Minor features (controller):
9591 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9592 is valid before any authentication has been received. It tells
9593 a controller what kind of authentication is expected, and what
9594 protocol is spoken. Implements proposal 119.
9595 - New config option CookieAuthFile to choose a new location for the
9596 cookie authentication file, and config option
9597 CookieAuthFileGroupReadable to make it group-readable.
9599 o Minor features (unit testing):
9600 - Add command-line arguments to unit-test executable so that we can
9601 invoke any chosen test from the command line rather than having
9602 to run the whole test suite at once; and so that we can turn on
9603 logging for the unit tests.
9605 o Minor bugfixes (on 0.1.2.x):
9606 - If we require CookieAuthentication but we fail to write the
9607 cookie file, we would warn but not exit, and end up in a state
9608 where no controller could authenticate. Now we exit.
9609 - If we require CookieAuthentication, stop generating a new cookie
9610 every time we change any piece of our config.
9611 - When loading bandwidth history, do not believe any information in
9612 the future. Fixes bug 434.
9613 - When loading entry guard information, do not believe any information
9615 - When we have our clock set far in the future and generate an
9616 onion key, then re-set our clock to be correct, we should not stop
9617 the onion key from getting rotated.
9618 - Clean up torrc sample config file.
9619 - Do not automatically run configure from autogen.sh. This
9620 non-standard behavior tended to annoy people who have built other
9623 o Minor bugfixes (on 0.2.0.x):
9624 - Fix a bug with AutomapHostsOnResolve that would always cause
9625 the second request to fail. Bug reported by Kate. Bugfix on
9627 - Fix a bug in ADDRMAP controller replies that would sometimes
9628 try to print a NULL. Patch from tup.
9629 - Read v3 directory authority keys from the right location.
9630 - Numerous bugfixes to directory voting code.
9633 Changes in version 0.1.2.16 - 2007-08-01
9634 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
9635 remote attacker in certain situations to rewrite the user's torrc
9636 configuration file. This can completely compromise anonymity of users
9637 in most configurations, including those running the Vidalia bundles,
9638 TorK, etc. Or worse.
9640 o Major security fixes:
9641 - Close immediately after missing authentication on control port;
9642 do not allow multiple authentication attempts.
9645 Changes in version 0.2.0.4-alpha - 2007-08-01
9646 This fourth development snapshot fixes a critical security vulnerability
9647 for most users, specifically those running Vidalia, TorK, etc. Everybody
9648 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
9650 o Major security fixes:
9651 - Close immediately after missing authentication on control port;
9652 do not allow multiple authentication attempts.
9654 o Major bugfixes (compilation):
9655 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
9658 o Minor features (performance):
9659 - Be even more aggressive about releasing RAM from small
9660 empty buffers. Thanks to our free-list code, this shouldn't be too
9661 performance-intensive.
9662 - Disable sentinel-based debugging for buffer code: we squashed all
9663 the bugs that this was supposed to detect a long time ago, and
9664 now its only effect is to change our buffer sizes from nice
9665 powers of two (which platform mallocs tend to like) to values
9666 slightly over powers of two (which make some platform mallocs sad).
9667 - Log malloc statistics from mallinfo() on platforms where it
9671 Changes in version 0.2.0.3-alpha - 2007-07-29
9672 This third development snapshot introduces new experimental
9673 blocking-resistance features and a preliminary version of the v3
9674 directory voting design, and includes many other smaller features
9678 - The first pieces of our "bridge" design for blocking-resistance
9679 are implemented. People can run bridge directory authorities;
9680 people can run bridges; and people can configure their Tor clients
9681 with a set of bridges to use as the first hop into the Tor network.
9682 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
9684 - Create listener connections before we setuid to the configured
9685 User and Group. Now non-Windows users can choose port values
9686 under 1024, start Tor as root, and have Tor bind those ports
9687 before it changes to another UID. (Windows users could already
9689 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
9690 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
9691 on "vserver" accounts. (Patch from coderman.)
9692 - Be even more aggressive about separating local traffic from relayed
9693 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
9695 o Major features (experimental):
9696 - First cut of code for "v3 dir voting": directory authorities will
9697 vote on a common network status document rather than each publishing
9698 their own opinion. This code needs more testing and more corner-case
9699 handling before it's ready for use.
9702 - Directory authorities now call routers Fast if their bandwidth is
9703 at least 100KB/s, and consider their bandwidth adequate to be a
9704 Guard if it is at least 250KB/s, no matter the medians. This fix
9705 complements proposal 107. [Bugfix on 0.1.2.x]
9706 - Directory authorities now never mark more than 3 servers per IP as
9707 Valid and Running. (Implements proposal 109, by Kevin Bauer and
9709 - Minor change to organizationName and commonName generation
9710 procedures in TLS certificates during Tor handshakes, to invalidate
9711 some earlier censorware approaches. This is not a long-term
9712 solution, but applying it will give us a bit of time to look into
9713 the epidemiology of countermeasures as they spread.
9715 o Major bugfixes (directory):
9716 - Rewrite directory tokenization code to never run off the end of
9717 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
9719 o Minor features (controller):
9720 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
9721 match requests to applications. (Patch from Robert Hogan.)
9722 - Report address and port correctly on connections to DNSPort. (Patch
9724 - Add a RESOLVE command to launch hostname lookups. (Original patch
9726 - Add GETINFO status/enough-dir-info to let controllers tell whether
9727 Tor has downloaded sufficient directory information. (Patch
9729 - You can now use the ControlSocket option to tell Tor to listen for
9730 controller connections on Unix domain sockets on systems that
9731 support them. (Patch from Peter Palfrader.)
9732 - STREAM NEW events are generated for DNSPort requests and for
9733 tunneled directory connections. (Patch from Robert Hogan.)
9734 - New "GETINFO address-mappings/*" command to get address mappings
9735 with expiry information. "addr-mappings/*" is now deprecated.
9738 o Minor features (misc):
9739 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
9741 - The tor-gencert tool for v3 directory authorities now creates all
9742 files as readable to the file creator only, and write-protects
9743 the authority identity key.
9744 - When dumping memory usage, list bytes used in buffer memory
9746 - When running with dmalloc, dump more stats on hup and on exit.
9747 - Directory authorities now fail quickly and (relatively) harmlessly
9748 if they generate a network status document that is somehow
9751 o Traffic load balancing improvements:
9752 - If exit bandwidth ever exceeds one third of total bandwidth, then
9753 use the correct formula to weight exit nodes when choosing paths.
9754 (Based on patch from Mike Perry.)
9755 - Choose perfectly fairly among routers when choosing by bandwidth and
9756 weighting by fraction of bandwidth provided by exits. Previously, we
9757 would choose with only approximate fairness, and correct ourselves
9758 if we ran off the end of the list. [Bugfix on 0.1.2.x]
9760 o Performance improvements:
9761 - Be more aggressive with freeing buffer RAM or putting it on the
9763 - Use Critical Sections rather than Mutexes for synchronizing threads
9764 on win32; Mutexes are heavier-weight, and designed for synchronizing
9767 o Deprecated and removed features:
9768 - RedirectExits is now deprecated.
9769 - Stop allowing address masks that do not correspond to bit prefixes.
9770 We have warned about these for a really long time; now it's time
9771 to reject them. (Patch from croup.)
9773 o Minor bugfixes (directory):
9774 - Fix another crash bug related to extra-info caching. (Bug found by
9775 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
9776 - Directories no longer return a "304 not modified" when they don't
9777 have the networkstatus the client asked for. Also fix a memory
9778 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
9779 - We had accidentally labelled 0.1.2.x directory servers as not
9780 suitable for begin_dir requests, and had labelled no directory
9781 servers as suitable for uploading extra-info documents. [Bugfix
9784 o Minor bugfixes (dns):
9785 - Fix a crash when DNSPort is set more than once. (Patch from Robert
9786 Hogan.) [Bugfix on 0.2.0.2-alpha]
9787 - Add DNSPort connections to the global connection list, so that we
9788 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
9790 - Fix a dangling reference that could lead to a crash when DNSPort is
9791 changed or closed (Patch from Robert Hogan.) [Bugfix on
9794 o Minor bugfixes (controller):
9795 - Provide DNS expiry times in GMT, not in local time. For backward
9796 compatibility, ADDRMAP events only provide GMT expiry in an extended
9797 field. "GETINFO address-mappings" always does the right thing.
9798 - Use CRLF line endings properly in NS events.
9799 - Terminate multi-line control events properly. (Original patch
9800 from tup.) [Bugfix on 0.1.2.x-alpha]
9801 - Do not include spaces in SOURCE_ADDR fields in STREAM
9802 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
9805 Changes in version 0.1.2.15 - 2007-07-17
9806 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9807 problems, fixes compilation on BSD, and fixes a variety of other
9808 bugs. Everybody should upgrade.
9810 o Major bugfixes (compilation):
9811 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9813 o Major bugfixes (crashes):
9814 - Try even harder not to dereference the first character after
9815 an mmap(). Reported by lodger.
9816 - Fix a crash bug in directory authorities when we re-number the
9817 routerlist while inserting a new router.
9818 - When the cached-routers file is an even multiple of the page size,
9819 don't run off the end and crash. (Fixes bug 455; based on idea
9821 - Fix eventdns.c behavior on Solaris: It is critical to include
9822 orconfig.h _before_ sys/types.h, so that we can get the expected
9823 definition of _FILE_OFFSET_BITS.
9825 o Major bugfixes (security):
9826 - Fix a possible buffer overrun when using BSD natd support. Bug
9828 - When sending destroy cells from a circuit's origin, don't include
9829 the reason for tearing down the circuit. The spec says we didn't,
9830 and now we actually don't. Reported by lodger.
9831 - Keep streamids from different exits on a circuit separate. This
9832 bug may have allowed other routers on a given circuit to inject
9833 cells into streams. Reported by lodger; fixes bug 446.
9834 - If there's a never-before-connected-to guard node in our list,
9835 never choose any guards past it. This way we don't expand our
9836 guard list unless we need to.
9838 o Minor bugfixes (guard nodes):
9839 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9840 don't get overused as guards.
9842 o Minor bugfixes (directory):
9843 - Correctly count the number of authorities that recommend each
9844 version. Previously, we were under-counting by 1.
9845 - Fix a potential crash bug when we load many server descriptors at
9846 once and some of them make others of them obsolete. Fixes bug 458.
9848 o Minor bugfixes (hidden services):
9849 - Stop tearing down the whole circuit when the user asks for a
9850 connection to a port that the hidden service didn't configure.
9853 o Minor bugfixes (misc):
9854 - On Windows, we were preventing other processes from reading
9855 cached-routers while Tor was running. Reported by janbar.
9856 - Fix a possible (but very unlikely) bug in picking routers by
9857 bandwidth. Add a log message to confirm that it is in fact
9858 unlikely. Patch from lodger.
9859 - Backport a couple of memory leak fixes.
9860 - Backport miscellaneous cosmetic bugfixes.
9863 Changes in version 0.2.0.2-alpha - 2007-06-02
9864 o Major bugfixes on 0.2.0.1-alpha:
9865 - Fix an assertion failure related to servers without extra-info digests.
9866 Resolves bugs 441 and 442.
9868 o Minor features (directory):
9869 - Support "If-Modified-Since" when answering HTTP requests for
9870 directories, running-routers documents, and network-status documents.
9871 (There's no need to support it for router descriptors, since those
9872 are downloaded by descriptor digest.)
9874 o Minor build issues:
9875 - Clear up some MIPSPro compiler warnings.
9876 - When building from a tarball on a machine that happens to have SVK
9877 installed, report the micro-revision as whatever version existed
9878 in the tarball, not as "x".
9881 Changes in version 0.2.0.1-alpha - 2007-06-01
9882 This early development snapshot provides new features for people running
9883 Tor as both a client and a server (check out the new RelayBandwidth
9884 config options); lets Tor run as a DNS proxy; and generally moves us
9885 forward on a lot of fronts.
9887 o Major features, server usability:
9888 - New config options RelayBandwidthRate and RelayBandwidthBurst:
9889 a separate set of token buckets for relayed traffic. Right now
9890 relayed traffic is defined as answers to directory requests, and
9891 OR connections that don't have any local circuits on them.
9893 o Major features, client usability:
9894 - A client-side DNS proxy feature to replace the need for
9895 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
9896 for DNS requests on port 9999, use the Tor network to resolve them
9897 anonymously, and send the reply back like a regular DNS server.
9898 The code still only implements a subset of DNS.
9899 - Make PreferTunneledDirConns and TunnelDirConns work even when
9900 we have no cached directory info. This means Tor clients can now
9901 do all of their connections protected by TLS.
9903 o Major features, performance and efficiency:
9904 - Directory authorities accept and serve "extra info" documents for
9905 routers. These documents contain fields from router descriptors
9906 that aren't usually needed, and that use a lot of excess
9907 bandwidth. Once these fields are removed from router descriptors,
9908 the bandwidth savings should be about 60%. [Partially implements
9910 - Servers upload extra-info documents to any authority that accepts
9911 them. Authorities (and caches that have been configured to download
9912 extra-info documents) download them as needed. [Partially implements
9914 - Change the way that Tor buffers data that it is waiting to write.
9915 Instead of queueing data cells in an enormous ring buffer for each
9916 client->OR or OR->OR connection, we now queue cells on a separate
9917 queue for each circuit. This lets us use less slack memory, and
9918 will eventually let us be smarter about prioritizing different kinds
9920 - Use memory pools to allocate cells with better speed and memory
9921 efficiency, especially on platforms where malloc() is inefficient.
9922 - Stop reading on edge connections when their corresponding circuit
9923 buffers are full; start again as the circuits empty out.
9925 o Major features, other:
9926 - Add an HSAuthorityRecordStats option that hidden service authorities
9927 can use to track statistics of overall hidden service usage without
9928 logging information that would be very useful to an attacker.
9929 - Start work implementing multi-level keys for directory authorities:
9930 Add a standalone tool to generate key certificates. (Proposal 103.)
9933 - Directory authorities now call routers Stable if they have an
9934 uptime of at least 30 days, even if that's not the median uptime
9935 in the network. Implements proposal 107, suggested by Kevin Bauer
9938 o Minor fixes (resource management):
9939 - Count the number of open sockets separately from the number
9940 of active connection_t objects. This will let us avoid underusing
9941 our allocated connection limit.
9942 - We no longer use socket pairs to link an edge connection to an
9943 anonymous directory connection or a DirPort test connection.
9944 Instead, we track the link internally and transfer the data
9945 in-process. This saves two sockets per "linked" connection (at the
9946 client and at the server), and avoids the nasty Windows socketpair()
9948 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
9949 for every single inactive connection_t. Free items from the
9950 4k/16k-buffer free lists when they haven't been used for a while.
9952 o Minor features (build):
9953 - Make autoconf search for libevent, openssl, and zlib consistently.
9954 - Update deprecated macros in configure.in.
9955 - When warning about missing headers, tell the user to let us
9956 know if the compile succeeds anyway, so we can downgrade the
9958 - Include the current subversion revision as part of the version
9959 string: either fetch it directly if we're in an SVN checkout, do
9960 some magic to guess it if we're in an SVK checkout, or use
9961 the last-detected version if we're building from a .tar.gz.
9962 Use this version consistently in log messages.
9964 o Minor features (logging):
9965 - Always prepend "Bug: " to any log message about a bug.
9966 - Put a platform string (e.g. "Linux i686") in the startup log
9967 message, so when people paste just their logs, we know if it's
9968 OpenBSD or Windows or what.
9969 - When logging memory usage, break down memory used in buffers by
9972 o Minor features (directory system):
9973 - New config option V2AuthoritativeDirectory that all directory
9974 authorities should set. This will let future authorities choose
9975 not to serve V2 directory information.
9976 - Directory authorities allow multiple router descriptors and/or extra
9977 info documents to be uploaded in a single go. This will make
9978 implementing proposal 104 simpler.
9980 o Minor features (controller):
9981 - Add a new config option __DisablePredictedCircuits designed for
9982 use by the controller, when we don't want Tor to build any circuits
9984 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9985 so we can exit from the middle of the circuit.
9986 - Implement "getinfo status/circuit-established".
9987 - Implement "getinfo status/version/..." so a controller can tell
9988 whether the current version is recommended, and whether any versions
9989 are good, and how many authorities agree. (Patch from shibz.)
9991 o Minor features (hidden services):
9992 - Allow multiple HiddenServicePort directives with the same virtual
9993 port; when they occur, the user is sent round-robin to one
9994 of the target ports chosen at random. Partially fixes bug 393 by
9995 adding limited ad-hoc round-robining.
9997 o Minor features (other):
9999 - Add a new AutomapHostsOnResolve option: when it is enabled, any
10000 resolve request for hosts matching a given pattern causes Tor to
10001 generate an internal virtual address mapping for that host. This
10002 allows DNSPort to work sensibly with hidden service users. By
10003 default, .exit and .onion addresses are remapped; the list of
10004 patterns can be reconfigured with AutomapHostsSuffixes.
10005 - Add an "-F" option to tor-resolve to force a resolve for a .onion
10006 address. Thanks to the AutomapHostsOnResolve option, this is no
10007 longer a completely silly thing to do.
10008 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
10009 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
10010 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
10011 minus 1 byte: the actual maximum declared bandwidth.
10013 o Removed features:
10014 - Removed support for the old binary "version 0" controller protocol.
10015 This has been deprecated since 0.1.1, and warnings have been issued
10016 since 0.1.2. When we encounter a v0 control message, we now send
10017 back an error and close the connection.
10018 - Remove the old "dns worker" server DNS code: it hasn't been default
10019 since 0.1.2.2-alpha, and all the servers seem to be using the new
10022 o Minor bugfixes (portability):
10023 - Even though Windows is equally happy with / and \ as path separators,
10024 try to use \ consistently on Windows and / consistently on Unix: it
10025 makes the log messages nicer.
10026 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
10027 - Read resolv.conf files correctly on platforms where read() returns
10028 partial results on small file reads.
10030 o Minor bugfixes (directory):
10031 - Correctly enforce that elements of directory objects do not appear
10032 more often than they are allowed to appear.
10033 - When we are reporting the DirServer line we just parsed, we were
10034 logging the second stanza of the key fingerprint, not the first.
10036 o Minor bugfixes (logging):
10037 - When we hit an EOF on a log (probably because we're shutting down),
10038 don't try to remove the log from the list: just mark it as
10039 unusable. (Bulletproofs against bug 222.)
10041 o Minor bugfixes (other):
10042 - In the exitlist script, only consider the most recently published
10043 server descriptor for each server. Also, when the user requests
10044 a list of servers that _reject_ connections to a given address,
10045 explicitly exclude the IPs that also have servers that accept
10046 connections to that address. (Resolves bug 405.)
10047 - Stop allowing hibernating servers to be "stable" or "fast".
10048 - On Windows, we were preventing other processes from reading
10049 cached-routers while Tor was running. (Reported by janbar)
10050 - Make the NodeFamilies config option work. (Reported by
10051 lodger -- it has never actually worked, even though we added it
10053 - Check return values from pthread_mutex functions.
10054 - Don't save non-general-purpose router descriptors to the disk cache,
10055 because we have no way of remembering what their purpose was when
10057 - Add even more asserts to hunt down bug 417.
10058 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
10059 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
10060 Add a log message to confirm that it is in fact unlikely.
10062 o Minor bugfixes (controller):
10063 - Make 'getinfo fingerprint' return a 551 error if we're not a
10064 server, so we match what the control spec claims we do. Reported
10066 - Fix a typo in an error message when extendcircuit fails that
10067 caused us to not follow the \r\n-based delimiter protocol. Reported
10070 o Code simplifications and refactoring:
10071 - Stop passing around circuit_t and crypt_path_t pointers that are
10072 implicit in other procedure arguments.
10073 - Drop the old code to choke directory connections when the
10074 corresponding OR connections got full: thanks to the cell queue
10075 feature, OR conns don't get full any more.
10076 - Make dns_resolve() handle attaching connections to circuits
10077 properly, so the caller doesn't have to.
10078 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
10079 - Keep the connection array as a dynamic smartlist_t, rather than as
10080 a fixed-sized array. This is important, as the number of connections
10081 is becoming increasingly decoupled from the number of sockets.
10084 Changes in version 0.1.2.14 - 2007-05-25
10085 Tor 0.1.2.14 changes the addresses of two directory authorities (this
10086 change especially affects those who serve or use hidden services),
10087 and fixes several other crash- and security-related bugs.
10089 o Directory authority changes:
10090 - Two directory authorities (moria1 and moria2) just moved to new
10091 IP addresses. This change will particularly affect those who serve
10092 or use hidden services.
10094 o Major bugfixes (crashes):
10095 - If a directory server runs out of space in the connection table
10096 as it's processing a begin_dir request, it will free the exit stream
10097 but leave it attached to the circuit, leading to unpredictable
10098 behavior. (Reported by seeess, fixes bug 425.)
10099 - Fix a bug in dirserv_remove_invalid() that would cause authorities
10100 to corrupt memory under some really unlikely scenarios.
10101 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
10102 - Avoid segfaults when reading from mmaped descriptor file. (Reported
10105 o Major bugfixes (security):
10106 - When choosing an entry guard for a circuit, avoid using guards
10107 that are in the same family as the chosen exit -- not just guards
10108 that are exactly the chosen exit. (Reported by lodger.)
10110 o Major bugfixes (resource management):
10111 - If a directory authority is down, skip it when deciding where to get
10112 networkstatus objects or descriptors. Otherwise we keep asking
10113 every 10 seconds forever. Fixes bug 384.
10114 - Count it as a failure if we fetch a valid network-status but we
10115 don't want to keep it. Otherwise we'll keep fetching it and keep
10116 not wanting to keep it. Fixes part of bug 422.
10117 - If all of our dirservers have given us bad or no networkstatuses
10118 lately, then stop hammering them once per minute even when we
10119 think they're failed. Fixes another part of bug 422.
10122 - Actually set the purpose correctly for descriptors inserted with
10123 purpose=controller.
10124 - When we have k non-v2 authorities in our DirServer config,
10125 we ignored the last k authorities in the list when updating our
10127 - Correctly back-off from requesting router descriptors that we are
10128 having a hard time downloading.
10129 - Read resolv.conf files correctly on platforms where read() returns
10130 partial results on small file reads.
10131 - Don't rebuild the entire router store every time we get 32K of
10132 routers: rebuild it when the journal gets very large, or when
10133 the gaps in the store get very large.
10136 - When routers publish SVN revisions in their router descriptors,
10137 authorities now include those versions correctly in networkstatus
10139 - Warn when using a version of libevent before 1.3b to run a server on
10140 OSX or BSD: these versions interact badly with userspace threads.
10143 Changes in version 0.1.2.13 - 2007-04-24
10144 This release features some major anonymity fixes, such as safer path
10145 selection; better client performance; faster bootstrapping, better
10146 address detection, and better DNS support for servers; write limiting as
10147 well as read limiting to make servers easier to run; and a huge pile of
10148 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
10150 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
10151 of the Freenode IRC network, remembering his patience and vision for
10152 free speech on the Internet.
10155 - Fix a memory leak when we ask for "all" networkstatuses and we
10156 get one we don't recognize.
10157 - Add more asserts to hunt down bug 417.
10158 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
10161 Changes in version 0.1.2.12-rc - 2007-03-16
10163 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
10164 directory information requested inside Tor connections (i.e. via
10165 begin_dir cells). It only triggered when the same connection was
10166 serving other data at the same time. Reported by seeess.
10169 - When creating a circuit via the controller, send a 'launched'
10170 event when we're done, so we follow the spec better.
10173 Changes in version 0.1.2.11-rc - 2007-03-15
10174 o Minor bugfixes (controller), reported by daejees:
10175 - Correct the control spec to match how the code actually responds
10176 to 'getinfo addr-mappings/*'.
10177 - The control spec described a GUARDS event, but the code
10178 implemented a GUARD event. Standardize on GUARD, but let people
10179 ask for GUARDS too.
10182 Changes in version 0.1.2.10-rc - 2007-03-07
10183 o Major bugfixes (Windows):
10184 - Do not load the NT services library functions (which may not exist)
10185 just to detect if we're a service trying to shut down. Now we run
10186 on Win98 and friends again.
10188 o Minor bugfixes (other):
10189 - Clarify a couple of log messages.
10190 - Fix a misleading socks5 error number.
10193 Changes in version 0.1.2.9-rc - 2007-03-02
10194 o Major bugfixes (Windows):
10195 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
10196 of the usual GCC "%llu". This prevents a bug when saving 64-bit
10197 int configuration values: the high-order 32 bits would get
10198 truncated. In particular, we were being bitten by the default
10199 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
10200 and maybe also bug 397.)
10202 o Minor bugfixes (performance):
10203 - Use OpenSSL's AES implementation on platforms where it's faster.
10204 This could save us as much as 10% CPU usage.
10206 o Minor bugfixes (server):
10207 - Do not rotate onion key immediately after setting it for the first
10210 o Minor bugfixes (directory authorities):
10211 - Stop calling servers that have been hibernating for a long time
10212 "stable". Also, stop letting hibernating or obsolete servers affect
10213 uptime and bandwidth cutoffs.
10214 - Stop listing hibernating servers in the v1 directory.
10216 o Minor bugfixes (hidden services):
10217 - Upload hidden service descriptors slightly less often, to reduce
10218 load on authorities.
10220 o Minor bugfixes (other):
10221 - Fix an assert that could trigger if a controller quickly set then
10222 cleared EntryNodes. Bug found by Udo van den Heuvel.
10223 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
10225 - Fix a potential race condition in the rpm installer. Found by
10227 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
10228 of 2 as indicating that the server is completely bad; it sometimes
10229 means that the server is just bad for the request in question. (may fix
10230 the last of bug 326.)
10231 - Disable encrypted directory connections when we don't have a server
10232 descriptor for the destination. We'll get this working again in
10236 Changes in version 0.1.2.8-beta - 2007-02-26
10237 o Major bugfixes (crashes):
10238 - Stop crashing when the controller asks us to resetconf more than
10239 one config option at once. (Vidalia 0.0.11 does this.)
10240 - Fix a crash that happened on Win98 when we're given command-line
10241 arguments: don't try to load NT service functions from advapi32.dll
10242 except when we need them. (Bug introduced in 0.1.2.7-alpha;
10244 - Fix a longstanding obscure crash bug that could occur when
10245 we run out of DNS worker processes. (Resolves bug 390.)
10247 o Major bugfixes (hidden services):
10248 - Correctly detect whether hidden service descriptor downloads are
10249 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
10251 o Major bugfixes (accounting):
10252 - When we start during an accounting interval before it's time to wake
10253 up, remember to wake up at the correct time. (May fix bug 342.)
10255 o Minor bugfixes (controller):
10256 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
10257 clear the corresponding on_circuit variable, and remember later
10258 that we don't need to send a redundant CLOSED event. Resolves part
10260 - Report events where a resolve succeeded or where we got a socks
10261 protocol error correctly, rather than calling both of them
10263 - Change reported stream target addresses to IP consistently when
10264 we finally get the IP from an exit node.
10265 - Send log messages to the controller even if they happen to be very
10268 o Minor bugfixes (other):
10269 - Display correct results when reporting which versions are
10270 recommended, and how recommended they are. (Resolves bug 383.)
10271 - Improve our estimates for directory bandwidth to be less random:
10272 guess that an unrecognized directory will have the average bandwidth
10273 from all known directories, not that it will have the average
10274 bandwidth from those directories earlier than it on the list.
10275 - If we start a server with ClientOnly 1, then set ClientOnly to 0
10276 and hup, stop triggering an assert based on an empty onion_key.
10277 - On platforms with no working mmap() equivalent, don't warn the
10278 user when cached-routers doesn't exist.
10279 - Warn the user when mmap() [or its equivalent] fails for some reason
10280 other than file-not-found.
10281 - Don't warn the user when cached-routers.new doesn't exist: that's
10282 perfectly fine when starting up for the first time.
10283 - When EntryNodes are configured, rebuild the guard list to contain,
10284 in order: the EntryNodes that were guards before; the rest of the
10285 EntryNodes; the nodes that were guards before.
10286 - Mask out all signals in sub-threads; only the libevent signal
10287 handler should be processing them. This should prevent some crashes
10288 on some machines using pthreads. (Patch from coderman.)
10289 - Fix switched arguments on memset in the implementation of
10290 tor_munmap() for systems with no mmap() call.
10291 - When Tor receives a router descriptor that it asked for, but
10292 no longer wants (because it has received fresh networkstatuses
10293 in the meantime), do not warn the user. Cache the descriptor if
10294 we're a cache; drop it if we aren't.
10295 - Make earlier entry guards _really_ get retried when the network
10297 - On a malformed DNS reply, always give an error to the corresponding
10299 - Build with recent libevents on platforms that do not define the
10300 nonstandard types "u_int8_t" and friends.
10302 o Minor features (controller):
10303 - Warn the user when an application uses the obsolete binary v0
10304 control protocol. We're planning to remove support for it during
10305 the next development series, so it's good to give people some
10307 - Add STREAM_BW events to report per-entry-stream bandwidth
10308 use. (Patch from Robert Hogan.)
10309 - Rate-limit SIGNEWNYM signals in response to controllers that
10310 impolitely generate them for every single stream. (Patch from
10311 mwenge; closes bug 394.)
10312 - Make REMAP stream events have a SOURCE (cache or exit), and
10313 make them generated in every case where we get a successful
10314 connected or resolved cell.
10316 o Minor bugfixes (performance):
10317 - Call router_have_min_dir_info half as often. (This is showing up in
10318 some profiles, but not others.)
10319 - When using GCC, make log_debug never get called at all, and its
10320 arguments never get evaluated, when no debug logs are configured.
10321 (This is showing up in some profiles, but not others.)
10324 - Remove some never-implemented options. Mark PathlenCoinWeight as
10326 - Implement proposal 106: Stop requiring clients to have well-formed
10327 certificates; stop checking nicknames in certificates. (Clients
10328 have certificates so that they can look like Tor servers, but in
10329 the future we might want to allow them to look like regular TLS
10330 clients instead. Nicknames in certificates serve no purpose other
10331 than making our protocol easier to recognize on the wire.)
10332 - Revise messages on handshake failure again to be even more clear about
10333 which are incoming connections and which are outgoing.
10334 - Discard any v1 directory info that's over 1 month old (for
10335 directories) or over 1 week old (for running-routers lists).
10336 - Do not warn when individual nodes in the configuration's EntryNodes,
10337 ExitNodes, etc are down: warn only when all possible nodes
10338 are down. (Fixes bug 348.)
10339 - Always remove expired routers and networkstatus docs before checking
10340 whether we have enough information to build circuits. (Fixes
10342 - Put a lower-bound on MaxAdvertisedBandwidth.
10345 Changes in version 0.1.2.7-alpha - 2007-02-06
10346 o Major bugfixes (rate limiting):
10347 - Servers decline directory requests much more aggressively when
10348 they're low on bandwidth. Otherwise they end up queueing more and
10349 more directory responses, which can't be good for latency.
10350 - But never refuse directory requests from local addresses.
10351 - Fix a memory leak when sending a 503 response for a networkstatus
10353 - Be willing to read or write on local connections (e.g. controller
10354 connections) even when the global rate limiting buckets are empty.
10355 - If our system clock jumps back in time, don't publish a negative
10356 uptime in the descriptor. Also, don't let the global rate limiting
10357 buckets go absurdly negative.
10358 - Flush local controller connection buffers periodically as we're
10359 writing to them, so we avoid queueing 4+ megabytes of data before
10362 o Major bugfixes (NT services):
10363 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
10364 command-line flag so that admins can override the default by saying
10365 "tor --service install --user "SomeUser"". This will not affect
10366 existing installed services. Also, warn the user that the service
10367 will look for its configuration file in the service user's
10368 %appdata% directory. (We can't do the 'hardwire the user's appdata
10369 directory' trick any more, since we may not have read access to that
10372 o Major bugfixes (other):
10373 - Previously, we would cache up to 16 old networkstatus documents
10374 indefinitely, if they came from nontrusted authorities. Now we
10375 discard them if they are more than 10 days old.
10376 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
10378 - Detect and reject malformed DNS responses containing circular
10380 - If exits are rare enough that we're not marking exits as guards,
10381 ignore exit bandwidth when we're deciding the required bandwidth
10383 - When we're handling a directory connection tunneled over Tor,
10384 don't fill up internal memory buffers with all the data we want
10385 to tunnel; instead, only add it if the OR connection that will
10386 eventually receive it has some room for it. (This can lead to
10387 slowdowns in tunneled dir connections; a better solution will have
10388 to wait for 0.2.0.)
10390 o Minor bugfixes (dns):
10391 - Add some defensive programming to eventdns.c in an attempt to catch
10392 possible memory-stomping bugs.
10393 - Detect and reject DNS replies containing IPv4 or IPv6 records with
10394 an incorrect number of bytes. (Previously, we would ignore the
10396 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
10397 in the correct order, and doesn't crash.
10398 - Free memory held in recently-completed DNS lookup attempts on exit.
10399 This was not a memory leak, but may have been hiding memory leaks.
10400 - Handle TTL values correctly on reverse DNS lookups.
10401 - Treat failure to parse resolv.conf as an error.
10403 o Minor bugfixes (other):
10404 - Fix crash with "tor --list-fingerprint" (reported by seeess).
10405 - When computing clock skew from directory HTTP headers, consider what
10406 time it was when we finished asking for the directory, not what
10408 - Expire socks connections if they spend too long waiting for the
10409 handshake to finish. Previously we would let them sit around for
10410 days, if the connecting application didn't close them either.
10411 - And if the socks handshake hasn't started, don't send a
10412 "DNS resolve socks failed" handshake reply; just close it.
10413 - Stop using C functions that OpenBSD's linker doesn't like.
10414 - Don't launch requests for descriptors unless we have networkstatuses
10415 from at least half of the authorities. This delays the first
10416 download slightly under pathological circumstances, but can prevent
10417 us from downloading a bunch of descriptors we don't need.
10418 - Do not log IPs with TLS failures for incoming TLS
10419 connections. (Fixes bug 382.)
10420 - If the user asks to use invalid exit nodes, be willing to use
10422 - Stop using the reserved ac_cv namespace in our configure script.
10423 - Call stat() slightly less often; use fstat() when possible.
10424 - Refactor the way we handle pending circuits when an OR connection
10425 completes or fails, in an attempt to fix a rare crash bug.
10426 - Only rewrite a conn's address based on X-Forwarded-For: headers
10427 if it's a parseable public IP address; and stop adding extra quotes
10428 to the resulting address.
10431 - Weight directory requests by advertised bandwidth. Now we can
10432 let servers enable write limiting but still allow most clients to
10433 succeed at their directory requests. (We still ignore weights when
10434 choosing a directory authority; I hope this is a feature.)
10437 - Create a new file ReleaseNotes which was the old ChangeLog. The
10438 new ChangeLog file now includes the summaries for all development
10440 - Check for addresses with invalid characters at the exit as well
10441 as at the client, and warn less verbosely when they fail. You can
10442 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
10443 - Adapt a patch from goodell to let the contrib/exitlist script
10444 take arguments rather than require direct editing.
10445 - Inform the server operator when we decide not to advertise a
10446 DirPort due to AccountingMax enabled or a low BandwidthRate. It
10447 was confusing Zax, so now we're hopefully more helpful.
10448 - Bring us one step closer to being able to establish an encrypted
10449 directory tunnel without knowing a descriptor first. Still not
10450 ready yet. As part of the change, now assume we can use a
10451 create_fast cell if we don't know anything about a router.
10452 - Allow exit nodes to use nameservers running on ports other than 53.
10453 - Servers now cache reverse DNS replies.
10454 - Add an --ignore-missing-torrc command-line option so that we can
10455 get the "use sensible defaults if the configuration file doesn't
10456 exist" behavior even when specifying a torrc location on the command
10459 o Minor features (controller):
10460 - Track reasons for OR connection failure; make these reasons
10461 available via the controller interface. (Patch from Mike Perry.)
10462 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
10463 can learn when clients are sending malformed hostnames to Tor.
10464 - Clean up documentation for controller status events.
10465 - Add a REMAP status to stream events to note that a stream's
10466 address has changed because of a cached address or a MapAddress
10470 Changes in version 0.1.2.6-alpha - 2007-01-09
10472 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
10473 connection handles more than 4 gigs in either direction, we crash.
10474 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
10475 advertised exit node, somebody might try to exit from us when
10476 we're bootstrapping and before we've built our descriptor yet.
10477 Refuse the connection rather than crashing.
10480 - Warn if we (as a server) find that we've resolved an address that we
10481 weren't planning to resolve.
10482 - Warn that using select() on any libevent version before 1.1 will be
10483 unnecessarily slow (even for select()).
10484 - Flush ERR-level controller status events just like we currently
10485 flush ERR-level log events, so that a Tor shutdown doesn't prevent
10486 the controller from learning about current events.
10488 o Minor features (more controller status events):
10489 - Implement EXTERNAL_ADDRESS server status event so controllers can
10490 learn when our address changes.
10491 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
10492 can learn when directories reject our descriptor.
10493 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
10494 can learn when a client application is speaking a non-socks protocol
10496 - Implement DANGEROUS_SOCKS client status event so controllers
10497 can learn when a client application is leaking DNS addresses.
10498 - Implement BUG general status event so controllers can learn when
10499 Tor is unhappy about its internal invariants.
10500 - Implement CLOCK_SKEW general status event so controllers can learn
10501 when Tor thinks the system clock is set incorrectly.
10502 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
10503 server status events so controllers can learn when their descriptors
10504 are accepted by a directory.
10505 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
10506 server status events so controllers can learn about Tor's progress in
10507 deciding whether it's reachable from the outside.
10508 - Implement BAD_LIBEVENT general status event so controllers can learn
10509 when we have a version/method combination in libevent that needs to
10511 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
10512 and DNS_USELESS server status events so controllers can learn
10513 about changes to DNS server status.
10515 o Minor features (directory):
10516 - Authorities no longer recommend exits as guards if this would shift
10517 too much load to the exit nodes.
10520 Changes in version 0.1.2.5-alpha - 2007-01-06
10522 - Enable write limiting as well as read limiting. Now we sacrifice
10523 capacity if we're pushing out lots of directory traffic, rather
10524 than overrunning the user's intended bandwidth limits.
10525 - Include TLS overhead when counting bandwidth usage; previously, we
10526 would count only the bytes sent over TLS, but not the bytes used
10528 - Support running the Tor service with a torrc not in the same
10529 directory as tor.exe and default to using the torrc located in
10530 the %appdata%\Tor\ of the user who installed the service. Patch
10532 - Servers now check for the case when common DNS requests are going to
10533 wildcarded addresses (i.e. all getting the same answer), and change
10534 their exit policy to reject *:* if it's happening.
10535 - Implement BEGIN_DIR cells, so we can connect to the directory
10536 server via TLS to do encrypted directory requests rather than
10537 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
10538 config options if you like.
10540 o Minor features (config and docs):
10541 - Start using the state file to store bandwidth accounting data:
10542 the bw_accounting file is now obsolete. We'll keep generating it
10543 for a while for people who are still using 0.1.2.4-alpha.
10544 - Try to batch changes to the state file so that we do as few
10545 disk writes as possible while still storing important things in
10547 - The state file and the bw_accounting file get saved less often when
10548 the AvoidDiskWrites config option is set.
10549 - Make PIDFile work on Windows (untested).
10550 - Add internal descriptions for a bunch of configuration options:
10551 accessible via controller interface and in comments in saved
10553 - Reject *:563 (NNTPS) in the default exit policy. We already reject
10554 NNTP by default, so this seems like a sensible addition.
10555 - Clients now reject hostnames with invalid characters. This should
10556 avoid some inadvertent info leaks. Add an option
10557 AllowNonRFC953Hostnames to disable this behavior, in case somebody
10558 is running a private network with hosts called @, !, and #.
10559 - Add a maintainer script to tell us which options are missing
10560 documentation: "make check-docs".
10561 - Add a new address-spec.txt document to describe our special-case
10562 addresses: .exit, .onion, and .noconnnect.
10564 o Minor features (DNS):
10565 - Ongoing work on eventdns infrastructure: now it has dns server
10566 and ipv6 support. One day Tor will make use of it.
10567 - Add client-side caching for reverse DNS lookups.
10568 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
10569 - When we change nameservers or IP addresses, reset and re-launch
10570 our tests for DNS hijacking.
10572 o Minor features (directory):
10573 - Authorities now specify server versions in networkstatus. This adds
10574 about 2% to the size of compressed networkstatus docs, and allows
10575 clients to tell which servers support BEGIN_DIR and which don't.
10576 The implementation is forward-compatible with a proposed future
10577 protocol version scheme not tied to Tor versions.
10578 - DirServer configuration lines now have an orport= option so
10579 clients can open encrypted tunnels to the authorities without
10580 having downloaded their descriptors yet. Enabled for moria1,
10581 moria2, tor26, and lefkada now in the default configuration.
10582 - Directory servers are more willing to send a 503 "busy" if they
10583 are near their write limit, especially for v1 directory requests.
10584 Now they can use their limited bandwidth for actual Tor traffic.
10585 - Clients track responses with status 503 from dirservers. After a
10586 dirserver has given us a 503, we try not to use it until an hour has
10587 gone by, or until we have no dirservers that haven't given us a 503.
10588 - When we get a 503 from a directory, and we're not a server, we don't
10589 count the failure against the total number of failures allowed
10590 for the thing we're trying to download.
10591 - Report X-Your-Address-Is correctly from tunneled directory
10592 connections; don't report X-Your-Address-Is when it's an internal
10593 address; and never believe reported remote addresses when they're
10595 - Protect against an unlikely DoS attack on directory servers.
10596 - Add a BadDirectory flag to network status docs so that authorities
10597 can (eventually) tell clients about caches they believe to be
10600 o Minor features (controller):
10601 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
10602 - Reimplement GETINFO so that info/names stays in sync with the
10604 - Implement "GETINFO fingerprint".
10605 - Implement "SETEVENTS GUARD" so controllers can get updates on
10606 entry guard status as it changes.
10608 o Minor features (clean up obsolete pieces):
10609 - Remove some options that have been deprecated since at least
10610 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
10611 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
10612 to set log options.
10613 - We no longer look for identity and onion keys in "identity.key" and
10614 "onion.key" -- these were replaced by secret_id_key and
10615 secret_onion_key in 0.0.8pre1.
10616 - We no longer require unrecognized directory entries to be
10619 o Major bugfixes (security):
10620 - Stop sending the HttpProxyAuthenticator string to directory
10621 servers when directory connections are tunnelled through Tor.
10622 - Clients no longer store bandwidth history in the state file.
10623 - Do not log introduction points for hidden services if SafeLogging
10625 - When generating bandwidth history, round down to the nearest
10626 1k. When storing accounting data, round up to the nearest 1k.
10627 - When we're running as a server, remember when we last rotated onion
10628 keys, so that we will rotate keys once they're a week old even if
10629 we never stay up for a week ourselves.
10631 o Major bugfixes (other):
10632 - Fix a longstanding bug in eventdns that prevented the count of
10633 timed-out resolves from ever being reset. This bug caused us to
10634 give up on a nameserver the third time it timed out, and try it
10635 10 seconds later... and to give up on it every time it timed out
10637 - Take out the '5 second' timeout from the connection retry
10638 schedule. Now the first connect attempt will wait a full 10
10639 seconds before switching to a new circuit. Perhaps this will help
10640 a lot. Based on observations from Mike Perry.
10641 - Fix a bug on the Windows implementation of tor_mmap_file() that
10642 would prevent the cached-routers file from ever loading. Reported
10646 - Fix an assert failure when a directory authority sets
10647 AuthDirRejectUnlisted and then receives a descriptor from an
10648 unlisted router. Reported by seeess.
10649 - Avoid a double-free when parsing malformed DirServer lines.
10650 - Fix a bug when a BSD-style PF socket is first used. Patch from
10652 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
10653 to resolve an address at a given exit node even when they ask for
10655 - Servers no longer ever list themselves in their "family" line,
10656 even if configured to do so. This makes it easier to configure
10657 family lists conveniently.
10658 - When running as a server, don't fall back to 127.0.0.1 when no
10659 nameservers are configured in /etc/resolv.conf; instead, make the
10660 user fix resolv.conf or specify nameservers explicitly. (Resolves
10662 - Stop accepting certain malformed ports in configured exit policies.
10663 - Don't re-write the fingerprint file every restart, unless it has
10665 - Stop warning when a single nameserver fails: only warn when _all_ of
10666 our nameservers have failed. Also, when we only have one nameserver,
10667 raise the threshold for deciding that the nameserver is dead.
10668 - Directory authorities now only decide that routers are reachable
10669 if their identity keys are as expected.
10670 - When the user uses bad syntax in the Log config line, stop
10671 suggesting other bad syntax as a replacement.
10672 - Correctly detect ipv6 DNS capability on OpenBSD.
10674 o Minor bugfixes (controller):
10675 - Report the circuit number correctly in STREAM CLOSED events. Bug
10676 reported by Mike Perry.
10677 - Do not report bizarre values for results of accounting GETINFOs
10678 when the last second's write or read exceeds the allotted bandwidth.
10679 - Report "unrecognized key" rather than an empty string when the
10680 controller tries to fetch a networkstatus that doesn't exist.
10683 Changes in version 0.1.1.26 - 2006-12-14
10684 o Security bugfixes:
10685 - Stop sending the HttpProxyAuthenticator string to directory
10686 servers when directory connections are tunnelled through Tor.
10687 - Clients no longer store bandwidth history in the state file.
10688 - Do not log introduction points for hidden services if SafeLogging
10692 - Fix an assert failure when a directory authority sets
10693 AuthDirRejectUnlisted and then receives a descriptor from an
10694 unlisted router (reported by seeess).
10697 Changes in version 0.1.2.4-alpha - 2006-12-03
10699 - Add support for using natd; this allows FreeBSDs earlier than
10700 5.1.2 to have ipfw send connections through Tor without using
10701 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
10704 - Make all connections to addresses of the form ".noconnect"
10705 immediately get closed. This lets application/controller combos
10706 successfully test whether they're talking to the same Tor by
10707 watching for STREAM events.
10708 - Make cross.sh cross-compilation script work even when autogen.sh
10709 hasn't been run. (Patch from Michael Mohr.)
10710 - Statistics dumped by -USR2 now include a breakdown of public key
10711 operations, for profiling.
10714 - Fix a major leak when directory authorities parse their
10715 approved-routers list, a minor memory leak when we fail to pick
10716 an exit node, and a few rare leaks on errors.
10717 - Handle TransPort connections even when the server sends data before
10718 the client sends data. Previously, the connection would just hang
10719 until the client sent data. (Patch from tup based on patch from
10721 - Avoid assert failure when our cached-routers file is empty on
10725 - Don't log spurious warnings when we see a circuit close reason we
10726 don't recognize; it's probably just from a newer version of Tor.
10727 - Have directory authorities allow larger amounts of drift in uptime
10728 without replacing the server descriptor: previously, a server that
10729 restarted every 30 minutes could have 48 "interesting" descriptors
10731 - Start linking to the Tor specification and Tor reference manual
10732 correctly in the Windows installer.
10733 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10734 Tor/Privoxy we also uninstall Vidalia.
10735 - Resume building on Irix64, and fix a lot of warnings from its
10736 MIPSpro C compiler.
10737 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
10738 when we're running as a client.
10741 Changes in version 0.1.1.25 - 2006-11-04
10743 - When a client asks us to resolve (rather than connect to)
10744 an address, and we have a cached answer, give them the cached
10745 answer. Previously, we would give them no answer at all.
10746 - We were building exactly the wrong circuits when we predict
10747 hidden service requirements, meaning Tor would have to build all
10748 its circuits on demand.
10749 - If none of our live entry guards have a high uptime, but we
10750 require a guard with a high uptime, try adding a new guard before
10751 we give up on the requirement. This patch should make long-lived
10752 connections more stable on average.
10753 - When testing reachability of our DirPort, don't launch new
10754 tests when there's already one in progress -- unreachable
10755 servers were stacking up dozens of testing streams.
10757 o Security bugfixes:
10758 - When the user sends a NEWNYM signal, clear the client-side DNS
10759 cache too. Otherwise we continue to act on previous information.
10762 - Avoid a memory corruption bug when creating a hash table for
10764 - Avoid possibility of controller-triggered crash when misusing
10765 certain commands from a v0 controller on platforms that do not
10766 handle printf("%s",NULL) gracefully.
10767 - Avoid infinite loop on unexpected controller input.
10768 - Don't log spurious warnings when we see a circuit close reason we
10769 don't recognize; it's probably just from a newer version of Tor.
10770 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10771 Tor/Privoxy we also uninstall Vidalia.
10774 Changes in version 0.1.2.3-alpha - 2006-10-29
10776 - Prepare for servers to publish descriptors less often: never
10777 discard a descriptor simply for being too old until either it is
10778 recommended by no authorities, or until we get a better one for
10779 the same router. Make caches consider retaining old recommended
10780 routers for even longer.
10781 - If most authorities set a BadExit flag for a server, clients
10782 don't think of it as a general-purpose exit. Clients only consider
10783 authorities that advertise themselves as listing bad exits.
10784 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
10785 headers for content, so that we can work better in the presence of
10786 caching HTTP proxies.
10787 - Allow authorities to list nodes as bad exits by fingerprint or by
10790 o Minor features, controller:
10791 - Add a REASON field to CIRC events; for backward compatibility, this
10792 field is sent only to controllers that have enabled the extended
10793 event format. Also, add additional reason codes to explain why
10794 a given circuit has been destroyed or truncated. (Patches from
10796 - Add a REMOTE_REASON field to extended CIRC events to tell the
10797 controller about why a remote OR told us to close a circuit.
10798 - Stream events also now have REASON and REMOTE_REASON fields,
10799 working much like those for circuit events.
10800 - There's now a GETINFO ns/... field so that controllers can ask Tor
10801 about the current status of a router.
10802 - A new event type "NS" to inform a controller when our opinion of
10803 a router's status has changed.
10804 - Add a GETINFO events/names and GETINFO features/names so controllers
10805 can tell which events and features are supported.
10806 - A new CLEARDNSCACHE signal to allow controllers to clear the
10807 client-side DNS cache without expiring circuits.
10809 o Security bugfixes:
10810 - When the user sends a NEWNYM signal, clear the client-side DNS
10811 cache too. Otherwise we continue to act on previous information.
10814 - Avoid sending junk to controllers or segfaulting when a controller
10815 uses EVENT_NEW_DESC with verbose nicknames.
10816 - Stop triggering asserts if the controller tries to extend hidden
10817 service circuits (reported by mwenge).
10818 - Avoid infinite loop on unexpected controller input.
10819 - When the controller does a "GETINFO network-status", tell it
10820 about even those routers whose descriptors are very old, and use
10821 long nicknames where appropriate.
10822 - Change NT service functions to be loaded on demand. This lets us
10823 build with MinGW without breaking Tor for Windows 98 users.
10824 - Do DirPort reachability tests less often, since a single test
10825 chews through many circuits before giving up.
10826 - In the hidden service example in torrc.sample, stop recommending
10827 esoteric and discouraged hidden service options.
10828 - When stopping an NT service, wait up to 10 sec for it to actually
10829 stop. Patch from Matt Edman; resolves bug 295.
10830 - Fix handling of verbose nicknames with ORCONN controller events:
10831 make them show up exactly when requested, rather than exactly when
10833 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
10834 printing a duplicate "$" in the keys we send (reported by mwenge).
10835 - Correctly set maximum connection limit on Cygwin. (This time
10837 - Try to detect Windows correctly when cross-compiling.
10838 - Detect the size of the routers file correctly even if it is
10839 corrupted (on systems without mmap) or not page-aligned (on systems
10840 with mmap). This bug was harmless.
10841 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
10842 to open a stream fails; now we do in more cases. This should
10843 make clients able to find a good exit faster in some cases, since
10844 unhandleable requests will now get an error rather than timing out.
10845 - Resolve two memory leaks when rebuilding the on-disk router cache
10846 (reported by fookoowa).
10847 - Clean up minor code warnings suggested by the MIPSpro C compiler,
10848 and reported by some Centos users.
10849 - Controller signals now work on non-Unix platforms that don't define
10850 SIGUSR1 and SIGUSR2 the way we expect.
10851 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10852 values before failing, and always enables eventdns.
10853 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10854 Try to fix this in configure.in by checking for most functions
10855 before we check for libevent.
10858 Changes in version 0.1.2.2-alpha - 2006-10-07
10860 - Make our async eventdns library on-by-default for Tor servers,
10861 and plan to deprecate the separate dnsworker threads.
10862 - Add server-side support for "reverse" DNS lookups (using PTR
10863 records so clients can determine the canonical hostname for a given
10864 IPv4 address). Only supported by servers using eventdns; servers
10865 now announce in their descriptors whether they support eventdns.
10866 - Specify and implement client-side SOCKS5 interface for reverse DNS
10867 lookups (see doc/socks-extensions.txt).
10868 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
10869 connect to directory servers through Tor. Previously, clients needed
10870 to find Tor exits to make private connections to directory servers.
10871 - Avoid choosing Exit nodes for entry or middle hops when the
10872 total bandwidth available from non-Exit nodes is much higher than
10873 the total bandwidth available from Exit nodes.
10874 - Workaround for name servers (like Earthlink's) that hijack failing
10875 DNS requests and replace the no-such-server answer with a "helpful"
10876 redirect to an advertising-driven search portal. Also work around
10877 DNS hijackers who "helpfully" decline to hijack known-invalid
10878 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
10879 lets you turn it off.
10880 - Send out a burst of long-range padding cells once we've established
10881 that we're reachable. Spread them over 4 circuits, so hopefully
10882 a few will be fast. This exercises our bandwidth and bootstraps
10883 us into the directory more quickly.
10885 o New/improved config options:
10886 - Add new config option "ResolvConf" to let the server operator
10887 choose an alternate resolve.conf file when using eventdns.
10888 - Add an "EnforceDistinctSubnets" option to control our "exclude
10889 servers on the same /16" behavior. It's still on by default; this
10890 is mostly for people who want to operate private test networks with
10891 all the machines on the same subnet.
10892 - If one of our entry guards is on the ExcludeNodes list, or the
10893 directory authorities don't think it's a good guard, treat it as
10894 if it were unlisted: stop using it as a guard, and throw it off
10895 the guards list if it stays that way for a long time.
10896 - Allow directory authorities to be marked separately as authorities
10897 for the v1 directory protocol, the v2 directory protocol, and
10898 as hidden service directories, to make it easier to retire old
10899 authorities. V1 authorities should set "HSAuthoritativeDir 1"
10900 to continue being hidden service authorities too.
10901 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
10903 o Minor features, controller:
10904 - Fix CIRC controller events so that controllers can learn the
10905 identity digests of non-Named servers used in circuit paths.
10906 - Let controllers ask for more useful identifiers for servers. Instead
10907 of learning identity digests for un-Named servers and nicknames
10908 for Named servers, the new identifiers include digest, nickname,
10909 and indication of Named status. Off by default; see control-spec.txt
10910 for more information.
10911 - Add a "getinfo address" controller command so it can display Tor's
10912 best guess to the user.
10913 - New controller event to alert the controller when our server
10914 descriptor has changed.
10915 - Give more meaningful errors on controller authentication failure.
10917 o Minor features, other:
10918 - When asked to resolve a hostname, don't use non-exit servers unless
10919 requested to do so. This allows servers with broken DNS to be
10920 useful to the network.
10921 - Divide eventdns log messages into warn and info messages.
10922 - Reserve the nickname "Unnamed" for routers that can't pick
10923 a hostname: any router can call itself Unnamed; directory
10924 authorities will never allocate Unnamed to any particular router;
10925 clients won't believe that any router is the canonical Unnamed.
10926 - Only include function names in log messages for info/debug messages.
10927 For notice/warn/err, the content of the message should be clear on
10928 its own, and printing the function name only confuses users.
10929 - Avoid some false positives during reachability testing: don't try
10930 to test via a server that's on the same /24 as us.
10931 - If we fail to build a circuit to an intended enclave, and it's
10932 not mandatory that we use that enclave, stop wanting it.
10933 - When eventdns is enabled, allow multithreaded builds on NetBSD and
10934 OpenBSD. (We had previously disabled threads on these platforms
10935 because they didn't have working thread-safe resolver functions.)
10937 o Major bugfixes, anonymity/security:
10938 - If a client asked for a server by name, and there's a named server
10939 in our network-status but we don't have its descriptor yet, we
10940 could return an unnamed server instead.
10941 - Fix NetBSD bug that could allow someone to force uninitialized RAM
10942 to be sent to a server's DNS resolver. This only affects NetBSD
10943 and other platforms that do not bounds-check tolower().
10944 - Reject (most) attempts to use Tor circuits with length one. (If
10945 many people start using Tor as a one-hop proxy, exit nodes become
10946 a more attractive target for compromise.)
10947 - Just because your DirPort is open doesn't mean people should be
10948 able to remotely teach you about hidden service descriptors. Now
10949 only accept rendezvous posts if you've got HSAuthoritativeDir set.
10951 o Major bugfixes, other:
10952 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10953 - When a client asks the server to resolve (not connect to)
10954 an address, and it has a cached answer, give them the cached answer.
10955 Previously, the server would give them no answer at all.
10956 - Allow really slow clients to not hang up five minutes into their
10957 directory downloads (suggested by Adam J. Richter).
10958 - We were building exactly the wrong circuits when we anticipated
10959 hidden service requirements, meaning Tor would have to build all
10960 its circuits on demand.
10961 - Avoid crashing when we mmap a router cache file of size 0.
10962 - When testing reachability of our DirPort, don't launch new
10963 tests when there's already one in progress -- unreachable
10964 servers were stacking up dozens of testing streams.
10966 o Minor bugfixes, correctness:
10967 - If we're a directory mirror and we ask for "all" network status
10968 documents, we would discard status documents from authorities
10969 we don't recognize.
10970 - Avoid a memory corruption bug when creating a hash table for
10972 - Avoid controller-triggered crash when misusing certain commands
10973 from a v0 controller on platforms that do not handle
10974 printf("%s",NULL) gracefully.
10975 - Don't crash when a controller sends a third argument to an
10976 "extendcircuit" request.
10977 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10978 response; fix error code when "getinfo dir/status/" fails.
10979 - Avoid crash when telling controller stream-status and a stream
10981 - Patch from Adam Langley to fix assert() in eventdns.c.
10982 - Fix a debug log message in eventdns to say "X resolved to Y"
10983 instead of "X resolved to X".
10984 - Make eventdns give strings for DNS errors, not just error numbers.
10985 - Track unreachable entry guards correctly: don't conflate
10986 'unreachable by us right now' with 'listed as down by the directory
10987 authorities'. With the old code, if a guard was unreachable by
10988 us but listed as running, it would clog our guard list forever.
10989 - Behave correctly in case we ever have a network with more than
10990 2GB/s total advertised capacity.
10991 - Make TrackExitHosts case-insensitive, and fix the behavior of
10992 ".suffix" TrackExitHosts items to avoid matching in the middle of
10994 - Finally fix the openssl warnings from newer gccs that believe that
10995 ignoring a return value is okay, but casting a return value and
10996 then ignoring it is a sign of madness.
10997 - Prevent the contrib/exitlist script from printing the same
10998 result more than once.
10999 - Patch from Steve Hildrey: Generate network status correctly on
11000 non-versioning dirservers.
11001 - Don't listen to the X-Your-Address-Is hint if you did the lookup
11002 via Tor; otherwise you'll think you're the exit node's IP address.
11004 o Minor bugfixes, performance:
11005 - Two small performance improvements on parsing descriptors.
11006 - Major performance improvement on inserting descriptors: change
11007 algorithm from O(n^2) to O(n).
11008 - Make the common memory allocation path faster on machines where
11009 malloc(0) returns a pointer.
11010 - Start remembering X-Your-Address-Is directory hints even if you're
11011 a client, so you can become a server more smoothly.
11012 - Avoid duplicate entries on MyFamily line in server descriptor.
11014 o Packaging, features:
11015 - Remove architecture from OS X builds. The official builds are
11016 now universal binaries.
11017 - The Debian package now uses --verify-config when (re)starting,
11018 to distinguish configuration errors from other errors.
11019 - Update RPMs to require libevent 1.1b.
11021 o Packaging, bugfixes:
11022 - Patches so Tor builds with MinGW on Windows.
11023 - Patches so Tor might run on Cygwin again.
11024 - Resume building on non-gcc compilers and ancient gcc. Resume
11025 building with the -O0 compile flag. Resume building cleanly on
11027 - Run correctly on OS X platforms with case-sensitive filesystems.
11028 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
11029 - Add autoconf checks so Tor can build on Solaris x86 again.
11032 - Documented (and renamed) ServerDNSSearchDomains and
11033 ServerDNSResolvConfFile options.
11034 - Be clearer that the *ListenAddress directives can be repeated
11038 Changes in version 0.1.1.24 - 2006-09-29
11040 - Allow really slow clients to not hang up five minutes into their
11041 directory downloads (suggested by Adam J. Richter).
11042 - Fix major performance regression from 0.1.0.x: instead of checking
11043 whether we have enough directory information every time we want to
11044 do something, only check when the directory information has changed.
11045 This should improve client CPU usage by 25-50%.
11046 - Don't crash if, after a server has been running for a while,
11047 it can't resolve its hostname.
11050 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11051 - Don't crash when the controller receives a third argument to an
11052 "extendcircuit" request.
11053 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11054 response; fix error code when "getinfo dir/status/" fails.
11055 - Fix configure.in to not produce broken configure files with
11056 more recent versions of autoconf. Thanks to Clint for his auto*
11058 - Fix security bug on NetBSD that could allow someone to force
11059 uninitialized RAM to be sent to a server's DNS resolver. This
11060 only affects NetBSD and other platforms that do not bounds-check
11062 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
11063 methods: these are known to be buggy.
11064 - If we're a directory mirror and we ask for "all" network status
11065 documents, we would discard status documents from authorities
11066 we don't recognize.
11069 Changes in version 0.1.2.1-alpha - 2006-08-27
11071 - Add "eventdns" async dns library from Adam Langley, tweaked to
11072 build on OSX and Windows. Only enabled if you pass the
11073 --enable-eventdns argument to configure.
11074 - Allow servers with no hostname or IP address to learn their
11075 IP address by asking the directory authorities. This code only
11076 kicks in when you would normally have exited with a "no address"
11077 error. Nothing's authenticated, so use with care.
11078 - Rather than waiting a fixed amount of time between retrying
11079 application connections, we wait only 5 seconds for the first,
11080 10 seconds for the second, and 15 seconds for each retry after
11081 that. Hopefully this will improve the expected user experience.
11082 - Patch from Tup to add support for transparent AP connections:
11083 this basically bundles the functionality of trans-proxy-tor
11084 into the Tor mainline. Now hosts with compliant pf/netfilter
11085 implementations can redirect TCP connections straight to Tor
11086 without diverting through SOCKS. Needs docs.
11087 - Busy directory servers save lots of memory by spooling server
11088 descriptors, v1 directories, and v2 networkstatus docs to buffers
11089 as needed rather than en masse. Also mmap the cached-routers
11090 files, so we don't need to keep the whole thing in memory too.
11091 - Automatically avoid picking more than one node from the same
11092 /16 network when constructing a circuit.
11093 - Revise and clean up the torrc.sample that we ship with; add
11094 a section for BandwidthRate and BandwidthBurst.
11097 - Split circuit_t into origin_circuit_t and or_circuit_t, and
11098 split connection_t into edge, or, dir, control, and base structs.
11099 These will save quite a bit of memory on busy servers, and they'll
11100 also help us track down bugs in the code and bugs in the spec.
11101 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
11102 or later. Log when we are doing this, so we can diagnose it when
11103 it fails. (Also, recommend libevent 1.1b for kqueue and
11104 win32 methods; deprecate libevent 1.0b harder; make libevent
11105 recommendation system saner.)
11106 - Start being able to build universal binaries on OS X (thanks
11108 - Export the default exit policy via the control port, so controllers
11109 don't need to guess what it is / will be later.
11110 - Add a man page entry for ProtocolWarnings.
11111 - Add TestVia config option to the man page.
11112 - Remove even more protocol-related warnings from Tor server logs,
11113 such as bad TLS handshakes and malformed begin cells.
11114 - Stop fetching descriptors if you're not a dir mirror and you
11115 haven't tried to establish any circuits lately. [This currently
11116 causes some dangerous behavior, because when you start up again
11117 you'll use your ancient server descriptors.]
11118 - New DirPort behavior: if you have your dirport set, you download
11119 descriptors aggressively like a directory mirror, whether or not
11120 your ORPort is set.
11121 - Get rid of the router_retry_connections notion. Now routers
11122 no longer try to rebuild long-term connections to directory
11123 authorities, and directory authorities no longer try to rebuild
11124 long-term connections to all servers. We still don't hang up
11125 connections in these two cases though -- we need to look at it
11126 more carefully to avoid flapping, and we likely need to wait til
11127 0.1.1.x is obsolete.
11128 - Drop compatibility with obsolete Tors that permit create cells
11129 to have the wrong circ_id_type.
11130 - Re-enable per-connection rate limiting. Get rid of the "OP
11131 bandwidth" concept. Lay groundwork for "bandwidth classes" --
11132 separate global buckets that apply depending on what sort of conn
11134 - Start publishing one minute or so after we find our ORPort
11135 to be reachable. This will help reduce the number of descriptors
11136 we have for ourselves floating around, since it's quite likely
11137 other things (e.g. DirPort) will change during that minute too.
11138 - Fork the v1 directory protocol into its own spec document,
11139 and mark dir-spec.txt as the currently correct (v2) spec.
11142 - When we find our DirPort to be reachable, publish a new descriptor
11143 so we'll tell the world (reported by pnx).
11144 - Publish a new descriptor after we hup/reload. This is important
11145 if our config has changed such that we'll want to start advertising
11146 our DirPort now, etc.
11147 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11148 - When we have a state file we cannot parse, tell the user and
11149 move it aside. Now we avoid situations where the user starts
11150 Tor in 1904, Tor writes a state file with that timestamp in it,
11151 the user fixes her clock, and Tor refuses to start.
11152 - Fix configure.in to not produce broken configure files with
11153 more recent versions of autoconf. Thanks to Clint for his auto*
11155 - "tor --verify-config" now exits with -1(255) or 0 depending on
11156 whether the config options are bad or good.
11157 - Resolve bug 321 when using dnsworkers: append a period to every
11158 address we resolve at the exit node, so that we do not accidentally
11159 pick up local addresses, and so that failing searches are retried
11160 in the resolver search domains. (This is already solved for
11161 eventdns.) (This breaks Blossom servers for now.)
11162 - If we are using an exit enclave and we can't connect, e.g. because
11163 its webserver is misconfigured to not listen on localhost, then
11164 back off and try connecting from somewhere else before we fail.
11167 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
11168 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
11169 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
11170 when the IP address is mapped through MapAddress to a hostname.
11171 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
11172 useless IPv6 DNS resolves.
11173 - Patch suggested by Karsten Loesing: respond to SIGNAL command
11174 before we execute the signal, in case the signal shuts us down.
11175 - Clean up AllowInvalidNodes man page entry.
11176 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
11177 - Add more asserts to track down an assert error on a windows Tor
11178 server with connection_add being called with socket == -1.
11179 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
11180 - Fix misleading log messages: an entry guard that is "unlisted",
11181 as well as not known to be "down" (because we've never heard
11182 of it), is not therefore "up".
11183 - Remove code to special-case "-cvs" ending, since it has not
11184 actually mattered since 0.0.9.
11185 - Make our socks5 handling more robust to broken socks clients:
11186 throw out everything waiting on the buffer in between socks
11187 handshake phases, since they can't possibly (so the theory
11188 goes) have predicted what we plan to respond to them.
11191 Changes in version 0.1.1.23 - 2006-07-30
11193 - Fast Tor servers, especially exit nodes, were triggering asserts
11194 due to a bug in handling the list of pending DNS resolves. Some
11195 bugs still remain here; we're hunting them.
11196 - Entry guards could crash clients by sending unexpected input.
11197 - More fixes on reachability testing: if you find yourself reachable,
11198 then don't ever make any client requests (so you stop predicting
11199 circuits), then hup or have your clock jump, then later your IP
11200 changes, you won't think circuits are working, so you won't try to
11201 test reachability, so you won't publish.
11204 - Avoid a crash if the controller does a resetconf firewallports
11205 and then a setconf fascistfirewall=1.
11206 - Avoid an integer underflow when the dir authority decides whether
11207 a router is stable: we might wrongly label it stable, and compute
11208 a slightly wrong median stability, when a descriptor is published
11210 - Fix a place where we might trigger an assert if we can't build our
11211 own server descriptor yet.
11214 Changes in version 0.1.1.22 - 2006-07-05
11216 - Fix a big bug that was causing servers to not find themselves
11217 reachable if they changed IP addresses. Since only 0.1.1.22+
11218 servers can do reachability testing correctly, now we automatically
11219 make sure to test via one of these.
11220 - Fix to allow clients and mirrors to learn directory info from
11221 descriptor downloads that get cut off partway through.
11222 - Directory authorities had a bug in deciding if a newly published
11223 descriptor was novel enough to make everybody want a copy -- a few
11224 servers seem to be publishing new descriptors many times a minute.
11226 - Fix a rare bug that was causing some servers to complain about
11227 "closing wedged cpuworkers" and skip some circuit create requests.
11228 - Make the Exit flag in directory status documents actually work.
11231 Changes in version 0.1.1.21 - 2006-06-10
11232 o Crash and assert fixes from 0.1.1.20:
11233 - Fix a rare crash on Tor servers that have enabled hibernation.
11234 - Fix a seg fault on startup for Tor networks that use only one
11235 directory authority.
11236 - Fix an assert from a race condition that occurs on Tor servers
11237 while exiting, where various threads are trying to log that they're
11238 exiting, and delete the logs, at the same time.
11239 - Make our unit tests pass again on certain obscure platforms.
11242 - Add support for building SUSE RPM packages.
11243 - Speed up initial bootstrapping for clients: if we are making our
11244 first ever connection to any entry guard, then don't mark it down
11246 - When only one Tor server in the network is labelled as a guard,
11247 and we've already picked him, we would cycle endlessly picking him
11248 again, being unhappy about it, etc. Now we specifically exclude
11249 current guards when picking a new guard.
11250 - Servers send create cells more reliably after the TLS connection
11251 is established: we were sometimes forgetting to send half of them
11252 when we had more than one pending.
11253 - If we get a create cell that asks us to extend somewhere, but the
11254 Tor server there doesn't match the expected digest, we now send
11255 a destroy cell back, rather than silently doing nothing.
11256 - Make options->RedirectExit work again.
11257 - Make cookie authentication for the controller work again.
11258 - Stop being picky about unusual characters in the arguments to
11259 mapaddress. It's none of our business.
11260 - Add a new config option "TestVia" that lets you specify preferred
11261 middle hops to use for test circuits. Perhaps this will let me
11262 debug the reachability problems better.
11264 o Log / documentation fixes:
11265 - If we're a server and some peer has a broken TLS certificate, don't
11266 log about it unless ProtocolWarnings is set, i.e., we want to hear
11267 about protocol violations by others.
11268 - Fix spelling of VirtualAddrNetwork in man page.
11269 - Add a better explanation at the top of the autogenerated torrc file
11270 about what happened to our old torrc.
11273 Changes in version 0.1.1.20 - 2006-05-23
11275 - Downgrade a log severity where servers complain that they're
11277 - Avoid a compile warning on FreeBSD.
11278 - Remove string size limit on NEWDESC messages; solve bug 291.
11279 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
11280 more thoroughly when we're running on windows.
11283 Changes in version 0.1.1.19-rc - 2006-05-03
11285 - Regenerate our local descriptor if it's dirty and we try to use
11286 it locally (e.g. if it changes during reachability detection).
11287 - If we setconf our ORPort to 0, we continued to listen on the
11288 old ORPort and receive connections.
11289 - Avoid a second warning about machine/limits.h on Debian
11291 - Be willing to add our own routerinfo into the routerlist.
11292 Now authorities will include themselves in their directories
11293 and network-statuses.
11294 - Stop trying to upload rendezvous descriptors to every
11295 directory authority: only try the v1 authorities.
11296 - Servers no longer complain when they think they're not
11297 registered with the directory authorities. There were too many
11299 - Backport dist-rpm changes so rpms can be built without errors.
11302 - Implement an option, VirtualAddrMask, to set which addresses
11303 get handed out in response to mapaddress requests. This works
11304 around a bug in tsocks where 127.0.0.0/8 is never socksified.
11307 Changes in version 0.1.1.18-rc - 2006-04-10
11309 - Work harder to download live network-statuses from all the
11310 directory authorities we know about. Improve the threshold
11311 decision logic so we're more robust to edge cases.
11312 - When fetching rendezvous descriptors, we were willing to ask
11313 v2 authorities too, which would always return 404.
11316 - Stop listing down or invalid nodes in the v1 directory. This will
11317 reduce its bulk by about 1/3, and reduce load on directory
11319 - When deciding whether a router is Fast or Guard-worthy, consider
11320 his advertised BandwidthRate and not just the BandwidthCapacity.
11321 - No longer ship INSTALL and README files -- they are useless now.
11322 - Force rpmbuild to behave and honor target_cpu.
11323 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
11324 - Start to include translated versions of the tor-doc-*.html
11325 files, along with the screenshots. Still needs more work.
11326 - Start sending back 512 and 451 errors if mapaddress fails,
11327 rather than not sending anything back at all.
11328 - When we fail to bind or listen on an incoming or outgoing
11329 socket, we should close it before failing. otherwise we just
11330 leak it. (thanks to weasel for finding.)
11331 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
11332 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
11333 - Make NoPublish (even though deprecated) work again.
11334 - Fix a minor security flaw where a versioning auth dirserver
11335 could list a recommended version many times in a row to make
11336 clients more convinced that it's recommended.
11337 - Fix crash bug if there are two unregistered servers running
11338 with the same nickname, one of them is down, and you ask for
11339 them by nickname in your EntryNodes or ExitNodes. Also, try
11340 to pick the one that's running rather than an arbitrary one.
11341 - Fix an infinite loop we could hit if we go offline for too long.
11342 - Complain when we hit WSAENOBUFS on recv() or write() too.
11343 Perhaps this will help us hunt the bug.
11344 - If you're not a versioning dirserver, don't put the string
11345 "client-versions \nserver-versions \n" in your network-status.
11346 - Lower the minimum required number of file descriptors to 1000,
11347 so we can have some overhead for Valgrind on Linux, where the
11348 default ulimit -n is 1024.
11351 - Add tor.dizum.com as the fifth authoritative directory server.
11352 - Add a new config option FetchUselessDescriptors, off by default,
11353 for when you plan to run "exitlist" on your client and you want
11354 to know about even the non-running descriptors.
11357 Changes in version 0.1.1.17-rc - 2006-03-28
11359 - Clients and servers since 0.1.1.10-alpha have been expiring
11360 connections whenever they are idle for 5 minutes and they *do*
11361 have circuits on them. Oops. With this new version, clients will
11362 discard their previous entry guard choices and avoid choosing
11363 entry guards running these flawed versions.
11364 - Fix memory leak when uncompressing concatenated zlib streams. This
11365 was causing substantial leaks over time on Tor servers.
11366 - The v1 directory was including servers as much as 48 hours old,
11367 because that's how the new routerlist->routers works. Now only
11368 include them if they're 20 hours old or less.
11371 - Resume building on irix64, netbsd 2.0, etc.
11372 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
11374 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
11375 and it is confusing some users.
11376 - Mirrors stop caching the v1 directory so often.
11377 - Make the max number of old descriptors that a cache will hold
11378 rise with the number of directory authorities, so we can scale.
11379 - Change our win32 uname() hack to be more forgiving about what
11380 win32 versions it thinks it's found.
11383 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
11385 - When the controller's *setconf commands fail, collect an error
11386 message in a string and hand it back to the controller.
11387 - Make the v2 dir's "Fast" flag based on relative capacity, just
11388 like "Stable" is based on median uptime. Name everything in the
11389 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
11390 - Log server fingerprint on startup, so new server operators don't
11391 have to go hunting around their filesystem for it.
11392 - Return a robots.txt on our dirport to discourage google indexing.
11393 - Let the controller ask for GETINFO dir/status/foo so it can ask
11394 directly rather than connecting to the dir port. Only works when
11395 dirport is set for now.
11397 o New config options rather than constants in the code:
11398 - SocksTimeout: How long do we let a socks connection wait
11399 unattached before we fail it?
11400 - CircuitBuildTimeout: Cull non-open circuits that were born
11401 at least this many seconds ago.
11402 - CircuitIdleTimeout: Cull open clean circuits that were born
11403 at least this many seconds ago.
11406 Changes in version 0.1.1.16-rc - 2006-03-18
11407 o Bugfixes on 0.1.1.15-rc:
11408 - Fix assert when the controller asks to attachstream a connect-wait
11409 or resolve-wait stream.
11410 - Now do address rewriting when the controller asks us to attach
11411 to a particular circuit too. This will let Blossom specify
11412 "moria2.exit" without having to learn what moria2's IP address is.
11413 - Make the "tor --verify-config" command-line work again, so people
11414 can automatically check if their torrc will parse.
11415 - Authoritative dirservers no longer require an open connection from
11416 a server to consider him "reachable". We need this change because
11417 when we add new auth dirservers, old servers won't know not to
11419 - Let Tor build on Sun CC again.
11420 - Fix an off-by-one buffer size in dirserv.c that magically never
11421 hit our three authorities but broke sjmurdoch's own tor network.
11422 - If we as a directory mirror don't know of any v1 directory
11423 authorities, then don't try to cache any v1 directories.
11424 - Stop warning about unknown servers in our family when they are
11425 given as hex digests.
11426 - Stop complaining as quickly to the server operator that he
11427 hasn't registered his nickname/key binding.
11428 - Various cleanups so we can add new V2 Auth Dirservers.
11429 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
11430 reflect the updated flags in our v2 dir protocol.
11431 - Resume allowing non-printable characters for exit streams (both
11432 for connecting and for resolving). Now we tolerate applications
11433 that don't follow the RFCs. But continue to block malformed names
11436 o Bugfixes on 0.1.0.x:
11437 - Fix assert bug in close_logs(): when we close and delete logs,
11438 remove them all from the global "logfiles" list.
11439 - Fix minor integer overflow in calculating when we expect to use up
11440 our bandwidth allocation before hibernating.
11441 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
11442 there are multiple SSLs installed with different versions.
11443 - When we try to be a server and Address is not explicitly set and
11444 our hostname resolves to a private IP address, try to use an
11445 interface address if it has a public address. Now Windows machines
11446 that think of themselves as localhost can work by default.
11449 - Let the controller ask for GETINFO dir/server/foo so it can ask
11450 directly rather than connecting to the dir port.
11451 - Let the controller tell us about certain router descriptors
11452 that it doesn't want Tor to use in circuits. Implement
11453 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
11454 - New config option SafeSocks to reject all application connections
11455 using unsafe socks protocols. Defaults to off.
11458 Changes in version 0.1.1.15-rc - 2006-03-11
11459 o Bugfixes and cleanups:
11460 - When we're printing strings from the network, don't try to print
11461 non-printable characters. This protects us against shell escape
11462 sequence exploits, and also against attacks to fool humans into
11463 misreading their logs.
11464 - Fix a bug where Tor would fail to establish any connections if you
11465 left it off for 24 hours and then started it: we were happy with
11466 the obsolete network statuses, but they all referred to router
11467 descriptors that were too old to fetch, so we ended up with no
11468 valid router descriptors.
11469 - Fix a seg fault in the controller's "getinfo orconn-status"
11470 command while listing status on incoming handshaking connections.
11471 Introduce a status name "NEW" for these connections.
11472 - If we get a linelist or linelist_s config option from the torrc
11473 (e.g. ExitPolicy) and it has no value, warn and skip rather than
11474 silently resetting it to its default.
11475 - Don't abandon entry guards until they've been down or gone for
11477 - Cleaner and quieter log messages.
11480 - New controller signal NEWNYM that makes new application requests
11481 use clean circuits.
11482 - Add a new circuit purpose 'controller' to let the controller ask
11483 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
11484 controller command to let you specify the purpose if you're
11485 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
11486 command to let you change a circuit's purpose after it's been
11488 - Accept "private:*" in routerdesc exit policies; not generated yet
11489 because older Tors do not understand it.
11490 - Add BSD-style contributed startup script "rc.subr" from Peter
11494 Changes in version 0.1.1.14-alpha - 2006-02-20
11495 o Bugfixes on 0.1.1.x:
11496 - Don't die if we ask for a stdout or stderr log (even implicitly)
11497 and we're set to RunAsDaemon -- just warn.
11498 - We still had a few bugs in the OR connection rotation code that
11499 caused directory servers to slowly aggregate connections to other
11500 fast Tor servers. This time for sure!
11501 - Make log entries on Win32 include the name of the function again.
11502 - We were treating a pair of exit policies if they were equal even
11503 if one said accept and the other said reject -- causing us to
11504 not always publish a new descriptor since we thought nothing
11506 - Retry pending server downloads as well as pending networkstatus
11507 downloads when we unexpectedly get a socks request.
11508 - We were ignoring the IS_FAST flag in the directory status,
11509 meaning we were willing to pick trivial-bandwidth nodes for "fast"
11511 - If the controller's SAVECONF command fails (e.g. due to file
11512 permissions), let the controller know that it failed.
11515 - If we're trying to be a Tor server and running Windows 95/98/ME
11516 as a server, explain that we'll likely crash.
11517 - When we're a server, a client asks for an old-style directory,
11518 and our write bucket is empty, don't give it to him. This way
11519 small servers can continue to serve the directory *sometimes*,
11520 without getting overloaded.
11521 - Compress exit policies even more -- look for duplicate lines
11523 - Clients now honor the "guard" flag in the router status when
11524 picking entry guards, rather than looking at is_fast or is_stable.
11525 - Retain unrecognized lines in $DATADIR/state file, so that we can
11526 be forward-compatible.
11527 - Generate 18.0.0.0/8 address policy format in descs when we can;
11528 warn when the mask is not reducible to a bit-prefix.
11529 - Let the user set ControlListenAddress in the torrc. This can be
11530 dangerous, but there are some cases (like a secured LAN) where it
11532 - Split ReachableAddresses into ReachableDirAddresses and
11533 ReachableORAddresses, so we can restrict Dir conns to port 80
11534 and OR conns to port 443.
11535 - Now we can target arch and OS in rpm builds (contributed by
11536 Phobos). Also make the resulting dist-rpm filename match the
11538 - New config options to help controllers: FetchServerDescriptors
11539 and FetchHidServDescriptors for whether to fetch server
11540 info and hidserv info or let the controller do it, and
11541 PublishServerDescriptor and PublishHidServDescriptors.
11542 - Also let the controller set the __AllDirActionsPrivate config
11543 option if you want all directory fetches/publishes to happen via
11544 Tor (it assumes your controller bootstraps your circuits).
11547 Changes in version 0.1.0.17 - 2006-02-17
11548 o Crash bugfixes on 0.1.0.x:
11549 - When servers with a non-zero DirPort came out of hibernation,
11550 sometimes they would trigger an assert.
11552 o Other important bugfixes:
11553 - On platforms that don't have getrlimit (like Windows), we were
11554 artificially constraining ourselves to a max of 1024
11555 connections. Now just assume that we can handle as many as 15000
11556 connections. Hopefully this won't cause other problems.
11558 o Backported features:
11559 - When we're a server, a client asks for an old-style directory,
11560 and our write bucket is empty, don't give it to him. This way
11561 small servers can continue to serve the directory *sometimes*,
11562 without getting overloaded.
11563 - Whenever you get a 503 in response to a directory fetch, try
11564 once more. This will become important once servers start sending
11565 503's whenever they feel busy.
11566 - Fetch a new directory every 120 minutes, not every 40 minutes.
11567 Now that we have hundreds of thousands of users running the old
11568 directory algorithm, it's starting to hurt a lot.
11569 - Bump up the period for forcing a hidden service descriptor upload
11570 from 20 minutes to 1 hour.
11573 Changes in version 0.1.1.13-alpha - 2006-02-09
11574 o Crashes in 0.1.1.x:
11575 - When you tried to setconf ORPort via the controller, Tor would
11576 crash. So people using TorCP to become a server were sad.
11577 - Solve (I hope) the stack-smashing bug that we were seeing on fast
11578 servers. The problem appears to be something do with OpenSSL's
11579 random number generation, or how we call it, or something. Let me
11580 know if the crashes continue.
11581 - Turn crypto hardware acceleration off by default, until we find
11582 somebody smart who can test it for us. (It appears to produce
11583 seg faults in at least some cases.)
11584 - Fix a rare assert error when we've tried all intro points for
11585 a hidden service and we try fetching the service descriptor again:
11586 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
11589 - Fix a major load balance bug: we were round-robining in 16 KB
11590 chunks, and servers with bandwidthrate of 20 KB, while downloading
11591 a 600 KB directory, would starve their other connections. Now we
11592 try to be a bit more fair.
11593 - Dir authorities and mirrors were never expiring the newest
11594 descriptor for each server, causing memory and directory bloat.
11595 - Fix memory-bloating and connection-bloating bug on servers: We
11596 were never closing any connection that had ever had a circuit on
11597 it, because we were checking conn->n_circuits == 0, yet we had a
11598 bug that let it go negative.
11599 - Make Tor work using squid as your http proxy again -- squid
11600 returns an error if you ask for a URL that's too long, and it uses
11601 a really generic error message. Plus, many people are behind a
11602 transparent squid so they don't even realize it.
11603 - On platforms that don't have getrlimit (like Windows), we were
11604 artificially constraining ourselves to a max of 1024
11605 connections. Now just assume that we can handle as many as 15000
11606 connections. Hopefully this won't cause other problems.
11607 - Add a new config option ExitPolicyRejectPrivate which defaults to
11608 1. This means all exit policies will begin with rejecting private
11609 addresses, unless the server operator explicitly turns it off.
11612 - Clients no longer download descriptors for non-running
11614 - Before we add new directory authorities, we should make it
11615 clear that only v1 authorities should receive/publish hidden
11616 service descriptors.
11619 - As soon as we've fetched some more directory info, immediately
11620 try to download more server descriptors. This way we don't have
11621 a 10 second pause during initial bootstrapping.
11622 - Remove even more loud log messages that the server operator can't
11624 - When we're running an obsolete or un-recommended version, make
11625 the log message more clear about what the problem is and what
11626 versions *are* still recommended.
11627 - Provide a more useful warn message when our onion queue gets full:
11628 the CPU is too slow or the exit policy is too liberal.
11629 - Don't warn when we receive a 503 from a dirserver/cache -- this
11630 will pave the way for them being able to refuse if they're busy.
11631 - When we fail to bind a listener, try to provide a more useful
11632 log message: e.g., "Is Tor already running?"
11633 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
11634 Goldberg can prove things about our handshake protocol more
11636 - MaxConn has been obsolete for a while now. Document the ConnLimit
11637 config option, which is a *minimum* number of file descriptors
11638 that must be available else Tor refuses to start.
11639 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
11640 if you log to syslog and want something other than LOG_DAEMON.
11641 - Make dirservers generate a separate "guard" flag to mean,
11642 "would make a good entry guard". Make clients parse it and vote
11643 on it. Not used by clients yet.
11644 - Implement --with-libevent-dir option to ./configure. Also, improve
11645 search techniques to find libevent, and use those for openssl too.
11646 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
11647 - Only start testing reachability once we've established a
11648 circuit. This will make startup on dirservers less noisy.
11649 - Don't try to upload hidden service descriptors until we have
11650 established a circuit.
11651 - Fix the controller's "attachstream 0" command to treat conn like
11652 it just connected, doing address remapping, handling .exit and
11653 .onion idioms, and so on. Now we're more uniform in making sure
11654 that the controller hears about new and closing connections.
11657 Changes in version 0.1.1.12-alpha - 2006-01-11
11658 o Bugfixes on 0.1.1.x:
11659 - The fix to close duplicate server connections was closing all
11660 Tor client connections if they didn't establish a circuit
11661 quickly enough. Oops.
11662 - Fix minor memory issue (double-free) that happened on exit.
11664 o Bugfixes on 0.1.0.x:
11665 - Tor didn't warn when it failed to open a log file.
11668 Changes in version 0.1.1.11-alpha - 2006-01-10
11669 o Crashes in 0.1.1.x:
11670 - Include all the assert/crash fixes from 0.1.0.16.
11671 - If you start Tor and then quit very quickly, there were some
11672 races that tried to free things that weren't allocated yet.
11673 - Fix a rare memory stomp if you're running hidden services.
11674 - Fix segfault when specifying DirServer in config without nickname.
11675 - Fix a seg fault when you finish connecting to a server but at
11676 that moment you dump his server descriptor.
11677 - Extendcircuit and Attachstream controller commands would
11678 assert/crash if you don't give them enough arguments.
11679 - Fix an assert error when we're out of space in the connection_list
11680 and we try to post a hidden service descriptor (reported by weasel).
11681 - If you specify a relative torrc path and you set RunAsDaemon in
11682 your torrc, then it chdir()'s to the new directory. If you HUP,
11683 it tries to load the new torrc location, fails, and exits.
11684 The fix: no longer allow a relative path to torrc using -f.
11687 - Implement "entry guards": automatically choose a handful of entry
11688 nodes and stick with them for all circuits. Only pick new guards
11689 when the ones you have are unsuitable, and if the old guards
11690 become suitable again, switch back. This will increase security
11691 dramatically against certain end-point attacks. The EntryNodes
11692 config option now provides some hints about which entry guards you
11693 want to use most; and StrictEntryNodes means to only use those.
11694 - New directory logic: download by descriptor digest, not by
11695 fingerprint. Caches try to download all listed digests from
11696 authorities; clients try to download "best" digests from caches.
11697 This avoids partitioning and isolating attacks better.
11698 - Make the "stable" router flag in network-status be the median of
11699 the uptimes of running valid servers, and make clients pay
11700 attention to the network-status flags. Thus the cutoff adapts
11701 to the stability of the network as a whole, making IRC, IM, etc
11702 connections more reliable.
11705 - Tor servers with dynamic IP addresses were needing to wait 18
11706 hours before they could start doing reachability testing using
11707 the new IP address and ports. This is because they were using
11708 the internal descriptor to learn what to test, yet they were only
11709 rebuilding the descriptor once they decided they were reachable.
11710 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
11711 to download certain server descriptors, throw them away, and then
11712 fetch them again after 30 minutes. Now mirrors throw away these
11713 server descriptors so clients can't get them.
11714 - We were leaving duplicate connections to other ORs open for a week,
11715 rather than closing them once we detect a duplicate. This only
11716 really affected authdirservers, but it affected them a lot.
11717 - Spread the authdirservers' reachability testing over the entire
11718 testing interval, so we don't try to do 500 TLS's at once every
11722 - If the network is down, and we try to connect to a conn because
11723 we have a circuit in mind, and we timeout (30 seconds) because the
11724 network never answers, we were expiring the circuit, but we weren't
11725 obsoleting the connection or telling the entry_guards functions.
11726 - Some Tor servers process billions of cells per day. These statistics
11727 need to be uint64_t's.
11728 - Check for integer overflows in more places, when adding elements
11729 to smartlists. This could possibly prevent a buffer overflow
11730 on malicious huge inputs. I don't see any, but I haven't looked
11732 - ReachableAddresses kept growing new "reject *:*" lines on every
11734 - When you "setconf log" via the controller, it should remove all
11735 logs. We were automatically adding back in a "log notice stdout".
11736 - Newly bootstrapped Tor networks couldn't establish hidden service
11737 circuits until they had nodes with high uptime. Be more tolerant.
11738 - We were marking servers down when they could not answer every piece
11739 of the directory request we sent them. This was far too harsh.
11740 - Fix the torify (tsocks) config file to not use Tor for localhost
11742 - Directory authorities now go to the proper authority when asking for
11743 a networkstatus, even when they want a compressed one.
11744 - Fix a harmless bug that was causing Tor servers to log
11745 "Got an end because of misc error, but we're not an AP. Closing."
11746 - Authorities were treating their own descriptor changes as cosmetic,
11747 meaning the descriptor available in the network-status and the
11748 descriptor that clients downloaded were different.
11749 - The OS X installer was adding a symlink for tor_resolve but
11750 the binary was called tor-resolve (reported by Thomas Hardly).
11751 - Workaround a problem with some http proxies where they refuse GET
11752 requests that specify "Content-Length: 0" (reported by Adrian).
11753 - Fix wrong log message when you add a "HiddenServiceNodes" config
11754 line without any HiddenServiceDir line (reported by Chris Thomas).
11757 - Write the TorVersion into the state file so we have a prayer of
11758 keeping forward and backward compatibility.
11759 - Revive the FascistFirewall config option rather than eliminating it:
11760 now it's a synonym for ReachableAddresses *:80,*:443.
11761 - Clients choose directory servers from the network status lists,
11762 not from their internal list of router descriptors. Now they can
11763 go to caches directly rather than needing to go to authorities
11765 - Directory authorities ignore router descriptors that have only
11766 cosmetic differences: do this for 0.1.0.x servers now too.
11767 - Add a new flag to network-status indicating whether the server
11768 can answer v2 directory requests too.
11769 - Authdirs now stop whining so loudly about bad descriptors that
11770 they fetch from other dirservers. So when there's a log complaint,
11771 it's for sure from a freshly uploaded descriptor.
11772 - Reduce memory requirements in our structs by changing the order
11774 - There used to be two ways to specify your listening ports in a
11775 server descriptor: on the "router" line and with a separate "ports"
11776 line. Remove support for the "ports" line.
11777 - New config option "AuthDirRejectUnlisted" for auth dirservers as
11778 a panic button: if we get flooded with unusable servers we can
11779 revert to only listing servers in the approved-routers file.
11780 - Auth dir servers can now mark a fingerprint as "!reject" or
11781 "!invalid" in the approved-routers file (as its nickname), to
11782 refuse descriptors outright or include them but marked as invalid.
11783 - Servers store bandwidth history across restarts/crashes.
11784 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
11785 get a better idea of why their circuits failed. Not used yet.
11786 - Directory mirrors now cache up to 16 unrecognized network-status
11787 docs. Now we can add new authdirservers and they'll be cached too.
11788 - When picking a random directory, prefer non-authorities if any
11790 - New controller option "getinfo desc/all-recent" to fetch the
11791 latest server descriptor for every router that Tor knows about.
11794 Changes in version 0.1.0.16 - 2006-01-02
11795 o Crash bugfixes on 0.1.0.x:
11796 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11797 corrupting the heap, losing FDs, or crashing when we need to resize
11798 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11799 - It turns out sparc64 platforms crash on unaligned memory access
11800 too -- so detect and avoid this.
11801 - Handle truncated compressed data correctly (by detecting it and
11803 - Fix possible-but-unlikely free(NULL) in control.c.
11804 - When we were closing connections, there was a rare case that
11805 stomped on memory, triggering seg faults and asserts.
11806 - Avoid potential infinite recursion when building a descriptor. (We
11807 don't know that it ever happened, but better to fix it anyway.)
11808 - We were neglecting to unlink marked circuits from soon-to-close OR
11809 connections, which caused some rare scribbling on freed memory.
11810 - Fix a memory stomping race bug when closing the joining point of two
11811 rendezvous circuits.
11812 - Fix an assert in time parsing found by Steven Murdoch.
11814 o Other bugfixes on 0.1.0.x:
11815 - When we're doing reachability testing, provide more useful log
11816 messages so the operator knows what to expect.
11817 - Do not check whether DirPort is reachable when we are suppressing
11818 advertising it because of hibernation.
11819 - When building with -static or on Solaris, we sometimes needed -ldl.
11820 - When we're deciding whether a stream has enough circuits around
11821 that can handle it, count the freshly dirty ones and not the ones
11822 that are so dirty they won't be able to handle it.
11823 - When we're expiring old circuits, we had a logic error that caused
11824 us to close new rendezvous circuits rather than old ones.
11825 - Give a more helpful log message when you try to change ORPort via
11826 the controller: you should upgrade Tor if you want that to work.
11827 - We were failing to parse Tor versions that start with "Tor ".
11828 - Tolerate faulty streams better: when a stream fails for reason
11829 exitpolicy, stop assuming that the router is lying about his exit
11830 policy. When a stream fails for reason misc, allow it to retry just
11831 as if it was resolvefailed. When a stream has failed three times,
11832 reset its failure count so we can try again and get all three tries.
11835 Changes in version 0.1.1.10-alpha - 2005-12-11
11836 o Correctness bugfixes on 0.1.0.x:
11837 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11838 corrupting the heap, losing FDs, or crashing when we need to resize
11839 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11840 - Stop doing the complex voodoo overkill checking for insecure
11841 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
11842 - When we were closing connections, there was a rare case that
11843 stomped on memory, triggering seg faults and asserts.
11844 - We were neglecting to unlink marked circuits from soon-to-close OR
11845 connections, which caused some rare scribbling on freed memory.
11846 - When we're deciding whether a stream has enough circuits around
11847 that can handle it, count the freshly dirty ones and not the ones
11848 that are so dirty they won't be able to handle it.
11849 - Recover better from TCP connections to Tor servers that are
11850 broken but don't tell you (it happens!); and rotate TLS
11851 connections once a week.
11852 - When we're expiring old circuits, we had a logic error that caused
11853 us to close new rendezvous circuits rather than old ones.
11854 - Fix a scary-looking but apparently harmless bug where circuits
11855 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
11856 servers, and never switch to state CIRCUIT_STATE_OPEN.
11857 - When building with -static or on Solaris, we sometimes needed to
11859 - Give a useful message when people run Tor as the wrong user,
11860 rather than telling them to start chowning random directories.
11861 - We were failing to inform the controller about new .onion streams.
11863 o Security bugfixes on 0.1.0.x:
11864 - Refuse server descriptors if the fingerprint line doesn't match
11865 the included identity key. Tor doesn't care, but other apps (and
11866 humans) might actually be trusting the fingerprint line.
11867 - We used to kill the circuit when we receive a relay command we
11868 don't recognize. Now we just drop it.
11869 - Start obeying our firewall options more rigorously:
11870 . If we can't get to a dirserver directly, try going via Tor.
11871 . Don't ever try to connect (as a client) to a place our
11872 firewall options forbid.
11873 . If we specify a proxy and also firewall options, obey the
11874 firewall options even when we're using the proxy: some proxies
11875 can only proxy to certain destinations.
11876 - Fix a bug found by Lasse Overlier: when we were making internal
11877 circuits (intended to be cannibalized later for rendezvous and
11878 introduction circuits), we were picking them so that they had
11879 useful exit nodes. There was no need for this, and it actually
11880 aids some statistical attacks.
11881 - Start treating internal circuits and exit circuits separately.
11882 It's important to keep them separate because internal circuits
11883 have their last hops picked like middle hops, rather than like
11884 exit hops. So exiting on them will break the user's expectations.
11886 o Bugfixes on 0.1.1.x:
11887 - Take out the mis-feature where we tried to detect IP address
11888 flapping for people with DynDNS, and chose not to upload a new
11889 server descriptor sometimes.
11890 - Try to be compatible with OpenSSL 0.9.6 again.
11891 - Log fix: when the controller is logging about .onion addresses,
11892 sometimes it didn't include the ".onion" part of the address.
11893 - Don't try to modify options->DirServers internally -- if the
11894 user didn't specify any, just add the default ones directly to
11895 the trusted dirserver list. This fixes a bug where people running
11896 controllers would use SETCONF on some totally unrelated config
11897 option, and Tor would start yelling at them about changing their
11899 - Let the controller's redirectstream command specify a port, in
11900 case the controller wants to change that too.
11901 - When we requested a pile of server descriptors, we sometimes
11902 accidentally launched a duplicate request for the first one.
11903 - Bugfix for trackhostexits: write down the fingerprint of the
11904 chosen exit, not its nickname, because the chosen exit might not
11906 - When parsing foo.exit, if foo is unknown, and we are leaving
11907 circuits unattached, set the chosen_exit field and leave the
11908 address empty. This matters because controllers got confused
11910 - Directory authorities no longer try to download server
11911 descriptors that they know they will reject.
11913 o Features and updates:
11914 - Replace balanced trees with hash tables: this should make stuff
11915 significantly faster.
11916 - Resume using the AES counter-mode implementation that we ship,
11917 rather than OpenSSL's. Ours is significantly faster.
11918 - Many other CPU and memory improvements.
11919 - Add a new config option FastFirstHopPK (on by default) so clients
11920 do a trivial crypto handshake for their first hop, since TLS has
11921 already taken care of confidentiality and authentication.
11922 - Add a new config option TestSocks so people can see if their
11923 applications are using socks4, socks4a, socks5-with-ip, or
11924 socks5-with-hostname. This way they don't have to keep mucking
11925 with tcpdump and wondering if something got cached somewhere.
11926 - Warn when listening on a public address for socks. I suspect a
11927 lot of people are setting themselves up as open socks proxies,
11928 and they have no idea that jerks on the Internet are using them,
11929 since they simply proxy the traffic into the Tor network.
11930 - Add "private:*" as an alias in configuration for policies. Now
11931 you can simplify your exit policy rather than needing to list
11932 every single internal or nonroutable network space.
11933 - Add a new controller event type that allows controllers to get
11934 all server descriptors that were uploaded to a router in its role
11935 as authoritative dirserver.
11936 - Start shipping socks-extensions.txt, tor-doc-unix.html,
11937 tor-doc-server.html, and stylesheet.css in the tarball.
11938 - Stop shipping tor-doc.html in the tarball.
11941 Changes in version 0.1.1.9-alpha - 2005-11-15
11942 o Usability improvements:
11943 - Start calling it FooListenAddress rather than FooBindAddress,
11944 since few of our users know what it means to bind an address
11946 - Reduce clutter in server logs. We're going to try to make
11947 them actually usable now. New config option ProtocolWarnings that
11948 lets you hear about how _other Tors_ are breaking the protocol. Off
11950 - Divide log messages into logging domains. Once we put some sort
11951 of interface on this, it will let people looking at more verbose
11952 log levels specify the topics they want to hear more about.
11953 - Make directory servers return better http 404 error messages
11954 instead of a generic "Servers unavailable".
11955 - Check for even more Windows version flags when writing the platform
11956 string in server descriptors, and note any we don't recognize.
11957 - Clean up more of the OpenSSL memory when exiting, so we can detect
11958 memory leaks better.
11959 - Make directory authorities be non-versioning, non-naming by
11960 default. Now we can add new directory servers without requiring
11961 their operators to pay close attention.
11962 - When logging via syslog, include the pid whenever we provide
11963 a log entry. Suggested by Todd Fries.
11965 o Performance improvements:
11966 - Directory servers now silently throw away new descriptors that
11967 haven't changed much if the timestamps are similar. We do this to
11968 tolerate older Tor servers that upload a new descriptor every 15
11969 minutes. (It seemed like a good idea at the time.)
11970 - Inline bottleneck smartlist functions; use fast versions by default.
11971 - Add a "Map from digest to void*" abstraction digestmap_t so we
11972 can do less hex encoding/decoding. Use it in router_get_by_digest()
11973 to resolve a performance bottleneck.
11974 - Allow tor_gzip_uncompress to extract as much as possible from
11975 truncated compressed data. Try to extract as many
11976 descriptors as possible from truncated http responses (when
11977 DIR_PURPOSE_FETCH_ROUTERDESC).
11978 - Make circ->onionskin a pointer, not a static array. moria2 was using
11979 125000 circuit_t's after it had been up for a few weeks, which
11980 translates to 20+ megs of wasted space.
11981 - The private half of our EDH handshake keys are now chosen out
11982 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11984 o Security improvements:
11985 - Start making directory caches retain old routerinfos, so soon
11986 clients can start asking by digest of descriptor rather than by
11987 fingerprint of server.
11988 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11989 to use egd (if present), openbsd weirdness (if present), vms/os2
11990 weirdness (if we ever port there), and more in the future.
11992 o Bugfixes on 0.1.0.x:
11993 - Do round-robin writes of at most 16 kB per write. This might be
11994 more fair on loaded Tor servers, and it might resolve our Windows
11995 crash bug. It might also slow things down.
11996 - Our TLS handshakes were generating a single public/private
11997 keypair for the TLS context, rather than making a new one for
11998 each new connections. Oops. (But we were still rotating them
11999 periodically, so it's not so bad.)
12000 - When we were cannibalizing a circuit with a particular exit
12001 node in mind, we weren't checking to see if that exit node was
12002 already present earlier in the circuit. Oops.
12003 - When a Tor server's IP changes (e.g. from a dyndns address),
12004 upload a new descriptor so clients will learn too.
12005 - Really busy servers were keeping enough circuits open on stable
12006 connections that they were wrapping around the circuit_id
12007 space. (It's only two bytes.) This exposed a bug where we would
12008 feel free to reuse a circuit_id even if it still exists but has
12009 been marked for close. Try to fix this bug. Some bug remains.
12010 - If we would close a stream early (e.g. it asks for a .exit that
12011 we know would refuse it) but the LeaveStreamsUnattached config
12012 option is set by the controller, then don't close it.
12014 o Bugfixes on 0.1.1.8-alpha:
12015 - Fix a big pile of memory leaks, some of them serious.
12016 - Do not try to download a routerdesc if we would immediately reject
12018 - Resume inserting a newline between all router descriptors when
12019 generating (old style) signed directories, since our spec says
12021 - When providing content-type application/octet-stream for
12022 server descriptors using .z, we were leaving out the
12023 content-encoding header. Oops. (Everything tolerated this just
12024 fine, but that doesn't mean we need to be part of the problem.)
12025 - Fix a potential seg fault in getconf and getinfo using version 1
12026 of the controller protocol.
12027 - Avoid crash: do not check whether DirPort is reachable when we
12028 are suppressing it because of hibernation.
12029 - Make --hash-password not crash on exit.
12032 Changes in version 0.1.1.8-alpha - 2005-10-07
12033 o New features (major):
12034 - Clients don't download or use the directory anymore. Now they
12035 download and use network-statuses from the trusted dirservers,
12036 and fetch individual server descriptors as needed from mirrors.
12037 See dir-spec.txt for all the gory details.
12038 - Be more conservative about whether to advertise our DirPort.
12039 The main change is to not advertise if we're running at capacity
12040 and either a) we could hibernate or b) our capacity is low and
12041 we're using a default DirPort.
12042 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
12044 o New features (minor):
12045 - Try to be smart about when to retry network-status and
12046 server-descriptor fetches. Still needs some tuning.
12047 - Stop parsing, storing, or using running-routers output (but
12048 mirrors still cache and serve it).
12049 - Consider a threshold of versioning dirservers (dirservers who have
12050 an opinion about which Tor versions are still recommended) before
12051 deciding whether to warn the user that he's obsolete.
12052 - Dirservers can now reject/invalidate by key and IP, with the
12053 config options "AuthDirInvalid" and "AuthDirReject". This is
12054 useful since currently we automatically list servers as running
12055 and usable even if we know they're jerks.
12056 - Provide dire warnings to any users who set DirServer; move it out
12057 of torrc.sample and into torrc.complete.
12058 - Add MyFamily to torrc.sample in the server section.
12059 - Add nicknames to the DirServer line, so we can refer to them
12060 without requiring all our users to memorize their IP addresses.
12061 - When we get an EOF or a timeout on a directory connection, note
12062 how many bytes of serverdesc we are dropping. This will help
12063 us determine whether it is smart to parse incomplete serverdesc
12065 - Add a new function to "change pseudonyms" -- that is, to stop
12066 using any currently-dirty circuits for new streams, so we don't
12067 link new actions to old actions. Currently it's only called on
12068 HUP (or SIGNAL RELOAD).
12069 - On sighup, if UseHelperNodes changed to 1, use new circuits.
12070 - Start using RAND_bytes rather than RAND_pseudo_bytes from
12071 OpenSSL. Also, reseed our entropy every hour, not just at
12072 startup. And entropy in 512-bit chunks, not 160-bit chunks.
12074 o Fixes on 0.1.1.7-alpha:
12075 - Nobody ever implemented EVENT_ADDRMAP for control protocol
12076 version 0, so don't let version 0 controllers ask for it.
12077 - If you requested something with too many newlines via the
12078 v1 controller protocol, you could crash tor.
12079 - Fix a number of memory leaks, including some pretty serious ones.
12080 - Re-enable DirPort testing again, so Tor servers will be willing
12081 to advertise their DirPort if it's reachable.
12082 - On TLS handshake, only check the other router's nickname against
12083 its expected nickname if is_named is set.
12085 o Fixes forward-ported from 0.1.0.15:
12086 - Don't crash when we don't have any spare file descriptors and we
12087 try to spawn a dns or cpu worker.
12088 - Make the numbers in read-history and write-history into uint64s,
12089 so they don't overflow and publish negatives in the descriptor.
12091 o Fixes on 0.1.0.x:
12092 - For the OS X package's modified privoxy config file, comment
12093 out the "logfile" line so we don't log everything passed
12095 - We were whining about using socks4 or socks5-with-local-lookup
12096 even when it's an IP in the "virtual" range we designed exactly
12098 - We were leaking some memory every time the client changes IPs.
12099 - Never call free() on tor_malloc()d memory. This will help us
12100 use dmalloc to detect memory leaks.
12101 - Check for named servers when looking them up by nickname;
12102 warn when we'recalling a non-named server by its nickname;
12103 don't warn twice about the same name.
12104 - Try to list MyFamily elements by key, not by nickname, and warn
12105 if we've not heard of the server.
12106 - Make windows platform detection (uname equivalent) smarter.
12107 - It turns out sparc64 doesn't like unaligned access either.
12110 Changes in version 0.1.0.15 - 2005-09-23
12111 o Bugfixes on 0.1.0.x:
12112 - Reject ports 465 and 587 (spam targets) in default exit policy.
12113 - Don't crash when we don't have any spare file descriptors and we
12114 try to spawn a dns or cpu worker.
12115 - Get rid of IgnoreVersion undocumented config option, and make us
12116 only warn, never exit, when we're running an obsolete version.
12117 - Don't try to print a null string when your server finds itself to
12118 be unreachable and the Address config option is empty.
12119 - Make the numbers in read-history and write-history into uint64s,
12120 so they don't overflow and publish negatives in the descriptor.
12121 - Fix a minor memory leak in smartlist_string_remove().
12122 - We were only allowing ourselves to upload a server descriptor at
12123 most every 20 minutes, even if it changed earlier than that.
12124 - Clean up log entries that pointed to old URLs.
12127 Changes in version 0.1.1.7-alpha - 2005-09-14
12128 o Fixes on 0.1.1.6-alpha:
12129 - Exit servers were crashing when people asked them to make a
12130 connection to an address not in their exit policy.
12131 - Looking up a non-existent stream for a v1 control connection would
12133 - Fix a seg fault if we ask a dirserver for a descriptor by
12134 fingerprint but he doesn't know about him.
12135 - SETCONF was appending items to linelists, not clearing them.
12136 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
12137 out and refuse the setconf if it would fail.
12138 - Downgrade the dirserver log messages when whining about
12142 - Add Peter Palfrader's check-tor script to tor/contrib/
12143 It lets you easily check whether a given server (referenced by
12144 nickname) is reachable by you.
12145 - Numerous changes to move towards client-side v2 directories. Not
12148 o Fixes on 0.1.0.x:
12149 - If the user gave tor an odd number of command-line arguments,
12150 we were silently ignoring the last one. Now we complain and fail.
12151 [This wins the oldest-bug prize -- this bug has been present since
12152 November 2002, as released in Tor 0.0.0.]
12153 - Do not use unaligned memory access on alpha, mips, or mipsel.
12154 It *works*, but is very slow, so we treat them as if it doesn't.
12155 - Retry directory requests if we fail to get an answer we like
12156 from a given dirserver (we were retrying before, but only if
12157 we fail to connect).
12158 - When writing the RecommendedVersions line, sort them first.
12159 - When the client asked for a rendezvous port that the hidden
12160 service didn't want to provide, we were sending an IP address
12161 back along with the end cell. Fortunately, it was zero. But stop
12163 - Correct "your server is reachable" log entries to indicate that
12164 it was self-testing that told us so.
12167 Changes in version 0.1.1.6-alpha - 2005-09-09
12168 o Fixes on 0.1.1.5-alpha:
12169 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
12170 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
12171 - Fix bug with tor_memmem finding a match at the end of the string.
12172 - Make unit tests run without segfaulting.
12173 - Resolve some solaris x86 compile warnings.
12174 - Handle duplicate lines in approved-routers files without warning.
12175 - Fix bug where as soon as a server refused any requests due to his
12176 exit policy (e.g. when we ask for localhost and he tells us that's
12177 127.0.0.1 and he won't do it), we decided he wasn't obeying his
12178 exit policy using him for any exits.
12179 - Only do openssl hardware accelerator stuff if openssl version is
12182 o New controller features/fixes:
12183 - Add a "RESETCONF" command so you can set config options like
12184 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
12185 a config option in the torrc with no value, then it clears it
12186 entirely (rather than setting it to its default).
12187 - Add a "GETINFO config-file" to tell us where torrc is.
12188 - Avoid sending blank lines when GETINFO replies should be empty.
12189 - Add a QUIT command for the controller (for using it manually).
12190 - Fix a bug in SAVECONF that was adding default dirservers and
12191 other redundant entries to the torrc file.
12193 o Start on the new directory design:
12194 - Generate, publish, cache, serve new network-status format.
12195 - Publish individual descriptors (by fingerprint, by "all", and by
12197 - Publish client and server recommended versions separately.
12198 - Allow tor_gzip_uncompress() to handle multiple concatenated
12199 compressed strings. Serve compressed groups of router
12200 descriptors. The compression logic here could be more
12202 - Distinguish v1 authorities (all currently trusted directories)
12203 from v2 authorities (all trusted directories).
12204 - Change DirServers config line to note which dirs are v1 authorities.
12205 - Add configuration option "V1AuthoritativeDirectory 1" which
12206 moria1, moria2, and tor26 should set.
12207 - Remove option when getting directory cache to see whether they
12208 support running-routers; they all do now. Replace it with one
12209 to see whether caches support v2 stuff.
12212 - Dirservers now do their own external reachability testing of each
12213 Tor server, and only list them as running if they've been found to
12214 be reachable. We also send back warnings to the server's logs if
12215 it uploads a descriptor that we already believe is unreachable.
12216 - Implement exit enclaves: if we know an IP address for the
12217 destination, and there's a running Tor server at that address
12218 which allows exit to the destination, then extend the circuit to
12219 that exit first. This provides end-to-end encryption and end-to-end
12220 authentication. Also, if the user wants a .exit address or enclave,
12221 use 4 hops rather than 3, and cannibalize a general circ for it
12223 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
12224 controller. Also, rotate dns and cpu workers if the controller
12225 changes options that will affect them; and initialize the dns
12226 worker cache tree whether or not we start out as a server.
12227 - Only upload a new server descriptor when options change, 18
12228 hours have passed, uptime is reset, or bandwidth changes a lot.
12229 - Check [X-]Forwarded-For headers in HTTP requests when generating
12230 log messages. This lets people run dirservers (and caches) behind
12231 Apache but still know which IP addresses are causing warnings.
12233 o Config option changes:
12234 - Replace (Fascist)Firewall* config options with a new
12235 ReachableAddresses option that understands address policies.
12236 For example, "ReachableAddresses *:80,*:443"
12237 - Get rid of IgnoreVersion undocumented config option, and make us
12238 only warn, never exit, when we're running an obsolete version.
12239 - Make MonthlyAccountingStart config option truly obsolete now.
12241 o Fixes on 0.1.0.x:
12242 - Reject ports 465 and 587 in the default exit policy, since
12243 people have started using them for spam too.
12244 - It turns out we couldn't bootstrap a network since we added
12245 reachability detection in 0.1.0.1-rc. Good thing the Tor network
12246 has never gone down. Add an AssumeReachable config option to let
12247 servers and dirservers bootstrap. When we're trying to build a
12248 high-uptime or high-bandwidth circuit but there aren't enough
12249 suitable servers, try being less picky rather than simply failing.
12250 - Our logic to decide if the OR we connected to was the right guy
12251 was brittle and maybe open to a mitm for unverified routers.
12252 - We weren't cannibalizing circuits correctly for
12253 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
12254 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
12255 build those from scratch. This should make hidden services faster.
12256 - Predict required circuits better, with an eye toward making hidden
12257 services faster on the service end.
12258 - Retry streams if the exit node sends back a 'misc' failure. This
12259 should result in fewer random failures. Also, after failing
12260 from resolve failed or misc, reset the num failures, so we give
12261 it a fair shake next time we try.
12262 - Clean up the rendezvous warn log msgs, and downgrade some to info.
12263 - Reduce severity on logs about dns worker spawning and culling.
12264 - When we're shutting down and we do something like try to post a
12265 server descriptor or rendezvous descriptor, don't complain that
12266 we seem to be unreachable. Of course we are, we're shutting down.
12267 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
12268 We don't use them yet, but maybe one day our DNS resolver will be
12269 able to discover them.
12270 - Make ContactInfo mandatory for authoritative directory servers.
12271 - Require server descriptors to list IPv4 addresses -- hostnames
12272 are no longer allowed. This also fixes some potential security
12273 problems with people providing hostnames as their address and then
12274 preferentially resolving them to partition users.
12275 - Change log line for unreachability to explicitly suggest /etc/hosts
12276 as the culprit. Also make it clearer what IP address and ports we're
12277 testing for reachability.
12278 - Put quotes around user-supplied strings when logging so users are
12279 more likely to realize if they add bad characters (like quotes)
12281 - Let auth dir servers start without specifying an Address config
12283 - Make unit tests (and other invocations that aren't the real Tor)
12284 run without launching listeners, creating subdirectories, and so on.
12287 Changes in version 0.1.1.5-alpha - 2005-08-08
12288 o Bugfixes included in 0.1.0.14.
12290 o Bugfixes on 0.1.0.x:
12291 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
12292 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
12293 it would silently using ignore the 6668.
12296 Changes in version 0.1.0.14 - 2005-08-08
12297 o Bugfixes on 0.1.0.x:
12298 - Fix the other half of the bug with crypto handshakes
12300 - Fix an assert trigger if you send a 'signal term' via the
12301 controller when it's listening for 'event info' messages.
12304 Changes in version 0.1.1.4-alpha - 2005-08-04
12305 o Bugfixes included in 0.1.0.13.
12308 - Improve tor_gettimeofday() granularity on windows.
12309 - Make clients regenerate their keys when their IP address changes.
12310 - Implement some more GETINFO goodness: expose helper nodes, config
12311 options, getinfo keys.
12314 Changes in version 0.1.0.13 - 2005-08-04
12315 o Bugfixes on 0.1.0.x:
12316 - Fix a critical bug in the security of our crypto handshakes.
12317 - Fix a size_t underflow in smartlist_join_strings2() that made
12318 it do bad things when you hand it an empty smartlist.
12319 - Fix Windows installer to ship Tor license (thanks to Aphex for
12320 pointing out this oversight) and put a link to the doc directory
12322 - Explicitly set no-unaligned-access for sparc: it turns out the
12323 new gcc's let you compile broken code, but that doesn't make it
12327 Changes in version 0.1.1.3-alpha - 2005-07-23
12328 o Bugfixes on 0.1.1.2-alpha:
12329 - Fix a bug in handling the controller's "post descriptor"
12331 - Fix several bugs in handling the controller's "extend circuit"
12333 - Fix a bug in handling the controller's "stream status" event.
12334 - Fix an assert failure if we have a controller listening for
12335 circuit events and we go offline.
12336 - Re-allow hidden service descriptors to publish 0 intro points.
12337 - Fix a crash when generating your hidden service descriptor if
12338 you don't have enough intro points already.
12340 o New features on 0.1.1.2-alpha:
12341 - New controller function "getinfo accounting", to ask how
12342 many bytes we've used in this time period.
12343 - Experimental support for helper nodes: a lot of the risk from
12344 a small static adversary comes because users pick new random
12345 nodes every time they rebuild a circuit. Now users will try to
12346 stick to the same small set of entry nodes if they can. Not
12347 enabled by default yet.
12349 o Bugfixes on 0.1.0.12:
12350 - If you're an auth dir server, always publish your dirport,
12351 even if you haven't yet found yourself to be reachable.
12352 - Fix a size_t underflow in smartlist_join_strings2() that made
12353 it do bad things when you hand it an empty smartlist.
12356 Changes in version 0.1.0.12 - 2005-07-18
12357 o New directory servers:
12358 - tor26 has changed IP address.
12360 o Bugfixes on 0.1.0.x:
12361 - Fix a possible double-free in tor_gzip_uncompress().
12362 - When --disable-threads is set, do not search for or link against
12363 pthreads libraries.
12364 - Don't trigger an assert if an authoritative directory server
12365 claims its dirport is 0.
12366 - Fix bug with removing Tor as an NT service: some people were
12367 getting "The service did not return an error." Thanks to Matt
12371 Changes in version 0.1.1.2-alpha - 2005-07-15
12372 o New directory servers:
12373 - tor26 has changed IP address.
12375 o Bugfixes on 0.1.0.x, crashes/leaks:
12376 - Port the servers-not-obeying-their-exit-policies fix from
12378 - Fix an fd leak in start_daemon().
12379 - On Windows, you can't always reopen a port right after you've
12380 closed it. So change retry_listeners() to only close and re-open
12381 ports that have changed.
12382 - Fix a possible double-free in tor_gzip_uncompress().
12384 o Bugfixes on 0.1.0.x, usability:
12385 - When tor_socketpair() fails in Windows, give a reasonable
12386 Windows-style errno back.
12387 - Let people type "tor --install" as well as "tor -install" when
12389 want to make it an NT service.
12390 - NT service patch from Matt Edman to improve error messages.
12391 - When the controller asks for a config option with an abbreviated
12392 name, give the full name in our response.
12393 - Correct the man page entry on TrackHostExitsExpire.
12394 - Looks like we were never delivering deflated (i.e. compressed)
12395 running-routers lists, even when asked. Oops.
12396 - When --disable-threads is set, do not search for or link against
12397 pthreads libraries.
12399 o Bugfixes on 0.1.1.x:
12400 - Fix a seg fault with autodetecting which controller version is
12404 - New hidden service descriptor format: put a version in it, and
12405 let people specify introduction/rendezvous points that aren't
12406 in "the directory" (which is subjective anyway).
12407 - Allow the DEBUG controller event to work again. Mark certain log
12408 entries as "don't tell this to controllers", so we avoid cycles.
12411 Changes in version 0.1.0.11 - 2005-06-30
12412 o Bugfixes on 0.1.0.x:
12413 - Fix major security bug: servers were disregarding their
12414 exit policies if clients behaved unexpectedly.
12415 - Make OS X init script check for missing argument, so we don't
12416 confuse users who invoke it incorrectly.
12417 - Fix a seg fault in "tor --hash-password foo".
12418 - The MAPADDRESS control command was broken.
12421 Changes in version 0.1.1.1-alpha - 2005-06-29
12423 - Make OS X init script check for missing argument, so we don't
12424 confuse users who invoke it incorrectly.
12425 - Fix a seg fault in "tor --hash-password foo".
12426 - Fix a possible way to DoS dirservers.
12427 - When we complain that your exit policy implicitly allows local or
12428 private address spaces, name them explicitly so operators can
12430 - Make the log message less scary when all the dirservers are
12431 temporarily unreachable.
12432 - We were printing the number of idle dns workers incorrectly when
12436 - Revised controller protocol (version 1) that uses ascii rather
12437 than binary. Add supporting libraries in python and java so you
12438 can use the controller from your applications without caring how
12439 our protocol works.
12440 - Spiffy new support for crypto hardware accelerators. Can somebody
12444 Changes in version 0.0.9.10 - 2005-06-16
12445 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
12446 - Refuse relay cells that claim to have a length larger than the
12447 maximum allowed. This prevents a potential attack that could read
12448 arbitrary memory (e.g. keys) from an exit server's process
12452 Changes in version 0.1.0.10 - 2005-06-14
12453 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
12454 libevent before 1.1a.
12457 Changes in version 0.1.0.9-rc - 2005-06-09
12459 - Reset buf->highwater every time buf_shrink() is called, not just on
12460 a successful shrink. This was causing significant memory bloat.
12461 - Fix buffer overflow when checking hashed passwords.
12462 - Security fix: if seeding the RNG on Win32 fails, quit.
12463 - Allow seeding the RNG on Win32 even when you're not running as
12465 - Disable threading on Solaris too. Something is wonky with it,
12466 cpuworkers, and reentrant libs.
12467 - Reenable the part of the code that tries to flush as soon as an
12468 OR outbuf has a full TLS record available. Perhaps this will make
12469 OR outbufs not grow as huge except in rare cases, thus saving lots
12470 of CPU time plus memory.
12471 - Reject malformed .onion addresses rather then passing them on as
12472 normal web requests.
12473 - Adapt patch from Adam Langley: fix possible memory leak in
12474 tor_lookup_hostname().
12475 - Initialize libevent later in the startup process, so the logs are
12476 already established by the time we start logging libevent warns.
12477 - Use correct errno on win32 if libevent fails.
12478 - Check and warn about known-bad/slow libevent versions.
12479 - Pay more attention to the ClientOnly config option.
12480 - Have torctl.in/tor.sh.in check for location of su binary (needed
12482 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
12483 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
12484 HttpProxyAuthenticator
12485 - Stop warning about sigpipes in the logs. We're going to
12486 pretend that getting these occassionally is normal and fine.
12487 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
12489 installer screens; and don't put stuff into StartupItems unless
12490 the user asks you to.
12491 - Require servers that use the default dirservers to have public IP
12492 addresses. We have too many servers that are configured with private
12493 IPs and their admins never notice the log entries complaining that
12494 their descriptors are being rejected.
12495 - Add OSX uninstall instructions. An actual uninstall script will
12499 Changes in version 0.1.0.8-rc - 2005-05-23
12501 - It turns out that kqueue on OS X 10.3.9 was causing kernel
12502 panics. Disable kqueue on all OS X Tors.
12503 - Fix RPM: remove duplicate line accidentally added to the rpm
12505 - Disable threads on openbsd too, since its gethostaddr is not
12507 - Tolerate libevent 0.8 since it still works, even though it's
12509 - Enable building on Red Hat 9.0 again.
12510 - Allow the middle hop of the testing circuit to be running any
12511 version, now that most of them have the bugfix to let them connect
12512 to unknown servers. This will allow reachability testing to work
12513 even when 0.0.9.7-0.0.9.9 become obsolete.
12514 - Handle relay cells with rh.length too large. This prevents
12515 a potential attack that could read arbitrary memory (maybe even
12516 keys) from the exit server's process.
12517 - We screwed up the dirport reachability testing when we don't yet
12518 have a cached version of the directory. Hopefully now fixed.
12519 - Clean up router_load_single_router() (used by the controller),
12520 so it doesn't seg fault on error.
12521 - Fix a minor memory leak when somebody establishes an introduction
12522 point at your Tor server.
12523 - If a socks connection ends because read fails, don't warn that
12524 you're not sending a socks reply back.
12527 - Add HttpProxyAuthenticator config option too, that works like
12528 the HttpsProxyAuthenticator config option.
12529 - Encode hashed controller passwords in hex instead of base64,
12530 to make it easier to write controllers.
12533 Changes in version 0.1.0.7-rc - 2005-05-17
12535 - Fix a bug in the OS X package installer that prevented it from
12536 installing on Tiger.
12537 - Fix a script bug in the OS X package installer that made it
12538 complain during installation.
12539 - Find libevent even if it's hiding in /usr/local/ and your
12540 CFLAGS and LDFLAGS don't tell you to look there.
12541 - Be able to link with libevent as a shared library (the default
12542 after 1.0d), even if it's hiding in /usr/local/lib and even
12543 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
12544 assuming you're running gcc. Otherwise fail and give a useful
12546 - Fix a bug in the RPM packager: set home directory for _tor to
12547 something more reasonable when first installing.
12548 - Free a minor amount of memory that is still reachable on exit.
12551 Changes in version 0.1.0.6-rc - 2005-05-14
12553 - Implement --disable-threads configure option. Disable threads on
12554 netbsd by default, because it appears to have no reentrant resolver
12556 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
12557 release (1.1) detects and disables kqueue if it's broken.
12558 - Append default exit policy before checking for implicit internal
12559 addresses. Now we don't log a bunch of complaints on startup
12560 when using the default exit policy.
12561 - Some people were putting "Address " in their torrc, and they had
12562 a buggy resolver that resolved " " to 0.0.0.0. Oops.
12563 - If DataDir is ~/.tor, and that expands to /.tor, then default to
12564 LOCALSTATEDIR/tor instead.
12565 - Fix fragmented-message bug in TorControl.py.
12566 - Resolve a minor bug which would prevent unreachable dirports
12567 from getting suppressed in the published descriptor.
12568 - When the controller gave us a new descriptor, we weren't resolving
12569 it immediately, so Tor would think its address was 0.0.0.0 until
12570 we fetched a new directory.
12571 - Fix an uppercase/lowercase case error in suppressing a bogus
12572 libevent warning on some Linuxes.
12575 - Begin scrubbing sensitive strings from logs by default. Turn off
12576 the config option SafeLogging if you need to do debugging.
12577 - Switch to a new buffer management algorithm, which tries to avoid
12578 reallocing and copying quite as much. In first tests it looks like
12579 it uses *more* memory on average, but less cpu.
12580 - First cut at support for "create-fast" cells. Clients can use
12581 these when extending to their first hop, since the TLS already
12582 provides forward secrecy and authentication. Not enabled on
12584 - When dirservers refuse a router descriptor, we now log its
12585 contactinfo, platform, and the poster's IP address.
12586 - Call tor_free_all instead of connections_free_all after forking, to
12587 save memory on systems that need to fork.
12588 - Whine at you if you're a server and you don't set your contactinfo.
12589 - Implement --verify-config command-line option to check if your torrc
12590 is valid without actually launching Tor.
12591 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
12592 rather than just rejecting it.
12595 Changes in version 0.1.0.5-rc - 2005-04-27
12597 - Stop trying to print a null pointer if an OR conn fails because
12598 we didn't like its cert.
12600 - Switch our internal buffers implementation to use a ring buffer,
12601 to hopefully improve performance for fast servers a lot.
12602 - Add HttpsProxyAuthenticator support (basic auth only), based
12603 on patch from Adam Langley.
12604 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
12605 the fast servers that have been joining lately.
12606 - Give hidden service accesses extra time on the first attempt,
12607 since 60 seconds is often only barely enough. This might improve
12609 - Improve performance for dirservers: stop re-parsing the whole
12610 directory every time you regenerate it.
12611 - Add more debugging info to help us find the weird dns freebsd
12612 pthreads bug; cleaner debug messages to help track future issues.
12615 Changes in version 0.0.9.9 - 2005-04-23
12616 o Bugfixes on 0.0.9.x:
12617 - If unofficial Tor clients connect and send weird TLS certs, our
12618 Tor server triggers an assert. This release contains a minimal
12619 backport from the broader fix that we put into 0.1.0.4-rc.
12622 Changes in version 0.1.0.4-rc - 2005-04-23
12624 - If unofficial Tor clients connect and send weird TLS certs, our
12625 Tor server triggers an assert. Stop asserting, and start handling
12626 TLS errors better in other situations too.
12627 - When the controller asks us to tell it about all the debug-level
12628 logs, it turns out we were generating debug-level logs while
12629 telling it about them, which turns into a bad loop. Now keep
12630 track of whether you're sending a debug log to the controller,
12631 and don't log when you are.
12632 - Fix the "postdescriptor" feature of the controller interface: on
12633 non-complete success, only say "done" once.
12635 - Clients are now willing to load balance over up to 2mB, not 1mB,
12636 of advertised bandwidth capacity.
12637 - Add a NoPublish config option, so you can be a server (e.g. for
12638 testing running Tor servers in other Tor networks) without
12639 publishing your descriptor to the primary dirservers.
12642 Changes in version 0.1.0.3-rc - 2005-04-08
12643 o Improvements on 0.1.0.2-rc:
12644 - Client now retries when streams end early for 'hibernating' or
12645 'resource limit' reasons, rather than failing them.
12646 - More automated handling for dirserver operators:
12647 - Automatically approve nodes running 0.1.0.2-rc or later,
12648 now that the the reachability detection stuff is working.
12649 - Now we allow two unverified servers with the same nickname
12650 but different keys. But if a nickname is verified, only that
12651 nickname+key are allowed.
12652 - If you're an authdirserver connecting to an address:port,
12653 and it's not the OR you were expecting, forget about that
12654 descriptor. If he *was* the one you were expecting, then forget
12655 about all other descriptors for that address:port.
12656 - Allow servers to publish descriptors from 12 hours in the future.
12657 Corollary: only whine about clock skew from the dirserver if
12658 he's a trusted dirserver (since now even verified servers could
12659 have quite wrong clocks).
12660 - Adjust maximum skew and age for rendezvous descriptors: let skew
12661 be 48 hours rather than 90 minutes.
12662 - Efficiency improvements:
12663 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
12664 it much faster to look up a circuit for each relay cell.
12665 - Remove most calls to assert_all_pending_dns_resolves_ok(),
12666 since they're eating our cpu on exit nodes.
12667 - Stop wasting time doing a case insensitive comparison for every
12668 dns name every time we do any lookup. Canonicalize the names to
12669 lowercase and be done with it.
12670 - Start sending 'truncated' cells back rather than destroy cells,
12671 if the circuit closes in front of you. This means we won't have
12672 to abandon partially built circuits.
12673 - Only warn once per nickname from add_nickname_list_to_smartlist
12674 per failure, so an entrynode or exitnode choice that's down won't
12676 - Put a note in the torrc about abuse potential with the default
12678 - Revise control spec and implementation to allow all log messages to
12679 be sent to controller with their severities intact (suggested by
12680 Matt Edman). Update TorControl to handle new log event types.
12681 - Provide better explanation messages when controller's POSTDESCRIPTOR
12683 - Stop putting nodename in the Platform string in server descriptors.
12684 It doesn't actually help, and it is confusing/upsetting some people.
12686 o Bugfixes on 0.1.0.2-rc:
12687 - We were printing the host mask wrong in exit policies in server
12688 descriptors. This isn't a critical bug though, since we were still
12689 obeying the exit policy internally.
12690 - Fix Tor when compiled with libevent but without pthreads: move
12691 connection_unregister() from _connection_free() to
12693 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
12694 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
12695 when we look through the connection array, we'll find any of the
12696 cpu/dnsworkers. This is no good.
12698 o Bugfixes on 0.0.9.8:
12699 - Fix possible bug on threading platforms (e.g. win32) which was
12700 leaking a file descriptor whenever a cpuworker or dnsworker died.
12701 - When using preferred entry or exit nodes, ignore whether the
12702 circuit wants uptime or capacity. They asked for the nodes, they
12704 - chdir() to your datadirectory at the *end* of the daemonize process,
12705 not the beginning. This was a problem because the first time you
12706 run tor, if your datadir isn't there, and you have runasdaemon set
12707 to 1, it will try to chdir to it before it tries to create it. Oops.
12708 - Handle changed router status correctly when dirserver reloads
12709 fingerprint file. We used to be dropping all unverified descriptors
12710 right then. The bug was hidden because we would immediately
12711 fetch a directory from another dirserver, which would include the
12712 descriptors we just dropped.
12713 - When we're connecting to an OR and he's got a different nickname/key
12714 than we were expecting, only complain loudly if we're an OP or a
12715 dirserver. Complaining loudly to the OR admins just confuses them.
12716 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
12717 artificially capped at 500kB.
12720 Changes in version 0.0.9.8 - 2005-04-07
12721 o Bugfixes on 0.0.9.x:
12722 - We have a bug that I haven't found yet. Sometimes, very rarely,
12723 cpuworkers get stuck in the 'busy' state, even though the cpuworker
12724 thinks of itself as idle. This meant that no new circuits ever got
12725 established. Here's a workaround to kill any cpuworker that's been
12726 busy for more than 100 seconds.
12729 Changes in version 0.1.0.2-rc - 2005-04-01
12730 o Bugfixes on 0.1.0.1-rc:
12731 - Fixes on reachability detection:
12732 - Don't check for reachability while hibernating.
12733 - If ORPort is reachable but DirPort isn't, still publish the
12734 descriptor, but zero out DirPort until it's found reachable.
12735 - When building testing circs for ORPort testing, use only
12736 high-bandwidth nodes, so fewer circuits fail.
12737 - Complain about unreachable ORPort separately from unreachable
12738 DirPort, so the user knows what's going on.
12739 - Make sure we only conclude ORPort reachability if we didn't
12740 initiate the conn. Otherwise we could falsely conclude that
12741 we're reachable just because we connected to the guy earlier
12742 and he used that same pipe to extend to us.
12743 - Authdirservers shouldn't do ORPort reachability detection,
12744 since they're in clique mode, so it will be rare to find a
12745 server not already connected to them.
12746 - When building testing circuits, always pick middle hops running
12747 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
12748 bug. (This is a kludge; it will go away when 0.0.9.x becomes
12750 - When we decide we're reachable, actually publish our descriptor
12752 - Fix bug in redirectstream in the controller.
12753 - Fix the state descriptor strings so logs don't claim edge streams
12754 are in a different state than they actually are.
12755 - Use recent libevent features when possible (this only really affects
12756 win32 and osx right now, because the new libevent with these
12757 features hasn't been released yet). Add code to suppress spurious
12759 - Prevent possible segfault in connection_close_unattached_ap().
12760 - Fix newlines on torrc in win32.
12761 - Improve error msgs when tor-resolve fails.
12763 o Improvements on 0.0.9.x:
12764 - New experimental script tor/contrib/ExerciseServer.py (needs more
12765 work) that uses the controller interface to build circuits and
12766 fetch pages over them. This will help us bootstrap servers that
12767 have lots of capacity but haven't noticed it yet.
12768 - New experimental script tor/contrib/PathDemo.py (needs more work)
12769 that uses the controller interface to let you choose whole paths
12771 "<hostname>.<path,separated by dots>.<length of path>.path"
12772 - When we've connected to an OR and handshaked but didn't like
12773 the result, we were closing the conn without sending destroy
12774 cells back for pending circuits. Now send those destroys.
12777 Changes in version 0.0.9.7 - 2005-04-01
12778 o Bugfixes on 0.0.9.x:
12779 - Fix another race crash bug (thanks to Glenn Fink for reporting).
12780 - Compare identity to identity, not to nickname, when extending to
12781 a router not already in the directory. This was preventing us from
12782 extending to unknown routers. Oops.
12783 - Make sure to create OS X Tor user in <500 range, so we aren't
12784 creating actual system users.
12785 - Note where connection-that-hasn't-sent-end was marked, and fix
12786 a few really loud instances of this harmless bug (it's fixed more
12790 Changes in version 0.1.0.1-rc - 2005-03-28
12792 - Add reachability testing. Your Tor server will automatically try
12793 to see if its ORPort and DirPort are reachable from the outside,
12794 and it won't upload its descriptor until it decides they are.
12795 - Handle unavailable hidden services better. Handle slow or busy
12796 hidden services better.
12797 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12799 - New exit policy: accept most low-numbered ports, rather than
12800 rejecting most low-numbered ports.
12801 - More Tor controller support (still experimental). See
12802 http://tor.eff.org/doc/control-spec.txt for all the new features,
12803 including signals to emulate unix signals from any platform;
12804 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12805 closestream; closecircuit; etc.
12806 - Make nt services work and start on startup on win32 (based on
12807 patch by Matt Edman).
12808 - Add a new AddressMap config directive to rewrite incoming socks
12809 addresses. This lets you, for example, declare an implicit
12810 required exit node for certain sites.
12811 - Add a new TrackHostExits config directive to trigger addressmaps
12812 for certain incoming socks addresses -- for sites that break when
12813 your exit keeps changing (based on patch by Mike Perry).
12814 - Redo the client-side dns cache so it's just an addressmap too.
12815 - Notice when our IP changes, and reset stats/uptime/reachability.
12816 - When an application is using socks5, give him the whole variety of
12817 potential socks5 responses (connect refused, host unreachable, etc),
12818 rather than just "success" or "failure".
12819 - A more sane version numbering system. See
12820 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12821 - New contributed script "exitlist": a simple python script to
12822 parse directories and find Tor nodes that exit to listed
12824 - New contributed script "privoxy-tor-toggle" to toggle whether
12825 Privoxy uses Tor. Seems to be configured for Debian by default.
12826 - Report HTTP reasons to client when getting a response from directory
12827 servers -- so you can actually know what went wrong.
12828 - New config option MaxAdvertisedBandwidth which lets you advertise
12829 a low bandwidthrate (to not attract as many circuits) while still
12830 allowing a higher bandwidthrate in reality.
12832 o Robustness/stability fixes:
12833 - Make Tor use Niels Provos's libevent instead of its current
12834 poll-but-sometimes-select mess. This will let us use faster async
12835 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
12837 - pthread support now too. This was forced because when we forked,
12838 we ended up wasting a lot of duplicate ram over time. Also switch
12839 to foo_r versions of some library calls to allow reentry and
12841 - Better handling for heterogeneous / unreliable nodes:
12842 - Annotate circuits w/ whether they aim to contain high uptime nodes
12843 and/or high capacity nodes. When building circuits, choose
12845 - This means that every single node in an intro rend circuit,
12846 not just the last one, will have a minimum uptime.
12847 - New config option LongLivedPorts to indicate application streams
12848 that will want high uptime circuits.
12849 - Servers reset uptime when a dir fetch entirely fails. This
12850 hopefully reflects stability of the server's network connectivity.
12851 - If somebody starts his tor server in Jan 2004 and then fixes his
12852 clock, don't make his published uptime be a year.
12853 - Reset published uptime when you wake up from hibernation.
12854 - Introduce a notion of 'internal' circs, which are chosen without
12855 regard to the exit policy of the last hop. Intro and rendezvous
12856 circs must be internal circs, to avoid leaking information. Resolve
12857 and connect streams can use internal circs if they want.
12858 - New circuit pooling algorithm: make sure to have enough circs around
12859 to satisfy any predicted ports, and also make sure to have 2 internal
12860 circs around if we've required internal circs lately (and with high
12861 uptime if we've seen that lately too).
12862 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12863 which describes how often we retry making new circuits if current
12864 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12865 how long we're willing to make use of an already-dirty circuit.
12866 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12867 circ as necessary, if there are any completed ones lying around
12868 when we try to launch one.
12869 - Make hidden services try to establish a rendezvous for 30 seconds,
12870 rather than for n (where n=3) attempts to build a circuit.
12871 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
12872 "ShutdownWaitLength".
12873 - Try to be more zealous about calling connection_edge_end when
12874 things go bad with edge conns in connection.c.
12875 - Revise tor-spec to add more/better stream end reasons.
12876 - Revise all calls to connection_edge_end to avoid sending "misc",
12877 and to take errno into account where possible.
12880 - Fix a race condition that can trigger an assert, when we have a
12881 pending create cell and an OR connection fails right then.
12882 - Fix several double-mark-for-close bugs, e.g. where we were finding
12883 a conn for a cell even if that conn is already marked for close.
12884 - Make sequence of log messages when starting on win32 with no config
12885 file more reasonable.
12886 - When choosing an exit node for a new non-internal circ, don't take
12887 into account whether it'll be useful for any pending x.onion
12888 addresses -- it won't.
12889 - Turn addr_policy_compare from a tristate to a quadstate; this should
12890 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12891 for google.com" problem.
12892 - Make "platform" string in descriptor more accurate for Win32 servers,
12893 so it's not just "unknown platform".
12894 - Fix an edge case in parsing config options (thanks weasel).
12895 If they say "--" on the commandline, it's not an option.
12896 - Reject odd-looking addresses at the client (e.g. addresses that
12897 contain a colon), rather than having the server drop them because
12899 - tor-resolve requests were ignoring .exit if there was a working circuit
12900 they could use instead.
12901 - REUSEADDR on normal platforms means you can rebind to the port
12902 right after somebody else has let it go. But REUSEADDR on win32
12903 means to let you bind to the port _even when somebody else
12904 already has it bound_! So, don't do that on Win32.
12905 - Change version parsing logic: a version is "obsolete" if it is not
12906 recommended and (1) there is a newer recommended version in the
12907 same series, or (2) there are no recommended versions in the same
12908 series, but there are some recommended versions in a newer series.
12909 A version is "new" if it is newer than any recommended version in
12911 - Stop most cases of hanging up on a socks connection without sending
12915 - Require BandwidthRate to be at least 20kB/s for servers.
12916 - When a dirserver causes you to give a warn, mention which dirserver
12918 - New config option DirAllowPrivateAddresses for authdirservers.
12919 Now by default they refuse router descriptors that have non-IP or
12920 private-IP addresses.
12921 - Stop publishing socksport in the directory, since it's not
12922 actually meant to be public. For compatibility, publish a 0 there
12924 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12925 smart" value, that is low for servers and high for clients.
12926 - If our clock jumps forward by 100 seconds or more, assume something
12927 has gone wrong with our network and abandon all not-yet-used circs.
12928 - Warn when exit policy implicitly allows local addresses.
12929 - If we get an incredibly skewed timestamp from a dirserver mirror
12930 that isn't a verified OR, don't warn -- it's probably him that's
12932 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12933 cookies to disk and doesn't log each web request to disk. (Thanks
12934 to Brett Carrington for pointing this out.)
12935 - When a client asks us for a dir mirror and we don't have one,
12936 launch an attempt to get a fresh one.
12937 - If we're hibernating and we get a SIGINT, exit immediately.
12938 - Add --with-dmalloc ./configure option, to track memory leaks.
12939 - And try to free all memory on closing, so we can detect what
12941 - Cache local dns resolves correctly even when they're .exit
12943 - Give a better warning when some other server advertises an
12944 ORPort that is actually an apache running ssl.
12945 - Add "opt hibernating 1" to server descriptor to make it clearer
12946 whether the server is hibernating.
12949 Changes in version 0.0.9.6 - 2005-03-24
12950 o Bugfixes on 0.0.9.x (crashes and asserts):
12951 - Add new end stream reasons to maintainance branch. Fix bug where
12952 reason (8) could trigger an assert. Prevent bug from recurring.
12953 - Apparently win32 stat wants paths to not end with a slash.
12954 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12955 blowing away the circuit that conn->cpath_layer points to, then
12956 checking to see if the circ is well-formed. Backport check to make
12957 sure we dont use the cpath on a closed connection.
12958 - Prevent circuit_resume_edge_reading_helper() from trying to package
12959 inbufs for marked-for-close streams.
12960 - Don't crash on hup if your options->address has become unresolvable.
12961 - Some systems (like OS X) sometimes accept() a connection and tell
12962 you the remote host is 0.0.0.0:0. If this happens, due to some
12963 other mis-features, we get confused; so refuse the conn for now.
12965 o Bugfixes on 0.0.9.x (other):
12966 - Fix harmless but scary "Unrecognized content encoding" warn message.
12967 - Add new stream error reason: TORPROTOCOL reason means "you are not
12968 speaking a version of Tor I understand; say bye-bye to your stream."
12969 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12970 into the future, now that we are more tolerant of skew. This
12971 resolves a bug where a Tor server would refuse to cache a directory
12972 because all the directories it gets are too far in the future;
12973 yet the Tor server never logs any complaints about clock skew.
12974 - Mac packaging magic: make man pages useable, and do not overwrite
12975 existing torrc files.
12976 - Make OS X log happily to /var/log/tor/tor.log
12979 Changes in version 0.0.9.5 - 2005-02-22
12980 o Bugfixes on 0.0.9.x:
12981 - Fix an assert race at exit nodes when resolve requests fail.
12982 - Stop picking unverified dir mirrors--it only leads to misery.
12983 - Patch from Matt Edman to make NT services work better. Service
12984 support is still not compiled into the executable by default.
12985 - Patch from Dmitri Bely so the Tor service runs better under
12986 the win32 SYSTEM account.
12987 - Make tor-resolve actually work (?) on Win32.
12988 - Fix a sign bug when getrlimit claims to have 4+ billion
12989 file descriptors available.
12990 - Stop refusing to start when bandwidthburst == bandwidthrate.
12991 - When create cells have been on the onion queue more than five
12992 seconds, just send back a destroy and take them off the list.
12995 Changes in version 0.0.9.4 - 2005-02-03
12996 o Bugfixes on 0.0.9:
12997 - Fix an assert bug that took down most of our servers: when
12998 a server claims to have 1 GB of bandwidthburst, don't
13000 - Don't crash as badly if we have spawned the max allowed number
13001 of dnsworkers, or we're out of file descriptors.
13002 - Block more file-sharing ports in the default exit policy.
13003 - MaxConn is now automatically set to the hard limit of max
13004 file descriptors we're allowed (ulimit -n), minus a few for
13006 - Give a clearer message when servers need to raise their
13007 ulimit -n when they start running out of file descriptors.
13008 - SGI Compatibility patches from Jan Schaumann.
13009 - Tolerate a corrupt cached directory better.
13010 - When a dirserver hasn't approved your server, list which one.
13011 - Go into soft hibernation after 95% of the bandwidth is used,
13012 not 99%. This is especially important for daily hibernators who
13013 have a small accounting max. Hopefully it will result in fewer
13014 cut connections when the hard hibernation starts.
13015 - Load-balance better when using servers that claim more than
13016 800kB/s of capacity.
13017 - Make NT services work (experimental, only used if compiled in).
13020 Changes in version 0.0.9.3 - 2005-01-21
13021 o Bugfixes on 0.0.9:
13022 - Backport the cpu use fixes from main branch, so busy servers won't
13023 need as much processor time.
13024 - Work better when we go offline and then come back, or when we
13025 run Tor at boot before the network is up. We do this by
13026 optimistically trying to fetch a new directory whenever an
13027 application request comes in and we think we're offline -- the
13028 human is hopefully a good measure of when the network is back.
13029 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13030 long as you keep using them; actually publish hidserv descriptors
13031 shortly after they change, rather than waiting 20-40 minutes.
13032 - Enable Mac startup script by default.
13033 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13034 - When you update AllowUnverifiedNodes or FirewallPorts via the
13035 controller's setconf feature, we were always appending, never
13037 - When you update HiddenServiceDir via setconf, it was screwing up
13038 the order of reading the lines, making it fail.
13039 - Do not rewrite a cached directory back to the cache; otherwise we
13040 will think it is recent and not fetch a newer one on startup.
13041 - Workaround for webservers that lie about Content-Encoding: Tor
13042 now tries to autodetect compressed directories and compression
13043 itself. This lets us Proxypass dir fetches through apache.
13046 Changes in version 0.0.9.2 - 2005-01-04
13047 o Bugfixes on 0.0.9 (crashes and asserts):
13048 - Fix an assert on startup when the disk is full and you're logging
13050 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13051 style address, then we'd crash.
13052 - Fix an assert trigger when the running-routers string we get from
13053 a dirserver is broken.
13054 - Make worker threads start and run on win32. Now win32 servers
13056 - Bandaid (not actually fix, but now it doesn't crash) an assert
13057 where the dns worker dies mysteriously and the main Tor process
13058 doesn't remember anything about the address it was resolving.
13060 o Bugfixes on 0.0.9 (Win32):
13061 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13062 name out of the warning/assert messages.
13063 - Fix a superficial "unhandled error on read" bug on win32.
13064 - The win32 installer no longer requires a click-through for our
13065 license, since our Free Software license grants rights but does not
13067 - Win32: When connecting to a dirserver fails, try another one
13068 immediately. (This was already working for non-win32 Tors.)
13069 - Stop trying to parse $HOME on win32 when hunting for default
13071 - Make tor-resolve.c work on win32 by calling network_init().
13073 o Bugfixes on 0.0.9 (other):
13074 - Make 0.0.9.x build on Solaris again.
13075 - Due to a fencepost error, we were blowing away the \n when reporting
13076 confvalue items in the controller. So asking for multiple config
13077 values at once couldn't work.
13078 - When listing circuits that are pending on an opening OR connection,
13079 if we're an OR we were listing circuits that *end* at us as
13080 being pending on every listener, dns/cpu worker, etc. Stop that.
13081 - Dirservers were failing to create 'running-routers' or 'directory'
13082 strings if we had more than some threshold of routers. Fix them so
13083 they can handle any number of routers.
13084 - Fix a superficial "Duplicate mark for close" bug.
13085 - Stop checking for clock skew for OR connections, even for servers.
13086 - Fix a fencepost error that was chopping off the last letter of any
13087 nickname that is the maximum allowed nickname length.
13088 - Update URLs in log messages so they point to the new website.
13089 - Fix a potential problem in mangling server private keys while
13090 writing to disk (not triggered yet, as far as we know).
13091 - Include the licenses for other free software we include in Tor,
13092 now that we're shipping binary distributions more regularly.
13095 Changes in version 0.0.9.1 - 2004-12-15
13096 o Bugfixes on 0.0.9:
13097 - Make hibernation actually work.
13098 - Make HashedControlPassword config option work.
13099 - When we're reporting event circuit status to a controller,
13100 don't use the stream status code.
13103 Changes in version 0.0.9 - 2004-12-12
13105 - Clean up manpage and torrc.sample file.
13106 - Clean up severities and text of log warnings.
13108 - Make servers trigger an assert when they enter hibernation.
13111 Changes in version 0.0.9rc7 - 2004-12-08
13112 o Bugfixes on 0.0.9rc:
13113 - Fix a stack-trashing crash when an exit node begins hibernating.
13114 - Avoid looking at unallocated memory while considering which
13115 ports we need to build circuits to cover.
13116 - Stop a sigpipe: when an 'end' cell races with eof from the app,
13117 we shouldn't hold-open-until-flush if the eof arrived first.
13118 - Fix a bug with init_cookie_authentication() in the controller.
13119 - When recommending new-format log lines, if the upper bound is
13120 LOG_ERR, leave it implicit.
13122 o Bugfixes on 0.0.8.1:
13123 - Fix a whole slew of memory leaks.
13124 - Fix isspace() and friends so they still make Solaris happy
13125 but also so they don't trigger asserts on win32.
13126 - Fix parse_iso_time on platforms without strptime (eg win32).
13127 - win32: tolerate extra "readable" events better.
13128 - win32: when being multithreaded, leave parent fdarray open.
13129 - Make unit tests work on win32.
13132 Changes in version 0.0.9rc6 - 2004-12-06
13133 o Bugfixes on 0.0.9pre:
13134 - Clean up some more integer underflow opportunities (not exploitable
13136 - While hibernating, hup should not regrow our listeners.
13137 - Send an end to the streams we close when we hibernate, rather
13138 than just chopping them off.
13139 - React to eof immediately on non-open edge connections.
13141 o Bugfixes on 0.0.8.1:
13142 - Calculate timeout for waiting for a connected cell from the time
13143 we sent the begin cell, not from the time the stream started. If
13144 it took a long time to establish the circuit, we would time out
13145 right after sending the begin cell.
13146 - Fix router_compare_addr_to_addr_policy: it was not treating a port
13147 of * as always matching, so we were picking reject *:* nodes as
13148 exit nodes too. Oops.
13151 - New circuit building strategy: keep a list of ports that we've
13152 used in the past 6 hours, and always try to have 2 circuits open
13153 or on the way that will handle each such port. Seed us with port
13154 80 so web users won't complain that Tor is "slow to start up".
13155 - Make kill -USR1 dump more useful stats about circuits.
13156 - When warning about retrying or giving up, print the address, so
13157 the user knows which one it's talking about.
13158 - If you haven't used a clean circuit in an hour, throw it away,
13159 just to be on the safe side. (This means after 6 hours a totally
13160 unused Tor client will have no circuits open.)
13163 Changes in version 0.0.9rc5 - 2004-12-01
13164 o Bugfixes on 0.0.8.1:
13165 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
13166 - Let resolve conns retry/expire also, rather than sticking around
13168 - If we are using select, make sure we stay within FD_SETSIZE.
13170 o Bugfixes on 0.0.9pre:
13171 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
13172 but doesn't seem to be currently; thanks to Ilja van Sprundel for
13174 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
13175 instead. Impose minima and maxima for all *Period options; impose
13176 even tighter maxima for fetching if we are a caching dirserver.
13177 Clip rather than rejecting.
13178 - Fetch cached running-routers from servers that serve it (that is,
13179 authdirservers and servers running 0.0.9rc5-cvs or later.)
13182 - Accept *:706 (silc) in default exit policy.
13183 - Implement new versioning format for post 0.1.
13184 - Support "foo.nickname.exit" addresses, to let Alice request the
13185 address "foo" as viewed by exit node "nickname". Based on a patch
13187 - Make tor --version --version dump the cvs Id of every file.
13190 Changes in version 0.0.9rc4 - 2004-11-28
13191 o Bugfixes on 0.0.8.1:
13192 - Make windows sockets actually non-blocking (oops), and handle
13193 win32 socket errors better.
13195 o Bugfixes on 0.0.9rc1:
13196 - Actually catch the -USR2 signal.
13199 Changes in version 0.0.9rc3 - 2004-11-25
13200 o Bugfixes on 0.0.8.1:
13201 - Flush the log file descriptor after we print "Tor opening log file",
13202 so we don't see those messages days later.
13204 o Bugfixes on 0.0.9rc1:
13205 - Make tor-resolve work again.
13206 - Avoid infinite loop in tor-resolve if tor hangs up on it.
13207 - Fix an assert trigger for clients/servers handling resolves.
13210 Changes in version 0.0.9rc2 - 2004-11-24
13211 o Bugfixes on 0.0.9rc1:
13212 - I broke socks5 support while fixing the eof bug.
13213 - Allow unitless bandwidths and intervals; they default to bytes
13215 - New servers don't start out hibernating; they are active until
13216 they run out of bytes, so they have a better estimate of how
13217 long it takes, and so their operators can know they're working.
13220 Changes in version 0.0.9rc1 - 2004-11-23
13221 o Bugfixes on 0.0.8.1:
13222 - Finally fix a bug that's been plaguing us for a year:
13223 With high load, circuit package window was reaching 0. Whenever
13224 we got a circuit-level sendme, we were reading a lot on each
13225 socket, but only writing out a bit. So we would eventually reach
13226 eof. This would be noticed and acted on even when there were still
13227 bytes sitting in the inbuf.
13228 - When poll() is interrupted, we shouldn't believe the revents values.
13230 o Bugfixes on 0.0.9pre6:
13231 - Fix hibernate bug that caused pre6 to be broken.
13232 - Don't keep rephist info for routers that haven't had activity for
13233 24 hours. (This matters now that clients have keys, since we track
13235 - Never call close_temp_logs while validating log options.
13236 - Fix backslash-escaping on tor.sh.in and torctl.in.
13239 - Implement weekly/monthly/daily accounting: now you specify your
13240 hibernation properties by
13241 AccountingMax N bytes|KB|MB|GB|TB
13242 AccountingStart day|week|month [day] HH:MM
13243 Defaults to "month 1 0:00".
13244 - Let bandwidth and interval config options be specified as 5 bytes,
13245 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
13246 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
13247 get back to normal.)
13248 - If your requested entry or exit node has advertised bandwidth 0,
13250 - Be more greedy about filling up relay cells -- we try reading again
13251 once we've processed the stuff we read, in case enough has arrived
13252 to fill the last cell completely.
13253 - Apply NT service patch from Osamu Fujino. Still needs more work.
13256 Changes in version 0.0.9pre6 - 2004-11-15
13257 o Bugfixes on 0.0.8.1:
13258 - Fix assert failure on malformed socks4a requests.
13259 - Use identity comparison, not nickname comparison, to choose which
13260 half of circuit-ID-space each side gets to use. This is needed
13261 because sometimes we think of a router as a nickname, and sometimes
13262 as a hex ID, and we can't predict what the other side will do.
13263 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
13264 write() call will fail and we handle it there.
13265 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
13266 and smartlist_len, which are two major profiling offenders.
13268 o Bugfixes on 0.0.9pre5:
13269 - Fix a bug in read_all that was corrupting config files on windows.
13270 - When we're raising the max number of open file descriptors to
13271 'unlimited', don't log that we just raised it to '-1'.
13272 - Include event code with events, as required by control-spec.txt.
13273 - Don't give a fingerprint when clients do --list-fingerprint:
13274 it's misleading, because it will never be the same again.
13275 - Stop using strlcpy in tor_strndup, since it was slowing us
13277 - Remove warn on startup about missing cached-directory file.
13278 - Make kill -USR1 work again.
13279 - Hibernate if we start tor during the "wait for wakeup-time" phase
13280 of an accounting interval. Log our hibernation plans better.
13281 - Authoritative dirservers now also cache their directory, so they
13282 have it on start-up.
13285 - Fetch running-routers; cache running-routers; compress
13286 running-routers; serve compressed running-routers.z
13287 - Add NSI installer script contributed by J Doe.
13288 - Commit VC6 and VC7 workspace/project files.
13289 - Commit a tor.spec for making RPM files, with help from jbash.
13290 - Add contrib/torctl.in contributed by Glenn Fink.
13291 - Implement the control-spec's SAVECONF command, to write your
13292 configuration to torrc.
13293 - Get cookie authentication for the controller closer to working.
13294 - Include control-spec.txt in the tarball.
13295 - When set_conf changes our server descriptor, upload a new copy.
13296 But don't upload it too often if there are frequent changes.
13297 - Document authentication config in man page, and document signals
13299 - Clean up confusing parts of man page and torrc.sample.
13300 - Make expand_filename handle ~ and ~username.
13301 - Use autoconf to enable largefile support where necessary. Use
13302 ftello where available, since ftell can fail at 2GB.
13303 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
13304 log more informatively.
13305 - Give a slightly more useful output for "tor -h".
13306 - Refuse application socks connections to port 0.
13307 - Check clock skew for verified servers, but allow unverified
13308 servers and clients to have any clock skew.
13309 - Break DirFetchPostPeriod into:
13310 - DirFetchPeriod for fetching full directory,
13311 - StatusFetchPeriod for fetching running-routers,
13312 - DirPostPeriod for posting server descriptor,
13313 - RendPostPeriod for posting hidden service descriptors.
13314 - Make sure the hidden service descriptors are at a random offset
13315 from each other, to hinder linkability.
13318 Changes in version 0.0.9pre5 - 2004-11-09
13319 o Bugfixes on 0.0.9pre4:
13320 - Fix a seg fault in unit tests (doesn't affect main program).
13321 - Fix an assert bug where a hidden service provider would fail if
13322 the first hop of his rendezvous circuit was down.
13323 - Hidden service operators now correctly handle version 1 style
13324 INTRODUCE1 cells (nobody generates them still, so not a critical
13326 - If do_hup fails, actually notice.
13327 - Handle more errnos from accept() without closing the listener.
13328 Some OpenBSD machines were closing their listeners because
13329 they ran out of file descriptors.
13330 - Send resolve cells to exit routers that are running a new
13331 enough version of the resolve code to work right.
13332 - Better handling of winsock includes on non-MSV win32 compilers.
13333 - Some people had wrapped their tor client/server in a script
13334 that would restart it whenever it died. This did not play well
13335 with our "shut down if your version is obsolete" code. Now people
13336 don't fetch a new directory if their local cached version is
13338 - Make our autogen.sh work on ksh as well as bash.
13341 - Hibernation: New config option "AccountingMaxKB" lets you
13342 set how many KBytes per month you want to allow your server to
13343 consume. Rather than spreading those bytes out evenly over the
13344 month, we instead hibernate for some of the month and pop up
13345 at a deterministic time, work until the bytes are consumed, then
13346 hibernate again. Config option "MonthlyAccountingStart" lets you
13347 specify which day of the month your billing cycle starts on.
13348 - Control interface: a separate program can now talk to your
13349 client/server over a socket, and get/set config options, receive
13350 notifications of circuits and streams starting/finishing/dying,
13351 bandwidth used, etc. The next step is to get some GUIs working.
13352 Let us know if you want to help out. See doc/control-spec.txt .
13353 - Ship a contrib/tor-control.py as an example script to interact
13354 with the control port.
13355 - "tor --hash-password zzyxz" will output a salted password for
13356 use in authenticating to the control interface.
13357 - New log format in config:
13358 "Log minsev[-maxsev] stdout|stderr|syslog" or
13359 "Log minsev[-maxsev] file /var/foo"
13362 - DirPolicy config option, to let people reject incoming addresses
13363 from their dirserver.
13364 - "tor --list-fingerprint" will list your identity key fingerprint
13366 - Add "pass" target for RedirectExit, to make it easier to break
13367 out of a sequence of RedirectExit rules.
13368 - Clients now generate a TLS cert too, in preparation for having
13369 them act more like real nodes.
13370 - Ship src/win32/ in the tarball, so people can use it to build.
13371 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
13373 - New "router-status" line in directory, to better bind each verified
13374 nickname to its identity key.
13375 - Deprecate unofficial config option abbreviations, and abbreviations
13376 not on the command line.
13377 - Add a pure-C tor-resolve implementation.
13378 - Use getrlimit and friends to ensure we can reach MaxConn (currently
13379 1024) file descriptors.
13381 o Code security improvements, inspired by Ilja:
13382 - Replace sprintf with snprintf. (I think they were all safe, but
13384 - Replace strcpy/strncpy with strlcpy in more places.
13385 - Avoid strcat; use snprintf or strlcat instead.
13386 - snprintf wrapper with consistent (though not C99) overflow behavior.
13389 Changes in version 0.0.9pre4 - 2004-10-17
13390 o Bugfixes on 0.0.9pre3:
13391 - If the server doesn't specify an exit policy, use the real default
13392 exit policy, not reject *:*.
13393 - Ignore fascistfirewall when uploading/downloading hidden service
13394 descriptors, since we go through Tor for those; and when using
13395 an HttpProxy, since we assume it can reach them all.
13396 - When looking for an authoritative dirserver, use only the ones
13397 configured at boot. Don't bother looking in the directory.
13398 - The rest of the fix for get_default_conf_file() on older win32.
13399 - Make 'Routerfile' config option obsolete.
13402 - New 'MyFamily nick1,...' config option for a server to
13403 specify other servers that shouldn't be used in the same circuit
13404 with it. Only believed if nick1 also specifies us.
13405 - New 'NodeFamily nick1,nick2,...' config option for a client to
13406 specify nodes that it doesn't want to use in the same circuit.
13407 - New 'Redirectexit pattern address:port' config option for a
13408 server to redirect exit connections, e.g. to a local squid.
13411 Changes in version 0.0.9pre3 - 2004-10-13
13412 o Bugfixes on 0.0.8.1:
13413 - Better torrc example lines for dirbindaddress and orbindaddress.
13414 - Improved bounds checking on parsed ints (e.g. config options and
13415 the ones we find in directories.)
13416 - Better handling of size_t vs int, so we're more robust on 64
13418 - Fix the rest of the bug where a newly started OR would appear
13419 as unverified even after we've added his fingerprint and hupped
13421 - Fix a bug from 0.0.7: when read() failed on a stream, we would
13422 close it without sending back an end. So 'connection refused'
13423 would simply be ignored and the user would get no response.
13425 o Bugfixes on 0.0.9pre2:
13426 - Serving the cached-on-disk directory to people is bad. We now
13427 provide no directory until we've fetched a fresh one.
13428 - Workaround for bug on windows where cached-directories get crlf
13430 - Make get_default_conf_file() work on older windows too.
13431 - If we write a *:* exit policy line in the descriptor, don't write
13432 any more exit policy lines.
13435 - Use only 0.0.9pre1 and later servers for resolve cells.
13436 - Make the dirservers file obsolete.
13437 - Include a dir-signing-key token in directories to tell the
13438 parsing entity which key is being used to sign.
13439 - Remove the built-in bulky default dirservers string.
13440 - New config option "Dirserver %s:%d [fingerprint]", which can be
13441 repeated as many times as needed. If no dirservers specified,
13442 default to moria1,moria2,tor26.
13443 - Make moria2 advertise a dirport of 80, so people behind firewalls
13444 will be able to get a directory.
13445 - Http proxy support
13446 - Dirservers translate requests for http://%s:%d/x to /x
13447 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
13448 be routed through this host.
13449 - Clients ask for /tor/x rather than /x for new enough dirservers.
13450 This way we can one day coexist peacefully with apache.
13451 - Clients specify a "Host: %s%d" http header, to be compatible
13452 with more proxies, and so running squid on an exit node can work.
13455 Changes in version 0.0.8.1 - 2004-10-13
13457 - Fix a seg fault that can be triggered remotely for Tor
13458 clients/servers with an open dirport.
13459 - Fix a rare assert trigger, where routerinfos for entries in
13460 our cpath would expire while we're building the path.
13461 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13462 - Fix a rare seg fault for people running hidden services on
13463 intermittent connections.
13464 - Fix a bug in parsing opt keywords with objects.
13465 - Fix a stale pointer assert bug when a stream detaches and
13467 - Fix a string format vulnerability (probably not exploitable)
13468 in reporting stats locally.
13469 - Fix an assert trigger: sometimes launching circuits can fail
13470 immediately, e.g. because too many circuits have failed recently.
13471 - Fix a compile warning on 64 bit platforms.
13474 Changes in version 0.0.9pre2 - 2004-10-03
13476 - Make fetching a cached directory work for 64-bit platforms too.
13477 - Make zlib.h a required header, not an optional header.
13480 Changes in version 0.0.9pre1 - 2004-10-01
13482 - Stop using separate defaults for no-config-file and
13483 empty-config-file. Now you have to explicitly turn off SocksPort,
13484 if you don't want it open.
13485 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13486 - Improve man page to mention more of the 0.0.8 features.
13487 - Fix a rare seg fault for people running hidden services on
13488 intermittent connections.
13489 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
13491 - Fix more dns related bugs: send back resolve_failed and end cells
13492 more reliably when the resolve fails, rather than closing the
13493 circuit and then trying to send the cell. Also attach dummy resolve
13494 connections to a circuit *before* calling dns_resolve(), to fix
13495 a bug where cached answers would never be sent in RESOLVED cells.
13496 - When we run out of disk space, or other log writing error, don't
13497 crash. Just stop logging to that log and continue.
13498 - We were starting to daemonize before we opened our logs, so if
13499 there were any problems opening logs, we would complain to stderr,
13500 which wouldn't work, and then mysteriously exit.
13501 - Fix a rare bug where sometimes a verified OR would connect to us
13502 before he'd uploaded his descriptor, which would cause us to
13503 assign conn->nickname as though he's unverified. Now we look through
13504 the fingerprint list to see if he's there.
13505 - Fix a rare assert trigger, where routerinfos for entries in
13506 our cpath would expire while we're building the path.
13509 - Clients can ask dirservers for /dir.z to get a compressed version
13510 of the directory. Only works for servers running 0.0.9, of course.
13511 - Make clients cache directories and use them to seed their router
13512 lists at startup. This means clients have a datadir again.
13513 - Configuration infrastructure support for warning on obsolete
13515 - Respond to content-encoding headers by trying to uncompress as
13517 - Reply with a deflated directory when a client asks for "dir.z".
13518 We could use allow-encodings instead, but allow-encodings isn't
13519 specified in HTTP 1.0.
13520 - Raise the max dns workers from 50 to 100.
13521 - Discourage people from setting their dirfetchpostperiod more often
13522 than once per minute.
13523 - Protect dirservers from overzealous descriptor uploading -- wait
13524 10 seconds after directory gets dirty, before regenerating.
13527 Changes in version 0.0.8 - 2004-08-25
13528 o Port it to SunOS 5.9 / Athena
13531 Changes in version 0.0.8rc2 - 2004-08-20
13532 o Make it compile on cygwin again.
13533 o When picking unverified routers, skip those with low uptime and/or
13534 low bandwidth, depending on what properties you care about.
13537 Changes in version 0.0.8rc1 - 2004-08-18
13538 o Changes from 0.0.7.3:
13540 - Fix assert triggers: if the other side returns an address 0.0.0.0,
13541 don't put it into the client dns cache.
13542 - If a begin failed due to exit policy, but we believe the IP address
13543 should have been allowed, switch that router to exitpolicy reject *:*
13544 until we get our next directory.
13546 - Clients choose nodes proportional to advertised bandwidth.
13547 - Avoid using nodes with low uptime as introduction points.
13548 - Handle servers with dynamic IP addresses: don't replace
13549 options->Address with the resolved one at startup, and
13550 detect our address right before we make a routerinfo each time.
13551 - 'FascistFirewall' option to pick dirservers and ORs on specific
13552 ports; plus 'FirewallPorts' config option to tell FascistFirewall
13553 which ports are open. (Defaults to 80,443)
13554 - Be more aggressive about trying to make circuits when the network
13555 has changed (e.g. when you unsuspend your laptop).
13556 - Check for time skew on http headers; report date in response to
13558 - If the entrynode config line has only one node, don't pick it as
13560 - Add strict{entry|exit}nodes config options. If set to 1, then
13561 we refuse to build circuits that don't include the specified entry
13563 - OutboundBindAddress config option, to bind to a specific
13564 IP address for outgoing connect()s.
13565 - End truncated log entries (e.g. directories) with "[truncated]".
13567 o Patches to 0.0.8preX:
13569 - Patches to compile and run on win32 again (maybe)?
13570 - Fix crash when looking for ~/.torrc with no $HOME set.
13571 - Fix a race bug in the unit tests.
13572 - Handle verified/unverified name collisions better when new
13573 routerinfo's arrive in a directory.
13574 - Sometimes routers were getting entered into the stats before
13575 we'd assigned their identity_digest. Oops.
13576 - Only pick and establish intro points after we've gotten a
13579 - AllowUnverifiedNodes config option to let circuits choose no-name
13580 routers in entry,middle,exit,introduction,rendezvous positions.
13581 Allow middle and rendezvous positions by default.
13582 - Add a man page for tor-resolve.
13585 Changes in version 0.0.7.3 - 2004-08-12
13586 o Stop dnsworkers from triggering an assert failure when you
13587 ask them to resolve the host "".
13590 Changes in version 0.0.8pre3 - 2004-08-09
13591 o Changes from 0.0.7.2:
13592 - Allow multiple ORs with same nickname in routerlist -- now when
13593 people give us one identity key for a nickname, then later
13594 another, we don't constantly complain until the first expires.
13595 - Remember used bandwidth (both in and out), and publish 15-minute
13596 snapshots for the past day into our descriptor.
13597 - You can now fetch $DIRURL/running-routers to get just the
13598 running-routers line, not the whole descriptor list. (But
13599 clients don't use this yet.)
13600 - When people mistakenly use Tor as an http proxy, point them
13601 at the tor-doc.html rather than the INSTALL.
13602 - Remove our mostly unused -- and broken -- hex_encode()
13603 function. Use base16_encode() instead. (Thanks to Timo Lindfors
13604 for pointing out this bug.)
13605 - Rotate onion keys every 12 hours, not every 2 hours, so we have
13606 fewer problems with people using the wrong key.
13607 - Change the default exit policy to reject the default edonkey,
13608 kazaa, gnutella ports.
13609 - Add replace_file() to util.[ch] to handle win32's rename().
13611 o Changes from 0.0.8preX:
13612 - Fix two bugs in saving onion keys to disk when rotating, so
13613 hopefully we'll get fewer people using old onion keys.
13614 - Fix an assert error that was making SocksPolicy not work.
13615 - Be willing to expire routers that have an open dirport -- it's
13616 just the authoritative dirservers we want to not forget.
13617 - Reject tor-resolve requests for .onion addresses early, so we
13618 don't build a whole rendezvous circuit and then fail.
13619 - When you're warning a server that he's unverified, don't cry
13620 wolf unpredictably.
13621 - Fix a race condition: don't try to extend onto a connection
13622 that's still handshaking.
13623 - For servers in clique mode, require the conn to be open before
13624 you'll choose it for your path.
13625 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
13626 end relay cell, etc.
13627 - Measure bandwidth capacity over the last 24 hours, not just 12
13628 - Bugfix: authoritative dirservers were making and signing a new
13629 directory for each client, rather than reusing the cached one.
13632 Changes in version 0.0.8pre2 - 2004-08-04
13633 o Changes from 0.0.7.2:
13635 - Check directory signature _before_ you decide whether you're
13636 you're running an obsolete version and should exit.
13637 - Check directory signature _before_ you parse the running-routers
13638 list to decide who's running or verified.
13639 - Bugfixes and features:
13640 - Check return value of fclose while writing to disk, so we don't
13641 end up with broken files when servers run out of disk space.
13642 - Log a warning if the user uses an unsafe socks variant, so people
13643 are more likely to learn about privoxy or socat.
13644 - Dirservers now include RFC1123-style dates in the HTTP headers,
13645 which one day we will use to better detect clock skew.
13647 o Changes from 0.0.8pre1:
13648 - Make it compile without warnings again on win32.
13649 - Log a warning if you're running an unverified server, to let you
13650 know you might want to get it verified.
13651 - Only pick a default nickname if you plan to be a server.
13654 Changes in version 0.0.8pre1 - 2004-07-23
13656 - Made our unit tests compile again on OpenBSD 3.5, and tor
13657 itself compile again on OpenBSD on a sparc64.
13658 - We were neglecting milliseconds when logging on win32, so
13659 everything appeared to happen at the beginning of each second.
13661 o Protocol changes:
13662 - 'Extend' relay cell payloads now include the digest of the
13663 intended next hop's identity key. Now we can verify that we're
13664 extending to the right router, and also extend to routers we
13665 hadn't heard of before.
13668 - Tor nodes can now act as relays (with an advertised ORPort)
13669 without being manually verified by the dirserver operators.
13670 - Uploaded descriptors of unverified routers are now accepted
13671 by the dirservers, and included in the directory.
13672 - Verified routers are listed by nickname in the running-routers
13673 list; unverified routers are listed as "$<fingerprint>".
13674 - We now use hash-of-identity-key in most places rather than
13675 nickname or addr:port, for improved security/flexibility.
13676 - To avoid Sybil attacks, paths still use only verified servers.
13677 But now we have a chance to play around with hybrid approaches.
13678 - Nodes track bandwidth usage to estimate capacity (not used yet).
13679 - ClientOnly option for nodes that never want to become servers.
13680 - Directory caching.
13681 - "AuthoritativeDir 1" option for the official dirservers.
13682 - Now other nodes (clients and servers) will cache the latest
13683 directory they've pulled down.
13684 - They can enable their DirPort to serve it to others.
13685 - Clients will pull down a directory from any node with an open
13686 DirPort, and check the signature/timestamp correctly.
13687 - Authoritative dirservers now fetch directories from other
13688 authdirservers, to stay better synced.
13689 - Running-routers list tells who's down also, along with noting
13690 if they're verified (listed by nickname) or unverified (listed
13692 - Allow dirservers to serve running-router list separately.
13693 This isn't used yet.
13694 - ORs connect-on-demand to other ORs
13695 - If you get an extend cell to an OR you're not connected to,
13696 connect, handshake, and forward the create cell.
13697 - The authoritative dirservers stay connected to everybody,
13698 and everybody stays connected to 0.0.7 servers, but otherwise
13699 clients/servers expire unused connections after 5 minutes.
13700 - When servers get a sigint, they delay 30 seconds (refusing new
13701 connections) then exit. A second sigint causes immediate exit.
13702 - File and name management:
13703 - Look for .torrc if no CONFDIR "torrc" is found.
13704 - If no datadir is defined, then choose, make, and secure ~/.tor
13706 - If torrc not found, exitpolicy reject *:*.
13707 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13708 - If no nickname is defined, derive default from hostname.
13709 - Rename secret key files, e.g. identity.key -> secret_id_key,
13710 to discourage people from mailing their identity key to tor-ops.
13711 - Refuse to build a circuit before the directory has arrived --
13712 it won't work anyway, since you won't know the right onion keys
13714 - Try other dirservers immediately if the one you try is down. This
13715 should tolerate down dirservers better now.
13716 - Parse tor version numbers so we can do an is-newer-than check
13717 rather than an is-in-the-list check.
13718 - New socks command 'resolve', to let us shim gethostbyname()
13720 - A 'tor_resolve' script to access the socks resolve functionality.
13721 - A new socks-extensions.txt doc file to describe our
13722 interpretation and extensions to the socks protocols.
13723 - Add a ContactInfo option, which gets published in descriptor.
13724 - Publish OR uptime in descriptor (and thus in directory) too.
13725 - Write tor version at the top of each log file
13726 - New docs in the tarball:
13728 - Document that you should proxy your SSL traffic too.
13731 Changes in version 0.0.7.2 - 2004-07-07
13732 o A better fix for the 0.0.0.0 problem, that will hopefully
13733 eliminate the remaining related assertion failures.
13736 Changes in version 0.0.7.1 - 2004-07-04
13737 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
13738 since internally we use 0.0.0.0 to signify "not yet resolved".
13741 Changes in version 0.0.7 - 2004-06-07
13742 o Updated the man page to reflect the new features.
13745 Changes in version 0.0.7rc2 - 2004-06-06
13746 o Changes from 0.0.7rc1:
13747 - Make it build on Win32 again.
13748 o Changes from 0.0.6.2:
13749 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
13753 Changes in version 0.0.7rc1 - 2004-06-02
13755 - On sighup, we were adding another log without removing the first
13756 one. So log messages would get duplicated n times for n sighups.
13757 - Several cases of using a connection after we'd freed it. The
13758 problem was that connections that are pending resolve are in both
13759 the pending_resolve tree, and also the circuit's resolving_streams
13760 list. When you want to remove one, you must remove it from both.
13761 - Fix a double-mark-for-close where an end cell arrived for a
13762 resolving stream, and then the resolve failed.
13763 - Check directory signatures based on name of signer, not on whom
13764 we got the directory from. This will let us cache directories more
13767 - Crank up some of our constants to handle more users.
13770 Changes in version 0.0.7pre1 - 2004-06-02
13771 o Fixes for crashes and other obnoxious bugs:
13772 - Fix an epipe bug: sometimes when directory connections failed
13773 to connect, we would give them a chance to flush before closing
13775 - When we detached from a circuit because of resolvefailed, we
13776 would immediately try the same circuit twice more, and then
13777 give up on the resolve thinking we'd tried three different
13779 - Limit the number of intro circuits we'll attempt to build for a
13780 hidden service per 15-minute period.
13781 - Check recommended-software string *early*, before actually parsing
13782 the directory. Thus we can detect an obsolete version and exit,
13783 even if the new directory format doesn't parse.
13784 o Fixes for security bugs:
13785 - Remember which nodes are dirservers when you startup, and if a
13786 random OR enables his dirport, don't automatically assume he's
13787 a trusted dirserver.
13789 - Directory connections were asking the wrong poll socket to
13790 start writing, and not asking themselves to start writing.
13791 - When we detached from a circuit because we sent a begin but
13792 didn't get a connected, we would use it again the first time;
13793 but after that we would correctly switch to a different one.
13794 - Stop warning when the first onion decrypt attempt fails; they
13795 will sometimes legitimately fail now that we rotate keys.
13796 - Override unaligned-access-ok check when $host_cpu is ia64 or
13797 arm. Apparently they allow it but the kernel whines.
13798 - Dirservers try to reconnect periodically too, in case connections
13800 - Fix some memory leaks in directory servers.
13801 - Allow backslash in Win32 filenames.
13802 - Made Tor build complain-free on FreeBSD, hopefully without
13803 breaking other BSD builds. We'll see.
13805 - Doxygen markup on all functions and global variables.
13806 - Make directory functions update routerlist, not replace it. So
13807 now directory disagreements are not so critical a problem.
13808 - Remove the upper limit on number of descriptors in a dirserver's
13809 directory (not that we were anywhere close).
13810 - Allow multiple logfiles at different severity ranges.
13811 - Allow *BindAddress to specify ":port" rather than setting *Port
13812 separately. Allow multiple instances of each BindAddress config
13813 option, so you can bind to multiple interfaces if you want.
13814 - Allow multiple exit policy lines, which are processed in order.
13815 Now we don't need that huge line with all the commas in it.
13816 - Enable accept/reject policies on SOCKS connections, so you can bind
13817 to 0.0.0.0 but still control who can use your OP.
13820 Changes in version 0.0.6.2 - 2004-05-16
13821 o Our integrity-checking digest was checking only the most recent cell,
13822 not the previous cells like we'd thought.
13823 Thanks to Stefan Mark for finding the flaw!
13826 Changes in version 0.0.6.1 - 2004-05-06
13827 o Fix two bugs in our AES counter-mode implementation (this affected
13828 onion-level stream encryption, but not TLS-level). It turns
13829 out we were doing something much more akin to a 16-character
13830 polyalphabetic cipher. Oops.
13831 Thanks to Stefan Mark for finding the flaw!
13832 o Retire moria3 as a directory server, and add tor26 as a directory
13836 Changes in version 0.0.6 - 2004-05-02
13837 [version bump only]
13840 Changes in version 0.0.6rc4 - 2004-05-01
13841 o Update the built-in dirservers list to use the new directory format
13842 o Fix a rare seg fault: if a node offering a hidden service attempts
13843 to build a circuit to Alice's rendezvous point and fails before it
13844 reaches the last hop, it retries with a different circuit, but
13846 o Handle windows socket errors correctly.
13849 Changes in version 0.0.6rc3 - 2004-04-28
13850 o Don't expire non-general excess circuits (if we had enough
13851 circuits open, we were expiring rendezvous circuits -- even
13852 when they had a stream attached. oops.)
13853 o Fetch randomness from /dev/urandom better (not via fopen/fread)
13854 o Better debugging for tls errors
13855 o Some versions of openssl have an SSL_pending function that erroneously
13856 returns bytes when there is a non-application record pending.
13857 o Set Content-Type on the directory and hidserv descriptor.
13858 o Remove IVs from cipher code, since AES-ctr has none.
13859 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13860 o We were using an array of length zero in a few places.
13861 o win32's gethostbyname can't resolve an IP to an IP.
13862 o win32's close can't close a socket.
13865 Changes in version 0.0.6rc2 - 2004-04-26
13866 o Fix a bug where we were closing tls connections intermittently.
13867 It turns out openssl keeps its errors around -- so if an error
13868 happens, and you don't ask about it, and then another openssl
13869 operation happens and succeeds, and you ask if there was an error,
13870 it tells you about the first error. Fun fun.
13871 o Fix a bug that's been lurking since 27 may 03 (!)
13872 When passing back a destroy cell, we would use the wrong circ id.
13873 'Mostly harmless', but still worth fixing.
13874 o Since we don't support truncateds much, don't bother sending them;
13875 just close the circ.
13876 o check for <machine/limits.h> so we build on NetBSD again (I hope).
13877 o don't crash if a conn that sent a begin has suddenly lost its circuit
13878 (this was quite rare).
13881 Changes in version 0.0.6rc1 - 2004-04-25
13882 o We now rotate link (tls context) keys and onion keys.
13883 o CREATE cells now include oaep padding, so you can tell
13884 if you decrypted them correctly.
13885 o Add bandwidthburst to server descriptor.
13886 o Directories now say which dirserver signed them.
13887 o Use a tor_assert macro that logs failed assertions too.
13890 Changes in version 0.0.6pre5 - 2004-04-18
13891 o changes from 0.0.6pre4:
13892 - make tor build on broken freebsd 5.2 installs
13893 - fix a failed assert when you try an intro point, get a nack, and try
13894 a second one and it works.
13895 - when alice uses a port that the hidden service doesn't accept,
13896 it now sends back an end cell (denied by exit policy). otherwise
13897 alice would just have to wait to time out.
13898 - fix another rare bug: when we had tried all the intro
13899 points for a hidden service, we fetched the descriptor
13900 again, but we left our introcirc thinking it had already
13901 sent an intro, so it kept waiting for a response...
13902 - bugfix: when you sleep your hidden-service laptop, as soon
13903 as it wakes up it tries to upload a service descriptor, but
13904 socketpair fails for some reason (localhost not up yet?).
13905 now we simply give up on that upload, and we'll try again later.
13906 i'd still like to find the bug though.
13907 - if an intro circ waiting for an ack dies before getting one, then
13909 - we were reusing stale service descriptors and refetching usable
13913 Changes in version 0.0.6pre4 - 2004-04-14
13914 o changes from 0.0.6pre3:
13915 - when bob fails to connect to the rendezvous point, and his
13916 circ didn't fail because of the rendezvous point itself, then
13917 he retries a couple of times
13918 - we expire introduction and rendezvous circs more thoroughly
13919 (sometimes they were hanging around forever)
13920 - we expire unattached rendezvous streams that have been around
13921 too long (they were sticking around forever).
13922 - fix a measly fencepost error that was crashing everybody with
13926 Changes in version 0.0.6pre3 - 2004-04-14
13927 o changes from 0.0.6pre2:
13928 - make hup work again
13929 - fix some memory leaks for dirservers
13930 - allow more skew in rendezvous descriptor timestamps, to help
13931 handle people like blanu who don't know what time it is
13932 - normal circs are 3 hops, but some rend/intro circs are 4, if
13933 the initiator doesn't get to choose the last hop
13934 - send acks for introductions, so alice can know whether to try
13936 - bob publishes intro points more correctly
13937 o changes from 0.0.5:
13938 - fix an assert trigger that's been plaguing us since the days
13939 of 0.0.2prexx (thanks weasel!)
13940 - retry stream correctly when we fail to connect because of
13941 exit-policy-reject (should try another) or can't-resolve-address
13942 (also should try another, because dns on random internet servers
13944 - when we hup a dirserver and we've *removed* a server from the
13945 approved-routers list, now we remove that server from the
13946 in-memory directories too
13949 Changes in version 0.0.6pre2 - 2004-04-08
13950 o We fixed our base32 implementation. Now it works on all architectures.
13953 Changes in version 0.0.6pre1 - 2004-04-08
13955 - Hidden services and rendezvous points are implemented. Go to
13956 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13957 hidden services. (This only works via a socks4a proxy such as
13958 Privoxy, and currently it's quite slow.)
13961 Changes in version 0.0.5 - 2004-03-30
13962 [version bump only]
13965 Changes in version 0.0.5rc3 - 2004-03-29
13966 o Install torrc as torrc.sample -- we no longer clobber your
13968 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13969 o Add in a 'notice' log level for things the operator should hear
13970 but that aren't warnings
13973 Changes in version 0.0.5rc2 - 2004-03-29
13974 o Hold socks connection open until reply is flushed (if possible)
13975 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13976 the dns farm to do it.
13977 o Fix c99 aliasing warnings in rephist.c
13978 o Don't include server descriptors that are older than 24 hours in the
13980 o Give socks 'reject' replies their whole 15s to attempt to flush,
13981 rather than seeing the 60s timeout and assuming the flush had failed.
13982 o Clean automake droppings from the cvs repository
13985 Changes in version 0.0.5rc1 - 2004-03-28
13986 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13987 o Only build circuits after we've fetched the directory: clients were
13988 using only the directory servers before they'd fetched a directory.
13989 This also means longer startup time; so it goes.
13990 o Fix an assert trigger where an OP would fail to handshake, and we'd
13991 expect it to have a nickname.
13992 o Work around a tsocks bug: do a socks reject when AP connection dies
13993 early, else tsocks goes into an infinite loop.
13996 Changes in version 0.0.4 - 2004-03-26
13997 o When connecting to a dirserver or OR and the network is down,
14001 Changes in version 0.0.3 - 2004-03-26
14002 o Warn and fail if server chose a nickname with illegal characters
14003 o Port to Solaris and Sparc:
14004 - include missing header fcntl.h
14005 - have autoconf find -lsocket -lnsl automatically
14006 - deal with hardware word alignment
14007 - make uname() work (solaris has a different return convention)
14008 - switch from using signal() to sigaction()
14009 o Preliminary work on reputation system:
14010 - Keep statistics on success/fail of connect attempts; they're published
14011 by kill -USR1 currently.
14012 - Add a RunTesting option to try to learn link state by creating test
14013 circuits, even when SocksPort is off.
14014 - Remove unused open circuits when there are too many.
14017 Changes in version 0.0.2 - 2004-03-19
14018 - Include strlcpy and strlcat for safer string ops
14019 - define INADDR_NONE so we compile (but still not run) on solaris
14022 Changes in version 0.0.2pre27 - 2004-03-14
14024 - Allow internal tor networks (we were rejecting internal IPs,
14025 now we allow them if they're set explicitly).
14026 - And fix a few endian issues.
14029 Changes in version 0.0.2pre26 - 2004-03-14
14031 - If a stream times out after 15s without a connected cell, don't
14032 try that circuit again: try a new one.
14033 - Retry streams at most 4 times. Then give up.
14034 - When a dirserver gets a descriptor from an unknown router, it
14035 logs its fingerprint (so the dirserver operator can choose to
14036 accept it even without mail from the server operator).
14037 - Inform unapproved servers when we reject their descriptors.
14038 - Make tor build on Windows again. It works as a client, who knows
14040 - Clearer instructions in the torrc for how to set up a server.
14041 - Be more efficient about reading fd's when our global token bucket
14042 (used for rate limiting) becomes empty.
14044 - Stop asserting that computers always go forward in time. It's
14046 - When we sent a cell (e.g. destroy) and then marked an OR connection
14047 expired, we might close it before finishing a flush if the other
14048 side isn't reading right then.
14049 - Don't allow dirservers to start if they haven't defined
14050 RecommendedVersions
14051 - We were caching transient dns failures. Oops.
14052 - Prevent servers from publishing an internal IP as their address.
14053 - Address a strcat vulnerability in circuit.c
14056 Changes in version 0.0.2pre25 - 2004-03-04
14058 - Put the OR's IP in its router descriptor, not its fqdn. That way
14059 we'll stop being stalled by gethostbyname for nodes with flaky dns,
14062 - If the user typed in an address that didn't resolve, the server
14066 Changes in version 0.0.2pre24 - 2004-03-03
14068 - Fix an assertion failure in dns.c, where we were trying to dequeue
14069 a pending dns resolve even if it wasn't pending
14070 - Fix a spurious socks5 warning about still trying to write after the
14071 connection is finished.
14072 - Hold certain marked_for_close connections open until they're finished
14073 flushing, rather than losing bytes by closing them too early.
14074 - Correctly report the reason for ending a stream
14075 - Remove some duplicate calls to connection_mark_for_close
14076 - Put switch_id and start_daemon earlier in the boot sequence, so it
14077 will actually try to chdir() to options.DataDirectory
14078 - Make 'make test' exit(1) if a test fails; fix some unit tests
14079 - Make tor fail when you use a config option it doesn't know about,
14080 rather than warn and continue.
14081 - Make --version work
14082 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
14085 Changes in version 0.0.2pre23 - 2004-02-29
14087 - Print a statement when the first circ is finished, so the user
14088 knows it's working.
14089 - If a relay cell is unrecognized at the end of the circuit,
14090 send back a destroy. (So attacks to mutate cells are more
14092 - New config option 'excludenodes' to avoid certain nodes for circuits.
14093 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
14094 so you can collect coredumps there.
14096 - Fix a bug in tls flushing where sometimes data got wedged and
14097 didn't flush until more data got sent. Hopefully this bug was
14098 a big factor in the random delays we were seeing.
14099 - Make 'connected' cells include the resolved IP, so the client
14100 dns cache actually gets populated.
14101 - Disallow changing from ORPort=0 to ORPort>0 on hup.
14102 - When we time-out on a stream and detach from the circuit, send an
14103 end cell down it first.
14104 - Only warn about an unknown router (in exitnodes, entrynodes,
14105 excludenodes) after we've fetched a directory.
14108 Changes in version 0.0.2pre22 - 2004-02-26
14110 - Servers publish less revealing uname information in descriptors.
14111 - More memory tracking and assertions, to crash more usefully when
14113 - If the default torrc isn't there, just use some default defaults.
14114 Plus provide an internal dirservers file if they don't have one.
14115 - When the user tries to use Tor as an http proxy, give them an http
14116 501 failure explaining that we're a socks proxy.
14117 - Dump a new router.desc on hup, to help confused people who change
14118 their exit policies and then wonder why router.desc doesn't reflect
14120 - Clean up the generic tor.sh init script that we ship with.
14122 - If the exit stream is pending on the resolve, and a destroy arrives,
14123 then the stream wasn't getting removed from the pending list. I
14124 think this was the one causing recent server crashes.
14125 - Use a more robust poll on OSX 10.3, since their poll is flaky.
14126 - When it couldn't resolve any dirservers, it was useless from then on.
14127 Now it reloads the RouterFile (or default dirservers) if it has no
14129 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
14130 many users don't even *have* a /usr/local/sbin/.
14133 Changes in version 0.0.2pre21 - 2004-02-18
14135 - There's a ChangeLog file that actually reflects the changelog.
14136 - There's a 'torify' wrapper script, with an accompanying
14137 tor-tsocks.conf, that simplifies the process of using tsocks for
14138 tor. It even has a man page.
14139 - The tor binary gets installed to sbin rather than bin now.
14140 - Retry streams where the connected cell hasn't arrived in 15 seconds
14141 - Clean up exit policy handling -- get the default out of the torrc,
14142 so we can update it without forcing each server operator to fix
14144 - Allow imaps and pop3s in default exit policy
14146 - Prevent picking middleman nodes as the last node in the circuit
14149 Changes in version 0.0.2pre20 - 2004-01-30
14151 - We now have a deb package, and it's in debian unstable. Go to
14152 it, apt-getters. :)
14153 - I've split the TotalBandwidth option into BandwidthRate (how many
14154 bytes per second you want to allow, long-term) and
14155 BandwidthBurst (how many bytes you will allow at once before the cap
14156 kicks in). This better token bucket approach lets you, say, set
14157 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
14158 performance while not exceeding your monthly bandwidth quota.
14159 - Push out a tls record's worth of data once you've got it, rather
14160 than waiting until you've read everything waiting to be read. This
14161 may improve performance by pipelining better. We'll see.
14162 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
14163 from failed circuits (if they haven't been connected yet) and attach
14165 - Expire old streams that haven't managed to connect. Some day we'll
14166 have them reattach to new circuits instead.
14169 - Fix several memory leaks that were causing servers to become bloated
14171 - Fix a few very rare assert triggers. A few more remain.
14172 - Setuid to User _before_ complaining about running as root.
14175 Changes in version 0.0.2pre19 - 2004-01-07
14177 - Fix deadlock condition in dns farm. We were telling a child to die by
14178 closing the parent's file descriptor to him. But newer children were
14179 inheriting the open file descriptor from the parent, and since they
14180 weren't closing it, the socket never closed, so the child never read
14181 eof, so he never knew to exit. Similarly, dns workers were holding
14182 open other sockets, leading to all sorts of chaos.
14183 - New cleaner daemon() code for forking and backgrounding.
14184 - If you log to a file, it now prints an entry at the top of the
14185 logfile so you know it's working.
14186 - The onionskin challenge length was 30 bytes longer than necessary.
14187 - Started to patch up the spec so it's not quite so out of date.
14190 Changes in version 0.0.2pre18 - 2004-01-02
14192 - Fix endian issues with the 'integrity' field in the relay header.
14193 - Fix a potential bug where connections in state
14194 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
14197 Changes in version 0.0.2pre17 - 2003-12-30
14199 - Made --debuglogfile (or any second log file, actually) work.
14200 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
14201 adversary could force us into an infinite loop.
14204 - Each onionskin handshake now includes a hash of the computed key,
14205 to prove the server's identity and help perfect forward secrecy.
14206 - Changed cell size from 256 to 512 bytes (working toward compatibility
14208 - Changed cell length to 2 bytes, and moved it to the relay header.
14209 - Implemented end-to-end integrity checking for the payloads of
14211 - Separated streamid from 'recognized' (otherwise circuits will get
14212 messed up when we try to have streams exit from the middle). We
14213 use the integrity-checking to confirm that a cell is addressed to
14215 - Randomize the initial circid and streamid values, so an adversary who
14216 breaks into a node can't learn how many circuits or streams have
14220 Changes in version 0.0.2pre16 - 2003-12-14
14222 - Fixed a bug that made HUP trigger an assert
14223 - Fixed a bug where a circuit that immediately failed wasn't being
14224 counted as a failed circuit in counting retries.
14227 - Now we close the circuit when we get a truncated cell: otherwise we're
14228 open to an anonymity attack where a bad node in the path truncates
14229 the circuit and then we open streams at him.
14230 - Add port ranges to exit policies
14231 - Add a conservative default exit policy
14232 - Warn if you're running tor as root
14233 - on HUP, retry OR connections and close/rebind listeners
14234 - options.EntryNodes: try these nodes first when picking the first node
14235 - options.ExitNodes: if your best choices happen to include any of
14236 your preferred exit nodes, you choose among just those preferred
14238 - options.ExcludedNodes: nodes that are never picked in path building
14241 Changes in version 0.0.2pre15 - 2003-12-03
14242 o Robustness and bugfixes:
14243 - Sometimes clients would cache incorrect DNS resolves, which would
14244 really screw things up.
14245 - An OP that goes offline would slowly leak all its sockets and stop
14247 - A wide variety of bugfixes in exit node selection, exit policy
14248 handling, and processing pending streams when a new circuit is
14250 - Pick nodes for a path only from those the directory says are up
14251 - Choose randomly from all running dirservers, not always the first one
14252 - Increase allowed http header size for directory fetch.
14253 - Stop writing to stderr (if we're daemonized it will be closed).
14254 - Enable -g always, so cores will be more useful to me.
14255 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
14258 - Wrote a man page. It lists commonly used options.
14261 - Change default loglevel to warn.
14262 - Make PidFile default to null rather than littering in your CWD.
14263 - OnionRouter config option is now obsolete. Instead it just checks
14265 - Moved to a single unified torrc file for both clients and servers.
14268 Changes in version 0.0.2pre14 - 2003-11-29
14269 o Robustness and bugfixes:
14270 - Force the admin to make the DataDirectory himself
14271 - to get ownership/permissions right
14272 - so clients no longer make a DataDirectory and then never use it
14273 - fix bug where a client who was offline for 45 minutes would never
14274 pull down a directory again
14275 - fix (or at least hide really well) the dns assert bug that was
14276 causing server crashes
14277 - warnings and improved robustness wrt clockskew for certs
14278 - use the native daemon(3) to daemonize, when available
14279 - exit if bind() fails
14280 - exit if neither socksport nor orport is defined
14281 - include our own tor_timegm (Win32 doesn't have its own)
14282 - bugfix for win32 with lots of connections
14283 - fix minor bias in PRNG
14284 - make dirserver more robust to corrupt cached directory
14287 - Wrote the design document (woo)
14289 o Circuit building and exit policies:
14290 - Circuits no longer try to use nodes that the directory has told them
14292 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
14293 bitcounts (18.0.0.0/8).
14294 - Make AP connections standby for a circuit if no suitable circuit
14295 exists, rather than failing
14296 - Circuits choose exit node based on addr/port, exit policies, and
14297 which AP connections are standing by
14298 - Bump min pathlen from 2 to 3
14299 - Relay end cells have a payload to describe why the stream ended.
14300 - If the stream failed because of exit policy, try again with a new
14302 - Clients have a dns cache to remember resolved addresses.
14303 - Notice more quickly when we have no working circuits
14306 - APPort is now called SocksPort
14307 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
14309 - RecommendedVersions is now a config variable rather than
14310 hardcoded (for dirservers)
14311 - Reloads config on HUP
14312 - Usage info on -h or --help
14313 - If you set User and Group config vars, it'll setu/gid to them.
14316 Changes in version 0.0.2pre13 - 2003-10-19
14317 o General stability:
14318 - SSL_write no longer fails when it returns WANTWRITE and the number
14319 of bytes in the buf has changed by the next SSL_write call.
14320 - Fix segfault fetching directory when network is down
14321 - Fix a variety of minor memory leaks
14322 - Dirservers reload the fingerprints file on HUP, so I don't have
14323 to take down the network when I approve a new router
14324 - Default server config file has explicit Address line to specify fqdn
14327 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
14328 - Make listener connections not ever alloc bufs
14330 o Autoconf improvements:
14331 - don't clobber an external CFLAGS in ./configure
14332 - Make install now works
14333 - create var/lib/tor on make install
14334 - autocreate a tor.sh initscript to help distribs
14335 - autocreate the torrc and sample-server-torrc with correct paths
14337 o Log files and Daemonizing now work:
14338 - If --DebugLogFile is specified, log to it at -l debug
14339 - If --LogFile is specified, use it instead of commandline
14340 - If --RunAsDaemon is set, tor forks and backgrounds on startup