2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.2.39 - 2012-09-11
7 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
11 - Fix an assertion failure in tor_timegm() that could be triggered
12 by a badly formatted directory object. Bug found by fuzzing with
13 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14 - Do not crash when comparing an address with port value 0 to an
15 address policy. This bug could have been used to cause a remote
16 assertion failure by or against directory authorities, or to
17 allow some applications to crash clients. Fixes bug 6690; bugfix
21 Changes in version 0.2.2.38 - 2012-08-12
22 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
23 attack that could in theory leak path information.
26 - Avoid an uninitialized memory read when reading a vote or consensus
27 document that has an unrecognized flavor name. This read could
28 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
29 - Try to leak less information about what relays a client is
30 choosing to a side-channel attacker. Previously, a Tor client would
31 stop iterating through the list of available relays as soon as it
32 had chosen one, thus finishing a little earlier when it picked
33 a router earlier in the list. If an attacker can recover this
34 timing information (nontrivial but not proven to be impossible),
35 they could learn some coarse-grained information about which relays
36 a client was picking (middle nodes in particular are likelier to
37 be affected than exits). The timing attack might be mitigated by
38 other factors (see bug 6537 for some discussion), but it's best
39 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
42 Changes in version 0.2.2.37 - 2012-06-06
43 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
44 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
48 - Work around a bug in OpenSSL that broke renegotiation with TLS
49 1.1 and TLS 1.2. Without this workaround, all attempts to speak
50 the v2 Tor connection protocol when both sides were using OpenSSL
51 1.0.1 would fail. Resolves ticket 6033.
52 - When waiting for a client to renegotiate, don't allow it to add
53 any bytes to the input buffer. This fixes a potential DoS issue.
54 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
55 - Fix an edge case where if we fetch or publish a hidden service
56 descriptor, we might build a 4-hop circuit and then use that circuit
57 for exiting afterwards -- even if the new last hop doesn't obey our
58 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
61 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
62 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
65 - Tell GCC and Clang to check for any errors in format strings passed
66 to the tor_v*(print|scan)f functions.
69 Changes in version 0.2.2.36 - 2012-05-24
70 Tor 0.2.2.36 updates the addresses for two of the eight directory
71 authorities, fixes some potential anonymity and security issues,
72 and fixes several crash bugs.
74 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
75 known flaws, and nobody should be using them. You should upgrade. If
76 you're using a Linux or BSD and its packages are obsolete, stop using
77 those packages and upgrade anyway.
79 o Directory authority changes:
80 - Change IP address for maatuska (v3 directory authority).
81 - Change IP address for ides (v3 directory authority), and rename
85 - When building or running with any version of OpenSSL earlier
86 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
87 versions have a bug (CVE-2011-4576) in which their block cipher
88 padding includes uninitialized data, potentially leaking sensitive
89 information to any peer with whom they make a SSLv3 connection. Tor
90 does not use SSL v3 by default, but a hostile client or server
91 could force an SSLv3 connection in order to gain information that
92 they shouldn't have been able to get. The best solution here is to
93 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
94 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
95 to make sure that the bug can't happen.
96 - Never use a bridge or a controller-supplied node as an exit, even
97 if its exit policy allows it. Found by wanoskarnet. Fixes bug
98 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
99 and 0.2.0.3-alpha (for bridge-purpose descriptors).
100 - Only build circuits if we have a sufficient threshold of the total
101 descriptors that are marked in the consensus with the "Exit"
102 flag. This mitigates an attack proposed by wanoskarnet, in which
103 all of a client's bridges collude to restrict the exit nodes that
104 the client knows about. Fixes bug 5343.
105 - Provide controllers with a safer way to implement the cookie
106 authentication mechanism. With the old method, if another locally
107 running program could convince a controller that it was the Tor
108 process, then that program could trick the controller into telling
109 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
110 authentication method uses a challenge-response approach to prevent
111 this attack. Fixes bug 5185; implements proposal 193.
114 - Avoid logging uninitialized data when unable to decode a hidden
115 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
116 - Avoid a client-side assertion failure when receiving an INTRODUCE2
117 cell on a general purpose circuit. Fixes bug 5644; bugfix on
119 - Fix builds when the path to sed, openssl, or sha1sum contains
120 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
122 - Correct our replacements for the timeradd() and timersub() functions
123 on platforms that lack them (for example, Windows). The timersub()
124 function is used when expiring circuits, while timeradd() is
125 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
126 bugfix on 0.2.2.24-alpha.
127 - Fix the SOCKET_OK test that we use to tell when socket
128 creation fails so that it works on Win64. Fixes part of bug 4533;
129 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
132 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
133 Fixes bug 5346; bugfix on 0.0.8pre3.
134 - Make our number-parsing functions always treat too-large values
135 as an error, even when those values exceed the width of the
136 underlying type. Previously, if the caller provided these
137 functions with minima or maxima set to the extreme values of the
138 underlying integer type, these functions would return those
139 values on overflow rather than treating overflow as an error.
140 Fixes part of bug 5786; bugfix on 0.0.9.
141 - Older Linux kernels erroneously respond to strange nmap behavior
142 by having accept() return successfully with a zero-length
143 socket. When this happens, just close the connection. Previously,
144 we would try harder to learn the remote address: but there was
145 no such remote address to learn, and our method for trying to
146 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
147 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
148 - Correct parsing of certain date types in parse_http_time().
149 Without this patch, If-Modified-Since would behave
150 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
151 Esteban Manchado Velázques.
152 - Change the BridgePassword feature (part of the "bridge community"
153 design, which is not yet implemented) to use a time-independent
154 comparison. The old behavior might have allowed an adversary
155 to use timing to guess the BridgePassword value. Fixes bug 5543;
156 bugfix on 0.2.0.14-alpha.
157 - Detect and reject certain misformed escape sequences in
158 configuration values. Previously, these values would cause us
159 to crash if received in a torrc file or over an authenticated
160 control port. Bug found by Esteban Manchado Velázquez, and
161 independently by Robert Connolly from Matta Consulting who further
162 noted that it allows a post-authentication heap overflow. Patch
163 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
164 bugfix on 0.2.0.16-alpha.
165 - Fix a compile warning when using the --enable-openbsd-malloc
166 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
167 - During configure, detect when we're building with clang version
168 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
169 CFLAGS. clang doesn't support them yet.
170 - When sending an HTTP/1.1 proxy request, include a Host header.
171 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
172 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
173 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
174 - If we hit the error case where routerlist_insert() replaces an
175 existing (old) server descriptor, make sure to remove that
176 server descriptor from the old_routers list. Fix related to bug
177 1776. Bugfix on 0.2.2.18-alpha.
179 o Minor bugfixes (documentation and log messages):
180 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
181 Fixes bug 4856; bugfix on Tor 0.0.6.
182 - Update "ClientOnly" man page entry to explain that there isn't
183 really any point to messing with it. Resolves ticket 5005.
184 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
185 directory authority option (introduced in Tor 0.2.2.34).
186 - Downgrade the "We're missing a certificate" message from notice
187 to info: people kept mistaking it for a real problem, whereas it
188 is seldom the problem even when we are failing to bootstrap. Fixes
189 bug 5067; bugfix on 0.2.0.10-alpha.
190 - Correctly spell "connect" in a log message on failure to create a
191 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
192 - Clarify the behavior of MaxCircuitDirtiness with hidden service
193 circuits. Fixes issue 5259.
196 - Directory authorities now reject versions of Tor older than
197 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
198 inclusive. These versions accounted for only a small fraction of
199 the Tor network, and have numerous known security issues. Resolves
201 - Update to the May 1 2012 Maxmind GeoLite Country database.
204 - When sending or relaying a RELAY_EARLY cell, we used to convert
205 it to a RELAY cell if the connection was using the v1 link
206 protocol. This was a workaround for older versions of Tor, which
207 didn't handle RELAY_EARLY cells properly. Now that all supported
208 versions can handle RELAY_EARLY cells, and now that we're enforcing
209 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
210 remove this workaround. Addresses bug 4786.
213 Changes in version 0.2.2.35 - 2011-12-16
214 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
215 buffers code. Absolutely everybody should upgrade.
217 The bug relied on an incorrect calculation when making data continuous
218 in one of our IO buffers, if the first chunk of the buffer was
219 misaligned by just the wrong amount. The miscalculation would allow an
220 attacker to overflow a piece of heap-allocated memory. To mount this
221 attack, the attacker would need to either open a SOCKS connection to
222 Tor's SocksPort (usually restricted to localhost), or target a Tor
223 instance configured to make its connections through a SOCKS proxy
224 (which Tor does not do by default).
226 Good security practice requires that all heap-overflow bugs should be
227 presumed to be exploitable until proven otherwise, so we are treating
228 this as a potential code execution attack. Please upgrade immediately!
229 This bug does not affect bufferevents-based builds of Tor. Special
230 thanks to "Vektor" for reporting this issue to us!
232 Tor 0.2.2.35 also fixes several bugs in previous versions, including
233 crash bugs for unusual configurations, and a long-term bug that
234 would prevent Tor from starting on Windows machines with draconian
237 With this release, we remind everyone that 0.2.0.x has reached its
238 formal end-of-life. Those Tor versions have many known flaws, and
239 nobody should be using them. You should upgrade -- ideally to the
240 0.2.2.x series. If you're using a Linux or BSD and its packages are
241 obsolete, stop using those packages and upgrade anyway.
243 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
244 longer receive support after some time in early 2012.
247 - Fix a heap overflow bug that could occur when trying to pull
248 data into the first chunk of a buffer, when that chunk had
249 already had some data drained from it. Fixes CVE-2011-2778;
250 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
251 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
252 that it doesn't attempt to allocate a socketpair. This could cause
253 some problems on Windows systems with overzealous firewalls. Fix for
254 bug 4457; workaround for Libevent versions 2.0.1-alpha through
256 - If we mark an OR connection for close based on a cell we process,
257 don't process any further cells on it. We already avoid further
258 reads on marked-for-close connections, but now we also discard the
259 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
260 which was the first version where we might mark a connection for
261 close based on processing a cell on it.
262 - Correctly sanity-check that we don't underflow on a memory
263 allocation (and then assert) for hidden service introduction
264 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
265 bugfix on 0.2.1.5-alpha.
266 - Fix a memory leak when we check whether a hidden service
267 descriptor has any usable introduction points left. Fixes bug
268 4424. Bugfix on 0.2.2.25-alpha.
269 - Don't crash when we're running as a relay and don't have a GeoIP
270 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
271 we've had in the 0.2.3.x branch already.
272 - When running as a client, do not print a misleading (and plain
273 wrong) log message that we're collecting "directory request"
274 statistics: clients don't collect statistics. Also don't create a
275 useless (because empty) stats file in the stats/ directory. Fixes
276 bug 4353; bugfix on 0.2.2.34.
279 - Detect failure to initialize Libevent. This fix provides better
280 detection for future instances of bug 4457.
281 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
282 function. This was eating up hideously large amounts of time on some
283 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
284 - Resolve an integer overflow bug in smartlist_ensure_capacity().
285 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
287 - Don't warn about unused log_mutex in log.c when building with
288 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
289 0.1.0.6-rc which introduced --disable-threads.
290 - When configuring, starting, or stopping an NT service, stop
291 immediately after the service configuration attempt has succeeded
292 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
293 - When sending a NETINFO cell, include the original address
294 received for the other side, not its canonical address. Found
295 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
296 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
297 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
298 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
299 occurred when a client tried to fetch a descriptor for a bridge
300 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
301 - Backport fixes for a pair of compilation warnings on Windows.
302 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
303 - If we had ever tried to call tor_addr_to_str on an address of
304 unknown type, we would have done a strdup on an uninitialized
305 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
306 Reported by "troll_un".
307 - Correctly detect and handle transient lookup failures from
308 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
309 Reported by "troll_un".
310 - Fix null-pointer access that could occur if TLS allocation failed.
311 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
312 - Use tor_socket_t type for listener argument to accept(). Fixes bug
313 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
316 - Add two new config options for directory authorities:
317 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
318 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
319 that is always sufficient to satisfy the bandwidth requirement for
320 the Guard flag. Now it will be easier for researchers to simulate
321 Tor networks with different values. Resolves ticket 4484.
322 - When Tor ignores a hidden service specified in its configuration,
323 include the hidden service's directory in the warning message.
324 Previously, we would only tell the user that some hidden service
325 was ignored. Bugfix on 0.0.6; fixes bug 4426.
326 - Update to the December 6 2011 Maxmind GeoLite Country database.
329 - Make it easier to automate expert package builds on Windows,
330 by removing an absolute path from makensis.exe command.
333 Changes in version 0.2.2.34 - 2011-10-26
334 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
335 can deanonymize Tor users. Everybody should upgrade.
337 The attack relies on four components: 1) Clients reuse their TLS cert
338 when talking to different relays, so relays can recognize a user by
339 the identity key in her cert. 2) An attacker who knows the client's
340 identity key can probe each guard relay to see if that identity key
341 is connected to that guard relay right now. 3) A variety of active
342 attacks in the literature (starting from "Low-Cost Traffic Analysis
343 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
344 discover the guard relays that a Tor user visiting the website is using.
345 4) Clients typically pick three guards at random, so the set of guards
346 for a given user could well be a unique fingerprint for her. This
347 release fixes components #1 and #2, which is enough to block the attack;
348 the other two remain as open research problems. Special thanks to
349 "frosty_un" for reporting the issue to us!
351 Clients should upgrade so they are no longer recognizable by the TLS
352 certs they present. Relays should upgrade so they no longer allow a
353 remote attacker to probe them to test whether unpatched clients are
354 currently connected to them.
356 This release also fixes several vulnerabilities that allow an attacker
357 to enumerate bridge relays. Some bridge enumeration attacks still
358 remain; see for example proposal 188.
360 o Privacy/anonymity fixes (clients):
361 - Clients and bridges no longer send TLS certificate chains on
362 outgoing OR connections. Previously, each client or bridge would
363 use the same cert chain for all outgoing OR connections until
364 its IP address changes, which allowed any relay that the client
365 or bridge contacted to determine which entry guards it is using.
366 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
367 - If a relay receives a CREATE_FAST cell on a TLS connection, it
368 no longer considers that connection as suitable for satisfying a
369 circuit EXTEND request. Now relays can protect clients from the
370 CVE-2011-2768 issue even if the clients haven't upgraded yet.
371 - Directory authorities no longer assign the Guard flag to relays
372 that haven't upgraded to the above "refuse EXTEND requests
373 to client connections" fix. Now directory authorities can
374 protect clients from the CVE-2011-2768 issue even if neither
375 the clients nor the relays have upgraded yet. There's a new
376 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
377 to let us transition smoothly, else tomorrow there would be no
380 o Privacy/anonymity fixes (bridge enumeration):
381 - Bridge relays now do their directory fetches inside Tor TLS
382 connections, like all the other clients do, rather than connecting
383 directly to the DirPort like public relays do. Removes another
384 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
385 - Bridges relays now build circuits for themselves in a more similar
386 way to how clients build them. Removes another avenue for
387 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
388 when bridges were introduced.
389 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
390 that they initiated. Relays could distinguish incoming bridge
391 connections from client connections, creating another avenue for
392 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
393 Found by "frosty_un".
396 - Fix a crash bug when changing node restrictions while a DNS lookup
397 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
399 - Don't launch a useless circuit after failing to use one of a
400 hidden service's introduction points. Previously, we would
401 launch a new introduction circuit, but not set the hidden service
402 which that circuit was intended to connect to, so it would never
403 actually be used. A different piece of code would then create a
404 new introduction circuit correctly. Bug reported by katmagic and
405 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
408 - Change an integer overflow check in the OpenBSD_Malloc code so
409 that GCC is less likely to eliminate it as impossible. Patch
410 from Mansour Moufid. Fixes bug 4059.
411 - When a hidden service turns an extra service-side introduction
412 circuit into a general-purpose circuit, free the rend_data and
413 intro_key fields first, so we won't leak memory if the circuit
414 is cannibalized for use as another service-side introduction
415 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
416 - Bridges now skip DNS self-tests, to act a little more stealthily.
417 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
418 bridges. Patch by "warms0x".
419 - Fix internal bug-checking logic that was supposed to catch
420 failures in digest generation so that it will fail more robustly
421 if we ask for a nonexistent algorithm. Found by Coverity Scan.
422 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
423 - Report any failure in init_keys() calls launched because our
424 IP address has changed. Spotted by Coverity Scan. Bugfix on
425 0.1.1.4-alpha; fixes CID 484.
427 o Minor bugfixes (log messages and documentation):
428 - Remove a confusing dollar sign from the example fingerprint in the
429 man page, and also make the example fingerprint a valid one. Fixes
430 bug 4309; bugfix on 0.2.1.3-alpha.
431 - The next version of Windows will be called Windows 8, and it has
432 a major version of 6, minor version of 2. Correctly identify that
433 version instead of calling it "Very recent version". Resolves
434 ticket 4153; reported by funkstar.
435 - Downgrade log messages about circuit timeout calibration from
436 "notice" to "info": they don't require or suggest any human
437 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
438 bugfix on 0.2.2.14-alpha.
441 - Turn on directory request statistics by default and include them in
442 extra-info descriptors. Don't break if we have no GeoIP database.
443 Backported from 0.2.3.1-alpha; implements ticket 3951.
444 - Update to the October 4 2011 Maxmind GeoLite Country database.
447 Changes in version 0.2.1.31 - 2011-10-26
448 Tor 0.2.1.31 backports important security and privacy fixes for
449 oldstable. This release is intended only for package maintainers and
450 others who cannot use the 0.2.2 stable series. All others should be
451 using Tor 0.2.2.x or newer.
453 o Security fixes (also included in 0.2.2.x):
454 - Replace all potentially sensitive memory comparison operations
455 with versions whose runtime does not depend on the data being
456 compared. This will help resist a class of attacks where an
457 adversary can use variations in timing information to learn
458 sensitive data. Fix for one case of bug 3122. (Safe memcmp
459 implementation by Robert Ransom based partially on code by DJB.)
460 - Fix an assert in parsing router descriptors containing IPv6
461 addresses. This one took down the directory authorities when
462 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
464 o Privacy/anonymity fixes (also included in 0.2.2.x):
465 - Clients and bridges no longer send TLS certificate chains on
466 outgoing OR connections. Previously, each client or bridge would
467 use the same cert chain for all outgoing OR connections until
468 its IP address changes, which allowed any relay that the client
469 or bridge contacted to determine which entry guards it is using.
470 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
471 - If a relay receives a CREATE_FAST cell on a TLS connection, it
472 no longer considers that connection as suitable for satisfying a
473 circuit EXTEND request. Now relays can protect clients from the
474 CVE-2011-2768 issue even if the clients haven't upgraded yet.
475 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
476 that they initiated. Relays could distinguish incoming bridge
477 connections from client connections, creating another avenue for
478 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
479 Found by "frosty_un".
480 - When receiving a hidden service descriptor, check that it is for
481 the hidden service we wanted. Previously, Tor would store any
482 hidden service descriptors that a directory gave it, whether it
483 wanted them or not. This wouldn't have let an attacker impersonate
484 a hidden service, but it did let directories pre-seed a client
485 with descriptors that it didn't want. Bugfix on 0.0.6.
486 - Avoid linkability based on cached hidden service descriptors: forget
487 all hidden service descriptors cached as a client when processing a
488 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
489 - Make the bridge directory authority refuse to answer directory
490 requests for "all" descriptors. It used to include bridge
491 descriptors in its answer, which was a major information leak.
492 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
493 - Don't attach new streams to old rendezvous circuits after SIGNAL
494 NEWNYM. Previously, we would keep using an existing rendezvous
495 circuit if it remained open (i.e. if it were kept open by a
496 long-lived stream, or if a new stream were attached to it before
497 Tor could notice that it was old and no longer in use). Bugfix on
498 0.1.1.15-rc; fixes bug 3375.
500 o Minor bugfixes (also included in 0.2.2.x):
501 - When we restart our relay, we might get a successful connection
502 from the outside before we've started our reachability tests,
503 triggering a warning: "ORPort found reachable, but I have no
504 routerinfo yet. Failing to inform controller of success." This
505 bug was harmless unless Tor is running under a controller
506 like Vidalia, in which case the controller would never get a
507 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
509 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
510 enabled. Fixes bug 1526.
511 - Remove undocumented option "-F" from tor-resolve: it hasn't done
512 anything since 0.2.1.16-rc.
513 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
514 None of the cases where we did this before were wrong, but by making
515 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
516 - Fix a rare crash bug that could occur when a client was configured
517 with a large number of bridges. Fixes bug 2629; bugfix on
518 0.2.1.2-alpha. Bugfix by trac user "shitlei".
519 - Correct the warning displayed when a rendezvous descriptor exceeds
520 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
522 - Fix an uncommon assertion failure when running with DNSPort under
523 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
524 - When warning about missing zlib development packages during compile,
525 give the correct package names. Bugfix on 0.2.0.1-alpha.
526 - Require that introduction point keys and onion keys have public
527 exponent 65537. Bugfix on 0.2.0.10-alpha.
528 - Do not crash when our configuration file becomes unreadable, for
529 example due to a permissions change, between when we start up
530 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
532 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
534 - Always NUL-terminate the sun_path field of a sockaddr_un before
535 passing it to the kernel. (Not a security issue: kernels are
536 smart enough to reject bad sockaddr_uns.) Found by Coverity;
537 CID #428. Bugfix on Tor 0.2.0.3-alpha.
538 - Don't stack-allocate the list of supplementary GIDs when we're
539 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
540 could take up to 256K, which is way too much stack. Found by
541 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
543 o Minor bugfixes (only in 0.2.1.x):
544 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
545 rely on them. Bugfix on 0.2.1.30.
546 - Use git revisions instead of svn revisions when generating our
547 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
549 o Minor features (also included in 0.2.2.x):
550 - Adjust the expiration time on our SSL session certificates to
551 better match SSL certs seen in the wild. Resolves ticket 4014.
552 - Allow nameservers with IPv6 address. Resolves bug 2574.
553 - Update to the October 4 2011 Maxmind GeoLite Country database.
556 Changes in version 0.2.2.33 - 2011-09-13
557 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
558 TLS handshake that makes relays and bridges that run this new version
559 reachable from Iran again.
562 - Avoid an assertion failure when reloading a configuration with
563 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
564 3923; bugfix on 0.2.2.25-alpha.
566 o Minor features (security):
567 - Check for replays of the public-key encrypted portion of an
568 INTRODUCE1 cell, in addition to the current check for replays of
569 the g^x value. This prevents a possible class of active attacks
570 by an attacker who controls both an introduction point and a
571 rendezvous point, and who uses the malleability of AES-CTR to
572 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
573 that these attacks are infeasible (requiring the attacker to send
574 on the order of zettabytes of altered cells in a short interval),
575 but we'd rather block them off in case there are any classes of
576 this attack that we missed. Reported by Willem Pinckaers.
579 - Adjust the expiration time on our SSL session certificates to
580 better match SSL certs seen in the wild. Resolves ticket 4014.
581 - Change the default required uptime for a relay to be accepted as
582 a HSDir (hidden service directory) from 24 hours to 25 hours.
583 Improves on 0.2.0.10-alpha; resolves ticket 2649.
584 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
585 authorities to abstain from voting on assignment of the HSDir
586 consensus flag. Related to bug 2649.
587 - Update to the September 6 2011 Maxmind GeoLite Country database.
589 o Minor bugfixes (documentation and log messages):
590 - Correct the man page to explain that HashedControlPassword and
591 CookieAuthentication can both be set, in which case either method
592 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
593 when we decided to allow these config options to both be set. Issue
595 - Demote the 'replay detected' log message emitted when a hidden
596 service receives the same Diffie-Hellman public key in two different
597 INTRODUCE2 cells to info level. A normal Tor client can cause that
598 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
599 fixes part of bug 2442.
600 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
601 level. There is nothing that a hidden service's operator can do
602 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
604 - Clarify a log message specifying the characters permitted in
605 HiddenServiceAuthorizeClient client names. Previously, the log
606 message said that "[A-Za-z0-9+-_]" were permitted; that could have
607 given the impression that every ASCII character between "+" and "_"
608 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
611 - Provide a substitute implementation of lround() for MSVC, which
612 apparently lacks it. Patch from Gisle Vanem.
613 - Clean up some code issues that prevented Tor from building on older
614 BSDs. Fixes bug 3894; reported by "grarpamp".
615 - Search for a platform-specific version of "ar" when cross-compiling.
616 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
619 Changes in version 0.2.2.32 - 2011-08-27
620 The Tor 0.2.2 release series is dedicated to the memory of Andreas
621 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
622 a founder of the PETS community, a leader in our field, a mentor,
623 and a friend. He left us with these words: "I had the possibility
624 to contribute to this world that is not as it should be. I hope I
625 could help in some areas to make the world a better place, and that
626 I could also encourage other people to be engaged in improving the
627 world. Please, stay engaged. This world needs you, your love, your
628 initiative -- now I cannot be part of that anymore."
630 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
631 ready. More than two years in the making, this release features improved
632 client performance and hidden service reliability, better compatibility
633 for Android, correct behavior for bridges that listen on more than
634 one address, more extensible and flexible directory object handling,
635 better reporting of network statistics, improved code security, and
636 many many other features and bugfixes.
638 o Major features (client performance):
639 - When choosing which cells to relay first, relays now favor circuits
640 that have been quiet recently, to provide lower latency for
641 low-volume circuits. By default, relays enable or disable this
642 feature based on a setting in the consensus. They can override
643 this default by using the new "CircuitPriorityHalflife" config
644 option. Design and code by Ian Goldberg, Can Tang, and Chris
646 - Directory authorities now compute consensus weightings that instruct
647 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
648 and no flag. Clients use these weightings to distribute network load
649 more evenly across these different relay types. The weightings are
650 in the consensus so we can change them globally in the future. Extra
651 thanks to "outofwords" for finding some nasty security bugs in
652 the first implementation of this feature.
654 o Major features (client performance, circuit build timeout):
655 - Tor now tracks how long it takes to build client-side circuits
656 over time, and adapts its timeout to local network performance.
657 Since a circuit that takes a long time to build will also provide
658 bad performance, we get significant latency improvements by
659 discarding the slowest 20% of circuits. Specifically, Tor creates
660 circuits more aggressively than usual until it has enough data
661 points for a good timeout estimate. Implements proposal 151.
662 - Circuit build timeout constants can be controlled by consensus
663 parameters. We set good defaults for these parameters based on
664 experimentation on broadband and simulated high-latency links.
665 - Circuit build time learning can be disabled via consensus parameter
666 or by the client via a LearnCircuitBuildTimeout config option. We
667 also automatically disable circuit build time calculation if either
668 AuthoritativeDirectory is set, or if we fail to write our state
669 file. Implements ticket 1296.
671 o Major features (relays use their capacity better):
672 - Set SO_REUSEADDR socket option on all sockets, not just
673 listeners. This should help busy exit nodes avoid running out of
674 useable ports just because all the ports have been used in the
675 near past. Resolves issue 2850.
676 - Relays now save observed peak bandwidth throughput rates to their
677 state file (along with total usage, which was already saved),
678 so that they can determine their correct estimated bandwidth on
679 restart. Resolves bug 1863, where Tor relays would reset their
680 estimated bandwidth to 0 after restarting.
681 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
682 should give us approximately 40-50% more Guard-flagged nodes,
683 improving the anonymity the Tor network can provide and also
684 decreasing the dropoff in throughput that relays experience when
685 they first get the Guard flag.
686 - Directory authorities now take changes in router IP address and
687 ORPort into account when determining router stability. Previously,
688 if a router changed its IP or ORPort, the authorities would not
689 treat it as having any downtime for the purposes of stability
690 calculation, whereas clients would experience downtime since the
691 change would take a while to propagate to them. Resolves issue 1035.
692 - New AccelName and AccelDir options add support for dynamic OpenSSL
693 hardware crypto acceleration engines.
695 o Major features (relays control their load better):
696 - Exit relays now try harder to block exit attempts from unknown
697 relays, to make it harder for people to use them as one-hop proxies
698 a la tortunnel. Controlled by the refuseunknownexits consensus
699 parameter (currently enabled), or you can override it on your
700 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
701 based on a variant of proposal 163.
702 - Add separate per-conn write limiting to go with the per-conn read
703 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
704 but never per-conn write limits.
705 - New consensus params "bwconnrate" and "bwconnburst" to let us
706 rate-limit client connections as they enter the network. It's
707 controlled in the consensus so we can turn it on and off for
708 experiments. It's starting out off. Based on proposal 163.
710 o Major features (controllers):
711 - Export GeoIP information on bridge usage to controllers even if we
712 have not yet been running for 24 hours. Now Vidalia bridge operators
713 can get more accurate and immediate feedback about their
714 contributions to the network.
715 - Add an __OwningControllerProcess configuration option and a
716 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
717 that when it exits, Tor will shut down. Implements feature 3049.
719 o Major features (directory authorities):
720 - Directory authorities now create, vote on, and serve multiple
721 parallel formats of directory data as part of their voting process.
722 Partially implements Proposal 162: "Publish the consensus in
724 - Directory authorities now agree on and publish small summaries
725 of router information that clients can use in place of regular
726 server descriptors. This transition will allow Tor 0.2.3 clients
727 to use far less bandwidth for downloading information about the
728 network. Begins the implementation of Proposal 158: "Clients
729 download consensus + microdescriptors".
730 - The directory voting system is now extensible to use multiple hash
731 algorithms for signatures and resource selection. Newer formats
732 are signed with SHA256, with a possibility for moving to a better
733 hash algorithm in the future.
734 - Directory authorities can now vote on arbitary integer values as
735 part of the consensus process. This is designed to help set
736 network-wide parameters. Implements proposal 167.
738 o Major features and bugfixes (node selection):
739 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
740 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
741 options. Previously, we had been ambiguous in describing what
742 counted as an "exit" node, and what operations exactly "StrictNodes
743 0" would permit. This created confusion when people saw nodes built
744 through unexpected circuits, and made it hard to tell real bugs from
745 surprises. Now the intended behavior is:
746 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
747 a node that delivers user traffic outside the Tor network.
748 . "Entry", in the context of EntryNodes, means a node used as the
749 first hop of a multihop circuit. It doesn't include direct
750 connections to directory servers.
751 . "ExcludeNodes" applies to all nodes.
752 . "StrictNodes" changes the behavior of ExcludeNodes only. When
753 StrictNodes is set, Tor should avoid all nodes listed in
754 ExcludeNodes, even when it will make user requests fail. When
755 StrictNodes is *not* set, then Tor should follow ExcludeNodes
756 whenever it can, except when it must use an excluded node to
757 perform self-tests, connect to a hidden service, provide a
758 hidden service, fulfill a .exit request, upload directory
759 information, or fetch directory information.
760 Collectively, the changes to implement the behavior fix bug 1090.
761 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
762 change during a config reload, mark and discard all our origin
763 circuits. This fix should address edge cases where we change the
764 config options and but then choose a circuit that we created before
766 - Make EntryNodes config option much more aggressive even when
767 StrictNodes is not set. Before it would prepend your requested
768 entrynodes to your list of guard nodes, but feel free to use others
769 after that. Now it chooses only from your EntryNodes if any of
770 those are available, and only falls back to others if a) they're
771 all down and b) StrictNodes is not set.
772 - Now we refresh your entry guards from EntryNodes at each consensus
773 fetch -- rather than just at startup and then they slowly rot as
775 - Add support for the country code "{??}" in torrc options like
776 ExcludeNodes, to indicate all routers of unknown country. Closes
778 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
779 a node is listed in both, it's treated as excluded.
780 - ExcludeNodes now applies to directory nodes -- as a preference if
781 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
782 Don't exclude all the directory authorities and set StrictNodes to 1
783 unless you really want your Tor to break.
784 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
785 - ExcludeExitNodes now overrides .exit requests.
786 - We don't use bridges listed in ExcludeNodes.
787 - When StrictNodes is 1:
788 . We now apply ExcludeNodes to hidden service introduction points
789 and to rendezvous points selected by hidden service users. This
790 can make your hidden service less reliable: use it with caution!
791 . If we have used ExcludeNodes on ourself, do not try relay
792 reachability self-tests.
793 . If we have excluded all the directory authorities, we will not
794 even try to upload our descriptor if we're a relay.
795 . Do not honor .exit requests to an excluded node.
796 - When the set of permitted nodes changes, we now remove any mappings
797 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
799 - We never cannibalize a circuit that had excluded nodes on it, even
800 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
801 - Improve log messages related to excluded nodes.
803 o Major features (misc):
804 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
805 to help Tor build correctly for Android phones.
806 - The options SocksPort, ControlPort, and so on now all accept a
807 value "auto" that opens a socket on an OS-selected port. A
808 new ControlPortWriteToFile option tells Tor to write its
809 actual control port or ports to a chosen file. If the option
810 ControlPortFileGroupReadable is set, the file is created as
811 group-readable. Now users can run two Tor clients on the same
812 system without needing to manually mess with parameters. Resolves
814 - Tor now supports tunneling all of its outgoing connections over
815 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
816 configuration options. Code by Christopher Davis.
818 o Code security improvements:
819 - Replace all potentially sensitive memory comparison operations
820 with versions whose runtime does not depend on the data being
821 compared. This will help resist a class of attacks where an
822 adversary can use variations in timing information to learn
823 sensitive data. Fix for one case of bug 3122. (Safe memcmp
824 implementation by Robert Ransom based partially on code by DJB.)
825 - Enable Address Space Layout Randomization (ASLR) and Data Execution
826 Prevention (DEP) by default on Windows to make it harder for
827 attackers to exploit vulnerabilities. Patch from John Brooks.
828 - New "--enable-gcc-hardening" ./configure flag (off by default)
829 to turn on gcc compile time hardening options. It ensures
830 that signed ints have defined behavior (-fwrapv), enables
831 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
832 with canaries (-fstack-protector-all), turns on ASLR protection if
833 supported by the kernel (-fPIE, -pie), and adds additional security
834 related warnings. Verified to work on Mac OS X and Debian Lenny.
835 - New "--enable-linker-hardening" ./configure flag (off by default)
836 to turn on ELF specific hardening features (relro, now). This does
837 not work with Mac OS X or any other non-ELF binary format.
838 - Always search the Windows system directory for system DLLs, and
839 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
840 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
841 current and future memory pages via mlockall(). On supported
842 platforms (modern Linux and probably BSD but not Windows or OS X),
843 this should effectively disable any and all attempts to page out
844 memory. This option requires that you start your Tor as root --
845 if you use DisableAllSwap, please consider using the User option
846 to properly reduce the privileges of your Tor.
848 o Major bugfixes (crashes):
849 - Fix crash bug on platforms where gmtime and localtime can return
850 NULL. Windows 7 users were running into this one. Fixes part of bug
851 2077. Bugfix on all versions of Tor. Found by boboper.
852 - Introduce minimum/maximum values that clients will believe
853 from the consensus. Now we'll have a better chance to avoid crashes
854 or worse when a consensus param has a weird value.
855 - Fix a rare crash bug that could occur when a client was configured
856 with a large number of bridges. Fixes bug 2629; bugfix on
857 0.2.1.2-alpha. Bugfix by trac user "shitlei".
858 - Do not crash when our configuration file becomes unreadable, for
859 example due to a permissions change, between when we start up
860 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
862 - If we're in the pathological case where there's no exit bandwidth
863 but there is non-exit bandwidth, or no guard bandwidth but there
864 is non-guard bandwidth, don't crash during path selection. Bugfix
866 - Fix a crash bug when trying to initialize the evdns module in
867 Libevent 2. Bugfix on 0.2.1.16-rc.
869 o Major bugfixes (stability):
870 - Fix an assert in parsing router descriptors containing IPv6
871 addresses. This one took down the directory authorities when
872 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
873 - Fix an uncommon assertion failure when running with DNSPort under
874 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
875 - Treat an unset $HOME like an empty $HOME rather than triggering an
876 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
877 - More gracefully handle corrupt state files, removing asserts
878 in favor of saving a backup and resetting state.
879 - Instead of giving an assertion failure on an internal mismatch
880 on estimated freelist size, just log a BUG warning and try later.
881 Mitigates but does not fix bug 1125.
882 - Fix an assert that got triggered when using the TestingTorNetwork
883 configuration option and then issuing a GETINFO config-text control
884 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
885 - If the cached cert file is unparseable, warn but don't exit.
887 o Privacy fixes (relays/bridges):
888 - Don't list Windows capabilities in relay descriptors. We never made
889 use of them, and maybe it's a bad idea to publish them. Bugfix
891 - If the Nickname configuration option isn't given, Tor would pick a
892 nickname based on the local hostname as the nickname for a relay.
893 Because nicknames are not very important in today's Tor and the
894 "Unnamed" nickname has been implemented, this is now problematic
895 behavior: It leaks information about the hostname without being
896 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
897 introduced the Unnamed nickname. Reported by tagnaq.
898 - Maintain separate TLS contexts and certificates for incoming and
899 outgoing connections in bridge relays. Previously we would use the
900 same TLS contexts and certs for incoming and outgoing connections.
901 Bugfix on 0.2.0.3-alpha; addresses bug 988.
902 - Maintain separate identity keys for incoming and outgoing TLS
903 contexts in bridge relays. Previously we would use the same
904 identity keys for incoming and outgoing TLS contexts. Bugfix on
905 0.2.0.3-alpha; addresses the other half of bug 988.
906 - Make the bridge directory authority refuse to answer directory
907 requests for "all descriptors". It used to include bridge
908 descriptors in its answer, which was a major information leak.
909 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
911 o Privacy fixes (clients):
912 - When receiving a hidden service descriptor, check that it is for
913 the hidden service we wanted. Previously, Tor would store any
914 hidden service descriptors that a directory gave it, whether it
915 wanted them or not. This wouldn't have let an attacker impersonate
916 a hidden service, but it did let directories pre-seed a client
917 with descriptors that it didn't want. Bugfix on 0.0.6.
918 - Start the process of disabling ".exit" address notation, since it
919 can be used for a variety of esoteric application-level attacks
920 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
922 - Reject attempts at the client side to open connections to private
923 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
924 a randomly chosen exit node. Attempts to do so are always
925 ill-defined, generally prevented by exit policies, and usually
926 in error. This will also help to detect loops in transparent
927 proxy configurations. You can disable this feature by setting
928 "ClientRejectInternalAddresses 0" in your torrc.
929 - Log a notice when we get a new control connection. Now it's easier
930 for security-conscious users to recognize when a local application
931 is knocking on their controller door. Suggested by bug 1196.
933 o Privacy fixes (newnym):
934 - Avoid linkability based on cached hidden service descriptors: forget
935 all hidden service descriptors cached as a client when processing a
936 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
937 - On SIGHUP, do not clear out all TrackHostExits mappings, client
938 DNS cache entries, and virtual address mappings: that's what
939 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
940 - Don't attach new streams to old rendezvous circuits after SIGNAL
941 NEWNYM. Previously, we would keep using an existing rendezvous
942 circuit if it remained open (i.e. if it were kept open by a
943 long-lived stream, or if a new stream were attached to it before
944 Tor could notice that it was old and no longer in use). Bugfix on
945 0.1.1.15-rc; fixes bug 3375.
947 o Major bugfixes (relay bandwidth accounting):
948 - Fix a bug that could break accounting on 64-bit systems with large
949 time_t values, making them hibernate for impossibly long intervals.
950 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
951 - Fix a bug in bandwidth accounting that could make us use twice
952 the intended bandwidth when our interval start changes due to
953 daylight saving time. Now we tolerate skew in stored vs computed
954 interval starts: if the start of the period changes by no more than
955 50% of the period's duration, we remember bytes that we transferred
956 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
958 o Major bugfixes (bridges):
959 - Bridges now use "reject *:*" as their default exit policy. Bugfix
960 on 0.2.0.3-alpha. Fixes bug 1113.
961 - If you configure your bridge with a known identity fingerprint,
962 and the bridge authority is unreachable (as it is in at least
963 one country now), fall back to directly requesting the descriptor
964 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
966 - Fix a bug where bridge users who configure the non-canonical
967 address of a bridge automatically switch to its canonical
968 address. If a bridge listens at more than one address, it
969 should be able to advertise those addresses independently and
970 any non-blocked addresses should continue to work. Bugfix on Tor
971 0.2.0.3-alpha. Fixes bug 2510.
972 - If you configure Tor to use bridge A, and then quit and
973 configure Tor to use bridge B instead (or if you change Tor
974 to use bridge B via the controller), it would happily continue
975 to use bridge A if it's still reachable. While this behavior is
976 a feature if your goal is connectivity, in some scenarios it's a
977 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
978 - When the controller configures a new bridge, don't wait 10 to 60
979 seconds before trying to fetch its descriptor. Bugfix on
980 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
982 o Major bugfixes (directory authorities):
983 - Many relays have been falling out of the consensus lately because
984 not enough authorities know about their descriptor for them to get
985 a majority of votes. When we deprecated the v2 directory protocol,
986 we got rid of the only way that v3 authorities can hear from each
987 other about other descriptors. Now authorities examine every v3
988 vote for new descriptors, and fetch them from that authority. Bugfix
990 - Authorities could be tricked into giving out the Exit flag to relays
991 that didn't allow exiting to any ports. This bug could screw
992 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
993 1238. Bug discovered by Martin Kowalczyk.
994 - If all authorities restart at once right before a consensus vote,
995 nobody will vote about "Running", and clients will get a consensus
996 with no usable relays. Instead, authorities refuse to build a
997 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
999 o Major bugfixes (stream-level fairness):
1000 - When receiving a circuit-level SENDME for a blocked circuit, try
1001 to package cells fairly from all the streams that had previously
1002 been blocked on that circuit. Previously, we had started with the
1003 oldest stream, and allowed each stream to potentially exhaust
1004 the circuit's package window. This gave older streams on any
1005 given circuit priority over newer ones. Fixes bug 1937. Detected
1006 originally by Camilo Viecco. This bug was introduced before the
1007 first Tor release, in svn commit r152: it is the new winner of
1008 the longest-lived bug prize.
1009 - Fix a stream fairness bug that would cause newer streams on a given
1010 circuit to get preference when reading bytes from the origin or
1011 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
1012 introduced before the first Tor release, in svn revision r152.
1013 - When the exit relay got a circuit-level sendme cell, it started
1014 reading on the exit streams, even if had 500 cells queued in the
1015 circuit queue already, so the circuit queue just grew and grew in
1016 some cases. We fix this by not re-enabling reading on receipt of a
1017 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
1018 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
1020 - Newly created streams were allowed to read cells onto circuits,
1021 even if the circuit's cell queue was blocked and waiting to drain.
1022 This created potential unfairness, as older streams would be
1023 blocked, but newer streams would gladly fill the queue completely.
1024 We add code to detect this situation and prevent any stream from
1025 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
1028 o Major bugfixes (hidden services):
1029 - Apply circuit timeouts to opened hidden-service-related circuits
1030 based on the correct start time. Previously, we would apply the
1031 circuit build timeout based on time since the circuit's creation;
1032 it was supposed to be applied based on time since the circuit
1033 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
1034 - Improve hidden service robustness: When we find that we have
1035 extended a hidden service's introduction circuit to a relay not
1036 listed as an introduction point in the HS descriptor we currently
1037 have, retry with an introduction point from the current
1038 descriptor. Previously we would just give up. Fixes bugs 1024 and
1039 1930; bugfix on 0.2.0.10-alpha.
1040 - Directory authorities now use data collected from their own
1041 uptime observations when choosing whether to assign the HSDir flag
1042 to relays, instead of trusting the uptime value the relay reports in
1043 its descriptor. This change helps prevent an attack where a small
1044 set of nodes with frequently-changing identity keys can blackhole
1045 a hidden service. (Only authorities need upgrade; others will be
1046 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
1047 - Stop assigning the HSDir flag to relays that disable their
1048 DirPort (and thus will refuse to answer directory requests). This
1049 fix should dramatically improve the reachability of hidden services:
1050 hidden services and hidden service clients pick six HSDir relays
1051 to store and retrieve the hidden service descriptor, and currently
1052 about half of the HSDir relays will refuse to work. Bugfix on
1053 0.2.0.10-alpha; fixes part of bug 1693.
1055 o Major bugfixes (misc):
1056 - Clients now stop trying to use an exit node associated with a given
1057 destination by TrackHostExits if they fail to reach that exit node.
1058 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
1059 - Fix a regression that caused Tor to rebind its ports if it receives
1060 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
1061 - Remove an extra pair of quotation marks around the error
1062 message in control-port STATUS_GENERAL BUG events. Bugfix on
1063 0.1.2.6-alpha; fixes bug 3732.
1065 o Minor features (relays):
1066 - Ensure that no empty [dirreq-](read|write)-history lines are added
1067 to an extrainfo document. Implements ticket 2497.
1068 - When bandwidth accounting is enabled, be more generous with how
1069 much bandwidth we'll use up before entering "soft hibernation".
1070 Previously, we'd refuse new connections and circuits once we'd
1071 used up 95% of our allotment. Now, we use up 95% of our allotment,
1072 AND make sure that we have no more than 500MB (or 3 hours of
1073 expected traffic, whichever is lower) remaining before we enter
1075 - Relays now log the reason for publishing a new relay descriptor,
1076 so we have a better chance of hunting down instances of bug 1810.
1077 Resolves ticket 3252.
1078 - Log a little more clearly about the times at which we're no longer
1079 accepting new connections (e.g. due to hibernating). Resolves
1081 - When AllowSingleHopExits is set, print a warning to explain to the
1082 relay operator why most clients are avoiding her relay.
1083 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
1084 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
1085 clients are already deprecated because of security bugs.
1087 o Minor features (network statistics):
1088 - Directory mirrors that set "DirReqStatistics 1" write statistics
1089 about directory requests to disk every 24 hours. As compared to the
1090 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
1091 improvements: 1) stats are written to disk exactly every 24 hours;
1092 2) estimated shares of v2 and v3 requests are determined as mean
1093 values, not at the end of a measurement period; 3) unresolved
1094 requests are listed with country code '??'; 4) directories also
1095 measure download times.
1096 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
1097 number of exit streams and transferred bytes per port to disk every
1099 - Relays that set "CellStatistics 1" write statistics on how long
1100 cells spend in their circuit queues to disk every 24 hours.
1101 - Entry nodes that set "EntryStatistics 1" write statistics on the
1102 rough number and origins of connecting clients to disk every 24
1104 - Relays that write any of the above statistics to disk and set
1105 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
1106 their extra-info documents. Implements proposal 166.
1108 o Minor features (GeoIP and statistics):
1109 - Provide a log message stating which geoip file we're parsing
1110 instead of just stating that we're parsing the geoip file.
1111 Implements ticket 2432.
1112 - Make sure every relay writes a state file at least every 12 hours.
1113 Previously, a relay could go for weeks without writing its state
1114 file, and on a crash could lose its bandwidth history, capacity
1115 estimates, client country statistics, and so on. Addresses bug 3012.
1116 - Relays report the number of bytes spent on answering directory
1117 requests in extra-info descriptors similar to {read,write}-history.
1118 Implements enhancement 1790.
1119 - Report only the top 10 ports in exit-port stats in order not to
1120 exceed the maximum extra-info descriptor length of 50 KB. Implements
1122 - If writing the state file to disk fails, wait up to an hour before
1123 retrying again, rather than trying again each second. Fixes bug
1124 2346; bugfix on Tor 0.1.1.3-alpha.
1125 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
1126 when we switch from being a public relay to a bridge. Otherwise
1127 there will still be clients that see the relay in their consensus,
1128 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
1130 - Update to the August 2 2011 Maxmind GeoLite Country database.
1132 o Minor features (clients):
1133 - When expiring circuits, use microsecond timers rather than
1134 one-second timers. This can avoid an unpleasant situation where a
1135 circuit is launched near the end of one second and expired right
1136 near the beginning of the next, and prevent fluctuations in circuit
1138 - If we've configured EntryNodes and our network goes away and/or all
1139 our entrynodes get marked down, optimistically retry them all when
1140 a new socks application request appears. Fixes bug 1882.
1141 - Always perform router selections using weighted relay bandwidth,
1142 even if we don't need a high capacity circuit at the time. Non-fast
1143 circuits now only differ from fast ones in that they can use relays
1144 not marked with the Fast flag. This "feature" could turn out to
1145 be a horrible bug; we should investigate more before it goes into
1147 - When we run out of directory information such that we can't build
1148 circuits, but then get enough that we can build circuits, log when
1149 we actually construct a circuit, so the user has a better chance of
1150 knowing what's going on. Fixes bug 1362.
1151 - Log SSL state transitions at debug level during handshake, and
1152 include SSL states in error messages. This may help debug future
1153 SSL handshake issues.
1155 o Minor features (directory authorities):
1156 - When a router changes IP address or port, authorities now launch
1157 a new reachability test for it. Implements ticket 1899.
1158 - Directory authorities now reject relays running any versions of
1159 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
1160 known bugs that keep RELAY_EARLY cells from working on rendezvous
1161 circuits. Followup to fix for bug 2081.
1162 - Directory authorities now reject relays running any version of Tor
1163 older than 0.2.0.26-rc. That version is the earliest that fetches
1164 current directory information correctly. Fixes bug 2156.
1165 - Directory authorities now do an immediate reachability check as soon
1166 as they hear about a new relay. This change should slightly reduce
1167 the time between setting up a relay and getting listed as running
1168 in the consensus. It should also improve the time between setting
1169 up a bridge and seeing use by bridge users.
1170 - Directory authorities no longer launch a TLS connection to every
1171 relay as they startup. Now that we have 2k+ descriptors cached,
1172 the resulting network hiccup is becoming a burden. Besides,
1173 authorities already avoid voting about Running for the first half
1174 hour of their uptime.
1175 - Directory authorities now log the source of a rejected POSTed v3
1176 networkstatus vote, so we can track failures better.
1177 - Backport code from 0.2.3.x that allows directory authorities to
1178 clean their microdescriptor caches. Needed to resolve bug 2230.
1180 o Minor features (hidden services):
1181 - Use computed circuit-build timeouts to decide when to launch
1182 parallel introduction circuits for hidden services. (Previously,
1183 we would retry after 15 seconds.)
1184 - Don't allow v0 hidden service authorities to act as clients.
1185 Required by fix for bug 3000.
1186 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
1187 by fix for bug 3000.
1188 - Make hidden services work better in private Tor networks by not
1189 requiring any uptime to join the hidden service descriptor
1190 DHT. Implements ticket 2088.
1191 - Log (at info level) when purging pieces of hidden-service-client
1192 state because of SIGNAL NEWNYM.
1194 o Minor features (controller interface):
1195 - New "GETINFO net/listeners/(type)" controller command to return
1196 a list of addresses and ports that are bound for listeners for a
1197 given connection type. This is useful when the user has configured
1198 "SocksPort auto" and the controller needs to know which port got
1199 chosen. Resolves another part of ticket 3076.
1200 - Have the controller interface give a more useful message than
1201 "Internal Error" in response to failed GETINFO requests.
1202 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
1203 event, to give information on the current rate of circuit timeouts
1204 over our stored history.
1205 - The 'EXTENDCIRCUIT' control port command can now be used with
1206 a circ id of 0 and no path. This feature will cause Tor to build
1207 a new 'fast' general purpose circuit using its own path selection
1209 - Added a BUILDTIMEOUT_SET controller event to describe changes
1210 to the circuit build timeout.
1211 - New controller command "getinfo config-text". It returns the
1212 contents that Tor would write if you send it a SAVECONF command,
1213 so the controller can write the file to disk itself.
1215 o Minor features (controller protocol):
1216 - Add a new ControlSocketsGroupWritable configuration option: when
1217 it is turned on, ControlSockets are group-writeable by the default
1218 group of the current user. Patch by Jérémy Bobbio; implements
1220 - Tor now refuses to create a ControlSocket in a directory that is
1221 world-readable (or group-readable if ControlSocketsGroupWritable
1222 is 0). This is necessary because some operating systems do not
1223 enforce permissions on an AF_UNIX sockets. Permissions on the
1224 directory holding the socket, however, seems to work everywhere.
1225 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
1226 not. This would lead to a cookie that is still not group readable.
1227 Closes bug 1843. Suggested by katmagic.
1228 - Future-proof the controller protocol a bit by ignoring keyword
1229 arguments we do not recognize.
1231 o Minor features (more useful logging):
1232 - Revise most log messages that refer to nodes by nickname to
1233 instead use the "$key=nickname at address" format. This should be
1234 more useful, especially since nicknames are less and less likely
1235 to be unique. Resolves ticket 3045.
1236 - When an HTTPS proxy reports "403 Forbidden", we now explain
1237 what it means rather than calling it an unexpected status code.
1238 Closes bug 2503. Patch from Michael Yakubovich.
1239 - Rate-limit a warning about failures to download v2 networkstatus
1240 documents. Resolves part of bug 1352.
1241 - Rate-limit the "your application is giving Tor only an IP address"
1242 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
1243 - Rate-limit "Failed to hand off onionskin" warnings.
1244 - When logging a rate-limited warning, we now mention how many messages
1245 got suppressed since the last warning.
1246 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
1247 2 no signature, 4 required" messages about consensus signatures
1248 easier to read, and make sure they get logged at the same severity
1249 as the messages explaining which keys are which. Fixes bug 1290.
1250 - Don't warn when we have a consensus that we can't verify because
1251 of missing certificates, unless those certificates are ones
1252 that we have been trying and failing to download. Fixes bug 1145.
1254 o Minor features (log domains):
1255 - Add documentation for configuring logging at different severities in
1256 different log domains. We've had this feature since 0.2.1.1-alpha,
1257 but for some reason it never made it into the manpage. Fixes
1259 - Make it simpler to specify "All log domains except for A and B".
1260 Previously you needed to say "[*,~A,~B]". Now you can just say
1262 - Add a "LogMessageDomains 1" option to include the domains of log
1263 messages along with the messages. Without this, there's no way
1264 to use log domains without reading the source or doing a lot
1266 - Add a new "Handshake" log domain for activities that happen
1267 during the TLS handshake.
1269 o Minor features (build process):
1270 - Make compilation with clang possible when using
1271 "--enable-gcc-warnings" by removing two warning options that clang
1272 hasn't implemented yet and by fixing a few warnings. Resolves
1274 - Detect platforms that brokenly use a signed size_t, and refuse to
1275 build there. Found and analyzed by doorss and rransom.
1276 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
1278 - Add support for statically linking zlib by specifying
1279 "--enable-static-zlib", to go with our support for statically
1280 linking openssl and libevent. Resolves bug 1358.
1281 - Instead of adding the svn revision to the Tor version string, report
1282 the git commit (when we're building from a git checkout).
1283 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
1285 - New --digests command-line switch to output the digests of the
1286 source files Tor was built with.
1287 - Generate our manpage and HTML documentation using Asciidoc. This
1288 change should make it easier to maintain the documentation, and
1289 produce nicer HTML. The build process fails if asciidoc cannot
1290 be found and building with asciidoc isn't disabled (via the
1291 "--disable-asciidoc" argument to ./configure. Skipping the manpage
1292 speeds up the build considerably.
1294 o Minor features (options / torrc):
1295 - Warn when the same option is provided more than once in a torrc
1296 file, on the command line, or in a single SETCONF statement, and
1297 the option is one that only accepts a single line. Closes bug 1384.
1298 - Warn when the user configures two HiddenServiceDir lines that point
1299 to the same directory. Bugfix on 0.0.6 (the version introducing
1300 HiddenServiceDir); fixes bug 3289.
1301 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
1302 do individual connection-level rate limiting of clients. The torrc
1303 config options with the same names trump the consensus params, if
1304 both are present. Replaces the old "bwconnrate" and "bwconnburst"
1305 consensus params which were broken from 0.2.2.7-alpha through
1306 0.2.2.14-alpha. Closes bug 1947.
1307 - New config option "WarnUnsafeSocks 0" disables the warning that
1308 occurs whenever Tor receives a socks handshake using a version of
1309 the socks protocol that can only provide an IP address (rather
1310 than a hostname). Setups that do DNS locally over Tor are fine,
1311 and we shouldn't spam the logs in that case.
1312 - New config option "CircuitStreamTimeout" to override our internal
1313 timeout schedule for how many seconds until we detach a stream from
1314 a circuit and try a new circuit. If your network is particularly
1315 slow, you might want to set this to a number like 60.
1316 - New options for SafeLogging to allow scrubbing only log messages
1317 generated while acting as a relay. Specify "SafeLogging relay" if
1318 you want to ensure that only messages known to originate from
1319 client use of the Tor process will be logged unsafely.
1320 - Time and memory units in the configuration file can now be set to
1321 fractional units. For example, "2.5 GB" is now a valid value for
1323 - Support line continuations in the torrc config file. If a line
1324 ends with a single backslash character, the newline is ignored, and
1325 the configuration value is treated as continuing on the next line.
1328 o Minor features (unit tests):
1329 - Revise our unit tests to use the "tinytest" framework, so we
1330 can run tests in their own processes, have smarter setup/teardown
1331 code, and so on. The unit test code has moved to its own
1332 subdirectory, and has been split into multiple modules.
1333 - Add a unit test for cross-platform directory-listing code.
1334 - Add some forgotten return value checks during unit tests. Found
1336 - Use GetTempDir to find the proper temporary directory location on
1337 Windows when generating temporary files for the unit tests. Patch
1340 o Minor features (misc):
1341 - The "torify" script now uses torsocks where available.
1342 - Make Libevent log messages get delivered to controllers later,
1343 and not from inside the Libevent log handler. This prevents unsafe
1344 reentrant Libevent calls while still letting the log messages
1346 - Certain Tor clients (such as those behind check.torproject.org) may
1347 want to fetch the consensus in an extra early manner. To enable this
1348 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
1349 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
1350 as only certain clients who must have this information sooner should
1352 - Expand homedirs passed to tor-checkkey. This should silence a
1353 coverity complaint about passing a user-supplied string into
1354 open() without checking it.
1355 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
1356 used on bridges, and it makes bridge scanning somewhat easier.
1357 - Create the /var/run/tor directory on startup on OpenSUSE if it is
1358 not already created. Patch from Andreas Stieger. Fixes bug 2573.
1360 o Minor bugfixes (relays):
1361 - When a relay decides that its DNS is too broken for it to serve
1362 as an exit server, it advertised itself as a non-exit, but
1363 continued to act as an exit. This could create accidental
1364 partitioning opportunities for users. Instead, if a relay is
1365 going to advertise reject *:* as its exit policy, it should
1366 really act with exit policy "reject *:*". Fixes bug 2366.
1367 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
1368 - Publish a router descriptor even if generating an extra-info
1369 descriptor fails. Previously we would not publish a router
1370 descriptor without an extra-info descriptor; this can cause fast
1371 exit relays collecting exit-port statistics to drop from the
1372 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
1373 - When we're trying to guess whether we know our IP address as
1374 a relay, we would log various ways that we failed to guess
1375 our address, but never log that we ended up guessing it
1376 successfully. Now add a log line to help confused and anxious
1377 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
1378 - For bandwidth accounting, calculate our expected bandwidth rate
1379 based on the time during which we were active and not in
1380 soft-hibernation during the last interval. Previously, we were
1381 also considering the time spent in soft-hibernation. If this
1382 was a long time, we would wind up underestimating our bandwidth
1383 by a lot, and skewing our wakeup time towards the start of the
1384 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
1385 - Demote a confusing TLS warning that relay operators might get when
1386 someone tries to talk to their ORPort. It is not the operator's
1387 fault, nor can they do anything about it. Fixes bug 1364; bugfix
1389 - Change "Application request when we're believed to be offline."
1390 notice to "Application request when we haven't used client
1391 functionality lately.", to clarify that it's not an error. Bugfix
1392 on 0.0.9.3; fixes bug 1222.
1394 o Minor bugfixes (bridges):
1395 - When a client starts or stops using bridges, never use a circuit
1396 that was built before the configuration change. This behavior could
1397 put at risk a user who uses bridges to ensure that her traffic
1398 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
1400 - Do not reset the bridge descriptor download status every time we
1401 re-parse our configuration or get a configuration change. Fixes
1402 bug 3019; bugfix on 0.2.0.3-alpha.
1403 - Users couldn't configure a regular relay to be their bridge. It
1404 didn't work because when Tor fetched the bridge descriptor, it found
1405 that it already had it, and didn't realize that the purpose of the
1406 descriptor had changed. Now we replace routers with a purpose other
1407 than bridge with bridge descriptors when fetching them. Bugfix on
1408 0.1.1.9-alpha. Fixes bug 1776.
1409 - In the special case where you configure a public exit relay as your
1410 bridge, Tor would be willing to use that exit relay as the last
1411 hop in your circuit as well. Now we fail that circuit instead.
1412 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
1414 o Minor bugfixes (clients):
1415 - We now ask the other side of a stream (the client or the exit)
1416 for more data on that stream when the amount of queued data on
1417 that stream dips low enough. Previously, we wouldn't ask the
1418 other side for more data until either it sent us more data (which
1419 it wasn't supposed to do if it had exhausted its window!) or we
1420 had completely flushed all our queued data. This flow control fix
1421 should improve throughput. Fixes bug 2756; bugfix on the earliest
1422 released versions of Tor (svn commit r152).
1423 - When a client finds that an origin circuit has run out of 16-bit
1424 stream IDs, we now mark it as unusable for new streams. Previously,
1425 we would try to close the entire circuit. Bugfix on 0.0.6.
1426 - Make it explicit that we don't cannibalize one-hop circuits. This
1427 happens in the wild, but doesn't turn out to be a problem because
1428 we fortunately don't use those circuits. Many thanks to outofwords
1429 for the initial analysis and to swissknife who confirmed that
1430 two-hop circuits are actually created.
1431 - Resolve an edge case in path weighting that could make us misweight
1432 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
1433 - Make the DNSPort option work with libevent 2.x. Don't alter the
1434 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
1436 o Minor bugfixes (directory authorities):
1437 - Make directory authorities more accurate at recording when
1438 relays that have failed several reachability tests became
1439 unreachable, so we can provide more accuracy at assigning Stable,
1440 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
1441 - Directory authorities are now more robust to hops back in time
1442 when calculating router stability. Previously, if a run of uptime
1443 or downtime appeared to be negative, the calculation could give
1444 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
1446 - Directory authorities will now attempt to download consensuses
1447 if their own efforts to make a live consensus have failed. This
1448 change means authorities that restart will fetch a valid
1449 consensus, and it means authorities that didn't agree with the
1450 current consensus will still fetch and serve it if it has enough
1451 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
1452 - Never vote for a server as "Running" if we have a descriptor for
1453 it claiming to be hibernating, and that descriptor was published
1454 more recently than our last contact with the server. Bugfix on
1455 0.2.0.3-alpha; fixes bug 911.
1456 - Directory authorities no longer change their opinion of, or vote on,
1457 whether a router is Running, unless they have themselves been
1458 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
1461 o Minor bugfixes (hidden services):
1462 - Log malformed requests for rendezvous descriptors as protocol
1463 warnings, not warnings. Also, use a more informative log message
1464 in case someone sees it at log level warning without prior
1465 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
1466 - Accept hidden service descriptors if we think we might be a hidden
1467 service directory, regardless of what our consensus says. This
1468 helps robustness, since clients and hidden services can sometimes
1469 have a more up-to-date view of the network consensus than we do,
1470 and if they think that the directory authorities list us a HSDir,
1471 we might actually be one. Related to bug 2732; bugfix on
1473 - Correct the warning displayed when a rendezvous descriptor exceeds
1474 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1476 - Clients and hidden services now use HSDir-flagged relays for hidden
1477 service descriptor downloads and uploads even if the relays have no
1478 DirPort set and the client has disabled TunnelDirConns. This will
1479 eventually allow us to give the HSDir flag to relays with no
1480 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
1481 - Only limit the lengths of single HS descriptors, even when multiple
1482 HS descriptors are published to an HSDir relay in a single POST
1483 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
1485 o Minor bugfixes (controllers):
1486 - Allow GETINFO fingerprint to return a fingerprint even when
1487 we have not yet built a router descriptor. Fixes bug 3577;
1488 bugfix on 0.2.0.1-alpha.
1489 - Send a SUCCEEDED stream event to the controller when a reverse
1490 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
1491 discovered by katmagic.
1492 - Remove a trailing asterisk from "exit-policy/default" in the
1493 output of the control port command "GETINFO info/names". Bugfix
1495 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
1496 2917. Bugfix on 0.1.1.1-alpha.
1497 - When we restart our relay, we might get a successful connection
1498 from the outside before we've started our reachability tests,
1499 triggering a warning: "ORPort found reachable, but I have no
1500 routerinfo yet. Failing to inform controller of success." This
1501 bug was harmless unless Tor is running under a controller
1502 like Vidalia, in which case the controller would never get a
1503 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1505 - When a controller changes TrackHostExits, remove mappings for
1506 hosts that should no longer have their exits tracked. Bugfix on
1508 - When a controller changes VirtualAddrNetwork, remove any mappings
1509 for hosts that were automapped to the old network. Bugfix on
1511 - When a controller changes one of the AutomapHosts* options, remove
1512 any mappings for hosts that should no longer be automapped. Bugfix
1514 - Fix an off-by-one error in calculating some controller command
1515 argument lengths. Fortunately, this mistake is harmless since
1516 the controller code does redundant NUL termination too. Found by
1517 boboper. Bugfix on 0.1.1.1-alpha.
1518 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
1519 would return "551 Internal error" rather than "552 Unrecognized key
1520 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
1521 - Don't spam the controller with events when we have no file
1522 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
1523 for log messages was already solved from bug 748.)
1524 - Emit a GUARD DROPPED controller event for a case we missed.
1525 - Ensure DNS requests launched by "RESOLVE" commands from the
1526 controller respect the __LeaveStreamsUnattached setconf options. The
1527 same goes for requests launched via DNSPort or transparent
1528 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
1530 o Minor bugfixes (config options):
1531 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
1532 Change the limit to 512 characters by removing base64 newlines.
1533 Fixes bug 2752. Fix by Michael Yakubovich.
1534 - Complain if PublishServerDescriptor is given multiple arguments that
1535 include 0 or 1. This configuration will be rejected in the future.
1536 Bugfix on 0.2.0.1-alpha; closes bug 1107.
1537 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
1538 Bugfix on 0.2.0.13-alpha; closes bug 928.
1540 o Minor bugfixes (log subsystem fixes):
1541 - When unable to format an address as a string, report its value
1542 as "???" rather than reusing the last formatted address. Bugfix
1544 - Be more consistent in our treatment of file system paths. "~" should
1545 get expanded to the user's home directory in the Log config option.
1546 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
1547 feature for the -f and --DataDirectory options.
1549 o Minor bugfixes (memory management):
1550 - Don't stack-allocate the list of supplementary GIDs when we're
1551 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1552 could take up to 256K, which is way too much stack. Found by
1553 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1554 - Save a couple bytes in memory allocation every time we escape
1555 certain characters in a string. Patch from Florian Zumbiehl.
1557 o Minor bugfixes (protocol correctness):
1558 - When checking for 1024-bit keys, check for 1024 bits, not 128
1559 bytes. This allows Tor to correctly discard keys of length 1017
1560 through 1023. Bugfix on 0.0.9pre5.
1561 - Require that introduction point keys and onion handshake keys
1562 have a public exponent of 65537. Starts to fix bug 3207; bugfix
1564 - Handle SOCKS messages longer than 128 bytes long correctly, rather
1565 than waiting forever for them to finish. Fixes bug 2330; bugfix
1566 on 0.2.0.16-alpha. Found by doorss.
1567 - Never relay a cell for a circuit we have already destroyed.
1568 Between marking a circuit as closeable and finally closing it,
1569 it may have been possible for a few queued cells to get relayed,
1570 even though they would have been immediately dropped by the next
1571 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
1572 - Never queue a cell for a circuit that's already been marked
1574 - Fix a spec conformance issue: the network-status-version token
1575 must be the first token in a v3 consensus or vote. Discovered by
1576 "parakeep". Bugfix on 0.2.0.3-alpha.
1577 - A networkstatus vote must contain exactly one signature. Spec
1578 conformance issue. Bugfix on 0.2.0.3-alpha.
1579 - When asked about a DNS record type we don't support via a
1580 client DNSPort, reply with NOTIMPL rather than an empty
1581 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
1582 - Make more fields in the controller protocol case-insensitive, since
1583 control-spec.txt said they were.
1585 o Minor bugfixes (log messages):
1586 - Fix a log message that said "bits" while displaying a value in
1587 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
1589 - Downgrade "no current certificates known for authority" message from
1590 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
1591 - Correctly describe errors that occur when generating a TLS object.
1592 Previously we would attribute them to a failure while generating a
1593 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
1595 - Fix an instance where a Tor directory mirror might accidentally
1596 log the IP address of a misbehaving Tor client. Bugfix on
1598 - Stop logging at severity 'warn' when some other Tor client tries
1599 to establish a circuit with us using weak DH keys. It's a protocol
1600 violation, but that doesn't mean ordinary users need to hear about
1601 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
1602 - If your relay can't keep up with the number of incoming create
1603 cells, it would log one warning per failure into your logs. Limit
1604 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
1606 o Minor bugfixes (build fixes):
1607 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1608 - When warning about missing zlib development packages during compile,
1609 give the correct package names. Bugfix on 0.2.0.1-alpha.
1610 - Fix warnings that newer versions of autoconf produce during
1611 ./autogen.sh. These warnings appear to be harmless in our case,
1612 but they were extremely verbose. Fixes bug 2020.
1613 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
1616 o Minor bugfixes (portability):
1617 - Write several files in text mode, on OSes that distinguish text
1618 mode from binary mode (namely, Windows). These files are:
1619 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1620 that collect those statistics; 'client_keys' and 'hostname' for
1621 hidden services that use authentication; and (in the tor-gencert
1622 utility) newly generated identity and signing keys. Previously,
1623 we wouldn't specify text mode or binary mode, leading to an
1624 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1625 the DirRecordUsageByCountry option which would have triggered
1626 the assertion failure was added), although this assertion failure
1627 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1628 - Selectively disable deprecation warnings on OS X because Lion
1629 started deprecating the shipped copy of openssl. Fixes bug 3643.
1630 - Use a wide type to hold sockets when built for 64-bit Windows.
1632 - Fix an issue that prevented static linking of libevent on
1633 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
1634 where we introduced the "--with-static-libevent" configure option.
1635 - Fix a bug with our locking implementation on Windows that couldn't
1636 correctly detect when a file was already locked. Fixes bug 2504,
1637 bugfix on 0.2.1.6-alpha.
1638 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1640 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
1641 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
1644 o Minor bugfixes (code correctness):
1645 - Always NUL-terminate the sun_path field of a sockaddr_un before
1646 passing it to the kernel. (Not a security issue: kernels are
1647 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1648 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1649 - Make connection_printf_to_buf()'s behaviour sane. Its callers
1650 expect it to emit a CRLF iff the format string ends with CRLF;
1651 it actually emitted a CRLF iff (a) the format string ended with
1652 CRLF or (b) the resulting string was over 1023 characters long or
1653 (c) the format string did not end with CRLF *and* the resulting
1654 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
1655 fixes part of bug 3407.
1656 - Make send_control_event_impl()'s behaviour sane. Its callers
1657 expect it to always emit a CRLF at the end of the string; it
1658 might have emitted extra control characters as well. Bugfix on
1659 0.1.1.9-alpha; fixes another part of bug 3407.
1660 - Make crypto_rand_int() check the value of its input correctly.
1661 Previously, it accepted values up to UINT_MAX, but could return a
1662 negative number if given a value above INT_MAX+1. Found by George
1663 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
1664 - Fix a potential null-pointer dereference while computing a
1665 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
1667 - If we fail to compute the identity digest of a v3 legacy keypair,
1668 warn, and don't use a buffer-full of junk instead. Bugfix on
1669 0.2.1.1-alpha; fixes bug 3106.
1670 - Resolve an untriggerable issue in smartlist_string_num_isin(),
1671 where if the function had ever in the future been used to check
1672 for the presence of a too-large number, it would have given an
1673 incorrect result. (Fortunately, we only used it for 16-bit
1674 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
1675 - Be more careful about reporting the correct error from a failed
1676 connect() system call. Under some circumstances, it was possible to
1677 look at an incorrect value for errno when sending the end reason.
1678 Bugfix on 0.1.0.1-rc.
1679 - Correctly handle an "impossible" overflow cases in connection byte
1680 counting, where we write or read more than 4GB on an edge connection
1681 in a single second. Bugfix on 0.1.2.8-beta.
1682 - Avoid a double mark-for-free warning when failing to attach a
1683 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
1685 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
1686 found by "cypherpunks". This bug was introduced before the first
1687 Tor release, in svn commit r110.
1688 - Fix a bug in bandwidth history state parsing that could have been
1689 triggered if a future version of Tor ever changed the timing
1690 granularity at which bandwidth history is measured. Bugfix on
1692 - Add assertions to check for overflow in arguments to
1693 base32_encode() and base32_decode(); fix a signed-unsigned
1694 comparison there too. These bugs are not actually reachable in Tor,
1695 but it's good to prevent future errors too. Found by doorss.
1696 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
1698 - Set target port in get_interface_address6() correctly. Bugfix
1699 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
1700 - Fix an impossible-to-actually-trigger buffer overflow in relay
1701 descriptor generation. Bugfix on 0.1.0.15.
1702 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
1704 o Minor bugfixes (code improvements):
1705 - After we free an internal connection structure, overwrite it
1706 with a different memory value than we use for overwriting a freed
1707 internal circuit structure. Should help with debugging. Suggested
1709 - If OpenSSL fails to make a duplicate of a private or public key, log
1710 an error message and try to exit cleanly. May help with debugging
1711 if bug 1209 ever remanifests.
1712 - Some options used different conventions for uppercasing of acronyms
1713 when comparing manpage and source. Fix those in favor of the
1714 manpage, as it makes sense to capitalize acronyms.
1715 - Take a first step towards making or.h smaller by splitting out
1716 function definitions for all source files in src/or/. Leave
1717 structures and defines in or.h for now.
1718 - Remove a few dead assignments during router parsing. Found by
1720 - Don't use 1-bit wide signed bit fields. Found by coverity.
1721 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1722 None of the cases where we did this before were wrong, but by making
1723 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1724 - The memarea code now uses a sentinel value at the end of each area
1725 to make sure nothing writes beyond the end of an area. This might
1726 help debug some conceivable causes of bug 930.
1727 - Always treat failure to allocate an RSA key as an unrecoverable
1729 - Add some more defensive programming for architectures that can't
1730 handle unaligned integer accesses. We don't know of any actual bugs
1731 right now, but that's the best time to fix them. Fixes bug 1943.
1733 o Minor bugfixes (misc):
1734 - Fix a rare bug in rend_fn unit tests: we would fail a test when
1735 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
1736 on 0.2.0.10-alpha; fixes bug 1808.
1737 - Where available, use Libevent 2.0's periodic timers so that our
1738 once-per-second cleanup code gets called even more closely to
1739 once per second than it would otherwise. Fixes bug 943.
1740 - Ignore OutboundBindAddress when connecting to localhost.
1741 Connections to localhost need to come _from_ localhost, or else
1742 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
1744 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
1746 - If any of the v3 certs we download are unparseable, we should
1747 actually notice the failure so we don't retry indefinitely. Bugfix
1748 on 0.2.0.x; reported by "rotator".
1749 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1750 Might help diagnosing bug 1051.
1751 - Make our 'torify' script more portable; if we have only one of
1752 'torsocks' or 'tsocks' installed, don't complain to the user;
1753 and explain our warning about tsocks better.
1754 - Fix some urls in the exit notice file and make it XHTML1.1 strict
1755 compliant. Based on a patch from Christian Kujau.
1757 o Documentation changes:
1758 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
1759 - Resolve all doxygen warnings except those for missing documentation.
1761 - Add doxygen documentation for more functions, fields, and types.
1762 - Convert the HACKING file to asciidoc, and add a few new sections
1763 to it, explaining how we use Git, how we make changelogs, and
1764 what should go in a patch.
1765 - Document the default socks host and port (127.0.0.1:9050) for
1767 - Removed some unnecessary files from the source distribution. The
1768 AUTHORS file has now been merged into the people page on the
1769 website. The roadmaps and design doc can now be found in the
1770 projects directory in svn.
1772 o Deprecated and removed features (config):
1773 - Remove the torrc.complete file. It hasn't been kept up to date
1774 and users will have better luck checking out the manpage.
1775 - Remove the HSAuthorityRecordStats option that version 0 hidden
1776 service authorities could use to track statistics of overall v0
1777 hidden service usage.
1778 - Remove the obsolete "NoPublish" option; it has been flagged
1779 as obsolete and has produced a warning since 0.1.1.18-rc.
1780 - Caches no longer download and serve v2 networkstatus documents
1781 unless FetchV2Networkstatus flag is set: these documents haven't
1782 haven't been used by clients or relays since 0.2.0.x. Resolves
1785 o Deprecated and removed features (controller):
1786 - The controller no longer accepts the old obsolete "addr-mappings/"
1787 or "unregistered-servers-" GETINFO values.
1788 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1789 always on; using them is necessary for correct forward-compatible
1792 o Deprecated and removed features (misc):
1793 - Hidden services no longer publish version 0 descriptors, and clients
1794 do not request or use version 0 descriptors. However, the old hidden
1795 service authorities still accept and serve version 0 descriptors
1796 when contacted by older hidden services/clients.
1797 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1798 anything since 0.2.1.16-rc.
1799 - Remove everything related to building the expert bundle for OS X.
1800 It has confused many users, doesn't work right on OS X 10.6,
1801 and is hard to get rid of once installed. Resolves bug 1274.
1802 - Remove support for .noconnect style addresses. Nobody was using
1803 them, and they provided another avenue for detecting Tor users
1804 via application-level web tricks.
1805 - When we fixed bug 1038 we had to put in a restriction not to send
1806 RELAY_EARLY cells on rend circuits. This was necessary as long
1807 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
1808 active. Now remove this obsolete check. Resolves bug 2081.
1809 - Remove workaround code to handle directory responses from servers
1810 that had bug 539 (they would send HTTP status 503 responses _and_
1811 send a body too). Since only server versions before
1812 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
1813 keep the workaround in place.
1814 - Remove the old 'fuzzy time' logic. It was supposed to be used for
1815 handling calculations where we have a known amount of clock skew and
1816 an allowed amount of unknown skew. But we only used it in three
1817 places, and we never adjusted the known/unknown skew values. This is
1818 still something we might want to do someday, but if we do, we'll
1819 want to do it differently.
1820 - Remove the "--enable-iphone" option to ./configure. According to
1821 reports from Marco Bonetti, Tor builds fine without any special
1822 tweaking on recent iPhone SDK versions.
1825 Changes in version 0.2.1.30 - 2011-02-23
1826 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
1827 change is a slight tweak to Tor's TLS handshake that makes relays
1828 and bridges that run this new version reachable from Iran again.
1829 We don't expect this tweak will win the arms race long-term, but it
1830 buys us time until we roll out a better solution.
1833 - Stop sending a CLOCK_SKEW controller status event whenever
1834 we fetch directory information from a relay that has a wrong clock.
1835 Instead, only inform the controller when it's a trusted authority
1836 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
1837 the rest of bug 1074.
1838 - Fix a bounds-checking error that could allow an attacker to
1839 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1841 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
1842 Tor would ignore their RelayBandwidthBurst setting,
1843 potentially using more bandwidth than expected. Bugfix on
1844 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
1845 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
1846 hidserv" in her torrc. The 'hidserv' argument never controlled
1847 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
1850 - Adjust our TLS Diffie-Hellman parameters to match those used by
1852 - Update to the February 1 2011 Maxmind GeoLite Country database.
1855 - Check for and reject overly long directory certificates and
1856 directory tokens before they have a chance to hit any assertions.
1857 Bugfix on 0.2.1.28. Found by "doorss".
1858 - Bring the logic that gathers routerinfos and assesses the
1859 acceptability of circuits into line. This prevents a Tor OP from
1860 getting locked in a cycle of choosing its local OR as an exit for a
1861 path (due to a .exit request) and then rejecting the circuit because
1862 its OR is not listed yet. It also prevents Tor clients from using an
1863 OR running in the same instance as an exit (due to a .exit request)
1864 if the OR does not meet the same requirements expected of an OR
1865 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1867 o Packaging changes:
1868 - Stop shipping the Tor specs files and development proposal documents
1869 in the tarball. They are now in a separate git repository at
1870 git://git.torproject.org/torspec.git
1871 - Do not include Git version tags as though they are SVN tags when
1872 generating a tarball from inside a repository that has switched
1873 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1876 Changes in version 0.2.1.29 - 2011-01-15
1877 Tor 0.2.1.29 continues our recent code security audit work. The main
1878 fix resolves a remote heap overflow vulnerability that can allow remote
1879 code execution. Other fixes address a variety of assert and crash bugs,
1880 most of which we think are hard to exploit remotely.
1882 o Major bugfixes (security):
1883 - Fix a heap overflow bug where an adversary could cause heap
1884 corruption. This bug probably allows remote code execution
1885 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1887 - Prevent a denial-of-service attack by disallowing any
1888 zlib-compressed data whose compression factor is implausibly
1889 high. Fixes part of bug 2324; reported by "doorss".
1890 - Zero out a few more keys in memory before freeing them. Fixes
1891 bug 2384 and part of bug 2385. These key instances found by
1892 "cypherpunks", based on Andrew Case's report about being able
1893 to find sensitive data in Tor's memory space if you have enough
1894 permissions. Bugfix on 0.0.2pre9.
1896 o Major bugfixes (crashes):
1897 - Prevent calls to Libevent from inside Libevent log handlers.
1898 This had potential to cause a nasty set of crashes, especially
1899 if running Libevent with debug logging enabled, and running
1900 Tor with a controller watching for low-severity log messages.
1901 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1902 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1903 underflow errors there too. Fixes the other part of bug 2324.
1904 - Fix a bug where we would assert if we ever had a
1905 cached-descriptors.new file (or another file read directly into
1906 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1907 on 0.2.1.25. Found by doorss.
1908 - Fix some potential asserts and parsing issues with grossly
1909 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1912 o Minor bugfixes (other):
1913 - Fix a bug with handling misformed replies to reverse DNS lookup
1914 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1915 bug reported by doorss.
1916 - Fix compilation on mingw when a pthreads compatibility library
1917 has been installed. (We don't want to use it, so we shouldn't
1918 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1919 - Fix a bug where we would declare that we had run out of virtual
1920 addresses when the address space was only half-exhausted. Bugfix
1922 - Correctly handle the case where AutomapHostsOnResolve is set but
1923 no virtual addresses are available. Fixes bug 2328; bugfix on
1924 0.1.2.1-alpha. Bug found by doorss.
1925 - Correctly handle wrapping around when we run out of virtual
1926 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
1929 - Update to the January 1 2011 Maxmind GeoLite Country database.
1930 - Introduce output size checks on all of our decryption functions.
1933 - Tor does not build packages correctly with Automake 1.6 and earlier;
1934 added a check to Makefile.am to make sure that we're building with
1935 Automake 1.7 or later.
1936 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1937 because we built it with a too-old version of automake. Thus that
1938 release broke ./configure --enable-openbsd-malloc, which is popular
1939 among really fast exit relays on Linux.
1942 Changes in version 0.2.1.28 - 2010-12-17
1943 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
1944 exploitable bugs. We also took this opportunity to change the IP address
1945 for one of our directory authorities, and to update the geoip database
1949 - Fix a remotely exploitable bug that could be used to crash instances
1950 of Tor remotely by overflowing on the heap. Remote-code execution
1951 hasn't been confirmed, but can't be ruled out. Everyone should
1952 upgrade. Bugfix on the 0.1.1 series and later.
1954 o Directory authority changes:
1955 - Change IP address and ports for gabelmoo (v3 directory authority).
1958 - Update to the December 1 2010 Maxmind GeoLite Country database.
1961 Changes in version 0.2.1.27 - 2010-11-23
1962 Yet another OpenSSL security patch broke its compatibility with Tor:
1963 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
1964 also took this opportunity to fix several crash bugs, integrate a new
1965 directory authority, and update the bundled GeoIP database.
1968 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1969 No longer set the tlsext_host_name extension on server SSL objects;
1970 but continue to set it on client SSL objects. Our goal in setting
1971 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1972 bugfix on 0.2.1.1-alpha.
1973 - Do not log messages to the controller while shrinking buffer
1974 freelists. Doing so would sometimes make the controller connection
1975 try to allocate a buffer chunk, which would mess up the internals
1976 of the freelist and cause an assertion failure. Fixes bug 1125;
1977 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1978 - Learn our external IP address when we're a relay or bridge, even if
1979 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1980 where we introduced bridge relays that don't need to publish to
1981 be useful. Fixes bug 2050.
1982 - Do even more to reject (and not just ignore) annotations on
1983 router descriptors received anywhere but from the cache. Previously
1984 we would ignore such annotations at first, but cache them to disk
1985 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1986 - When you're using bridges and your network goes away and your
1987 bridges get marked as down, recover when you attempt a new socks
1988 connection (if the network is back), rather than waiting up to an
1989 hour to try fetching new descriptors for your bridges. Bugfix on
1990 0.2.0.3-alpha; fixes bug 1981.
1993 - Move to the November 2010 Maxmind GeoLite country db (rather
1994 than the June 2009 ip-to-country GeoIP db) for our statistics that
1995 count how many users relays are seeing from each country. Now we'll
1996 have more accurate data, especially for many African countries.
1998 o New directory authorities:
1999 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
2003 - Fix an assertion failure that could occur in directory caches or
2004 bridge users when using a very short voting interval on a testing
2005 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
2007 - Enforce multiplicity rules when parsing annotations. Bugfix on
2008 0.2.0.8-alpha. Found by piebeer.
2009 - Allow handshaking OR connections to take a full KeepalivePeriod
2010 seconds to handshake. Previously, we would close them after
2011 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
2012 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
2014 - When building with --enable-gcc-warnings on OpenBSD, disable
2015 warnings in system headers. This makes --enable-gcc-warnings
2016 pass on OpenBSD 4.8.
2019 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
2020 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
2021 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
2022 Servers can start sending this code when enough clients recognize
2023 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
2024 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
2025 Patch from mingw-san.
2028 - Remove the old debian/ directory from the main Tor distribution.
2029 The official Tor-for-debian git repository lives at the URL
2030 https://git.torproject.org/debian/tor.git
2031 - Stop shipping the old doc/website/ directory in the tarball. We
2032 changed the website format in late 2010, and what we shipped in
2033 0.2.1.26 really wasn't that useful anyway.
2036 Changes in version 0.2.1.26 - 2010-05-02
2037 Tor 0.2.1.26 addresses the recent connection and memory overload
2038 problems we've been seeing on relays, especially relays with their
2039 DirPort open. If your relay has been crashing, or you turned it off
2040 because it used too many resources, give this release a try.
2042 This release also fixes yet another instance of broken OpenSSL libraries
2043 that was causing some relays to drop out of the consensus.
2046 - Teach relays to defend themselves from connection overload. Relays
2047 now close idle circuits early if it looks like they were intended
2048 for directory fetches. Relays are also more aggressive about closing
2049 TLS connections that have no circuits on them. Such circuits are
2050 unlikely to be re-used, and tens of thousands of them were piling
2051 up at the fast relays, causing the relays to run out of sockets
2052 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
2053 their directory fetches over TLS).
2054 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
2055 that claim to be earlier than 0.9.8m, but which have in reality
2056 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
2057 behavior. Possible fix for some cases of bug 1346.
2058 - Directory mirrors were fetching relay descriptors only from v2
2059 directory authorities, rather than v3 authorities like they should.
2060 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
2061 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
2064 - Finally get rid of the deprecated and now harmful notion of "clique
2065 mode", where directory authorities maintain TLS connections to
2069 - In the util/threads test, no longer free the test_mutex before all
2070 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2071 - The master thread could starve the worker threads quite badly on
2072 certain systems, causing them to run only partially in the allowed
2073 window. This resulted in test failures. Now the master thread sleeps
2074 occasionally for a few microseconds while the two worker-threads
2075 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2078 Changes in version 0.2.1.25 - 2010-03-16
2079 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
2080 prevent relays from guessing their IP address correctly. It also fixes
2081 several minor potential security bugs.
2084 - Fix a regression from our patch for bug 1244 that caused relays
2085 to guess their IP address incorrectly if they didn't set Address
2086 in their torrc and/or their address fails to resolve. Bugfix on
2087 0.2.1.23; fixes bug 1269.
2088 - When freeing a session key, zero it out completely. We only zeroed
2089 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2090 patched by ekir. Fixes bug 1254.
2093 - Fix a dereference-then-NULL-check sequence when publishing
2094 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2096 - Fix another dereference-then-NULL-check sequence. Bugfix on
2097 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2098 - Make sure we treat potentially not NUL-terminated strings correctly.
2099 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2102 Changes in version 0.2.1.24 - 2010-02-21
2103 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
2107 - Work correctly out-of-the-box with even more vendor-patched versions
2108 of OpenSSL. In particular, make it so Debian and OS X don't need
2109 customized patches to run/build.
2112 Changes in version 0.2.1.23 - 2010-02-13
2113 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
2114 again on the latest OS X, and updates the location of a directory
2117 o Major bugfixes (performance):
2118 - We were selecting our guards uniformly at random, and then weighting
2119 which of our guards we'd use uniformly at random. This imbalance
2120 meant that Tor clients were severely limited on throughput (and
2121 probably latency too) by the first hop in their circuit. Now we
2122 select guards weighted by currently advertised bandwidth. We also
2123 automatically discard guards picked using the old algorithm. Fixes
2124 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2127 - Make Tor work again on the latest OS X: when deciding whether to
2128 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2129 version at run-time, not compile time. We need to do this because
2130 Apple doesn't update its dev-tools headers when it updates its
2131 libraries in a security patch.
2132 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2133 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2134 a memory leak when requesting a hidden service descriptor we've
2135 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2139 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2140 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2143 - Avoid a mad rush at the beginning of each month when each client
2144 rotates half of its guards. Instead we spread the rotation out
2145 throughout the month, but we still avoid leaving a precise timestamp
2146 in the state file about when we first picked the guard. Improves
2147 over the behavior introduced in 0.1.2.17.
2150 Changes in version 0.2.1.22 - 2010-01-19
2151 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
2152 authorities -- it would tell you its whole history of bridge descriptors
2153 if you make the right directory request. This stable update also
2154 rotates two of the seven v3 directory authority keys and locations.
2156 o Directory authority changes:
2157 - Rotate keys (both v3 identity and relay identity) for moria1
2161 - Stop bridge directory authorities from answering dbg-stability.txt
2162 directory queries, which would let people fetch a list of all
2163 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2166 Changes in version 0.2.1.21 - 2009-12-21
2167 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
2168 library. If you use Tor on Linux / Unix and you're getting SSL
2169 renegotiation errors, upgrading should help. We also recommend an
2170 upgrade if you're an exit relay.
2173 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2174 handshake from working unless we explicitly tell OpenSSL that we
2175 are using SSL renegotiation safely. We are, of course, but OpenSSL
2176 0.9.8l won't work unless we say we are.
2177 - Avoid crashing if the client is trying to upload many bytes and the
2178 circuit gets torn down at the same time, or if the flip side
2179 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
2182 - Do not refuse to learn about authority certs and v2 networkstatus
2183 documents that are older than the latest consensus. This bug might
2184 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2185 Spotted and fixed by xmux.
2186 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
2187 trigger platform-specific option misparsing case found by Coverity
2189 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
2190 trigger assert. Fixes bug 1173.
2193 Changes in version 0.2.1.20 - 2009-10-15
2194 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
2195 services at once, prepares for more performance improvements, and
2196 fixes a bunch of smaller bugs.
2198 The Windows and OS X bundles also include a more recent Vidalia,
2199 and switch from Privoxy to Polipo.
2201 The OS X installers are now drag and drop. It's best to un-install
2202 Tor/Vidalia and then install this new bundle, rather than upgrade. If
2203 you want to upgrade, you'll need to update the paths for Tor and Polipo
2204 in the Vidalia Settings window.
2207 - Send circuit or stream sendme cells when our window has decreased
2208 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
2209 by Karsten when testing the "reduce circuit window" performance
2210 patch. Bugfix on the 54th commit on Tor -- from July 2002,
2211 before the release of Tor 0.0.0. This is the new winner of the
2213 - Fix a remotely triggerable memory leak when a consensus document
2214 contains more than one signature from the same voter. Bugfix on
2216 - Avoid segfault in rare cases when finishing an introduction circuit
2217 as a client and finding out that we don't have an introduction key
2218 for it. Fixes bug 1073. Reported by Aaron Swartz.
2221 - Tor now reads the "circwindow" parameter out of the consensus,
2222 and uses that value for its circuit package window rather than the
2223 default of 1000 cells. Begins the implementation of proposal 168.
2225 o New directory authorities:
2226 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
2228 - Move moria1 and tonga to alternate IP addresses.
2231 - Fix a signed/unsigned compile warning in 0.2.1.19.
2232 - Fix possible segmentation fault on directory authorities. Bugfix on
2234 - Fix an extremely rare infinite recursion bug that could occur if
2235 we tried to log a message after shutting down the log subsystem.
2236 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
2237 - Fix an obscure bug where hidden services on 64-bit big-endian
2238 systems might mis-read the timestamp in v3 introduce cells, and
2239 refuse to connect back to the client. Discovered by "rotor".
2240 Bugfix on 0.2.1.6-alpha.
2241 - We were triggering a CLOCK_SKEW controller status event whenever
2242 we connect via the v2 connection protocol to any relay that has
2243 a wrong clock. Instead, we should only inform the controller when
2244 it's a trusted authority that claims our clock is wrong. Bugfix
2245 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
2246 - We were telling the controller about CHECKING_REACHABILITY and
2247 REACHABILITY_FAILED status events whenever we launch a testing
2248 circuit or notice that one has failed. Instead, only tell the
2249 controller when we want to inform the user of overall success or
2250 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
2252 - Don't warn when we're using a circuit that ends with a node
2253 excluded in ExcludeExitNodes, but the circuit is not used to access
2254 the outside world. This should help fix bug 1090. Bugfix on
2256 - Work around a small memory leak in some versions of OpenSSL that
2257 stopped the memory used by the hostname TLS extension from being
2261 - Add a "getinfo status/accepted-server-descriptor" controller
2262 command, which is the recommended way for controllers to learn
2263 whether our server descriptor has been successfully received by at
2264 least on directory authority. Un-recommend good-server-descriptor
2265 getinfo and status events until we have a better design for them.
2268 Changes in version 0.2.1.19 - 2009-07-28
2269 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
2273 - Make accessing hidden services on 0.2.1.x work right again.
2274 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
2275 part of patch provided by "optimist".
2278 - When a relay/bridge is writing out its identity key fingerprint to
2279 the "fingerprint" file and to its logs, write it without spaces. Now
2280 it will look like the fingerprints in our bridges documentation,
2281 and confuse fewer users.
2284 - Relays no longer publish a new server descriptor if they change
2285 their MaxAdvertisedBandwidth config option but it doesn't end up
2286 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
2287 fixes bug 1026. Patch from Sebastian.
2288 - Avoid leaking memory every time we get a create cell but we have
2289 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
2290 fixes bug 1034. Reported by BarkerJr.
2293 Changes in version 0.2.1.18 - 2009-07-24
2294 Tor 0.2.1.18 lays the foundations for performance improvements,
2295 adds status events to help users diagnose bootstrap problems, adds
2296 optional authentication/authorization for hidden services, fixes a
2297 variety of potential anonymity problems, and includes a huge pile of
2298 other features and bug fixes.
2300 o Major features (clients):
2301 - Start sending "bootstrap phase" status events to the controller,
2302 so it can keep the user informed of progress fetching directory
2303 information and establishing circuits. Also inform the controller
2304 if we think we're stuck at a particular bootstrap phase. Implements
2306 - Clients replace entry guards that were chosen more than a few months
2307 ago. This change should significantly improve client performance,
2308 especially once more people upgrade, since relays that have been
2309 a guard for a long time are currently overloaded.
2310 - Network status consensus documents and votes now contain bandwidth
2311 information for each relay. Clients use the bandwidth values
2312 in the consensus, rather than the bandwidth values in each
2313 relay descriptor. This approach opens the door to more accurate
2314 bandwidth estimates once the directory authorities start doing
2315 active measurements. Implements part of proposal 141.
2317 o Major features (relays):
2318 - Disable and refactor some debugging checks that forced a linear scan
2319 over the whole server-side DNS cache. These accounted for over 50%
2320 of CPU time on a relatively busy exit node's gprof profile. Also,
2321 disable some debugging checks that appeared in exit node profile
2322 data. Found by Jacob.
2323 - New DirPortFrontPage option that takes an html file and publishes
2324 it as "/" on the DirPort. Now relay operators can provide a
2325 disclaimer without needing to set up a separate webserver. There's
2326 a sample disclaimer in contrib/tor-exit-notice.html.
2328 o Major features (hidden services):
2329 - Make it possible to build hidden services that only certain clients
2330 are allowed to connect to. This is enforced at several points,
2331 so that unauthorized clients are unable to send INTRODUCE cells
2332 to the service, or even (depending on the type of authentication)
2333 to learn introduction points. This feature raises the bar for
2334 certain kinds of active attacks against hidden services. Design
2335 and code by Karsten Loesing. Implements proposal 121.
2336 - Relays now store and serve v2 hidden service descriptors by default,
2337 i.e., the new default value for HidServDirectoryV2 is 1. This is
2338 the last step in proposal 114, which aims to make hidden service
2339 lookups more reliable.
2341 o Major features (path selection):
2342 - ExitNodes and Exclude*Nodes config options now allow you to restrict
2343 by country code ("{US}") or IP address or address pattern
2344 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
2345 refinement to decide what config options should take priority if
2346 you ask to both use a particular node and exclude it.
2348 o Major features (misc):
2349 - When building a consensus, do not include routers that are down.
2350 This cuts down 30% to 40% on consensus size. Implements proposal
2352 - New TestingTorNetwork config option to allow adjustment of
2353 previously constant values that could slow bootstrapping. Implements
2354 proposal 135. Patch from Karsten.
2355 - Convert many internal address representations to optionally hold
2356 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
2357 elements. Make resolver code handle nameservers located at IPv6
2359 - More work on making our TLS handshake blend in: modify the list
2360 of ciphers advertised by OpenSSL in client mode to even more
2361 closely resemble a common web browser. We cheat a little so that
2362 we can advertise ciphers that the locally installed OpenSSL doesn't
2364 - Use the TLS1 hostname extension to more closely resemble browser
2367 o Security fixes (anonymity/entropy):
2368 - Never use a connection with a mismatched address to extend a
2369 circuit, unless that connection is canonical. A canonical
2370 connection is one whose address is authenticated by the router's
2371 identity key, either in a NETINFO cell or in a router descriptor.
2372 - Implement most of proposal 110: The first K cells to be sent
2373 along a circuit are marked as special "early" cells; only K "early"
2374 cells will be allowed. Once this code is universal, we can block
2375 certain kinds of denial-of-service attack by requiring that EXTEND
2376 commands must be sent using an "early" cell.
2377 - Resume using OpenSSL's RAND_poll() for better (and more portable)
2378 cross-platform entropy collection again. We used to use it, then
2379 stopped using it because of a bug that could crash systems that
2380 called RAND_poll when they had a lot of fds open. It looks like the
2381 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
2382 at startup, and to call RAND_poll() when we reseed later only if
2383 we have a non-buggy OpenSSL version.
2384 - When the client is choosing entry guards, now it selects at most
2385 one guard from a given relay family. Otherwise we could end up with
2386 all of our entry points into the network run by the same operator.
2387 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
2388 - Do not use or believe expired v3 authority certificates. Patch
2389 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
2390 - Drop begin cells to a hidden service if they come from the middle
2391 of a circuit. Patch from lark.
2392 - When we erroneously receive two EXTEND cells for the same circuit
2393 ID on the same connection, drop the second. Patch from lark.
2394 - Authorities now vote for the Stable flag for any router whose
2395 weighted MTBF is at least 5 days, regardless of the mean MTBF.
2396 - Clients now never report any stream end reason except 'MISC'.
2397 Implements proposal 148.
2399 o Major bugfixes (crashes):
2400 - Parse dates and IPv4 addresses in a locale- and libc-independent
2401 manner, to avoid platform-dependent behavior on malformed input.
2402 - Fix a crash that occurs on exit nodes when a nameserver request
2403 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
2404 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
2406 - Do not assume that a stack-allocated character array will be
2407 64-bit aligned on platforms that demand that uint64_t access is
2408 aligned. Possible fix for bug 604.
2409 - Resolve a very rare crash bug that could occur when the user forced
2410 a nameserver reconfiguration during the middle of a nameserver
2411 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
2412 - Avoid a "0 divided by 0" calculation when calculating router uptime
2413 at directory authorities. Bugfix on 0.2.0.8-alpha.
2414 - Fix an assertion bug in parsing policy-related options; possible fix
2416 - Rate-limit too-many-sockets messages: when they happen, they happen
2417 a lot and end up filling up the disk. Resolves bug 748.
2418 - Fix a race condition that could cause crashes or memory corruption
2419 when running as a server with a controller listening for log
2421 - Avoid crashing when we have a policy specified in a DirPolicy or
2422 SocksPolicy or ReachableAddresses option with ports set on it,
2423 and we re-load the policy. May fix bug 996.
2424 - Fix an assertion failure on 64-bit platforms when we allocated
2425 memory right up to the end of a memarea, then realigned the memory
2426 one step beyond the end. Fixes a possible cause of bug 930.
2427 - Protect the count of open sockets with a mutex, so we can't
2428 corrupt it when two threads are closing or opening sockets at once.
2429 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
2431 o Major bugfixes (clients):
2432 - Discard router descriptors as we load them if they are more than
2433 five days old. Otherwise if Tor is off for a long time and then
2434 starts with cached descriptors, it will try to use the onion keys
2435 in those obsolete descriptors when building circuits. Fixes bug 887.
2436 - When we choose to abandon a new entry guard because we think our
2437 older ones might be better, close any circuits pending on that
2438 new entry guard connection. This fix should make us recover much
2439 faster when our network is down and then comes back. Bugfix on
2440 0.1.2.8-beta; found by lodger.
2441 - When Tor clients restart after 1-5 days, they discard all their
2442 cached descriptors as too old, but they still use the cached
2443 consensus document. This approach is good for robustness, but
2444 bad for performance: since they don't know any bandwidths, they
2445 end up choosing at random rather than weighting their choice by
2446 speed. Fixed by the above feature of putting bandwidths in the
2449 o Major bugfixes (relays):
2450 - Relays were falling out of the networkstatus consensus for
2451 part of a day if they changed their local config but the
2452 authorities discarded their new descriptor as "not sufficiently
2453 different". Now directory authorities accept a descriptor as changed
2454 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
2456 - Ensure that two circuits can never exist on the same connection
2457 with the same circuit ID, even if one is marked for close. This
2458 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2459 - Directory authorities were neglecting to mark relays down in their
2460 internal histories if the relays fall off the routerlist without
2461 ever being found unreachable. So there were relays in the histories
2462 that haven't been seen for eight months, and are listed as being
2463 up for eight months. This wreaked havoc on the "median wfu" and
2464 "median mtbf" calculations, in turn making Guard and Stable flags
2465 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
2468 o Major bugfixes (hidden services):
2469 - When establishing a hidden service, introduction points that
2470 originate from cannibalized circuits were completely ignored
2471 and not included in rendezvous service descriptors. This might
2472 have been another reason for delay in making a hidden service
2473 available. Bugfix from long ago (0.0.9.x?)
2475 o Major bugfixes (memory and resource management):
2476 - Fixed some memory leaks -- some quite frequent, some almost
2477 impossible to trigger -- based on results from Coverity.
2478 - Speed up parsing and cut down on memory fragmentation by using
2479 stack-style allocations for parsing directory objects. Previously,
2480 this accounted for over 40% of allocations from within Tor's code
2481 on a typical directory cache.
2482 - Use a Bloom filter rather than a digest-based set to track which
2483 descriptors we need to keep around when we're cleaning out old
2484 router descriptors. This speeds up the computation significantly,
2485 and may reduce fragmentation.
2487 o New/changed config options:
2488 - Now NodeFamily and MyFamily config options allow spaces in
2489 identity fingerprints, so it's easier to paste them in.
2490 Suggested by Lucky Green.
2491 - Allow ports 465 and 587 in the default exit policy again. We had
2492 rejected them in 0.1.0.15, because back in 2005 they were commonly
2493 misconfigured and ended up as spam targets. We hear they are better
2494 locked down these days.
2495 - Make TrackHostExit mappings expire a while after their last use, not
2496 after their creation. Patch from Robert Hogan.
2497 - Add an ExcludeExitNodes option so users can list a set of nodes
2498 that should be be excluded from the exit node position, but
2499 allowed elsewhere. Implements proposal 151.
2500 - New --hush command-line option similar to --quiet. While --quiet
2501 disables all logging to the console on startup, --hush limits the
2502 output to messages of warning and error severity.
2503 - New configure/torrc options (--enable-geoip-stats,
2504 DirRecordUsageByCountry) to record how many IPs we've served
2505 directory info to in each country code, how many status documents
2506 total we've sent to each country code, and what share of the total
2507 directory requests we should expect to see.
2508 - Make outbound DNS packets respect the OutboundBindAddress setting.
2509 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
2510 - Allow separate log levels to be configured for different logging
2511 domains. For example, this allows one to log all notices, warnings,
2512 or errors, plus all memory management messages of level debug or
2513 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
2514 - Update to the "June 3 2009" ip-to-country file.
2516 o Minor features (relays):
2517 - Raise the minimum rate limiting to be a relay from 20000 bytes
2518 to 20480 bytes (aka 20KB/s), to match our documentation. Also
2519 update directory authorities so they always assign the Fast flag
2520 to relays with 20KB/s of capacity. Now people running relays won't
2521 suddenly find themselves not seeing any use, if the network gets
2523 - If we're a relay and we change our IP address, be more verbose
2524 about the reason that made us change. Should help track down
2525 further bugs for relays on dynamic IP addresses.
2526 - Exit servers can now answer resolve requests for ip6.arpa addresses.
2527 - Implement most of Proposal 152: allow specialized servers to permit
2528 single-hop circuits, and clients to use those servers to build
2529 single-hop circuits when using a specialized controller. Patch
2530 from Josh Albrecht. Resolves feature request 768.
2531 - When relays do their initial bandwidth measurement, don't limit
2532 to just our entry guards for the test circuits. Otherwise we tend
2533 to have multiple test circuits going through a single entry guard,
2534 which makes our bandwidth test less accurate. Fixes part of bug 654;
2535 patch contributed by Josh Albrecht.
2537 o Minor features (directory authorities):
2538 - Try not to open more than one descriptor-downloading connection
2539 to an authority at once. This should reduce load on directory
2540 authorities. Fixes bug 366.
2541 - Add cross-certification to newly generated certificates, so that
2542 a signing key is enough information to look up a certificate. Start
2543 serving certificates by <identity digest, signing key digest>
2544 pairs. Implements proposal 157.
2545 - When a directory authority downloads a descriptor that it then
2546 immediately rejects, do not retry downloading it right away. Should
2547 save some bandwidth on authorities. Fix for bug 888. Patch by
2549 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2550 help debug WFU and MTBF calculations.
2551 - In directory authorities' approved-routers files, allow
2552 fingerprints with or without space.
2554 o Minor features (directory mirrors):
2555 - When a download gets us zero good descriptors, do not notify
2556 Tor that new directory information has arrived.
2557 - Servers support a new URL scheme for consensus downloads that
2558 allows the client to specify which authorities are trusted.
2559 The server then only sends the consensus if the client will trust
2560 it. Otherwise a 404 error is sent back. Clients use this
2561 new scheme when the server supports it (meaning it's running
2562 0.2.1.1-alpha or later). Implements proposal 134.
2564 o Minor features (bridges):
2565 - If the bridge config line doesn't specify a port, assume 443.
2566 This makes bridge lines a bit smaller and easier for users to
2568 - If we're using bridges and our network goes away, be more willing
2569 to forgive our bridges and try again when we get an application
2572 o Minor features (hidden services):
2573 - When the client launches an introduction circuit, retry with a
2574 new circuit after 30 seconds rather than 60 seconds.
2575 - Launch a second client-side introduction circuit in parallel
2576 after a delay of 15 seconds (based on work by Christian Wilms).
2577 - Hidden services start out building five intro circuits rather
2578 than three, and when the first three finish they publish a service
2579 descriptor using those. Now we publish our service descriptor much
2580 faster after restart.
2581 - Drop the requirement to have an open dir port for storing and
2582 serving v2 hidden service descriptors.
2584 o Minor features (build and packaging):
2585 - On Linux, use the prctl call to re-enable core dumps when the User
2587 - Try to make sure that the version of Libevent we're running with
2588 is binary-compatible with the one we built with. May address bug
2590 - Add a new --enable-local-appdata configuration switch to change
2591 the default location of the datadir on win32 from APPDATA to
2592 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
2593 entirely. Patch from coderman.
2594 - Build correctly against versions of OpenSSL 0.9.8 or later that
2595 are built without support for deprecated functions.
2596 - On platforms with a maximum syslog string length, truncate syslog
2597 messages to that length ourselves, rather than relying on the
2598 system to do it for us.
2599 - Automatically detect MacOSX versions earlier than 10.4.0, and
2600 disable kqueue from inside Tor when running with these versions.
2601 We previously did this from the startup script, but that was no
2602 help to people who didn't use the startup script. Resolves bug 863.
2603 - Build correctly when configured to build outside the main source
2604 path. Patch from Michael Gold.
2605 - Disable GCC's strict alias optimization by default, to avoid the
2606 likelihood of its introducing subtle bugs whenever our code violates
2607 the letter of C99's alias rules.
2608 - Change the contrib/tor.logrotate script so it makes the new
2609 logs as "_tor:_tor" rather than the default, which is generally
2610 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2611 - Change our header file guard macros to be less likely to conflict
2612 with system headers. Adam Langley noticed that we were conflicting
2613 with log.h on Android.
2614 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2615 and stop using a warning that had become unfixably verbose under
2617 - Use a lockfile to make sure that two Tor processes are not
2618 simultaneously running with the same datadir.
2619 - Allow OpenSSL to use dynamic locks if it wants.
2620 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
2622 o Minor features (controllers):
2623 - When generating circuit events with verbose nicknames for
2624 controllers, try harder to look up nicknames for routers on a
2625 circuit. (Previously, we would look in the router descriptors we had
2626 for nicknames, but not in the consensus.) Partial fix for bug 941.
2627 - New controller event NEWCONSENSUS that lists the networkstatus
2628 lines for every recommended relay. Now controllers like Torflow
2629 can keep up-to-date on which relays they should be using.
2630 - New controller event "clients_seen" to report a geoip-based summary
2631 of which countries we've seen clients from recently. Now controllers
2632 like Vidalia can show bridge operators that they're actually making
2634 - Add a 'getinfo status/clients-seen' controller command, in case
2635 controllers want to hear clients_seen events but connect late.
2636 - New CONSENSUS_ARRIVED event to note when a new consensus has
2637 been fetched and validated.
2638 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
2639 controllers to prevent SIGHUP from reloading the configuration.
2641 - Return circuit purposes in response to GETINFO circuit-status.
2643 - Serve the latest v3 networkstatus consensus via the control
2644 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2645 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2646 controller can query our current bootstrap state in case it attaches
2647 partway through and wants to catch up.
2648 - Provide circuit purposes along with circuit events to the controller.
2650 o Minor features (tools):
2651 - Do not have tor-resolve automatically refuse all .onion addresses;
2652 if AutomapHostsOnResolve is set in your torrc, this will work fine.
2653 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2654 people find host:port too confusing.
2655 - Print the SOCKS5 error message string as well as the error code
2656 when a tor-resolve request fails. Patch from Jacob.
2658 o Minor bugfixes (memory and resource management):
2659 - Clients no longer cache certificates for authorities they do not
2660 recognize. Bugfix on 0.2.0.9-alpha.
2661 - Do not use C's stdio library for writing to log files. This will
2662 improve logging performance by a minute amount, and will stop
2663 leaking fds when our disk is full. Fixes bug 861.
2664 - Stop erroneous use of O_APPEND in cases where we did not in fact
2665 want to re-seek to the end of a file before every last write().
2666 - Fix a small alignment and memory-wasting bug on buffer chunks.
2668 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2669 to avoid unused RAM in buffer chunks and memory pools.
2670 - Reduce the default smartlist size from 32 to 16; it turns out that
2671 most smartlists hold around 8-12 elements tops.
2672 - Make dumpstats() log the fullness and size of openssl-internal
2674 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2675 patch to their OpenSSL, turn it on to save memory on servers. This
2676 patch will (with any luck) get included in a mainline distribution
2678 - Fix a memory leak when v3 directory authorities load their keys
2679 and cert from disk. Bugfix on 0.2.0.1-alpha.
2680 - Stop using malloc_usable_size() to use more area than we had
2681 actually allocated: it was safe, but made valgrind really unhappy.
2682 - Make the assert_circuit_ok() function work correctly on circuits that
2683 have already been marked for close.
2684 - Fix uninitialized size field for memory area allocation: may improve
2685 memory performance during directory parsing.
2687 o Minor bugfixes (clients):
2688 - Stop reloading the router list from disk for no reason when we
2689 run out of reachable directory mirrors. Once upon a time reloading
2690 it would set the 'is_running' flag back to 1 for them. It hasn't
2691 done that for a long time.
2692 - When we had picked an exit node for a connection, but marked it as
2693 "optional", and it turned out we had no onion key for the exit,
2694 stop wanting that exit and try again. This situation may not
2695 be possible now, but will probably become feasible with proposal
2696 158. Spotted by rovv. Fixes another case of bug 752.
2697 - Fix a bug in address parsing that was preventing bridges or hidden
2698 service targets from being at IPv6 addresses.
2699 - Do not remove routers as too old if we do not have any consensus
2700 document. Bugfix on 0.2.0.7-alpha.
2701 - When an exit relay resolves a stream address to a local IP address,
2702 do not just keep retrying that same exit relay over and
2703 over. Instead, just close the stream. Addresses bug 872. Bugfix
2704 on 0.2.0.32. Patch from rovv.
2705 - Made Tor a little less aggressive about deleting expired
2706 certificates. Partial fix for bug 854.
2707 - Treat duplicate certificate fetches as failures, so that we do
2708 not try to re-fetch an expired certificate over and over and over.
2709 - Do not say we're fetching a certificate when we'll in fact skip it
2710 because of a pending download.
2711 - If we have correct permissions on $datadir, we complain to stdout
2712 and fail to start. But dangerous permissions on
2713 $datadir/cached-status/ would cause us to open a log and complain
2714 there. Now complain to stdout and fail to start in both cases. Fixes
2715 bug 820, reported by seeess.
2717 o Minor bugfixes (bridges):
2718 - When we made bridge authorities stop serving bridge descriptors over
2719 unencrypted links, we also broke DirPort reachability testing for
2720 bridges. So bridges with a non-zero DirPort were printing spurious
2721 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
2722 - Don't allow a bridge to publish its router descriptor to a
2723 non-bridge directory authority. Fixes part of bug 932.
2724 - When we change to or from being a bridge, reset our counts of
2725 client usage by country. Fixes bug 932.
2727 o Minor bugfixes (relays):
2728 - Log correct error messages for DNS-related network errors on
2730 - Actually return -1 in the error case for read_bandwidth_usage().
2731 Harmless bug, since we currently don't care about the return value
2732 anywhere. Bugfix on 0.2.0.9-alpha.
2733 - Provide a more useful log message if bug 977 (related to buffer
2734 freelists) ever reappears, and do not crash right away.
2735 - We were already rejecting relay begin cells with destination port
2736 of 0. Now also reject extend cells with destination port or address
2737 of 0. Suggested by lark.
2738 - When we can't transmit a DNS request due to a network error, retry
2739 it after a while, and eventually transmit a failing response to
2740 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
2741 - Solve a bug that kept hardware crypto acceleration from getting
2742 enabled when accounting was turned on. Fixes bug 907. Bugfix on
2744 - When a canonical connection appears later in our internal list
2745 than a noncanonical one for a given OR ID, always use the
2746 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
2748 - Avoid some nasty corner cases in the logic for marking connections
2749 as too old or obsolete or noncanonical for circuits. Partial
2751 - Fix another interesting corner-case of bug 891 spotted by rovv:
2752 Previously, if two hosts had different amounts of clock drift, and
2753 one of them created a new connection with just the wrong timing,
2754 the other might decide to deprecate the new connection erroneously.
2755 Bugfix on 0.1.1.13-alpha.
2756 - If one win32 nameserver fails to get added, continue adding the
2757 rest, and don't automatically fail.
2758 - Fix a bug where an unreachable relay would establish enough
2759 reachability testing circuits to do a bandwidth test -- if
2760 we already have a connection to the middle hop of the testing
2761 circuit, then it could establish the last hop by using the existing
2762 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2763 circuits no longer use entry guards in 0.2.1.3-alpha.
2765 o Minor bugfixes (directory authorities):
2766 - Limit uploaded directory documents to be 16M rather than 500K.
2767 The directory authorities were refusing v3 consensus votes from
2768 other authorities, since the votes are now 504K. Fixes bug 959;
2769 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
2770 - Directory authorities should never send a 503 "busy" response to
2771 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
2773 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
2774 headers. Bugfix on 0.2.0.10-alpha.
2776 o Minor bugfixes (hidden services):
2777 - When we can't find an intro key for a v2 hidden service descriptor,
2778 fall back to the v0 hidden service descriptor and log a bug message.
2779 Workaround for bug 1024.
2780 - In very rare situations new hidden service descriptors were
2781 published earlier than 30 seconds after the last change to the
2782 service. (We currently think that a hidden service descriptor
2783 that's been stable for 30 seconds is worth publishing.)
2784 - If a hidden service sends us an END cell, do not consider
2785 retrying the connection; just close it. Patch from rovv.
2786 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2787 service directories if they have no advertised dir port. Bugfix
2790 o Minor bugfixes (tools):
2791 - In the torify(1) manpage, mention that tsocks will leak your
2794 o Minor bugfixes (controllers):
2795 - If the controller claimed responsibility for a stream, but that
2796 stream never finished making its connection, it would live
2797 forever in circuit_wait state. Now we close it after SocksTimeout
2798 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
2799 - Make DNS resolved controller events into "CLOSED", not
2800 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2802 - The control port would close the connection before flushing long
2803 replies, such as the network consensus, if a QUIT command was issued
2804 before the reply had completed. Now, the control port flushes all
2805 pending replies before closing the connection. Also fix a spurious
2806 warning when a QUIT command is issued after a malformed or rejected
2807 AUTHENTICATE command, but before the connection was closed. Patch
2808 by Marcus Griep. Fixes bugs 1015 and 1016.
2809 - Fix a bug that made stream bandwidth get misreported to the
2812 o Deprecated and removed features:
2813 - The old "tor --version --version" command, which would print out
2814 the subversion "Id" of most of the source files, is now removed. It
2815 turned out to be less useful than we'd expected, and harder to
2817 - RedirectExits has been removed. It was deprecated since
2819 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
2820 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
2821 - Cell pools are now always enabled; --disable-cell-pools is ignored.
2822 - Directory mirrors no longer fetch the v1 directory or
2823 running-routers files. They are obsolete, and nobody asks for them
2824 anymore. This is the first step to making v1 authorities obsolete.
2825 - Take out the TestVia config option, since it was a workaround for
2826 a bug that was fixed in Tor 0.1.1.21.
2827 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2828 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2829 and nobody seems to be using them. Fixes bug 754. Bugfix on
2830 0.1.0.1-rc. Patch from Christian Wilms.
2831 - Remove all backward-compatibility code for relays running
2832 versions of Tor so old that they no longer work at all on the
2835 o Code simplifications and refactoring:
2836 - Tool-assisted documentation cleanup. Nearly every function or
2837 static variable in Tor should have its own documentation now.
2838 - Rename the confusing or_is_obsolete field to the more appropriate
2839 is_bad_for_new_circs, and move it to or_connection_t where it
2841 - Move edge-only flags from connection_t to edge_connection_t: not
2842 only is this better coding, but on machines of plausible alignment,
2843 it should save 4-8 bytes per connection_t. "Every little bit helps."
2844 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
2845 for consistency; keep old option working for backward compatibility.
2846 - Simplify the code for finding connections to use for a circuit.
2847 - Revise the connection_new functions so that a more typesafe variant
2848 exists. This will work better with Coverity, and let us find any
2849 actual mistakes we're making here.
2850 - Refactor unit testing logic so that dmalloc can be used sensibly
2851 with unit tests to check for memory leaks.
2852 - Move all hidden-service related fields from connection and circuit
2853 structure to substructures: this way they won't eat so much memory.
2854 - Squeeze 2-5% out of client performance (according to oprofile) by
2855 improving the implementation of some policy-manipulation functions.
2856 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2857 be more efficient. Formerly it was quadratic in the number of
2858 servers; now it should be linear. Fixes bug 509.
2859 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2860 and n_conn_id_digest fields into a separate structure that's
2861 only needed when the circuit has not yet attached to an n_conn.
2862 - Optimize out calls to time(NULL) that occur for every IO operation,
2863 or for every cell. On systems like Windows where time() is a
2864 slow syscall, this fix will be slightly helpful.
2867 Changes in version 0.2.0.35 - 2009-06-24
2869 - Avoid crashing in the presence of certain malformed descriptors.
2870 Found by lark, and by automated fuzzing.
2871 - Fix an edge case where a malicious exit relay could convince a
2872 controller that the client's DNS question resolves to an internal IP
2873 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
2876 - Finally fix the bug where dynamic-IP relays disappear when their
2877 IP address changes: directory mirrors were mistakenly telling
2878 them their old address if they asked via begin_dir, so they
2879 never got an accurate answer about their new address, so they
2880 just vanished after a day. For belt-and-suspenders, relays that
2881 don't set Address in their config now avoid using begin_dir for
2882 all direct connections. Should fix bugs 827, 883, and 900.
2883 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
2884 that would occur on some exit nodes when DNS failures and timeouts
2885 occurred in certain patterns. Fix for bug 957.
2888 - When starting with a cache over a few days old, do not leak
2889 memory for the obsolete router descriptors in it. Bugfix on
2890 0.2.0.33; fixes bug 672.
2891 - Hidden service clients didn't use a cached service descriptor that
2892 was older than 15 minutes, but wouldn't fetch a new one either,
2893 because there was already one in the cache. Now, fetch a v2
2894 descriptor unless the same descriptor was added to the cache within
2895 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
2898 Changes in version 0.2.0.34 - 2009-02-08
2899 Tor 0.2.0.34 features several more security-related fixes. You should
2900 upgrade, especially if you run an exit relay (remote crash) or a
2901 directory authority (remote infinite loop), or you're on an older
2902 (pre-XP) or not-recently-patched Windows (remote exploit).
2904 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
2905 have many known flaws, and nobody should be using them. You should
2906 upgrade. If you're using a Linux or BSD and its packages are obsolete,
2907 stop using those packages and upgrade anyway.
2910 - Fix an infinite-loop bug on handling corrupt votes under certain
2911 circumstances. Bugfix on 0.2.0.8-alpha.
2912 - Fix a temporary DoS vulnerability that could be performed by
2913 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
2914 - Avoid a potential crash on exit nodes when processing malformed
2915 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
2916 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
2917 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
2920 - Fix compilation on systems where time_t is a 64-bit integer.
2921 Patch from Matthias Drochner.
2922 - Don't consider expiring already-closed client connections. Fixes
2923 bug 893. Bugfix on 0.0.2pre20.
2926 Changes in version 0.2.0.33 - 2009-01-21
2927 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
2928 useful to users. It also finally fixes a bug where a relay or client
2929 that's been off for many days would take a long time to bootstrap.
2931 This update also fixes an important security-related bug reported by
2932 Ilja van Sprundel. You should upgrade. (We'll send out more details
2933 about the bug once people have had some time to upgrade.)
2936 - Fix a heap-corruption bug that may be remotely triggerable on
2937 some platforms. Reported by Ilja van Sprundel.
2940 - When a stream at an exit relay is in state "resolving" or
2941 "connecting" and it receives an "end" relay cell, the exit relay
2942 would silently ignore the end cell and not close the stream. If
2943 the client never closes the circuit, then the exit relay never
2944 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
2946 - When sending CREATED cells back for a given circuit, use a 64-bit
2947 connection ID to find the right connection, rather than an addr:port
2948 combination. Now that we can have multiple OR connections between
2949 the same ORs, it is no longer possible to use addr:port to uniquely
2950 identify a connection.
2951 - Bridge relays that had DirPort set to 0 would stop fetching
2952 descriptors shortly after startup, and then briefly resume
2953 after a new bandwidth test and/or after publishing a new bridge
2954 descriptor. Bridge users that try to bootstrap from them would
2955 get a recent networkstatus but would get descriptors from up to
2956 18 hours earlier, meaning most of the descriptors were obsolete
2957 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
2958 - Prevent bridge relays from serving their 'extrainfo' document
2959 to anybody who asks, now that extrainfo docs include potentially
2960 sensitive aggregated client geoip summaries. Bugfix on
2962 - If the cached networkstatus consensus is more than five days old,
2963 discard it rather than trying to use it. In theory it could be
2964 useful because it lists alternate directory mirrors, but in practice
2965 it just means we spend many minutes trying directory mirrors that
2966 are long gone from the network. Also discard router descriptors as
2967 we load them if they are more than five days old, since the onion
2968 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
2971 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2972 could make gcc generate non-functional binary search code. Bugfix
2974 - Build correctly on platforms without socklen_t.
2975 - Compile without warnings on solaris.
2976 - Avoid potential crash on internal error during signature collection.
2977 Fixes bug 864. Patch from rovv.
2978 - Correct handling of possible malformed authority signing key
2979 certificates with internal signature types. Fixes bug 880.
2980 Bugfix on 0.2.0.3-alpha.
2981 - Fix a hard-to-trigger resource leak when logging credential status.
2983 - When we can't initialize DNS because the network is down, do not
2984 automatically stop Tor from starting. Instead, we retry failed
2985 dns_init() every 10 minutes, and change the exit policy to reject
2986 *:* until one succeeds. Fixes bug 691.
2987 - Use 64 bits instead of 32 bits for connection identifiers used with
2988 the controller protocol, to greatly reduce risk of identifier reuse.
2989 - When we're choosing an exit node for a circuit, and we have
2990 no pending streams, choose a good general exit rather than one that
2991 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2992 - Fix another case of assuming, when a specific exit is requested,
2993 that we know more than the user about what hosts it allows.
2994 Fixes one case of bug 752. Patch from rovv.
2995 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2996 seconds. Warn the user if lower values are given in the
2997 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2998 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2999 user if lower values are given in the configuration. Bugfix on
3000 0.1.1.17-rc. Patch by Sebastian.
3001 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
3002 the cache because we already had a v0 descriptor with the same ID.
3003 Bugfix on 0.2.0.18-alpha.
3004 - Fix a race condition when freeing keys shared between main thread
3005 and CPU workers that could result in a memory leak. Bugfix on
3006 0.1.0.1-rc. Fixes bug 889.
3007 - Send a valid END cell back when a client tries to connect to a
3008 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3009 840. Patch from rovv.
3010 - Check which hops rendezvous stream cells are associated with to
3011 prevent possible guess-the-streamid injection attacks from
3012 intermediate hops. Fixes another case of bug 446. Based on patch
3014 - If a broken client asks a non-exit router to connect somewhere,
3015 do not even do the DNS lookup before rejecting the connection.
3016 Fixes another case of bug 619. Patch from rovv.
3017 - When a relay gets a create cell it can't decrypt (e.g. because it's
3018 using the wrong onion key), we were dropping it and letting the
3019 client time out. Now actually answer with a destroy cell. Fixes
3020 bug 904. Bugfix on 0.0.2pre8.
3022 o Minor bugfixes (hidden services):
3023 - Do not throw away existing introduction points on SIGHUP. Bugfix on
3024 0.0.6pre1. Patch by Karsten. Fixes bug 874.
3027 - Report the case where all signatures in a detached set are rejected
3028 differently than the case where there is an error handling the
3030 - When we realize that another process has modified our cached
3031 descriptors, print out a more useful error message rather than
3032 triggering an assertion. Fixes bug 885. Patch from Karsten.
3033 - Implement the 0x20 hack to better resist DNS poisoning: set the
3034 case on outgoing DNS requests randomly, and reject responses that do
3035 not match the case correctly. This logic can be disabled with the
3036 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
3037 of servers that do not reliably preserve case in replies. See
3038 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3040 - Check DNS replies for more matching fields to better resist DNS
3042 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3043 compress cells, which are basically all encrypted, compressed, or
3047 Changes in version 0.2.0.32 - 2008-11-20
3048 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
3049 packages (and maybe other packages) noticed by Theo de Raadt, fixes
3050 a smaller security flaw that might allow an attacker to access local
3051 services, further improves hidden service performance, and fixes a
3052 variety of other issues.
3055 - The "User" and "Group" config options did not clear the
3056 supplementary group entries for the Tor process. The "User" option
3057 is now more robust, and we now set the groups to the specified
3058 user's primary group. The "Group" option is now ignored. For more
3059 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
3060 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
3061 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
3062 - The "ClientDNSRejectInternalAddresses" config option wasn't being
3063 consistently obeyed: if an exit relay refuses a stream because its
3064 exit policy doesn't allow it, we would remember what IP address
3065 the relay said the destination address resolves to, even if it's
3066 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
3069 - Fix a DOS opportunity during the voting signature collection process
3070 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
3072 o Major bugfixes (hidden services):
3073 - When fetching v0 and v2 rendezvous service descriptors in parallel,
3074 we were failing the whole hidden service request when the v0
3075 descriptor fetch fails, even if the v2 fetch is still pending and
3076 might succeed. Similarly, if the last v2 fetch fails, we were
3077 failing the whole hidden service request even if a v0 fetch is
3078 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
3079 - When extending a circuit to a hidden service directory to upload a
3080 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
3081 requests failed, because the router descriptor has not been
3082 downloaded yet. In these cases, do not attempt to upload the
3083 rendezvous descriptor, but wait until the router descriptor is
3084 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
3085 descriptor from a hidden service directory for which the router
3086 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
3090 - Fix several infrequent memory leaks spotted by Coverity.
3091 - When testing for libevent functions, set the LDFLAGS variable
3092 correctly. Found by Riastradh.
3093 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
3094 bootstrapping with tunneled directory connections. Bugfix on
3095 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
3096 - When asked to connect to A.B.exit:80, if we don't know the IP for A
3097 and we know that server B rejects most-but-not all connections to
3098 port 80, we would previously reject the connection. Now, we assume
3099 the user knows what they were asking for. Fixes bug 752. Bugfix
3100 on 0.0.9rc5. Diagnosed by BarkerJr.
3101 - If we overrun our per-second write limits a little, count this as
3102 having used up our write allocation for the second, and choke
3103 outgoing directory writes. Previously, we had only counted this when
3104 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
3105 Bugfix on 0.2.0.x (??).
3106 - Remove the old v2 directory authority 'lefkada' from the default
3107 list. It has been gone for many months.
3108 - Stop doing unaligned memory access that generated bus errors on
3109 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
3110 - Make USR2 log-level switch take effect immediately. Bugfix on
3113 o Minor bugfixes (controller):
3114 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
3115 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
3118 Changes in version 0.2.0.31 - 2008-09-03
3119 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
3120 a big bug we're seeing where in rare cases traffic from one Tor stream
3121 gets mixed into another stream, and fixes a variety of smaller issues.
3124 - Make sure that two circuits can never exist on the same connection
3125 with the same circuit ID, even if one is marked for close. This
3126 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
3127 - Relays now reject risky extend cells: if the extend cell includes
3128 a digest of all zeroes, or asks to extend back to the relay that
3129 sent the extend cell, tear down the circuit. Ideas suggested
3131 - If not enough of our entry guards are available so we add a new
3132 one, we might use the new one even if it overlapped with the
3133 current circuit's exit relay (or its family). Anonymity bugfix
3134 pointed out by rovv.
3137 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
3138 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
3139 - Correctly detect the presence of the linux/netfilter_ipv4.h header
3140 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
3141 - Pick size of default geoip filename string correctly on windows.
3142 Fixes bug 806. Bugfix on 0.2.0.30.
3143 - Make the autoconf script accept the obsolete --with-ssl-dir
3144 option as an alias for the actually-working --with-openssl-dir
3145 option. Fix the help documentation to recommend --with-openssl-dir.
3146 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
3147 - When using the TransPort option on OpenBSD, and using the User
3148 option to change UID and drop privileges, make sure to open
3149 /dev/pf before dropping privileges. Fixes bug 782. Patch from
3150 Christopher Davis. Bugfix on 0.1.2.1-alpha.
3151 - Try to attach connections immediately upon receiving a RENDEZVOUS2
3152 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
3153 on the client side when connecting to a hidden service. Bugfix
3154 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
3155 - When closing an application-side connection because its circuit is
3156 getting torn down, generate the stream event correctly. Bugfix on
3157 0.1.2.x. Anonymous patch.
3160 Changes in version 0.2.0.30 - 2008-07-15
3161 This new stable release switches to a more efficient directory
3162 distribution design, adds features to make connections to the Tor
3163 network harder to block, allows Tor to act as a DNS proxy, adds separate
3164 rate limiting for relayed traffic to make it easier for clients to
3165 become relays, fixes a variety of potential anonymity problems, and
3166 includes the usual huge pile of other features and bug fixes.
3168 o New v3 directory design:
3169 - Tor now uses a new way to learn about and distribute information
3170 about the network: the directory authorities vote on a common
3171 network status document rather than each publishing their own
3172 opinion. Now clients and caches download only one networkstatus
3173 document to bootstrap, rather than downloading one for each
3174 authority. Clients only download router descriptors listed in
3175 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
3177 - Set up moria1, tor26, and dizum as v3 directory authorities
3178 in addition to being v2 authorities. Also add three new ones:
3179 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
3180 dannenberg (run by CCC).
3181 - Switch to multi-level keys for directory authorities: now their
3182 long-term identity key can be kept offline, and they periodically
3183 generate a new signing key. Clients fetch the "key certificates"
3184 to keep up to date on the right keys. Add a standalone tool
3185 "tor-gencert" to generate key certificates. Implements proposal 103.
3186 - Add a new V3AuthUseLegacyKey config option to make it easier for
3187 v3 authorities to change their identity keys if another bug like
3188 Debian's OpenSSL RNG flaw appears.
3189 - Authorities and caches fetch the v2 networkstatus documents
3190 less often, now that v3 is recommended.
3192 o Make Tor connections stand out less on the wire:
3193 - Use an improved TLS handshake designed by Steven Murdoch in proposal
3194 124, as revised in proposal 130. The new handshake is meant to
3195 be harder for censors to fingerprint, and it adds the ability
3196 to detect certain kinds of man-in-the-middle traffic analysis
3197 attacks. The new handshake format includes version negotiation for
3198 OR connections as described in proposal 105, which will allow us
3199 to improve Tor's link protocol more safely in the future.
3200 - Enable encrypted directory connections by default for non-relays,
3201 so censor tools that block Tor directory connections based on their
3202 plaintext patterns will no longer work. This means Tor works in
3203 certain censored countries by default again.
3204 - Stop including recognizeable strings in the commonname part of
3205 Tor's x509 certificates.
3207 o Implement bridge relays:
3208 - Bridge relays (or "bridges" for short) are Tor relays that aren't
3209 listed in the main Tor directory. Since there is no complete public
3210 list of them, even an ISP that is filtering connections to all the
3211 known Tor relays probably won't be able to block all the bridges.
3212 See doc/design-paper/blocking.pdf and proposal 125 for details.
3213 - New config option BridgeRelay that specifies you want to be a
3214 bridge relay rather than a normal relay. When BridgeRelay is set
3215 to 1, then a) you cache dir info even if your DirPort ins't on,
3216 and b) the default for PublishServerDescriptor is now "bridge"
3217 rather than "v2,v3".
3218 - New config option "UseBridges 1" for clients that want to use bridge
3219 relays instead of ordinary entry guards. Clients then specify
3220 bridge relays by adding "Bridge" lines to their config file. Users
3221 can learn about a bridge relay either manually through word of
3222 mouth, or by one of our rate-limited mechanisms for giving out
3223 bridge addresses without letting an attacker easily enumerate them
3224 all. See https://www.torproject.org/bridges for details.
3225 - Bridge relays behave like clients with respect to time intervals
3226 for downloading new v3 consensus documents -- otherwise they
3227 stand out. Bridge users now wait until the end of the interval,
3228 so their bridge relay will be sure to have a new consensus document.
3230 o Implement bridge directory authorities:
3231 - Bridge authorities are like normal directory authorities, except
3232 they don't serve a list of known bridges. Therefore users that know
3233 a bridge's fingerprint can fetch a relay descriptor for that bridge,
3234 including fetching updates e.g. if the bridge changes IP address,
3235 yet an attacker can't just fetch a list of all the bridges.
3236 - Set up Tonga as the default bridge directory authority.
3237 - Bridge authorities refuse to serve bridge descriptors or other
3238 bridge information over unencrypted connections (that is, when
3239 responding to direct DirPort requests rather than begin_dir cells.)
3240 - Bridge directory authorities do reachability testing on the
3241 bridges they know. They provide router status summaries to the
3242 controller via "getinfo ns/purpose/bridge", and also dump summaries
3243 to a file periodically, so we can keep internal stats about which
3244 bridges are functioning.
3245 - If bridge users set the UpdateBridgesFromAuthority config option,
3246 but the digest they ask for is a 404 on the bridge authority,
3247 they fall back to contacting the bridge directly.
3248 - Bridges always use begin_dir to publish their server descriptor to
3249 the bridge authority using an anonymous encrypted tunnel.
3250 - Early work on a "bridge community" design: if bridge authorities set
3251 the BridgePassword config option, they will serve a snapshot of
3252 known bridge routerstatuses from their DirPort to anybody who
3253 knows that password. Unset by default.
3254 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
3255 report sanitized aggregated summaries in their extra-info documents
3256 privately to the bridge authority, listing which countries are
3257 able to reach them. We hope this mechanism will let us learn when
3258 certain countries start trying to block bridges.
3259 - Bridge authorities write bridge descriptors to disk, so they can
3260 reload them after a reboot. They can also export the descriptors
3261 to other programs, so we can distribute them to blocked users via
3262 the BridgeDB interface, e.g. via https://bridges.torproject.org/
3263 and bridges@torproject.org.
3265 o Tor can be a DNS proxy:
3266 - The new client-side DNS proxy feature replaces the need for
3267 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
3268 for DNS requests on port 9999, use the Tor network to resolve them
3269 anonymously, and send the reply back like a regular DNS server.
3270 The code still only implements a subset of DNS.
3271 - Add a new AutomapHostsOnResolve option: when it is enabled, any
3272 resolve request for hosts matching a given pattern causes Tor to
3273 generate an internal virtual address mapping for that host. This
3274 allows DNSPort to work sensibly with hidden service users. By
3275 default, .exit and .onion addresses are remapped; the list of
3276 patterns can be reconfigured with AutomapHostsSuffixes.
3277 - Add an "-F" option to tor-resolve to force a resolve for a .onion
3278 address. Thanks to the AutomapHostsOnResolve option, this is no
3279 longer a completely silly thing to do.
3281 o Major features (relay usability):
3282 - New config options RelayBandwidthRate and RelayBandwidthBurst:
3283 a separate set of token buckets for relayed traffic. Right now
3284 relayed traffic is defined as answers to directory requests, and
3285 OR connections that don't have any local circuits on them. See
3286 proposal 111 for details.
3287 - Create listener connections before we setuid to the configured
3288 User and Group. Now non-Windows users can choose port values
3289 under 1024, start Tor as root, and have Tor bind those ports
3290 before it changes to another UID. (Windows users could already
3292 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
3293 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
3294 on "vserver" accounts. Patch from coderman.
3296 o Major features (directory authorities):
3297 - Directory authorities track weighted fractional uptime and weighted
3298 mean-time-between failures for relays. WFU is suitable for deciding
3299 whether a node is "usually up", while MTBF is suitable for deciding
3300 whether a node is "likely to stay up." We need both, because
3301 "usually up" is a good requirement for guards, while "likely to
3302 stay up" is a good requirement for long-lived connections.
3303 - Directory authorities use a new formula for selecting which relays
3304 to advertise as Guards: they must be in the top 7/8 in terms of
3305 how long we have known about them, and above the median of those
3306 nodes in terms of weighted fractional uptime.
3307 - Directory authorities use a new formula for selecting which relays
3308 to advertise as Stable: when we have 4 or more days of data, use
3309 median measured MTBF rather than median declared uptime. Implements
3311 - Directory authorities accept and serve "extra info" documents for
3312 routers. Routers now publish their bandwidth-history lines in the
3313 extra-info docs rather than the main descriptor. This step saves
3314 60% (!) on compressed router descriptor downloads. Servers upload
3315 extra-info docs to any authority that accepts them; directory
3316 authorities now allow multiple router descriptors and/or extra
3317 info documents to be uploaded in a single go. Authorities, and
3318 caches that have been configured to download extra-info documents,
3319 download them as needed. Implements proposal 104.
3320 - Authorities now list relays who have the same nickname as
3321 a different named relay, but list them with a new flag:
3322 "Unnamed". Now we can make use of relays that happen to pick the
3323 same nickname as a server that registered two years ago and then
3324 disappeared. Implements proposal 122.
3325 - Store routers in a file called cached-descriptors instead of in
3326 cached-routers. Initialize cached-descriptors from cached-routers
3327 if the old format is around. The new format allows us to store
3328 annotations along with descriptors, to record the time we received
3329 each descriptor, its source, and its purpose: currently one of
3330 general, controller, or bridge.
3332 o Major features (other):
3333 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3334 Tor can warn and/or refuse connections to ports commonly used with
3335 vulnerable-plaintext protocols. Currently we warn on ports 23,
3336 109, 110, and 143, but we don't reject any. Based on proposal 129
3337 by Kevin Bauer and Damon McCoy.
3338 - Integrate Karsten Loesing's Google Summer of Code project to publish
3339 hidden service descriptors on a set of redundant relays that are a
3340 function of the hidden service address. Now we don't have to rely
3341 on three central hidden service authorities for publishing and
3342 fetching every hidden service descriptor. Implements proposal 114.
3343 - Allow tunnelled directory connections to ask for an encrypted
3344 "begin_dir" connection or an anonymized "uses a full Tor circuit"
3345 connection independently. Now we can make anonymized begin_dir
3346 connections for (e.g.) more secure hidden service posting and
3349 o Major bugfixes (crashes and assert failures):
3350 - Stop imposing an arbitrary maximum on the number of file descriptors
3351 used for busy servers. Bug reported by Olaf Selke; patch from
3353 - Avoid possible failures when generating a directory with routers
3354 with over-long versions strings, or too many flags set.
3355 - Fix a rare assert error when we're closing one of our threads:
3356 use a mutex to protect the list of logs, so we never write to the
3357 list as it's being freed. Fixes the very rare bug 575, which is
3358 kind of the revenge of bug 222.
3359 - Avoid segfault in the case where a badly behaved v2 versioning
3360 directory sends a signed networkstatus with missing client-versions.
3361 - When we hit an EOF on a log (probably because we're shutting down),
3362 don't try to remove the log from the list: just mark it as
3363 unusable. (Bulletproofs against bug 222.)
3365 o Major bugfixes (code security fixes):
3366 - Detect size overflow in zlib code. Reported by Justin Ferguson and
3368 - Rewrite directory tokenization code to never run off the end of
3369 a string. Fixes bug 455. Patch from croup.
3370 - Be more paranoid about overwriting sensitive memory on free(),
3371 as a defensive programming tactic to ensure forward secrecy.
3373 o Major bugfixes (anonymity fixes):
3374 - Reject requests for reverse-dns lookup of names that are in
3375 a private address space. Patch from lodger.
3376 - Never report that we've used more bandwidth than we're willing to
3377 relay: it leaks how much non-relay traffic we're using. Resolves
3379 - As a client, do not believe any server that tells us that an
3380 address maps to an internal address space.
3381 - Warn about unsafe ControlPort configurations.
3382 - Directory authorities now call routers Fast if their bandwidth is
3383 at least 100KB/s, and consider their bandwidth adequate to be a
3384 Guard if it is at least 250KB/s, no matter the medians. This fix
3385 complements proposal 107.
3386 - Directory authorities now never mark more than 2 servers per IP as
3387 Valid and Running (or 5 on addresses shared by authorities).
3388 Implements proposal 109, by Kevin Bauer and Damon McCoy.
3389 - If we're a relay, avoid picking ourselves as an introduction point,
3390 a rendezvous point, or as the final hop for internal circuits. Bug
3391 reported by taranis and lodger.
3392 - Exit relays that are used as a client can now reach themselves
3393 using the .exit notation, rather than just launching an infinite
3394 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
3395 - Fix a bug where, when we were choosing the 'end stream reason' to
3396 put in our relay end cell that we send to the exit relay, Tor
3397 clients on Windows were sometimes sending the wrong 'reason'. The
3398 anonymity problem is that exit relays may be able to guess whether
3399 the client is running Windows, thus helping partition the anonymity
3400 set. Down the road we should stop sending reasons to exit relays,
3401 or otherwise prevent future versions of this bug.
3402 - Only update guard status (usable / not usable) once we have
3403 enough directory information. This was causing us to discard all our
3404 guards on startup if we hadn't been running for a few weeks. Fixes
3406 - When our directory information has been expired for a while, stop
3407 being willing to build circuits using it. Fixes bug 401.
3409 o Major bugfixes (peace of mind for relay operators)
3410 - Non-exit relays no longer answer "resolve" relay cells, so they
3411 can't be induced to do arbitrary DNS requests. (Tor clients already
3412 avoid using non-exit relays for resolve cells, but now servers
3413 enforce this too.) Fixes bug 619. Patch from lodger.
3414 - When we setconf ClientOnly to 1, close any current OR and Dir
3415 listeners. Reported by mwenge.
3417 o Major bugfixes (other):
3418 - If we only ever used Tor for hidden service lookups or posts, we
3419 would stop building circuits and start refusing connections after
3420 24 hours, since we falsely believed that Tor was dormant. Reported
3422 - Add a new __HashedControlSessionPassword option for controllers
3423 to use for one-off session password hashes that shouldn't get
3424 saved to disk by SAVECONF --- Vidalia users were accumulating a
3425 pile of HashedControlPassword lines in their torrc files, one for
3426 each time they had restarted Tor and then clicked Save. Make Tor
3427 automatically convert "HashedControlPassword" to this new option but
3428 only when it's given on the command line. Partial fix for bug 586.
3429 - Patch from "Andrew S. Lists" to catch when we contact a directory
3430 mirror at IP address X and he says we look like we're coming from
3431 IP address X. Otherwise this would screw up our address detection.
3432 - Reject uploaded descriptors and extrainfo documents if they're
3433 huge. Otherwise we'll cache them all over the network and it'll
3434 clog everything up. Suggested by Aljosha Judmayer.
3435 - When a hidden service was trying to establish an introduction point,
3436 and Tor *did* manage to reuse one of the preemptively built
3437 circuits, it didn't correctly remember which one it used,
3438 so it asked for another one soon after, until there were no
3439 more preemptive circuits, at which point it launched one from
3440 scratch. Bugfix on 0.0.9.x.
3442 o Rate limiting and load balancing improvements:
3443 - When we add data to a write buffer in response to the data on that
3444 write buffer getting low because of a flush, do not consider the
3445 newly added data as a candidate for immediate flushing, but rather
3446 make it wait until the next round of writing. Otherwise, we flush
3447 and refill recursively, and a single greedy TLS connection can
3448 eat all of our bandwidth.
3449 - When counting the number of bytes written on a TLS connection,
3450 look at the BIO actually used for writing to the network, not
3451 at the BIO used (sometimes) to buffer data for the network.
3452 Looking at different BIOs could result in write counts on the
3453 order of ULONG_MAX. Fixes bug 614.
3454 - If we change our MaxAdvertisedBandwidth and then reload torrc,
3455 Tor won't realize it should publish a new relay descriptor. Fixes
3456 bug 688, reported by mfr.
3457 - Avoid using too little bandwidth when our clock skips a few seconds.
3458 - Choose which bridge to use proportional to its advertised bandwidth,
3459 rather than uniformly at random. This should speed up Tor for
3460 bridge users. Also do this for people who set StrictEntryNodes.
3462 o Bootstrapping faster and building circuits more intelligently:
3463 - Fix bug 660 that was preventing us from knowing that we should
3464 preemptively build circuits to handle expected directory requests.
3465 - When we're checking if we have enough dir info for each relay
3466 to begin establishing circuits, make sure that we actually have
3467 the descriptor listed in the consensus, not just any descriptor.
3468 - Correctly notify one-hop connections when a circuit build has
3469 failed. Possible fix for bug 669. Found by lodger.
3470 - Clients now hold circuitless TLS connections open for 1.5 times
3471 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
3472 rebuild a new circuit over them within that timeframe. Previously,
3473 they held them open only for KeepalivePeriod (5 minutes).
3475 o Performance improvements (memory):
3476 - Add OpenBSD malloc code from "phk" as an optional malloc
3477 replacement on Linux: some glibc libraries do very poorly with
3478 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
3479 ./configure to get the replacement malloc code.
3480 - Switch our old ring buffer implementation for one more like that
3481 used by free Unix kernels. The wasted space in a buffer with 1mb
3482 of data will now be more like 8k than 1mb. The new implementation
3483 also avoids realloc();realloc(); patterns that can contribute to
3484 memory fragmentation.
3485 - Change the way that Tor buffers data that it is waiting to write.
3486 Instead of queueing data cells in an enormous ring buffer for each
3487 client->OR or OR->OR connection, we now queue cells on a separate
3488 queue for each circuit. This lets us use less slack memory, and
3489 will eventually let us be smarter about prioritizing different kinds
3491 - Reference-count and share copies of address policy entries; only 5%
3492 of them were actually distinct.
3493 - Tune parameters for cell pool allocation to minimize amount of
3495 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
3496 for every single inactive connection_t. Free items from the
3497 4k/16k-buffer free lists when they haven't been used for a while.
3498 - Make memory debugging information describe more about history
3499 of cell allocation, so we can help reduce our memory use.
3500 - Be even more aggressive about releasing RAM from small
3501 empty buffers. Thanks to our free-list code, this shouldn't be too
3502 performance-intensive.
3503 - Log malloc statistics from mallinfo() on platforms where it exists.
3504 - Use memory pools to allocate cells with better speed and memory
3505 efficiency, especially on platforms where malloc() is inefficient.
3506 - Add a --with-tcmalloc option to the configure script to link
3507 against tcmalloc (if present). Does not yet search for non-system
3510 o Performance improvements (socket management):
3511 - Count the number of open sockets separately from the number of
3512 active connection_t objects. This will let us avoid underusing
3513 our allocated connection limit.
3514 - We no longer use socket pairs to link an edge connection to an
3515 anonymous directory connection or a DirPort test connection.
3516 Instead, we track the link internally and transfer the data
3517 in-process. This saves two sockets per "linked" connection (at the
3518 client and at the server), and avoids the nasty Windows socketpair()
3520 - We were leaking a file descriptor if Tor started with a zero-length
3521 cached-descriptors file. Patch by "freddy77".
3523 o Performance improvements (CPU use):
3524 - Never walk through the list of logs if we know that no log target
3525 is interested in a given message.
3526 - Call routerlist_remove_old_routers() much less often. This should
3527 speed startup, especially on directory caches.
3528 - Base64 decoding was actually showing up on our profile when parsing
3529 the initial descriptor file; switch to an in-process all-at-once
3530 implementation that's about 3.5x times faster than calling out to
3532 - Use a slightly simpler string hashing algorithm (copying Python's
3533 instead of Java's) and optimize our digest hashing algorithm to take
3534 advantage of 64-bit platforms and to remove some possibly-costly
3536 - When implementing AES counter mode, update only the portions of the
3537 counter buffer that need to change, and don't keep separate
3538 network-order and host-order counters on big-endian hosts (where
3540 - Add an in-place version of aes_crypt() so that we can avoid doing a
3541 needless memcpy() call on each cell payload.
3542 - Use Critical Sections rather than Mutexes for synchronizing threads
3543 on win32; Mutexes are heavier-weight, and designed for synchronizing
3546 o Performance improvements (bandwidth use):
3547 - Don't try to launch new descriptor downloads quite so often when we
3548 already have enough directory information to build circuits.
3549 - Version 1 directories are no longer generated in full. Instead,
3550 authorities generate and serve "stub" v1 directories that list
3551 no servers. This will stop Tor versions 0.1.0.x and earlier from
3552 working, but (for security reasons) nobody should be running those
3554 - Avoid going directly to the directory authorities even if you're a
3555 relay, if you haven't found yourself reachable yet or if you've
3556 decided not to advertise your dirport yet. Addresses bug 556.
3557 - If we've gone 12 hours since our last bandwidth check, and we
3558 estimate we have less than 50KB bandwidth capacity but we could
3559 handle more, do another bandwidth test.
3560 - Support "If-Modified-Since" when answering HTTP requests for
3561 directories, running-routers documents, and v2 and v3 networkstatus
3562 documents. (There's no need to support it for router descriptors,
3563 since those are downloaded by descriptor digest.)
3564 - Stop fetching directory info so aggressively if your DirPort is
3565 on but your ORPort is off; stop fetching v2 dir info entirely.
3566 You can override these choices with the new FetchDirInfoEarly
3569 o Changed config option behavior (features):
3570 - Configuration files now accept C-style strings as values. This
3571 helps encode characters not allowed in the current configuration
3572 file format, such as newline or #. Addresses bug 557.
3573 - Add hidden services and DNSPorts to the list of things that make
3574 Tor accept that it has running ports. Change starting Tor with no
3575 ports from a fatal error to a warning; we might change it back if
3576 this turns out to confuse anybody. Fixes bug 579.
3577 - Make PublishServerDescriptor default to 1, so the default doesn't
3578 have to change as we invent new directory protocol versions.
3579 - Allow people to say PreferTunnelledDirConns rather than
3580 PreferTunneledDirConns, for those alternate-spellers out there.
3581 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
3582 accommodate the growing number of servers that use the default
3583 and are reaching it.
3584 - Make it possible to enable HashedControlPassword and
3585 CookieAuthentication at the same time.
3586 - When a TrackHostExits-chosen exit fails too many times in a row,
3587 stop using it. Fixes bug 437.
3589 o Changed config option behavior (bugfixes):
3590 - Do not read the configuration file when we've only been told to
3591 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
3592 based on patch from Sebastian Hahn.
3593 - Actually validate the options passed to AuthDirReject,
3594 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3595 - Make "ClientOnly 1" config option disable directory ports too.
3596 - Don't stop fetching descriptors when FetchUselessDescriptors is
3597 set, even if we stop asking for circuits. Bug reported by tup
3599 - Servers used to decline to publish their DirPort if their
3600 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
3601 they look only at BandwidthRate and RelayBandwidthRate.
3602 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
3603 minus 1 byte: the actual maximum declared bandwidth.
3604 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
3605 - Make the NodeFamilies config option work. (Reported by
3606 lodger -- it has never actually worked, even though we added it
3608 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
3609 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
3611 o New config options:
3612 - New configuration options AuthDirMaxServersPerAddr and
3613 AuthDirMaxServersperAuthAddr to override default maximum number
3614 of servers allowed on a single IP address. This is important for
3615 running a test network on a single host.
3616 - Three new config options (AlternateDirAuthority,
3617 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3618 user selectively replace the default directory authorities by type,
3619 rather than the all-or-nothing replacement that DirServer offers.
3620 - New config options AuthDirBadDir and AuthDirListBadDirs for
3621 authorities to mark certain relays as "bad directories" in the
3622 networkstatus documents. Also supports the "!baddir" directive in
3623 the approved-routers file.
3624 - New config option V2AuthoritativeDirectory that all v2 directory
3625 authorities must set. This lets v3 authorities choose not to serve
3626 v2 directory information.
3628 o Minor features (other):
3629 - When we're not serving v2 directory information, there is no reason
3630 to actually keep any around. Remove the obsolete files and directory
3631 on startup if they are very old and we aren't going to serve them.
3632 - When we negotiate a v2 link-layer connection (not yet implemented),
3633 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3634 negotiated a v1 connection for their next step. Initial steps for
3636 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3637 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3638 we can start out knowing some directory caches. We don't ship with
3639 a fallback consensus by default though, because it was making
3640 bootstrapping take too long while we tried many down relays.
3641 - Authorities send back an X-Descriptor-Not-New header in response to
3642 an accepted-but-discarded descriptor upload. Partially implements
3644 - If we find a cached-routers file that's been sitting around for more
3645 than 28 days unmodified, then most likely it's a leftover from
3646 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
3648 - When we (as a cache) download a descriptor because it was listed
3649 in a consensus, remember when the consensus was supposed to expire,
3650 and don't expire the descriptor until then.
3651 - Optionally (if built with -DEXPORTMALLINFO) export the output
3652 of mallinfo via http, as tor/mallinfo.txt. Only accessible
3654 - Tag every guard node in our state file with the version that
3655 we believe added it, or with our own version if we add it. This way,
3656 if a user temporarily runs an old version of Tor and then switches
3657 back to a new one, she doesn't automatically lose her guards.
3658 - When somebody requests a list of statuses or servers, and we have
3659 none of those, return a 404 rather than an empty 200.
3660 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
3662 - Add an HSAuthorityRecordStats option that hidden service authorities
3663 can use to track statistics of overall hidden service usage without
3664 logging information that would be as useful to an attacker.
3665 - Allow multiple HiddenServicePort directives with the same virtual
3666 port; when they occur, the user is sent round-robin to one
3667 of the target ports chosen at random. Partially fixes bug 393 by
3668 adding limited ad-hoc round-robining.
3669 - Revamp file-writing logic so we don't need to have the entire
3670 contents of a file in memory at once before we write to disk. Tor,
3673 o Minor bugfixes (other):
3674 - Alter the code that tries to recover from unhandled write
3675 errors, to not try to flush onto a socket that's given us
3677 - Directory mirrors no longer include a guess at the client's IP
3678 address if the connection appears to be coming from the same /24
3679 network; it was producing too many wrong guesses.
3680 - If we're trying to flush the last bytes on a connection (for
3681 example, when answering a directory request), reset the
3682 time-to-give-up timeout every time we manage to write something
3684 - Reject router descriptors with out-of-range bandwidthcapacity or
3685 bandwidthburst values.
3686 - If we can't expand our list of entry guards (e.g. because we're
3687 using bridges or we have StrictEntryNodes set), don't mark relays
3688 down when they fail a directory request. Otherwise we're too quick
3689 to mark all our entry points down.
3690 - Authorities no longer send back "400 you're unreachable please fix
3691 it" errors to Tor servers that aren't online all the time. We're
3692 supposed to tolerate these servers now.
3693 - Let directory authorities startup even when they can't generate
3694 a descriptor immediately, e.g. because they don't know their
3696 - Correctly enforce that elements of directory objects do not appear
3697 more often than they are allowed to appear.
3698 - Stop allowing hibernating servers to be "stable" or "fast".
3699 - On Windows, we were preventing other processes from reading
3700 cached-routers while Tor was running. (Reported by janbar)
3701 - Check return values from pthread_mutex functions.
3702 - When opening /dev/null in finish_daemonize(), do not pass the
3703 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
3704 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
3706 o Controller features:
3707 - The GETCONF command now escapes and quotes configuration values
3708 that don't otherwise fit into the torrc file.
3709 - The SETCONF command now handles quoted values correctly.
3710 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3711 ask about source, timestamp of arrival, purpose, etc. We need
3712 something like this to help Vidalia not do GeoIP lookups on bridge
3714 - Allow multiple HashedControlPassword config lines, to support
3715 multiple controller passwords.
3716 - Accept LF instead of CRLF on controller, since some software has a
3717 hard time generating real Internet newlines.
3718 - Add GETINFO values for the server status events
3719 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
3721 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
3722 GETINFO for Torstat to use until it can switch to using extrainfos.
3723 - New config option CookieAuthFile to choose a new location for the
3724 cookie authentication file, and config option
3725 CookieAuthFileGroupReadable to make it group-readable.
3726 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
3727 match requests to applications. Patch from Robert Hogan.
3728 - Add a RESOLVE command to launch hostname lookups. Original patch
3730 - Add GETINFO status/enough-dir-info to let controllers tell whether
3731 Tor has downloaded sufficient directory information. Patch from Tup.
3732 - You can now use the ControlSocket option to tell Tor to listen for
3733 controller connections on Unix domain sockets on systems that
3734 support them. Patch from Peter Palfrader.
3735 - New "GETINFO address-mappings/*" command to get address mappings
3736 with expiry information. "addr-mappings/*" is now deprecated.
3738 - Add a new config option __DisablePredictedCircuits designed for
3739 use by the controller, when we don't want Tor to build any circuits
3741 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
3742 so we can exit from the middle of the circuit.
3743 - Implement "getinfo status/circuit-established".
3744 - Implement "getinfo status/version/..." so a controller can tell
3745 whether the current version is recommended, and whether any versions
3746 are good, and how many authorities agree. Patch from "shibz".
3747 - Controllers should now specify cache=no or cache=yes when using
3748 the +POSTDESCRIPTOR command.
3749 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
3750 Robert Hogan. Fixes the first part of bug 681.
3751 - When reporting clock skew, and we know that the clock is _at least
3752 as skewed_ as some value, but we don't know the actual value,
3753 report the value as a "minimum skew."
3755 o Controller bugfixes:
3756 - Generate "STATUS_SERVER" events rather than misspelled
3757 "STATUS_SEVER" events. Caught by mwenge.
3758 - Reject controller commands over 1MB in length, so rogue
3759 processes can't run us out of memory.
3760 - Change the behavior of "getinfo status/good-server-descriptor"
3761 so it doesn't return failure when any authority disappears.
3762 - Send NAMESERVER_STATUS messages for a single failed nameserver
3764 - When the DANGEROUS_VERSION controller status event told us we're
3765 running an obsolete version, it used the string "OLD" to describe
3766 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3767 "OBSOLETE" in both cases.
3768 - Respond to INT and TERM SIGNAL commands before we execute the
3769 signal, in case the signal shuts us down. We had a patch in
3770 0.1.2.1-alpha that tried to do this by queueing the response on
3771 the connection's buffer before shutting down, but that really
3772 isn't the same thing at all. Bug located by Matt Edman.
3773 - Provide DNS expiry times in GMT, not in local time. For backward
3774 compatibility, ADDRMAP events only provide GMT expiry in an extended
3775 field. "GETINFO address-mappings" always does the right thing.
3776 - Use CRLF line endings properly in NS events.
3777 - Make 'getinfo fingerprint' return a 551 error if we're not a
3778 server, so we match what the control spec claims we do. Reported
3780 - Fix a typo in an error message when extendcircuit fails that
3781 caused us to not follow the \r\n-based delimiter protocol. Reported
3783 - When tunneling an encrypted directory connection, and its first
3784 circuit fails, do not leave it unattached and ask the controller
3785 to deal. Fixes the second part of bug 681.
3786 - Treat some 403 responses from directory servers as INFO rather than
3787 WARN-severity events.
3789 o Portability / building / compiling:
3790 - When building with --enable-gcc-warnings, check for whether Apple's
3791 warning "-Wshorten-64-to-32" is available.
3792 - Support compilation to target iPhone; patch from cjacker huang.
3793 To build for iPhone, pass the --enable-iphone option to configure.
3794 - Port Tor to build and run correctly on Windows CE systems, using
3795 the wcecompat library. Contributed by Valerio Lupi.
3796 - Detect non-ASCII platforms (if any still exist) and refuse to
3797 build there: some of our code assumes that 'A' is 65 and so on.
3798 - Clear up some MIPSPro compiler warnings.
3799 - Make autoconf search for libevent, openssl, and zlib consistently.
3800 - Update deprecated macros in configure.in.
3801 - When warning about missing headers, tell the user to let us
3802 know if the compile succeeds anyway, so we can downgrade the
3804 - Include the current subversion revision as part of the version
3805 string: either fetch it directly if we're in an SVN checkout, do
3806 some magic to guess it if we're in an SVK checkout, or use
3807 the last-detected version if we're building from a .tar.gz.
3808 Use this version consistently in log messages.
3809 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
3810 - Read resolv.conf files correctly on platforms where read() returns
3811 partial results on small file reads.
3812 - Build without verbose warnings even on gcc 4.2 and 4.3.
3813 - On Windows, correctly detect errors when listing the contents of
3814 a directory. Fix from lodger.
3815 - Run 'make test' as part of 'make dist', so we stop releasing so
3816 many development snapshots that fail their unit tests.
3817 - Add support to detect Libevent versions in the 1.4.x series
3819 - Add command-line arguments to unit-test executable so that we can
3820 invoke any chosen test from the command line rather than having
3821 to run the whole test suite at once; and so that we can turn on
3822 logging for the unit tests.
3823 - Do not automatically run configure from autogen.sh. This
3824 non-standard behavior tended to annoy people who have built other
3826 - Fix a macro/CPP interaction that was confusing some compilers:
3827 some GCCs don't like #if/#endif pairs inside macro arguments.
3829 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
3830 Fixes bug 704; fix from Steven Murdoch.
3831 - Correctly detect transparent proxy support on Linux hosts that
3832 require in.h to be included before netfilter_ipv4.h. Patch
3835 o Logging improvements:
3836 - When we haven't had any application requests lately, don't bother
3837 logging that we have expired a bunch of descriptors.
3838 - When attempting to open a logfile fails, tell us why.
3839 - Only log guard node status when guard node status has changed.
3840 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
3841 make "INFO" 75% less verbose.
3842 - When SafeLogging is disabled, log addresses along with all TLS
3844 - Report TLS "zero return" case as a "clean close" and "IO error"
3845 as a "close". Stop calling closes "unexpected closes": existing
3846 Tors don't use SSL_close(), so having a connection close without
3847 the TLS shutdown handshake is hardly unexpected.
3848 - When we receive a consensus from the future, warn about skew.
3849 - Make "not enough dir info yet" warnings describe *why* Tor feels
3850 it doesn't have enough directory info yet.
3851 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3852 consumers. (We already do this on HUP.)
3853 - Give more descriptive well-formedness errors for out-of-range
3854 hidden service descriptor/protocol versions.
3855 - Stop recommending that every server operator send mail to tor-ops.
3856 Resolves bug 597. Bugfix on 0.1.2.x.
3857 - Improve skew reporting: try to give the user a better log message
3858 about how skewed they are, and how much this matters.
3859 - New --quiet command-line option to suppress the default console log.
3860 Good in combination with --hash-password.
3861 - Don't complain that "your server has not managed to confirm that its
3862 ports are reachable" if we haven't been able to build any circuits
3864 - Detect the reason for failing to mmap a descriptor file we just
3865 wrote, and give a more useful log message. Fixes bug 533.
3866 - Always prepend "Bug: " to any log message about a bug.
3867 - When dumping memory usage, list bytes used in buffer memory
3869 - When running with dmalloc, dump more stats on hup and on exit.
3870 - Put a platform string (e.g. "Linux i686") in the startup log
3871 message, so when people paste just their logs, we know if it's
3872 OpenBSD or Windows or what.
3873 - When logging memory usage, break down memory used in buffers by
3875 - When we are reporting the DirServer line we just parsed, we were
3876 logging the second stanza of the key fingerprint, not the first.
3877 - Even though Windows is equally happy with / and \ as path separators,
3878 try to use \ consistently on Windows and / consistently on Unix: it
3879 makes the log messages nicer.
3880 - On OSX, stop warning the user that kqueue support in libevent is
3881 "experimental", since it seems to have worked fine for ages.
3883 o Contributed scripts and tools:
3884 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3885 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3887 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
3888 Unix users an easy way to script their Tor process (e.g. by
3889 adjusting bandwidth based on the time of the day).
3890 - In the exitlist script, only consider the most recently published
3891 server descriptor for each server. Also, when the user requests
3892 a list of servers that _reject_ connections to a given address,
3893 explicitly exclude the IPs that also have servers that accept
3894 connections to that address. Resolves bug 405.
3895 - Include a new contrib/tor-exit-notice.html file that exit relay
3896 operators can put on their website to help reduce abuse queries.
3898 o Newly deprecated features:
3899 - The status/version/num-versioning and status/version/num-concurring
3900 GETINFO controller options are no longer useful in the v3 directory
3901 protocol: treat them as deprecated, and warn when they're used.
3902 - The RedirectExits config option is now deprecated.
3905 - Drop the old code to choke directory connections when the
3906 corresponding OR connections got full: thanks to the cell queue
3907 feature, OR conns don't get full any more.
3908 - Remove the old "dns worker" server DNS code: it hasn't been default
3909 since 0.1.2.2-alpha, and all the servers are using the new
3911 - Remove the code to generate the oldest (v1) directory format.
3912 - Remove support for the old bw_accounting file: we've been storing
3913 bandwidth accounting information in the state file since
3914 0.1.2.5-alpha. This may result in bandwidth accounting errors
3915 if you try to upgrade from 0.1.1.x or earlier, or if you try to
3916 downgrade to 0.1.1.x or earlier.
3917 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3918 it, it had no AES, and it hasn't seen any security patches since
3920 - Stop overloading the circuit_t.onionskin field for both "onionskin
3921 from a CREATE cell that we are waiting for a cpuworker to be
3922 assigned" and "onionskin from an EXTEND cell that we are going to
3923 send to an OR as soon as we are connected". Might help with bug 600.
3924 - Remove the tor_strpartition() function: its logic was confused,
3925 and it was only used for one thing that could be implemented far
3927 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
3928 and TorControl.py, as they use the old v0 controller protocol,
3929 and are obsoleted by TorFlow anyway.
3930 - Drop support for v1 rendezvous descriptors, since we never used
3931 them anyway, and the code has probably rotted by now. Based on
3932 patch from Karsten Loesing.
3933 - Stop allowing address masks that do not correspond to bit prefixes.
3934 We have warned about these for a really long time; now it's time
3935 to reject them. (Patch from croup.)
3936 - Remove an optimization in the AES counter-mode code that assumed
3937 that the counter never exceeded 2^68. When the counter can be set
3938 arbitrarily as an IV (as it is by Karsten's new hidden services
3939 code), this assumption no longer holds.
3940 - Disable the SETROUTERPURPOSE controller command: it is now
3944 Changes in version 0.1.2.19 - 2008-01-17
3945 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3946 exit policy a little bit more conservative so it's safer to run an
3947 exit relay on a home system, and fixes a variety of smaller issues.
3950 - Exit policies now reject connections that are addressed to a
3951 relay's public (external) IP address too, unless
3952 ExitPolicyRejectPrivate is turned off. We do this because too
3953 many relays are running nearby to services that trust them based
3957 - When the clock jumps forward a lot, do not allow the bandwidth
3958 buckets to become negative. Fixes bug 544.
3959 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3960 on every successful resolve. Reported by Mike Perry.
3961 - Purge old entries from the "rephist" database and the hidden
3962 service descriptor database even when DirPort is zero.
3963 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3964 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3965 crashing or mis-answering these requests.
3966 - When we decide to send a 503 response to a request for servers, do
3967 not then also send the server descriptors: this defeats the whole
3968 purpose. Fixes bug 539.
3971 - Changing the ExitPolicyRejectPrivate setting should cause us to
3972 rebuild our server descriptor.
3973 - Fix handling of hex nicknames when answering controller requests for
3974 networkstatus by name, or when deciding whether to warn about
3975 unknown routers in a config option. (Patch from mwenge.)
3976 - Fix a couple of hard-to-trigger autoconf problems that could result
3977 in really weird results on platforms whose sys/types.h files define
3978 nonstandard integer types.
3979 - Don't try to create the datadir when running --verify-config or
3980 --hash-password. Resolves bug 540.
3981 - If we were having problems getting a particular descriptor from the
3982 directory caches, and then we learned about a new descriptor for
3983 that router, we weren't resetting our failure count. Reported
3985 - Although we fixed bug 539 (where servers would send HTTP status 503
3986 responses _and_ send a body too), there are still servers out there
3987 that haven't upgraded. Therefore, make clients parse such bodies
3988 when they receive them.
3989 - Run correctly on systems where rlim_t is larger than unsigned long.
3990 This includes some 64-bit systems.
3991 - Run correctly on platforms (like some versions of OS X 10.5) where
3992 the real limit for number of open files is OPEN_FILES, not rlim_max
3993 from getrlimit(RLIMIT_NOFILES).
3994 - Avoid a spurious free on base64 failure.
3995 - Avoid segfaults on certain complex invocations of
3996 router_get_by_hexdigest().
3997 - Fix rare bug on REDIRECTSTREAM control command when called with no
3998 port set: it could erroneously report an error when none had
4002 Changes in version 0.1.2.18 - 2007-10-28
4003 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
4004 hidden service introduction that were causing huge delays, and a big
4005 bug that was causing some servers to disappear from the network status
4006 lists for a few hours each day.
4008 o Major bugfixes (crashes):
4009 - If a connection is shut down abruptly because of something that
4010 happened inside connection_flushed_some(), do not call
4011 connection_finished_flushing(). Should fix bug 451:
4012 "connection_stop_writing: Assertion conn->write_event failed"
4013 Bugfix on 0.1.2.7-alpha.
4014 - Fix possible segfaults in functions called from
4015 rend_process_relay_cell().
4017 o Major bugfixes (hidden services):
4018 - Hidden services were choosing introduction points uniquely by
4019 hexdigest, but when constructing the hidden service descriptor
4020 they merely wrote the (potentially ambiguous) nickname.
4021 - Clients now use the v2 intro format for hidden service
4022 connections: they specify their chosen rendezvous point by identity
4023 digest rather than by (potentially ambiguous) nickname. These
4024 changes could speed up hidden service connections dramatically.
4026 o Major bugfixes (other):
4027 - Stop publishing a new server descriptor just because we get a
4028 HUP signal. This led (in a roundabout way) to some servers getting
4029 dropped from the networkstatus lists for a few hours each day.
4030 - When looking for a circuit to cannibalize, consider family as well
4031 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4032 circuit cannibalization).
4033 - When a router wasn't listed in a new networkstatus, we were leaving
4034 the flags for that router alone -- meaning it remained Named,
4035 Running, etc -- even though absence from the networkstatus means
4036 that it shouldn't be considered to exist at all anymore. Now we
4037 clear all the flags for routers that fall out of the networkstatus
4038 consensus. Fixes bug 529.
4041 - Don't try to access (or alter) the state file when running
4042 --list-fingerprint or --verify-config or --hash-password. Resolves
4044 - When generating information telling us how to extend to a given
4045 router, do not try to include the nickname if it is
4046 absent. Resolves bug 467.
4047 - Fix a user-triggerable segfault in expand_filename(). (There isn't
4048 a way to trigger this remotely.)
4049 - When sending a status event to the controller telling it that an
4050 OR address is reachable, set the port correctly. (Previously we
4051 were reporting the dir port.)
4052 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4053 command. Bugfix on 0.1.2.17.
4054 - When loading bandwidth history, do not believe any information in
4055 the future. Fixes bug 434.
4056 - When loading entry guard information, do not believe any information
4058 - When we have our clock set far in the future and generate an
4059 onion key, then re-set our clock to be correct, we should not stop
4060 the onion key from getting rotated.
4061 - On some platforms, accept() can return a broken address. Detect
4062 this more quietly, and deal accordingly. Fixes bug 483.
4063 - It's not actually an error to find a non-pending entry in the DNS
4064 cache when canceling a pending resolve. Don't log unless stuff
4065 is fishy. Resolves bug 463.
4066 - Don't reset trusted dir server list when we set a configuration
4067 option. Patch from Robert Hogan.
4070 Changes in version 0.1.2.17 - 2007-08-30
4071 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4072 X bundles. Vidalia 0.0.14 makes authentication required for the
4073 ControlPort in the default configuration, which addresses important
4074 security risks. Everybody who uses Vidalia (or another controller)
4077 In addition, this Tor update fixes major load balancing problems with
4078 path selection, which should speed things up a lot once many people
4081 o Major bugfixes (security):
4082 - We removed support for the old (v0) control protocol. It has been
4083 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4084 become more of a headache than it's worth.
4086 o Major bugfixes (load balancing):
4087 - When choosing nodes for non-guard positions, weight guards
4088 proportionally less, since they already have enough load. Patch
4090 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4091 will allow fast Tor servers to get more attention.
4092 - When we're upgrading from an old Tor version, forget our current
4093 guards and pick new ones according to the new weightings. These
4094 three load balancing patches could raise effective network capacity
4095 by a factor of four. Thanks to Mike Perry for measurements.
4097 o Major bugfixes (stream expiration):
4098 - Expire not-yet-successful application streams in all cases if
4099 they've been around longer than SocksTimeout. Right now there are
4100 some cases where the stream will live forever, demanding a new
4101 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4103 o Minor features (controller):
4104 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4105 is valid before any authentication has been received. It tells
4106 a controller what kind of authentication is expected, and what
4107 protocol is spoken. Implements proposal 119.
4109 o Minor bugfixes (performance):
4110 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4111 greatly speeding up loading cached-routers from disk on startup.
4112 - Disable sentinel-based debugging for buffer code: we squashed all
4113 the bugs that this was supposed to detect a long time ago, and now
4114 its only effect is to change our buffer sizes from nice powers of
4115 two (which platform mallocs tend to like) to values slightly over
4116 powers of two (which make some platform mallocs sad).
4118 o Minor bugfixes (misc):
4119 - If exit bandwidth ever exceeds one third of total bandwidth, then
4120 use the correct formula to weight exit nodes when choosing paths.
4121 Based on patch from Mike Perry.
4122 - Choose perfectly fairly among routers when choosing by bandwidth and
4123 weighting by fraction of bandwidth provided by exits. Previously, we
4124 would choose with only approximate fairness, and correct ourselves
4125 if we ran off the end of the list.
4126 - If we require CookieAuthentication but we fail to write the
4127 cookie file, we would warn but not exit, and end up in a state
4128 where no controller could authenticate. Now we exit.
4129 - If we require CookieAuthentication, stop generating a new cookie
4130 every time we change any piece of our config.
4131 - Refuse to start with certain directory authority keys, and
4132 encourage people using them to stop.
4133 - Terminate multi-line control events properly. Original patch
4135 - Fix a minor memory leak when we fail to find enough suitable
4136 servers to choose a circuit.
4137 - Stop leaking part of the descriptor when we run into a particularly
4138 unparseable piece of it.
4141 Changes in version 0.1.2.16 - 2007-08-01
4142 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4143 remote attacker in certain situations to rewrite the user's torrc
4144 configuration file. This can completely compromise anonymity of users
4145 in most configurations, including those running the Vidalia bundles,
4146 TorK, etc. Or worse.
4148 o Major security fixes:
4149 - Close immediately after missing authentication on control port;
4150 do not allow multiple authentication attempts.
4153 Changes in version 0.1.2.15 - 2007-07-17
4154 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
4155 problems, fixes compilation on BSD, and fixes a variety of other
4156 bugs. Everybody should upgrade.
4158 o Major bugfixes (compilation):
4159 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
4161 o Major bugfixes (crashes):
4162 - Try even harder not to dereference the first character after
4163 an mmap(). Reported by lodger.
4164 - Fix a crash bug in directory authorities when we re-number the
4165 routerlist while inserting a new router.
4166 - When the cached-routers file is an even multiple of the page size,
4167 don't run off the end and crash. (Fixes bug 455; based on idea
4169 - Fix eventdns.c behavior on Solaris: It is critical to include
4170 orconfig.h _before_ sys/types.h, so that we can get the expected
4171 definition of _FILE_OFFSET_BITS.
4173 o Major bugfixes (security):
4174 - Fix a possible buffer overrun when using BSD natd support. Bug
4176 - When sending destroy cells from a circuit's origin, don't include
4177 the reason for tearing down the circuit. The spec says we didn't,
4178 and now we actually don't. Reported by lodger.
4179 - Keep streamids from different exits on a circuit separate. This
4180 bug may have allowed other routers on a given circuit to inject
4181 cells into streams. Reported by lodger; fixes bug 446.
4182 - If there's a never-before-connected-to guard node in our list,
4183 never choose any guards past it. This way we don't expand our
4184 guard list unless we need to.
4186 o Minor bugfixes (guard nodes):
4187 - Weight guard selection by bandwidth, so that low-bandwidth nodes
4188 don't get overused as guards.
4190 o Minor bugfixes (directory):
4191 - Correctly count the number of authorities that recommend each
4192 version. Previously, we were under-counting by 1.
4193 - Fix a potential crash bug when we load many server descriptors at
4194 once and some of them make others of them obsolete. Fixes bug 458.
4196 o Minor bugfixes (hidden services):
4197 - Stop tearing down the whole circuit when the user asks for a
4198 connection to a port that the hidden service didn't configure.
4201 o Minor bugfixes (misc):
4202 - On Windows, we were preventing other processes from reading
4203 cached-routers while Tor was running. Reported by janbar.
4204 - Fix a possible (but very unlikely) bug in picking routers by
4205 bandwidth. Add a log message to confirm that it is in fact
4206 unlikely. Patch from lodger.
4207 - Backport a couple of memory leak fixes.
4208 - Backport miscellaneous cosmetic bugfixes.
4211 Changes in version 0.1.2.14 - 2007-05-25
4212 Tor 0.1.2.14 changes the addresses of two directory authorities (this
4213 change especially affects those who serve or use hidden services),
4214 and fixes several other crash- and security-related bugs.
4216 o Directory authority changes:
4217 - Two directory authorities (moria1 and moria2) just moved to new
4218 IP addresses. This change will particularly affect those who serve
4219 or use hidden services.
4221 o Major bugfixes (crashes):
4222 - If a directory server runs out of space in the connection table
4223 as it's processing a begin_dir request, it will free the exit stream
4224 but leave it attached to the circuit, leading to unpredictable
4225 behavior. (Reported by seeess, fixes bug 425.)
4226 - Fix a bug in dirserv_remove_invalid() that would cause authorities
4227 to corrupt memory under some really unlikely scenarios.
4228 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
4229 - Avoid segfaults when reading from mmaped descriptor file. (Reported
4232 o Major bugfixes (security):
4233 - When choosing an entry guard for a circuit, avoid using guards
4234 that are in the same family as the chosen exit -- not just guards
4235 that are exactly the chosen exit. (Reported by lodger.)
4237 o Major bugfixes (resource management):
4238 - If a directory authority is down, skip it when deciding where to get
4239 networkstatus objects or descriptors. Otherwise we keep asking
4240 every 10 seconds forever. Fixes bug 384.
4241 - Count it as a failure if we fetch a valid network-status but we
4242 don't want to keep it. Otherwise we'll keep fetching it and keep
4243 not wanting to keep it. Fixes part of bug 422.
4244 - If all of our dirservers have given us bad or no networkstatuses
4245 lately, then stop hammering them once per minute even when we
4246 think they're failed. Fixes another part of bug 422.
4249 - Actually set the purpose correctly for descriptors inserted with
4251 - When we have k non-v2 authorities in our DirServer config,
4252 we ignored the last k authorities in the list when updating our
4254 - Correctly back-off from requesting router descriptors that we are
4255 having a hard time downloading.
4256 - Read resolv.conf files correctly on platforms where read() returns
4257 partial results on small file reads.
4258 - Don't rebuild the entire router store every time we get 32K of
4259 routers: rebuild it when the journal gets very large, or when
4260 the gaps in the store get very large.
4263 - When routers publish SVN revisions in their router descriptors,
4264 authorities now include those versions correctly in networkstatus
4266 - Warn when using a version of libevent before 1.3b to run a server on
4267 OSX or BSD: these versions interact badly with userspace threads.
4270 Changes in version 0.1.2.13 - 2007-04-24
4271 This release features some major anonymity fixes, such as safer path
4272 selection; better client performance; faster bootstrapping, better
4273 address detection, and better DNS support for servers; write limiting as
4274 well as read limiting to make servers easier to run; and a huge pile of
4275 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
4277 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
4278 of the Freenode IRC network, remembering his patience and vision for
4279 free speech on the Internet.
4281 o Major features, client performance:
4282 - Weight directory requests by advertised bandwidth. Now we can
4283 let servers enable write limiting but still allow most clients to
4284 succeed at their directory requests. (We still ignore weights when
4285 choosing a directory authority; I hope this is a feature.)
4286 - Stop overloading exit nodes -- avoid choosing them for entry or
4287 middle hops when the total bandwidth available from non-exit nodes
4288 is much higher than the total bandwidth available from exit nodes.
4289 - Rather than waiting a fixed amount of time between retrying
4290 application connections, we wait only 10 seconds for the first,
4291 10 seconds for the second, and 15 seconds for each retry after
4292 that. Hopefully this will improve the expected user experience.
4293 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
4294 to open a stream fails; now we do in more cases. This should
4295 make clients able to find a good exit faster in some cases, since
4296 unhandleable requests will now get an error rather than timing out.
4298 o Major features, client functionality:
4299 - Implement BEGIN_DIR cells, so we can connect to a directory
4300 server via TLS to do encrypted directory requests rather than
4301 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
4302 config options if you like. For now, this feature only works if
4303 you already have a descriptor for the destination dirserver.
4304 - Add support for transparent application connections: this basically
4305 bundles the functionality of trans-proxy-tor into the Tor
4306 mainline. Now hosts with compliant pf/netfilter implementations
4307 can redirect TCP connections straight to Tor without diverting
4308 through SOCKS. (Based on patch from tup.)
4309 - Add support for using natd; this allows FreeBSDs earlier than
4310 5.1.2 to have ipfw send connections through Tor without using
4311 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
4313 o Major features, servers:
4314 - Setting up a dyndns name for your server is now optional: servers
4315 with no hostname or IP address will learn their IP address by
4316 asking the directory authorities. This code only kicks in when you
4317 would normally have exited with a "no address" error. Nothing's
4318 authenticated, so use with care.
4319 - Directory servers now spool server descriptors, v1 directories,
4320 and v2 networkstatus objects to buffers as needed rather than en
4321 masse. They also mmap the cached-routers files. These steps save
4323 - Stop requiring clients to have well-formed certificates, and stop
4324 checking nicknames in certificates. (Clients have certificates so
4325 that they can look like Tor servers, but in the future we might want
4326 to allow them to look like regular TLS clients instead. Nicknames
4327 in certificates serve no purpose other than making our protocol
4328 easier to recognize on the wire.) Implements proposal 106.
4330 o Improvements on DNS support:
4331 - Add "eventdns" asynchronous dns library originally based on code
4332 from Adam Langley. Now we can discard the old rickety dnsworker
4333 concept, and support a wider variety of DNS functions. Allows
4334 multithreaded builds on NetBSD and OpenBSD again.
4335 - Add server-side support for "reverse" DNS lookups (using PTR
4336 records so clients can determine the canonical hostname for a given
4337 IPv4 address). Only supported by servers using eventdns; servers
4338 now announce in their descriptors if they don't support eventdns.
4339 - Workaround for name servers (like Earthlink's) that hijack failing
4340 DNS requests and replace the no-such-server answer with a "helpful"
4341 redirect to an advertising-driven search portal. Also work around
4342 DNS hijackers who "helpfully" decline to hijack known-invalid
4343 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
4344 lets you turn it off.
4345 - Servers now check for the case when common DNS requests are going to
4346 wildcarded addresses (i.e. all getting the same answer), and change
4347 their exit policy to reject *:* if it's happening.
4348 - When asked to resolve a hostname, don't use non-exit servers unless
4349 requested to do so. This allows servers with broken DNS to be
4350 useful to the network.
4351 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
4352 useless IPv6 DNS resolves.
4353 - Specify and implement client-side SOCKS5 interface for reverse DNS
4354 lookups (see doc/socks-extensions.txt). Also cache them.
4355 - When we change nameservers or IP addresses, reset and re-launch
4356 our tests for DNS hijacking.
4358 o Improvements on reachability testing:
4359 - Servers send out a burst of long-range padding cells once they've
4360 established that they're reachable. Spread them over 4 circuits,
4361 so hopefully a few will be fast. This exercises bandwidth and
4362 bootstraps them into the directory more quickly.
4363 - When we find our DirPort to be reachable, publish a new descriptor
4364 so we'll tell the world (reported by pnx).
4365 - Directory authorities now only decide that routers are reachable
4366 if their identity keys are as expected.
4367 - Do DirPort reachability tests less often, since a single test
4368 chews through many circuits before giving up.
4369 - Avoid some false positives during reachability testing: don't try
4370 to test via a server that's on the same /24 network as us.
4371 - Start publishing one minute or so after we find our ORPort
4372 to be reachable. This will help reduce the number of descriptors
4373 we have for ourselves floating around, since it's quite likely
4374 other things (e.g. DirPort) will change during that minute too.
4375 - Routers no longer try to rebuild long-term connections to directory
4376 authorities, and directory authorities no longer try to rebuild
4377 long-term connections to all servers. We still don't hang up
4378 connections in these two cases though -- we need to look at it
4379 more carefully to avoid flapping, and we likely need to wait til
4380 0.1.1.x is obsolete.
4382 o Improvements on rate limiting:
4383 - Enable write limiting as well as read limiting. Now we sacrifice
4384 capacity if we're pushing out lots of directory traffic, rather
4385 than overrunning the user's intended bandwidth limits.
4386 - Include TLS overhead when counting bandwidth usage; previously, we
4387 would count only the bytes sent over TLS, but not the bytes used
4389 - Servers decline directory requests much more aggressively when
4390 they're low on bandwidth. Otherwise they end up queueing more and
4391 more directory responses, which can't be good for latency.
4392 - But never refuse directory requests from local addresses.
4393 - Be willing to read or write on local connections (e.g. controller
4394 connections) even when the global rate limiting buckets are empty.
4395 - Flush local controller connection buffers periodically as we're
4396 writing to them, so we avoid queueing 4+ megabytes of data before
4398 - Revise and clean up the torrc.sample that we ship with; add
4399 a section for BandwidthRate and BandwidthBurst.
4401 o Major features, NT services:
4402 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
4403 command-line flag so that admins can override the default by saying
4404 "tor --service install --user "SomeUser"". This will not affect
4405 existing installed services. Also, warn the user that the service
4406 will look for its configuration file in the service user's
4407 %appdata% directory. (We can't do the "hardwire the user's appdata
4408 directory" trick any more, since we may not have read access to that
4410 - Support running the Tor service with a torrc not in the same
4411 directory as tor.exe and default to using the torrc located in
4412 the %appdata%\Tor\ of the user who installed the service. Patch
4414 - Add an --ignore-missing-torrc command-line option so that we can
4415 get the "use sensible defaults if the configuration file doesn't
4416 exist" behavior even when specifying a torrc location on the
4418 - When stopping an NT service, wait up to 10 sec for it to actually
4419 stop. (Patch from Matt Edman; resolves bug 295.)
4421 o Directory authority improvements:
4422 - Stop letting hibernating or obsolete servers affect uptime and
4424 - Stop listing hibernating servers in the v1 directory.
4425 - Authorities no longer recommend exits as guards if this would shift
4426 too much load to the exit nodes.
4427 - Authorities now specify server versions in networkstatus. This adds
4428 about 2% to the size of compressed networkstatus docs, and allows
4429 clients to tell which servers support BEGIN_DIR and which don't.
4430 The implementation is forward-compatible with a proposed future
4431 protocol version scheme not tied to Tor versions.
4432 - DirServer configuration lines now have an orport= option so
4433 clients can open encrypted tunnels to the authorities without
4434 having downloaded their descriptors yet. Enabled for moria1,
4435 moria2, tor26, and lefkada now in the default configuration.
4436 - Add a BadDirectory flag to network status docs so that authorities
4437 can (eventually) tell clients about caches they believe to be
4438 broken. Not used yet.
4439 - Allow authorities to list nodes as bad exits in their
4440 approved-routers file by fingerprint or by address. If most
4441 authorities set a BadExit flag for a server, clients don't think
4442 of it as a general-purpose exit. Clients only consider authorities
4443 that advertise themselves as listing bad exits.
4444 - Patch from Steve Hildrey: Generate network status correctly on
4445 non-versioning dirservers.
4446 - Have directory authorities allow larger amounts of drift in uptime
4447 without replacing the server descriptor: previously, a server that
4448 restarted every 30 minutes could have 48 "interesting" descriptors
4450 - Reserve the nickname "Unnamed" for routers that can't pick
4451 a hostname: any router can call itself Unnamed; directory
4452 authorities will never allocate Unnamed to any particular router;
4453 clients won't believe that any router is the canonical Unnamed.
4455 o Directory mirrors and clients:
4456 - Discard any v1 directory info that's over 1 month old (for
4457 directories) or over 1 week old (for running-routers lists).
4458 - Clients track responses with status 503 from dirservers. After a
4459 dirserver has given us a 503, we try not to use it until an hour has
4460 gone by, or until we have no dirservers that haven't given us a 503.
4461 - When we get a 503 from a directory, and we're not a server, we no
4462 longer count the failure against the total number of failures
4463 allowed for the object we're trying to download.
4464 - Prepare for servers to publish descriptors less often: never
4465 discard a descriptor simply for being too old until either it is
4466 recommended by no authorities, or until we get a better one for
4467 the same router. Make caches consider retaining old recommended
4468 routers for even longer.
4469 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
4470 headers for content, so that we can work better in the presence of
4471 caching HTTP proxies.
4472 - Stop fetching descriptors if you're not a dir mirror and you
4473 haven't tried to establish any circuits lately. (This currently
4474 causes some dangerous behavior, because when you start up again
4475 you'll use your ancient server descriptors.)
4477 o Major fixes, crashes:
4478 - Stop crashing when the controller asks us to resetconf more than
4479 one config option at once. (Vidalia 0.0.11 does this.)
4480 - Fix a longstanding obscure crash bug that could occur when we run
4481 out of DNS worker processes, if we're not using eventdns. (Resolves
4483 - Fix an assert that could trigger if a controller quickly set then
4484 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
4485 - Avoid crash when telling controller about stream-status and a
4487 - Avoid sending junk to controllers or segfaulting when a controller
4488 uses EVENT_NEW_DESC with verbose nicknames.
4489 - Stop triggering asserts if the controller tries to extend hidden
4490 service circuits (reported by mwenge).
4491 - If we start a server with ClientOnly 1, then set ClientOnly to 0
4492 and hup, stop triggering an assert based on an empty onion_key.
4493 - Mask out all signals in sub-threads; only the libevent signal
4494 handler should be processing them. This should prevent some crashes
4495 on some machines using pthreads. (Patch from coderman.)
4496 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
4498 o Major fixes, anonymity/security:
4499 - Automatically avoid picking more than one node from the same
4500 /16 network when constructing a circuit. Add an
4501 "EnforceDistinctSubnets" option to let people disable it if they
4502 want to operate private test networks on a single subnet.
4503 - When generating bandwidth history, round down to the nearest
4504 1k. When storing accounting data, round up to the nearest 1k.
4505 - When we're running as a server, remember when we last rotated onion
4506 keys, so that we will rotate keys once they're a week old even if
4507 we never stay up for a week ourselves.
4508 - If a client asked for a server by name, and there's a named server
4509 in our network-status but we don't have its descriptor yet, we
4510 could return an unnamed server instead.
4511 - Reject (most) attempts to use Tor circuits with length one. (If
4512 many people start using Tor as a one-hop proxy, exit nodes become
4513 a more attractive target for compromise.)
4514 - Just because your DirPort is open doesn't mean people should be
4515 able to remotely teach you about hidden service descriptors. Now
4516 only accept rendezvous posts if you've got HSAuthoritativeDir set.
4517 - Fix a potential race condition in the rpm installer. Found by
4519 - Do not log IPs with TLS failures for incoming TLS
4520 connections. (Fixes bug 382.)
4522 o Major fixes, other:
4523 - If our system clock jumps back in time, don't publish a negative
4524 uptime in the descriptor.
4525 - When we start during an accounting interval before it's time to wake
4526 up, remember to wake up at the correct time. (May fix bug 342.)
4527 - Previously, we would cache up to 16 old networkstatus documents
4528 indefinitely, if they came from nontrusted authorities. Now we
4529 discard them if they are more than 10 days old.
4530 - When we have a state file we cannot parse, tell the user and
4531 move it aside. Now we avoid situations where the user starts
4532 Tor in 1904, Tor writes a state file with that timestamp in it,
4533 the user fixes her clock, and Tor refuses to start.
4534 - Publish a new descriptor after we hup/reload. This is important
4535 if our config has changed such that we'll want to start advertising
4536 our DirPort now, etc.
4537 - If we are using an exit enclave and we can't connect, e.g. because
4538 its webserver is misconfigured to not listen on localhost, then
4539 back off and try connecting from somewhere else before we fail.
4541 o New config options or behaviors:
4542 - When EntryNodes are configured, rebuild the guard list to contain,
4543 in order: the EntryNodes that were guards before; the rest of the
4544 EntryNodes; the nodes that were guards before.
4545 - Do not warn when individual nodes in the configuration's EntryNodes,
4546 ExitNodes, etc are down: warn only when all possible nodes
4547 are down. (Fixes bug 348.)
4548 - Put a lower-bound on MaxAdvertisedBandwidth.
4549 - Start using the state file to store bandwidth accounting data:
4550 the bw_accounting file is now obsolete. We'll keep generating it
4551 for a while for people who are still using 0.1.2.4-alpha.
4552 - Try to batch changes to the state file so that we do as few
4553 disk writes as possible while still storing important things in
4555 - The state file and the bw_accounting file get saved less often when
4556 the AvoidDiskWrites config option is set.
4557 - Make PIDFile work on Windows.
4558 - Add internal descriptions for a bunch of configuration options:
4559 accessible via controller interface and in comments in saved
4561 - Reject *:563 (NNTPS) in the default exit policy. We already reject
4562 NNTP by default, so this seems like a sensible addition.
4563 - Clients now reject hostnames with invalid characters. This should
4564 avoid some inadvertent info leaks. Add an option
4565 AllowNonRFC953Hostnames to disable this behavior, in case somebody
4566 is running a private network with hosts called @, !, and #.
4567 - Check for addresses with invalid characters at the exit as well,
4568 and warn less verbosely when they fail. You can override this by
4569 setting ServerDNSAllowNonRFC953Addresses to 1.
4570 - Remove some options that have been deprecated since at least
4571 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
4572 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
4573 to set log options. Mark PathlenCoinWeight as obsolete.
4574 - Stop accepting certain malformed ports in configured exit policies.
4575 - When the user uses bad syntax in the Log config line, stop
4576 suggesting other bad syntax as a replacement.
4577 - Add new config option "ResolvConf" to let the server operator
4578 choose an alternate resolve.conf file when using eventdns.
4579 - If one of our entry guards is on the ExcludeNodes list, or the
4580 directory authorities don't think it's a good guard, treat it as
4581 if it were unlisted: stop using it as a guard, and throw it off
4582 the guards list if it stays that way for a long time.
4583 - Allow directory authorities to be marked separately as authorities
4584 for the v1 directory protocol, the v2 directory protocol, and
4585 as hidden service directories, to make it easier to retire old
4586 authorities. V1 authorities should set "HSAuthoritativeDir 1"
4587 to continue being hidden service authorities too.
4588 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
4589 - Make TrackExitHosts case-insensitive, and fix the behavior of
4590 ".suffix" TrackExitHosts items to avoid matching in the middle of
4592 - New DirPort behavior: if you have your dirport set, you download
4593 descriptors aggressively like a directory mirror, whether or not
4597 - Create a new file ReleaseNotes which was the old ChangeLog. The
4598 new ChangeLog file now includes the notes for all development
4600 - Add a new address-spec.txt document to describe our special-case
4601 addresses: .exit, .onion, and .noconnnect.
4602 - Fork the v1 directory protocol into its own spec document,
4603 and mark dir-spec.txt as the currently correct (v2) spec.
4605 o Packaging, porting, and contrib
4606 - "tor --verify-config" now exits with -1(255) or 0 depending on
4607 whether the config options are bad or good.
4608 - The Debian package now uses --verify-config when (re)starting,
4609 to distinguish configuration errors from other errors.
4610 - Adapt a patch from goodell to let the contrib/exitlist script
4611 take arguments rather than require direct editing.
4612 - Prevent the contrib/exitlist script from printing the same
4613 result more than once.
4614 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
4615 - In the hidden service example in torrc.sample, stop recommending
4616 esoteric and discouraged hidden service options.
4617 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
4618 values before failing, and always enables eventdns.
4619 - Try to detect Windows correctly when cross-compiling.
4620 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
4621 Try to fix this in configure.in by checking for most functions
4622 before we check for libevent.
4623 - Update RPMs to require libevent 1.2.
4624 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
4625 or later. Log when we are doing this, so we can diagnose it when
4626 it fails. (Also, recommend libevent 1.1b for kqueue and
4627 win32 methods; deprecate libevent 1.0b harder; make libevent
4628 recommendation system saner.)
4629 - Build with recent (1.3+) libevents on platforms that do not
4630 define the nonstandard types "u_int8_t" and friends.
4631 - Remove architecture from OS X builds. The official builds are
4632 now universal binaries.
4633 - Run correctly on OS X platforms with case-sensitive filesystems.
4634 - Correctly set maximum connection limit on Cygwin. (This time
4636 - Start compiling on MinGW on Windows (patches from Mike Chiussi
4638 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
4639 - Finally fix the openssl warnings from newer gccs that believe that
4640 ignoring a return value is okay, but casting a return value and
4641 then ignoring it is a sign of madness.
4642 - On architectures where sizeof(int)>4, still clamp declarable
4643 bandwidth to INT32_MAX.
4645 o Minor features, controller:
4646 - Warn the user when an application uses the obsolete binary v0
4647 control protocol. We're planning to remove support for it during
4648 the next development series, so it's good to give people some
4650 - Add STREAM_BW events to report per-entry-stream bandwidth
4651 use. (Patch from Robert Hogan.)
4652 - Rate-limit SIGNEWNYM signals in response to controllers that
4653 impolitely generate them for every single stream. (Patch from
4654 mwenge; closes bug 394.)
4655 - Add a REMAP status to stream events to note that a stream's
4656 address has changed because of a cached address or a MapAddress
4658 - Make REMAP stream events have a SOURCE (cache or exit), and
4659 make them generated in every case where we get a successful
4660 connected or resolved cell.
4661 - Track reasons for OR connection failure; make these reasons
4662 available via the controller interface. (Patch from Mike Perry.)
4663 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
4664 can learn when clients are sending malformed hostnames to Tor.
4665 - Specify and implement some of the controller status events.
4666 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
4667 - Reimplement GETINFO so that info/names stays in sync with the
4669 - Implement "GETINFO fingerprint".
4670 - Implement "SETEVENTS GUARD" so controllers can get updates on
4671 entry guard status as it changes.
4672 - Make all connections to addresses of the form ".noconnect"
4673 immediately get closed. This lets application/controller combos
4674 successfully test whether they're talking to the same Tor by
4675 watching for STREAM events.
4676 - Add a REASON field to CIRC events; for backward compatibility, this
4677 field is sent only to controllers that have enabled the extended
4678 event format. Also, add additional reason codes to explain why
4679 a given circuit has been destroyed or truncated. (Patches from
4681 - Add a REMOTE_REASON field to extended CIRC events to tell the
4682 controller why a remote OR told us to close a circuit.
4683 - Stream events also now have REASON and REMOTE_REASON fields,
4684 working much like those for circuit events.
4685 - There's now a GETINFO ns/... field so that controllers can ask Tor
4686 about the current status of a router.
4687 - A new event type "NS" to inform a controller when our opinion of
4688 a router's status has changed.
4689 - Add a GETINFO events/names and GETINFO features/names so controllers
4690 can tell which events and features are supported.
4691 - A new CLEARDNSCACHE signal to allow controllers to clear the
4692 client-side DNS cache without expiring circuits.
4693 - Fix CIRC controller events so that controllers can learn the
4694 identity digests of non-Named servers used in circuit paths.
4695 - Let controllers ask for more useful identifiers for servers. Instead
4696 of learning identity digests for un-Named servers and nicknames
4697 for Named servers, the new identifiers include digest, nickname,
4698 and indication of Named status. Off by default; see control-spec.txt
4699 for more information.
4700 - Add a "getinfo address" controller command so it can display Tor's
4701 best guess to the user.
4702 - New controller event to alert the controller when our server
4703 descriptor has changed.
4704 - Give more meaningful errors on controller authentication failure.
4705 - Export the default exit policy via the control port, so controllers
4706 don't need to guess what it is / will be later.
4708 o Minor bugfixes, controller:
4709 - When creating a circuit via the controller, send a 'launched'
4710 event when we're done, so we follow the spec better.
4711 - Correct the control spec to match how the code actually responds
4712 to 'getinfo addr-mappings/*'. Reported by daejees.
4713 - The control spec described a GUARDS event, but the code
4714 implemented a GUARD event. Standardize on GUARD, but let people
4715 ask for GUARDS too. Reported by daejees.
4716 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
4717 clear the corresponding on_circuit variable, and remember later
4718 that we don't need to send a redundant CLOSED event. (Resolves part
4720 - Report events where a resolve succeeded or where we got a socks
4721 protocol error correctly, rather than calling both of them
4723 - Change reported stream target addresses to IP consistently when
4724 we finally get the IP from an exit node.
4725 - Send log messages to the controller even if they happen to be very
4727 - Flush ERR-level controller status events just like we currently
4728 flush ERR-level log events, so that a Tor shutdown doesn't prevent
4729 the controller from learning about current events.
4730 - Report the circuit number correctly in STREAM CLOSED events. Bug
4731 reported by Mike Perry.
4732 - Do not report bizarre values for results of accounting GETINFOs
4733 when the last second's write or read exceeds the allotted bandwidth.
4734 - Report "unrecognized key" rather than an empty string when the
4735 controller tries to fetch a networkstatus that doesn't exist.
4736 - When the controller does a "GETINFO network-status", tell it
4737 about even those routers whose descriptors are very old, and use
4738 long nicknames where appropriate.
4739 - Fix handling of verbose nicknames with ORCONN controller events:
4740 make them show up exactly when requested, rather than exactly when
4742 - Controller signals now work on non-Unix platforms that don't define
4743 SIGUSR1 and SIGUSR2 the way we expect.
4744 - Respond to SIGNAL command before we execute the signal, in case
4745 the signal shuts us down. Suggested by Karsten Loesing.
4746 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
4748 o Minor features, code performance:
4749 - Major performance improvement on inserting descriptors: change
4750 algorithm from O(n^2) to O(n).
4751 - Do not rotate onion key immediately after setting it for the first
4753 - Call router_have_min_dir_info half as often. (This is showing up in
4754 some profiles, but not others.)
4755 - When using GCC, make log_debug never get called at all, and its
4756 arguments never get evaluated, when no debug logs are configured.
4757 (This is showing up in some profiles, but not others.)
4758 - Statistics dumped by -USR2 now include a breakdown of public key
4759 operations, for profiling.
4760 - Make the common memory allocation path faster on machines where
4761 malloc(0) returns a pointer.
4762 - Split circuit_t into origin_circuit_t and or_circuit_t, and
4763 split connection_t into edge, or, dir, control, and base structs.
4764 These will save quite a bit of memory on busy servers, and they'll
4765 also help us track down bugs in the code and bugs in the spec.
4766 - Use OpenSSL's AES implementation on platforms where it's faster.
4767 This could save us as much as 10% CPU usage.
4769 o Minor features, descriptors and descriptor handling:
4770 - Avoid duplicate entries on MyFamily line in server descriptor.
4771 - When Tor receives a router descriptor that it asked for, but
4772 no longer wants (because it has received fresh networkstatuses
4773 in the meantime), do not warn the user. Cache the descriptor if
4774 we're a cache; drop it if we aren't.
4775 - Servers no longer ever list themselves in their "family" line,
4776 even if configured to do so. This makes it easier to configure
4777 family lists conveniently.
4779 o Minor fixes, confusing/misleading log messages:
4780 - Display correct results when reporting which versions are
4781 recommended, and how recommended they are. (Resolves bug 383.)
4782 - Inform the server operator when we decide not to advertise a
4783 DirPort due to AccountingMax enabled or a low BandwidthRate.
4784 - Only include function names in log messages for info/debug messages.
4785 For notice/warn/err, the content of the message should be clear on
4786 its own, and printing the function name only confuses users.
4787 - Remove even more protocol-related warnings from Tor server logs,
4788 such as bad TLS handshakes and malformed begin cells.
4789 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
4790 when the IP address is mapped through MapAddress to a hostname.
4791 - Fix misleading log messages: an entry guard that is "unlisted",
4792 as well as not known to be "down" (because we've never heard
4793 of it), is not therefore "up".
4795 o Minor fixes, old/obsolete behavior:
4796 - Start assuming we can use a create_fast cell if we don't know
4797 what version a router is running.
4798 - We no longer look for identity and onion keys in "identity.key" and
4799 "onion.key" -- these were replaced by secret_id_key and
4800 secret_onion_key in 0.0.8pre1.
4801 - We no longer require unrecognized directory entries to be
4803 - Drop compatibility with obsolete Tors that permit create cells
4804 to have the wrong circ_id_type.
4805 - Remove code to special-case "-cvs" ending, since it has not
4806 actually mattered since 0.0.9.
4807 - Don't re-write the fingerprint file every restart, unless it has
4810 o Minor fixes, misc client-side behavior:
4811 - Always remove expired routers and networkstatus docs before checking
4812 whether we have enough information to build circuits. (Fixes
4814 - When computing clock skew from directory HTTP headers, consider what
4815 time it was when we finished asking for the directory, not what
4817 - Make our socks5 handling more robust to broken socks clients:
4818 throw out everything waiting on the buffer in between socks
4819 handshake phases, since they can't possibly (so the theory
4820 goes) have predicted what we plan to respond to them.
4821 - Expire socks connections if they spend too long waiting for the
4822 handshake to finish. Previously we would let them sit around for
4823 days, if the connecting application didn't close them either.
4824 - And if the socks handshake hasn't started, don't send a
4825 "DNS resolve socks failed" handshake reply; just close it.
4826 - If the user asks to use invalid exit nodes, be willing to use
4828 - Track unreachable entry guards correctly: don't conflate
4829 'unreachable by us right now' with 'listed as down by the directory
4830 authorities'. With the old code, if a guard was unreachable by us
4831 but listed as running, it would clog our guard list forever.
4832 - Behave correctly in case we ever have a network with more than
4833 2GB/s total advertised capacity.
4834 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
4835 - Fix a memory leak when we ask for "all" networkstatuses and we
4836 get one we don't recognize.
4839 Changes in version 0.1.1.26 - 2006-12-14
4840 o Security bugfixes:
4841 - Stop sending the HttpProxyAuthenticator string to directory
4842 servers when directory connections are tunnelled through Tor.
4843 - Clients no longer store bandwidth history in the state file.
4844 - Do not log introduction points for hidden services if SafeLogging
4848 - Fix an assert failure when a directory authority sets
4849 AuthDirRejectUnlisted and then receives a descriptor from an
4850 unlisted router (reported by seeess).
4853 Changes in version 0.1.1.25 - 2006-11-04
4855 - When a client asks us to resolve (rather than connect to)
4856 an address, and we have a cached answer, give them the cached
4857 answer. Previously, we would give them no answer at all.
4858 - We were building exactly the wrong circuits when we predict
4859 hidden service requirements, meaning Tor would have to build all
4860 its circuits on demand.
4861 - If none of our live entry guards have a high uptime, but we
4862 require a guard with a high uptime, try adding a new guard before
4863 we give up on the requirement. This patch should make long-lived
4864 connections more stable on average.
4865 - When testing reachability of our DirPort, don't launch new
4866 tests when there's already one in progress -- unreachable
4867 servers were stacking up dozens of testing streams.
4869 o Security bugfixes:
4870 - When the user sends a NEWNYM signal, clear the client-side DNS
4871 cache too. Otherwise we continue to act on previous information.
4874 - Avoid a memory corruption bug when creating a hash table for
4876 - Avoid possibility of controller-triggered crash when misusing
4877 certain commands from a v0 controller on platforms that do not
4878 handle printf("%s",NULL) gracefully.
4879 - Avoid infinite loop on unexpected controller input.
4880 - Don't log spurious warnings when we see a circuit close reason we
4881 don't recognize; it's probably just from a newer version of Tor.
4882 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4883 Tor/Privoxy we also uninstall Vidalia.
4886 Changes in version 0.1.1.24 - 2006-09-29
4888 - Allow really slow clients to not hang up five minutes into their
4889 directory downloads (suggested by Adam J. Richter).
4890 - Fix major performance regression from 0.1.0.x: instead of checking
4891 whether we have enough directory information every time we want to
4892 do something, only check when the directory information has changed.
4893 This should improve client CPU usage by 25-50%.
4894 - Don't crash if, after a server has been running for a while,
4895 it can't resolve its hostname.
4896 - When a client asks us to resolve (not connect to) an address,
4897 and we have a cached answer, give them the cached answer.
4898 Previously, we would give them no answer at all.
4901 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4902 - Don't crash when the controller receives a third argument to an
4903 "extendcircuit" request.
4904 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4905 response; fix error code when "getinfo dir/status/" fails.
4906 - Fix configure.in to not produce broken configure files with
4907 more recent versions of autoconf. Thanks to Clint for his auto*
4909 - Fix security bug on NetBSD that could allow someone to force
4910 uninitialized RAM to be sent to a server's DNS resolver. This
4911 only affects NetBSD and other platforms that do not bounds-check
4913 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
4914 methods: these are known to be buggy.
4915 - If we're a directory mirror and we ask for "all" network status
4916 documents, we would discard status documents from authorities
4920 Changes in version 0.1.1.23 - 2006-07-30
4922 - Fast Tor servers, especially exit nodes, were triggering asserts
4923 due to a bug in handling the list of pending DNS resolves. Some
4924 bugs still remain here; we're hunting them.
4925 - Entry guards could crash clients by sending unexpected input.
4926 - More fixes on reachability testing: if you find yourself reachable,
4927 then don't ever make any client requests (so you stop predicting
4928 circuits), then hup or have your clock jump, then later your IP
4929 changes, you won't think circuits are working, so you won't try to
4930 test reachability, so you won't publish.
4933 - Avoid a crash if the controller does a resetconf firewallports
4934 and then a setconf fascistfirewall=1.
4935 - Avoid an integer underflow when the dir authority decides whether
4936 a router is stable: we might wrongly label it stable, and compute
4937 a slightly wrong median stability, when a descriptor is published
4939 - Fix a place where we might trigger an assert if we can't build our
4940 own server descriptor yet.
4943 Changes in version 0.1.1.22 - 2006-07-05
4945 - Fix a big bug that was causing servers to not find themselves
4946 reachable if they changed IP addresses. Since only 0.1.1.22+
4947 servers can do reachability testing correctly, now we automatically
4948 make sure to test via one of these.
4949 - Fix to allow clients and mirrors to learn directory info from
4950 descriptor downloads that get cut off partway through.
4951 - Directory authorities had a bug in deciding if a newly published
4952 descriptor was novel enough to make everybody want a copy -- a few
4953 servers seem to be publishing new descriptors many times a minute.
4955 - Fix a rare bug that was causing some servers to complain about
4956 "closing wedged cpuworkers" and skip some circuit create requests.
4957 - Make the Exit flag in directory status documents actually work.
4960 Changes in version 0.1.1.21 - 2006-06-10
4961 o Crash and assert fixes from 0.1.1.20:
4962 - Fix a rare crash on Tor servers that have enabled hibernation.
4963 - Fix a seg fault on startup for Tor networks that use only one
4964 directory authority.
4965 - Fix an assert from a race condition that occurs on Tor servers
4966 while exiting, where various threads are trying to log that they're
4967 exiting, and delete the logs, at the same time.
4968 - Make our unit tests pass again on certain obscure platforms.
4971 - Add support for building SUSE RPM packages.
4972 - Speed up initial bootstrapping for clients: if we are making our
4973 first ever connection to any entry guard, then don't mark it down
4975 - When only one Tor server in the network is labelled as a guard,
4976 and we've already picked him, we would cycle endlessly picking him
4977 again, being unhappy about it, etc. Now we specifically exclude
4978 current guards when picking a new guard.
4979 - Servers send create cells more reliably after the TLS connection
4980 is established: we were sometimes forgetting to send half of them
4981 when we had more than one pending.
4982 - If we get a create cell that asks us to extend somewhere, but the
4983 Tor server there doesn't match the expected digest, we now send
4984 a destroy cell back, rather than silently doing nothing.
4985 - Make options->RedirectExit work again.
4986 - Make cookie authentication for the controller work again.
4987 - Stop being picky about unusual characters in the arguments to
4988 mapaddress. It's none of our business.
4989 - Add a new config option "TestVia" that lets you specify preferred
4990 middle hops to use for test circuits. Perhaps this will let me
4991 debug the reachability problems better.
4993 o Log / documentation fixes:
4994 - If we're a server and some peer has a broken TLS certificate, don't
4995 log about it unless ProtocolWarnings is set, i.e., we want to hear
4996 about protocol violations by others.
4997 - Fix spelling of VirtualAddrNetwork in man page.
4998 - Add a better explanation at the top of the autogenerated torrc file
4999 about what happened to our old torrc.
5002 Changes in version 0.1.1.20 - 2006-05-23
5003 o Crash and assert fixes from 0.1.0.17:
5004 - Fix assert bug in close_logs() on exit: when we close and delete
5005 logs, remove them all from the global "logfiles" list.
5006 - Fix an assert error when we're out of space in the connection_list
5007 and we try to post a hidden service descriptor (reported by Peter
5009 - Fix a rare assert error when we've tried all intro points for
5010 a hidden service and we try fetching the service descriptor again:
5011 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
5012 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
5013 out and refuse the setconf if it would fail.
5014 - If you specify a relative torrc path and you set RunAsDaemon in
5015 your torrc, then it chdir()'s to the new directory. If you then
5016 HUP, it tries to load the new torrc location, fails, and exits.
5017 The fix: no longer allow a relative path to torrc when using -f.
5018 - Check for integer overflows in more places, when adding elements
5019 to smartlists. This could possibly prevent a buffer overflow
5020 on malicious huge inputs.
5022 o Security fixes, major:
5023 - When we're printing strings from the network, don't try to print
5024 non-printable characters. Now we're safer against shell escape
5025 sequence exploits, and also against attacks to fool users into
5026 misreading their logs.
5027 - Implement entry guards: automatically choose a handful of entry
5028 nodes and stick with them for all circuits. Only pick new guards
5029 when the ones you have are unsuitable, and if the old guards
5030 become suitable again, switch back. This will increase security
5031 dramatically against certain end-point attacks. The EntryNodes
5032 config option now provides some hints about which entry guards you
5033 want to use most; and StrictEntryNodes means to only use those.
5034 Fixes CVE-2006-0414.
5035 - Implement exit enclaves: if we know an IP address for the
5036 destination, and there's a running Tor server at that address
5037 which allows exit to the destination, then extend the circuit to
5038 that exit first. This provides end-to-end encryption and end-to-end
5039 authentication. Also, if the user wants a .exit address or enclave,
5040 use 4 hops rather than 3, and cannibalize a general circ for it
5042 - Obey our firewall options more faithfully:
5043 . If we can't get to a dirserver directly, try going via Tor.
5044 . Don't ever try to connect (as a client) to a place our
5045 firewall options forbid.
5046 . If we specify a proxy and also firewall options, obey the
5047 firewall options even when we're using the proxy: some proxies
5048 can only proxy to certain destinations.
5049 - Make clients regenerate their keys when their IP address changes.
5050 - For the OS X package's modified privoxy config file, comment
5051 out the "logfile" line so we don't log everything passed
5053 - Our TLS handshakes were generating a single public/private
5054 keypair for the TLS context, rather than making a new one for
5055 each new connection. Oops. (But we were still rotating them
5056 periodically, so it's not so bad.)
5057 - When we were cannibalizing a circuit with a particular exit
5058 node in mind, we weren't checking to see if that exit node was
5059 already present earlier in the circuit. Now we are.
5060 - Require server descriptors to list IPv4 addresses -- hostnames
5061 are no longer allowed. This also fixes potential vulnerabilities
5062 to servers providing hostnames as their address and then
5063 preferentially resolving them so they can partition users.
5064 - Our logic to decide if the OR we connected to was the right guy
5065 was brittle and maybe open to a mitm for invalid routers.
5067 o Security fixes, minor:
5068 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
5069 Ian Goldberg can prove things about our handshake protocol more
5071 - Make directory authorities generate a separate "guard" flag to
5072 mean "would make a good entry guard". Clients now honor the
5073 is_guard flag rather than looking at is_fast or is_stable.
5074 - Try to list MyFamily elements by key, not by nickname, and warn
5075 if we've not heard of a server.
5076 - Start using RAND_bytes rather than RAND_pseudo_bytes from
5077 OpenSSL. Also, reseed our entropy every hour, not just at
5078 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
5079 - Refuse server descriptors where the fingerprint line doesn't match
5080 the included identity key. Tor doesn't care, but other apps (and
5081 humans) might actually be trusting the fingerprint line.
5082 - We used to kill the circuit when we receive a relay command we
5083 don't recognize. Now we just drop that cell.
5084 - Fix a bug found by Lasse Overlier: when we were making internal
5085 circuits (intended to be cannibalized later for rendezvous and
5086 introduction circuits), we were picking them so that they had
5087 useful exit nodes. There was no need for this, and it actually
5088 aids some statistical attacks.
5089 - Start treating internal circuits and exit circuits separately.
5090 It's important to keep them separate because internal circuits
5091 have their last hops picked like middle hops, rather than like
5092 exit hops. So exiting on them will break the user's expectations.
5093 - Fix a possible way to DoS dirservers.
5094 - When the client asked for a rendezvous port that the hidden
5095 service didn't want to provide, we were sending an IP address
5096 back along with the end cell. Fortunately, it was zero. But stop
5099 o Packaging improvements:
5100 - Implement --with-libevent-dir option to ./configure. Improve
5101 search techniques to find libevent, and use those for openssl too.
5102 - Fix a couple of bugs in OpenSSL detection. Deal better when
5103 there are multiple SSLs installed with different versions.
5104 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
5105 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
5107 - Make unit tests (and other invocations that aren't the real Tor)
5108 run without launching listeners, creating subdirectories, and so on.
5109 - The OS X installer was adding a symlink for tor_resolve but
5110 the binary was called tor-resolve (reported by Thomas Hardly).
5111 - Now we can target arch and OS in rpm builds (contributed by
5112 Phobos). Also make the resulting dist-rpm filename match the
5114 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
5115 if you log to syslog and want something other than LOG_DAEMON.
5116 - Fix the torify (tsocks) config file to not use Tor for localhost
5118 - Start shipping socks-extensions.txt, tor-doc-unix.html,
5119 tor-doc-server.html, and stylesheet.css in the tarball.
5120 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
5121 They are useless now.
5122 - Add Peter Palfrader's contributed check-tor script. It lets you
5123 easily check whether a given server (referenced by nickname)
5124 is reachable by you.
5125 - Add BSD-style contributed startup script "rc.subr" from Peter
5128 o Directory improvements -- new directory protocol:
5129 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
5130 - Authorities and caches publish individual descriptors (by
5131 digest, by fingerprint, by "all", and by "tell me yours").
5132 - Clients don't download or use the old directory anymore. Now they
5133 download network-statuses from the directory authorities, and
5134 fetch individual server descriptors as needed from mirrors.
5135 - Clients don't download descriptors of non-running servers.
5136 - Download descriptors by digest, not by fingerprint. Caches try to
5137 download all listed digests from authorities; clients try to
5138 download "best" digests from caches. This avoids partitioning
5139 and isolating attacks better.
5140 - Only upload a new server descriptor when options change, 18
5141 hours have passed, uptime is reset, or bandwidth changes a lot.
5142 - Directory authorities silently throw away new descriptors that
5143 haven't changed much if the timestamps are similar. We do this to
5144 tolerate older Tor servers that upload a new descriptor every 15
5145 minutes. (It seemed like a good idea at the time.)
5146 - Clients choose directory servers from the network status lists,
5147 not from their internal list of router descriptors. Now they can
5148 go to caches directly rather than needing to go to authorities
5149 to bootstrap the first set of descriptors.
5150 - When picking a random directory, prefer non-authorities if any
5152 - Add a new flag to network-status indicating whether the server
5153 can answer v2 directory requests too.
5154 - Directory mirrors now cache up to 16 unrecognized network-status
5155 docs, so new directory authorities will be cached too.
5156 - Stop parsing, storing, or using running-routers output (but
5157 mirrors still cache and serve it).
5158 - Clients consider a threshold of "versioning" directory authorities
5159 before deciding whether to warn the user that he's obsolete.
5160 - Authorities publish separate sorted lists of recommended versions
5161 for clients and for servers.
5162 - Change DirServers config line to note which dirs are v1 authorities.
5163 - Put nicknames on the DirServer line, so we can refer to them
5164 without requiring all our users to memorize their IP addresses.
5165 - Remove option when getting directory cache to see whether they
5166 support running-routers; they all do now. Replace it with one
5167 to see whether caches support v2 stuff.
5168 - Stop listing down or invalid nodes in the v1 directory. This
5169 reduces its bulk by about 1/3, and reduces load on mirrors.
5170 - Mirrors no longer cache the v1 directory as often.
5171 - If we as a directory mirror don't know of any v1 directory
5172 authorities, then don't try to cache any v1 directories.
5174 o Other directory improvements:
5175 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
5176 fifth authoritative directory servers.
5177 - Directory authorities no longer require an open connection from
5178 a server to consider him "reachable". We need this change because
5179 when we add new directory authorities, old servers won't know not
5181 - Dir authorities now do their own external reachability testing
5182 of each server, and only list as running the ones they found to
5183 be reachable. We also send back warnings to the server's logs if
5184 it uploads a descriptor that we already believe is unreachable.
5185 - Spread the directory authorities' reachability testing over the
5186 entire testing interval, so we don't try to do 500 TLS's at once
5188 - Make the "stable" router flag in network-status be the median of
5189 the uptimes of running valid servers, and make clients pay
5190 attention to the network-status flags. Thus the cutoff adapts
5191 to the stability of the network as a whole, making IRC, IM, etc
5192 connections more reliable.
5193 - Make the v2 dir's "Fast" flag based on relative capacity, just
5194 like "Stable" is based on median uptime. Name everything in the
5195 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
5196 - Retry directory requests if we fail to get an answer we like
5197 from a given dirserver (we were retrying before, but only if
5198 we fail to connect).
5199 - Return a robots.txt on our dirport to discourage google indexing.
5201 o Controller protocol improvements:
5202 - Revised controller protocol (version 1) that uses ascii rather
5203 than binary: tor/doc/control-spec.txt. Add supporting libraries
5204 in python and java and c# so you can use the controller from your
5205 applications without caring how our protocol works.
5206 - Allow the DEBUG controller event to work again. Mark certain log
5207 entries as "don't tell this to controllers", so we avoid cycles.
5208 - New controller function "getinfo accounting", to ask how
5209 many bytes we've used in this time period.
5210 - Add a "resetconf" command so you can set config options like
5211 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
5212 a config option in the torrc with no value, then it clears it
5213 entirely (rather than setting it to its default).
5214 - Add a "getinfo config-file" to tell us where torrc is. Also
5215 expose guard nodes, config options/names.
5216 - Add a "quit" command (when when using the controller manually).
5217 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
5218 stop using any currently-dirty circuits for new streams, so we
5219 don't link new actions to old actions. This also occurs on HUP
5221 - If we would close a stream early (e.g. it asks for a .exit that
5222 we know would refuse it) but the LeaveStreamsUnattached config
5223 option is set by the controller, then don't close it.
5224 - Add a new controller event type "authdir_newdescs" that allows
5225 controllers to get all server descriptors that were uploaded to
5226 a router in its role as directory authority.
5227 - New controller option "getinfo desc/all-recent" to fetch the
5228 latest server descriptor for every router that Tor knows about.
5229 - Fix the controller's "attachstream 0" command to treat conn like
5230 it just connected, doing address remapping, handling .exit and
5231 .onion idioms, and so on. Now we're more uniform in making sure
5232 that the controller hears about new and closing connections.
5233 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
5234 the controller. Also, rotate dns and cpu workers if the controller
5235 changes options that will affect them; and initialize the dns
5236 worker cache tree whether or not we start out as a server.
5237 - Add a new circuit purpose 'controller' to let the controller ask
5238 for a circuit that Tor won't try to use. Extend the "extendcircuit"
5239 controller command to let you specify the purpose if you're starting
5240 a new circuit. Add a new "setcircuitpurpose" controller command to
5241 let you change a circuit's purpose after it's been created.
5242 - Let the controller ask for "getinfo dir/server/foo" so it can ask
5243 directly rather than connecting to the dir port. "getinfo
5244 dir/status/foo" also works, but currently only if your DirPort
5246 - Let the controller tell us about certain router descriptors
5247 that it doesn't want Tor to use in circuits. Implement
5248 "setrouterpurpose" and modify "+postdescriptor" to do this.
5249 - If the controller's *setconf commands fail, collect an error
5250 message in a string and hand it back to the controller -- don't
5251 just tell them to go read their logs.
5253 o Scalability, resource management, and performance:
5254 - Fix a major load balance bug: we were round-robin reading in 16 KB
5255 chunks, and servers with bandwidthrate of 20 KB, while downloading
5256 a 600 KB directory, would starve their other connections. Now we
5257 try to be a bit more fair.
5258 - Be more conservative about whether to advertise our DirPort.
5259 The main change is to not advertise if we're running at capacity
5260 and either a) we could hibernate ever or b) our capacity is low
5261 and we're using a default DirPort.
5262 - We weren't cannibalizing circuits correctly for
5263 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
5264 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
5265 build those from scratch. This should make hidden services faster.
5266 - Predict required circuits better, with an eye toward making hidden
5267 services faster on the service end.
5268 - Compress exit policies even more: look for duplicate lines and
5270 - Generate 18.0.0.0/8 address policy format in descs when we can;
5271 warn when the mask is not reducible to a bit-prefix.
5272 - There used to be two ways to specify your listening ports in a
5273 server descriptor: on the "router" line and with a separate "ports"
5274 line. Remove support for the "ports" line.
5275 - Reduce memory requirements in our structs by changing the order
5276 of fields. Replace balanced trees with hash tables. Inline
5277 bottleneck smartlist functions. Add a "Map from digest to void*"
5278 abstraction so we can do less hex encoding/decoding, and use it
5279 in router_get_by_digest(). Many other CPU and memory improvements.
5280 - Allow tor_gzip_uncompress to extract as much as possible from
5281 truncated compressed data. Try to extract as many
5282 descriptors as possible from truncated http responses (when
5283 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
5284 - Make circ->onionskin a pointer, not a static array. moria2 was using
5285 125000 circuit_t's after it had been up for a few weeks, which
5286 translates to 20+ megs of wasted space.
5287 - The private half of our EDH handshake keys are now chosen out
5288 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
5289 - Stop doing the complex voodoo overkill checking for insecure
5290 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
5291 - Do round-robin writes for TLS of at most 16 kB per write. This
5292 might be more fair on loaded Tor servers.
5293 - Do not use unaligned memory access on alpha, mips, or mipsel.
5294 It *works*, but is very slow, so we treat them as if it doesn't.
5296 o Other bugfixes and improvements:
5297 - Start storing useful information to $DATADIR/state, so we can
5298 remember things across invocations of Tor. Retain unrecognized
5299 lines so we can be forward-compatible, and write a TorVersion line
5300 so we can be backward-compatible.
5301 - If ORPort is set, Address is not explicitly set, and our hostname
5302 resolves to a private IP address, try to use an interface address
5303 if it has a public address. Now Windows machines that think of
5304 themselves as localhost can guess their address.
5305 - Regenerate our local descriptor if it's dirty and we try to use
5306 it locally (e.g. if it changes during reachability detection).
5307 This was causing some Tor servers to keep publishing the same
5308 initial descriptor forever.
5309 - Tor servers with dynamic IP addresses were needing to wait 18
5310 hours before they could start doing reachability testing using
5311 the new IP address and ports. This is because they were using
5312 the internal descriptor to learn what to test, yet they were only
5313 rebuilding the descriptor once they decided they were reachable.
5314 - It turns out we couldn't bootstrap a network since we added
5315 reachability detection in 0.1.0.1-rc. Good thing the Tor network
5316 has never gone down. Add an AssumeReachable config option to let
5317 servers and authorities bootstrap. When we're trying to build a
5318 high-uptime or high-bandwidth circuit but there aren't enough
5319 suitable servers, try being less picky rather than simply failing.
5320 - Newly bootstrapped Tor networks couldn't establish hidden service
5321 circuits until they had nodes with high uptime. Be more tolerant.
5322 - Really busy servers were keeping enough circuits open on stable
5323 connections that they were wrapping around the circuit_id
5324 space. (It's only two bytes.) This exposed a bug where we would
5325 feel free to reuse a circuit_id even if it still exists but has
5326 been marked for close. Try to fix this bug. Some bug remains.
5327 - When we fail to bind or listen on an incoming or outgoing
5328 socket, we now close it before refusing, rather than just
5329 leaking it. (Thanks to Peter Palfrader for finding.)
5330 - Fix a file descriptor leak in start_daemon().
5331 - On Windows, you can't always reopen a port right after you've
5332 closed it. So change retry_listeners() to only close and re-open
5333 ports that have changed.
5334 - Workaround a problem with some http proxies that refuse GET
5335 requests that specify "Content-Length: 0". Reported by Adrian.
5336 - Recover better from TCP connections to Tor servers that are
5337 broken but don't tell you (it happens!); and rotate TLS
5338 connections once a week.
5339 - Fix a scary-looking but apparently harmless bug where circuits
5340 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
5341 servers, and never switch to state CIRCUIT_STATE_OPEN.
5342 - Check for even more Windows version flags when writing the platform
5343 string in server descriptors, and note any we don't recognize.
5344 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
5345 get a better idea of why their circuits failed. Not used yet.
5346 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
5347 We don't use them yet, but maybe one day our DNS resolver will be
5348 able to discover them.
5349 - Let people type "tor --install" as well as "tor -install" when they
5350 want to make it an NT service.
5351 - Looks like we were never delivering deflated (i.e. compressed)
5352 running-routers lists, even when asked. Oops.
5353 - We were leaking some memory every time the client changed IPs.
5354 - Clean up more of the OpenSSL memory when exiting, so we can detect
5355 memory leaks better.
5356 - Never call free() on tor_malloc()d memory. This will help us
5357 use dmalloc to detect memory leaks.
5358 - Some Tor servers process billions of cells per day. These
5359 statistics are now uint64_t's.
5360 - Check [X-]Forwarded-For headers in HTTP requests when generating
5361 log messages. This lets people run dirservers (and caches) behind
5362 Apache but still know which IP addresses are causing warnings.
5363 - Fix minor integer overflow in calculating when we expect to use up
5364 our bandwidth allocation before hibernating.
5365 - Lower the minimum required number of file descriptors to 1000,
5366 so we can have some overhead for Valgrind on Linux, where the
5367 default ulimit -n is 1024.
5368 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
5369 and its existence is confusing some users.
5371 o Config option fixes:
5372 - Add a new config option ExitPolicyRejectPrivate which defaults
5373 to on. Now all exit policies will begin with rejecting private
5374 addresses, unless the server operator explicitly turns it off.
5375 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
5376 - Add new ReachableORAddresses and ReachableDirAddresses options
5377 that understand address policies. FascistFirewall is now a synonym
5378 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
5379 - Start calling it FooListenAddress rather than FooBindAddress,
5380 since few of our users know what it means to bind an address
5382 - If the user gave Tor an odd number of command-line arguments,
5383 we were silently ignoring the last one. Now we complain and fail.
5384 This wins the oldest-bug prize -- this bug has been present since
5385 November 2002, as released in Tor 0.0.0.
5386 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
5387 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
5388 it would silently ignore the 6668.
5389 - If we get a linelist or linelist_s config option from the torrc,
5390 e.g. ExitPolicy, and it has no value, warn and skip rather than
5391 silently resetting it to its default.
5392 - Setconf was appending items to linelists, not clearing them.
5393 - Add MyFamily to torrc.sample in the server section, so operators
5394 will be more likely to learn that it exists.
5395 - Make ContactInfo mandatory for authoritative directory servers.
5396 - MaxConn has been obsolete for a while now. Document the ConnLimit
5397 config option, which is a *minimum* number of file descriptors
5398 that must be available else Tor refuses to start.
5399 - Get rid of IgnoreVersion undocumented config option, and make us
5400 only warn, never exit, when we're running an obsolete version.
5401 - Make MonthlyAccountingStart config option truly obsolete now.
5402 - Correct the man page entry on TrackHostExitsExpire.
5403 - Let directory authorities start even if they don't specify an
5404 Address config option.
5405 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
5406 reflect the updated flags in our v2 dir protocol.
5408 o Config option features:
5409 - Add a new config option FastFirstHopPK (on by default) so clients
5410 do a trivial crypto handshake for their first hop, since TLS has
5411 already taken care of confidentiality and authentication.
5412 - Let the user set ControlListenAddress in the torrc. This can be
5413 dangerous, but there are some cases (like a secured LAN) where it
5415 - New config options to help controllers: FetchServerDescriptors
5416 and FetchHidServDescriptors for whether to fetch server
5417 info and hidserv info or let the controller do it, and
5418 PublishServerDescriptor and PublishHidServDescriptors.
5419 - Also let the controller set the __AllDirActionsPrivate config
5420 option if you want all directory fetches/publishes to happen via
5421 Tor (it assumes your controller bootstraps your circuits).
5422 - Add "HardwareAccel" config option: support for crypto hardware
5423 accelerators via OpenSSL. Off by default, until we find somebody
5424 smart who can test it for us. (It appears to produce seg faults
5425 in at least some cases.)
5426 - New config option "AuthDirRejectUnlisted" for directory authorities
5427 as a panic button: if we get flooded with unusable servers we can
5428 revert to only listing servers in the approved-routers file.
5429 - Directory authorities can now reject/invalidate by key and IP,
5430 with the config options "AuthDirInvalid" and "AuthDirReject", or
5431 by marking a fingerprint as "!reject" or "!invalid" (as its
5432 nickname) in the approved-routers file. This is useful since
5433 currently we automatically list servers as running and usable
5434 even if we know they're jerks.
5435 - Add a new config option TestSocks so people can see whether their
5436 applications are using socks4, socks4a, socks5-with-ip, or
5437 socks5-with-fqdn. This way they don't have to keep mucking
5438 with tcpdump and wondering if something got cached somewhere.
5439 - Add "private:*" as an alias in configuration for policies. Now
5440 you can simplify your exit policy rather than needing to list
5441 every single internal or nonroutable network space.
5442 - Accept "private:*" in routerdesc exit policies; not generated yet
5443 because older Tors do not understand it.
5444 - Add configuration option "V1AuthoritativeDirectory 1" which
5445 moria1, moria2, and tor26 have set.
5446 - Implement an option, VirtualAddrMask, to set which addresses
5447 get handed out in response to mapaddress requests. This works
5448 around a bug in tsocks where 127.0.0.0/8 is never socksified.
5449 - Add a new config option FetchUselessDescriptors, off by default,
5450 for when you plan to run "exitlist" on your client and you want
5451 to know about even the non-running descriptors.
5452 - SocksTimeout: How long do we let a socks connection wait
5453 unattached before we fail it?
5454 - CircuitBuildTimeout: Cull non-open circuits that were born
5455 at least this many seconds ago.
5456 - CircuitIdleTimeout: Cull open clean circuits that were born
5457 at least this many seconds ago.
5458 - New config option SafeSocks to reject all application connections
5459 using unsafe socks protocols. Defaults to off.
5461 o Improved and clearer log messages:
5462 - Reduce clutter in server logs. We're going to try to make
5463 them actually usable now. New config option ProtocolWarnings that
5464 lets you hear about how _other Tors_ are breaking the protocol. Off
5466 - Divide log messages into logging domains. Once we put some sort
5467 of interface on this, it will let people looking at more verbose
5468 log levels specify the topics they want to hear more about.
5469 - Log server fingerprint on startup, so new server operators don't
5470 have to go hunting around their filesystem for it.
5471 - Provide dire warnings to any users who set DirServer manually;
5472 move it out of torrc.sample and into torrc.complete.
5473 - Make the log message less scary when all the dirservers are
5474 temporarily unreachable.
5475 - When tor_socketpair() fails in Windows, give a reasonable
5476 Windows-style errno back.
5477 - Improve tor_gettimeofday() granularity on windows.
5478 - We were printing the number of idle dns workers incorrectly when
5480 - Handle duplicate lines in approved-routers files without warning.
5481 - We were whining about using socks4 or socks5-with-local-lookup
5482 even when it's an IP address in the "virtual" range we designed
5483 exactly for this case.
5484 - Check for named servers when looking them up by nickname;
5485 warn when we're calling a non-named server by its nickname;
5486 don't warn twice about the same name.
5487 - Downgrade the dirserver log messages when whining about
5489 - Correct "your server is reachable" log entries to indicate that
5490 it was self-testing that told us so.
5491 - If we're trying to be a Tor server and running Windows 95/98/ME
5492 as a server, explain that we'll likely crash.
5493 - Provide a more useful warn message when our onion queue gets full:
5494 the CPU is too slow or the exit policy is too liberal.
5495 - Don't warn when we receive a 503 from a dirserver/cache -- this
5496 will pave the way for them being able to refuse if they're busy.
5497 - When we fail to bind a listener, try to provide a more useful
5498 log message: e.g., "Is Tor already running?"
5499 - Only start testing reachability once we've established a
5500 circuit. This will make startup on dir authorities less noisy.
5501 - Don't try to upload hidden service descriptors until we have
5502 established a circuit.
5503 - Tor didn't warn when it failed to open a log file.
5504 - Warn when listening on a public address for socks. We suspect a
5505 lot of people are setting themselves up as open socks proxies,
5506 and they have no idea that jerks on the Internet are using them,
5507 since they simply proxy the traffic into the Tor network.
5508 - Give a useful message when people run Tor as the wrong user,
5509 rather than telling them to start chowning random directories.
5510 - Fix a harmless bug that was causing Tor servers to log
5511 "Got an end because of misc error, but we're not an AP. Closing."
5512 - Fix wrong log message when you add a "HiddenServiceNodes" config
5513 line without any HiddenServiceDir line (reported by Chris Thomas).
5514 - Directory authorities now stop whining so loudly about bad
5515 descriptors that they fetch from other dirservers. So when there's
5516 a log complaint, it's for sure from a freshly uploaded descriptor.
5517 - When logging via syslog, include the pid whenever we provide
5518 a log entry. Suggested by Todd Fries.
5519 - When we're shutting down and we do something like try to post a
5520 server descriptor or rendezvous descriptor, don't complain that
5521 we seem to be unreachable. Of course we are, we're shutting down.
5522 - Change log line for unreachability to explicitly suggest /etc/hosts
5523 as the culprit. Also make it clearer what IP address and ports we're
5524 testing for reachability.
5525 - Put quotes around user-supplied strings when logging so users are
5526 more likely to realize if they add bad characters (like quotes)
5528 - NT service patch from Matt Edman to improve error messages on Win32.
5531 Changes in version 0.1.0.17 - 2006-02-17
5532 o Crash bugfixes on 0.1.0.x:
5533 - When servers with a non-zero DirPort came out of hibernation,
5534 sometimes they would trigger an assert.
5536 o Other important bugfixes:
5537 - On platforms that don't have getrlimit (like Windows), we were
5538 artificially constraining ourselves to a max of 1024
5539 connections. Now just assume that we can handle as many as 15000
5540 connections. Hopefully this won't cause other problems.
5542 o Backported features:
5543 - When we're a server, a client asks for an old-style directory,
5544 and our write bucket is empty, don't give it to him. This way
5545 small servers can continue to serve the directory *sometimes*,
5546 without getting overloaded.
5547 - Whenever you get a 503 in response to a directory fetch, try
5548 once more. This will become important once servers start sending
5549 503's whenever they feel busy.
5550 - Fetch a new directory every 120 minutes, not every 40 minutes.
5551 Now that we have hundreds of thousands of users running the old
5552 directory algorithm, it's starting to hurt a lot.
5553 - Bump up the period for forcing a hidden service descriptor upload
5554 from 20 minutes to 1 hour.
5557 Changes in version 0.1.0.16 - 2006-01-02
5558 o Crash bugfixes on 0.1.0.x:
5559 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5560 corrupting the heap, losing FDs, or crashing when we need to resize
5561 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5562 - It turns out sparc64 platforms crash on unaligned memory access
5563 too -- so detect and avoid this.
5564 - Handle truncated compressed data correctly (by detecting it and
5566 - Fix possible-but-unlikely free(NULL) in control.c.
5567 - When we were closing connections, there was a rare case that
5568 stomped on memory, triggering seg faults and asserts.
5569 - Avoid potential infinite recursion when building a descriptor. (We
5570 don't know that it ever happened, but better to fix it anyway.)
5571 - We were neglecting to unlink marked circuits from soon-to-close OR
5572 connections, which caused some rare scribbling on freed memory.
5573 - Fix a memory stomping race bug when closing the joining point of two
5574 rendezvous circuits.
5575 - Fix an assert in time parsing found by Steven Murdoch.
5577 o Other bugfixes on 0.1.0.x:
5578 - When we're doing reachability testing, provide more useful log
5579 messages so the operator knows what to expect.
5580 - Do not check whether DirPort is reachable when we are suppressing
5581 advertising it because of hibernation.
5582 - When building with -static or on Solaris, we sometimes needed -ldl.
5583 - One of the dirservers (tor26) changed its IP address.
5584 - When we're deciding whether a stream has enough circuits around
5585 that can handle it, count the freshly dirty ones and not the ones
5586 that are so dirty they won't be able to handle it.
5587 - When we're expiring old circuits, we had a logic error that caused
5588 us to close new rendezvous circuits rather than old ones.
5589 - Give a more helpful log message when you try to change ORPort via
5590 the controller: you should upgrade Tor if you want that to work.
5591 - We were failing to parse Tor versions that start with "Tor ".
5592 - Tolerate faulty streams better: when a stream fails for reason
5593 exitpolicy, stop assuming that the router is lying about his exit
5594 policy. When a stream fails for reason misc, allow it to retry just
5595 as if it was resolvefailed. When a stream has failed three times,
5596 reset its failure count so we can try again and get all three tries.
5599 Changes in version 0.1.0.15 - 2005-09-23
5600 o Bugfixes on 0.1.0.x:
5601 - Reject ports 465 and 587 (spam targets) in default exit policy.
5602 - Don't crash when we don't have any spare file descriptors and we
5603 try to spawn a dns or cpu worker.
5604 - Get rid of IgnoreVersion undocumented config option, and make us
5605 only warn, never exit, when we're running an obsolete version.
5606 - Don't try to print a null string when your server finds itself to
5607 be unreachable and the Address config option is empty.
5608 - Make the numbers in read-history and write-history into uint64s,
5609 so they don't overflow and publish negatives in the descriptor.
5610 - Fix a minor memory leak in smartlist_string_remove().
5611 - We were only allowing ourselves to upload a server descriptor at
5612 most every 20 minutes, even if it changed earlier than that.
5613 - Clean up log entries that pointed to old URLs.
5616 Changes in version 0.1.0.14 - 2005-08-08
5617 o Bugfixes on 0.1.0.x:
5618 - Fix the other half of the bug with crypto handshakes
5620 - Fix an assert trigger if you send a 'signal term' via the
5621 controller when it's listening for 'event info' messages.
5624 Changes in version 0.1.0.13 - 2005-08-04
5625 o Bugfixes on 0.1.0.x:
5626 - Fix a critical bug in the security of our crypto handshakes.
5627 - Fix a size_t underflow in smartlist_join_strings2() that made
5628 it do bad things when you hand it an empty smartlist.
5629 - Fix Windows installer to ship Tor license (thanks to Aphex for
5630 pointing out this oversight) and put a link to the doc directory
5632 - Explicitly set no-unaligned-access for sparc: it turns out the
5633 new gcc's let you compile broken code, but that doesn't make it
5637 Changes in version 0.1.0.12 - 2005-07-18
5638 o New directory servers:
5639 - tor26 has changed IP address.
5641 o Bugfixes on 0.1.0.x:
5642 - Fix a possible double-free in tor_gzip_uncompress().
5643 - When --disable-threads is set, do not search for or link against
5645 - Don't trigger an assert if an authoritative directory server
5646 claims its dirport is 0.
5647 - Fix bug with removing Tor as an NT service: some people were
5648 getting "The service did not return an error." Thanks to Matt
5652 Changes in version 0.1.0.11 - 2005-06-30
5653 o Bugfixes on 0.1.0.x:
5654 - Fix major security bug: servers were disregarding their
5655 exit policies if clients behaved unexpectedly.
5656 - Make OS X init script check for missing argument, so we don't
5657 confuse users who invoke it incorrectly.
5658 - Fix a seg fault in "tor --hash-password foo".
5659 - The MAPADDRESS control command was broken.
5662 Changes in version 0.1.0.10 - 2005-06-14
5664 - Make NT services work and start on startup on Win32 (based on
5665 patch by Matt Edman). See the FAQ entry for details.
5666 - Make 'platform' string in descriptor more accurate for Win32
5667 servers, so it's not just "unknown platform".
5668 - REUSEADDR on normal platforms means you can rebind to the port
5669 right after somebody else has let it go. But REUSEADDR on Win32
5670 means you can bind to the port _even when somebody else already
5671 has it bound_! So, don't do that on Win32.
5672 - Clean up the log messages when starting on Win32 with no config
5674 - Allow seeding the RNG on Win32 even when you're not running as
5675 Administrator. If seeding the RNG on Win32 fails, quit.
5677 o Assert / crash bugs:
5678 - Refuse relay cells that claim to have a length larger than the
5679 maximum allowed. This prevents a potential attack that could read
5680 arbitrary memory (e.g. keys) from an exit server's process
5682 - If unofficial Tor clients connect and send weird TLS certs, our
5683 Tor server triggers an assert. Stop asserting, and start handling
5684 TLS errors better in other situations too.
5685 - Fix a race condition that can trigger an assert when we have a
5686 pending create cell and an OR connection attempt fails.
5689 - Use pthreads for worker processes rather than forking. This was
5690 forced because when we forked, we ended up wasting a lot of
5691 duplicate ram over time.
5692 - Also switch to foo_r versions of some library calls to allow
5693 reentry and threadsafeness.
5694 - Implement --disable-threads configure option. Disable threads on
5695 netbsd and openbsd by default, because they have no reentrant
5696 resolver functions (!), and on solaris since it has other
5698 - Fix possible bug on threading platforms (e.g. win32) which was
5699 leaking a file descriptor whenever a cpuworker or dnsworker died.
5700 - Fix a minor memory leak when somebody establishes an introduction
5701 point at your Tor server.
5702 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
5704 - Add ./configure --with-dmalloc option, to track memory leaks.
5705 - And try to free all memory on closing, so we can detect what
5708 o Protocol correctness:
5709 - When we've connected to an OR and handshaked but didn't like
5710 the result, we were closing the conn without sending destroy
5711 cells back for pending circuits. Now send those destroys.
5712 - Start sending 'truncated' cells back rather than destroy cells
5713 if the circuit closes in front of you. This means we won't have
5714 to abandon partially built circuits.
5715 - Handle changed router status correctly when dirserver reloads
5716 fingerprint file. We used to be dropping all unverified descriptors
5717 right then. The bug was hidden because we would immediately
5718 fetch a directory from another dirserver, which would include the
5719 descriptors we just dropped.
5720 - Revise tor-spec to add more/better stream end reasons.
5721 - Revise all calls to connection_edge_end to avoid sending 'misc',
5722 and to take errno into account where possible.
5723 - Client now retries when streams end early for 'hibernating' or
5724 'resource limit' reasons, rather than failing them.
5725 - Try to be more zealous about calling connection_edge_end when
5726 things go bad with edge conns in connection.c.
5728 o Robustness improvements:
5729 - Better handling for heterogeneous / unreliable nodes:
5730 - Annotate circuits with whether they aim to contain high uptime
5731 nodes and/or high capacity nodes. When building circuits, choose
5733 - This means that every single node in an intro rend circuit,
5734 not just the last one, will have a minimum uptime.
5735 - New config option LongLivedPorts to indicate application streams
5736 that will want high uptime circuits.
5737 - Servers reset uptime when a dir fetch entirely fails. This
5738 hopefully reflects stability of the server's network connectivity.
5739 - If somebody starts his tor server in Jan 2004 and then fixes his
5740 clock, don't make his published uptime be a year.
5741 - Reset published uptime when we wake up from hibernation.
5742 - Introduce a notion of 'internal' circs, which are chosen without
5743 regard to the exit policy of the last hop. Intro and rendezvous
5744 circs must be internal circs, to avoid leaking information. Resolve
5745 and connect streams can use internal circs if they want.
5746 - New circuit pooling algorithm: keep track of what destination ports
5747 we've used recently (start out assuming we'll want to use 80), and
5748 make sure to have enough circs around to satisfy these ports. Also
5749 make sure to have 2 internal circs around if we've required internal
5750 circs lately (and with high uptime if we've seen that lately too).
5751 - Turn addr_policy_compare from a tristate to a quadstate; this should
5752 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
5753 for google.com" problem.
5754 - When a client asks us for a dir mirror and we don't have one,
5755 launch an attempt to get a fresh one.
5756 - First cut at support for "create-fast" cells. Clients can use
5757 these when extending to their first hop, since the TLS already
5758 provides forward secrecy and authentication. Not enabled on
5761 o Reachability testing.
5762 - Your Tor server will automatically try to see if its ORPort and
5763 DirPort are reachable from the outside, and it won't upload its
5764 descriptor until it decides at least ORPort is reachable (when
5765 DirPort is not yet found reachable, publish it as zero).
5766 - When building testing circs for ORPort testing, use only
5767 high-bandwidth nodes, so fewer circuits fail.
5768 - Notice when our IP changes, and reset stats/uptime/reachability.
5769 - Authdirservers don't do ORPort reachability detection, since
5770 they're in clique mode, so it will be rare to find a server not
5771 already connected to them.
5772 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
5776 - Now we allow two unverified servers with the same nickname
5777 but different keys. But if a nickname is verified, only that
5778 nickname+key are allowed.
5779 - If you're an authdirserver connecting to an address:port,
5780 and it's not the OR you were expecting, forget about that
5781 descriptor. If he *was* the one you were expecting, then forget
5782 about all other descriptors for that address:port.
5783 - Allow servers to publish descriptors from 12 hours in the future.
5784 Corollary: only whine about clock skew from the dirserver if
5785 he's a trusted dirserver (since now even verified servers could
5786 have quite wrong clocks).
5787 - Require servers that use the default dirservers to have public IP
5788 addresses. We have too many servers that are configured with private
5789 IPs and their admins never notice the log entries complaining that
5790 their descriptors are being rejected.
5792 o Efficiency improvements:
5793 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
5794 and /dev/poll), and hopefully work better on Windows too.
5795 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
5796 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
5797 - Find libevent even if it's hiding in /usr/local/ and your
5798 CFLAGS and LDFLAGS don't tell you to look there.
5799 - Be able to link with libevent as a shared library (the default
5800 after 1.0d), even if it's hiding in /usr/local/lib and even
5801 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
5802 assuming you're running gcc. Otherwise fail and give a useful
5804 - Switch to a new buffer management algorithm, which tries to avoid
5805 reallocing and copying quite as much. In first tests it looks like
5806 it uses *more* memory on average, but less cpu.
5807 - Switch our internal buffers implementation to use a ring buffer,
5808 to hopefully improve performance for fast servers a lot.
5809 - Reenable the part of the code that tries to flush as soon as an
5810 OR outbuf has a full TLS record available. Perhaps this will make
5811 OR outbufs not grow as huge except in rare cases, thus saving lots
5812 of CPU time plus memory.
5813 - Improve performance for dirservers: stop re-parsing the whole
5814 directory every time you regenerate it.
5815 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
5816 it much faster to look up a circuit for each relay cell.
5817 - Remove most calls to assert_all_pending_dns_resolves_ok(),
5818 since they're eating our cpu on exit nodes.
5819 - Stop wasting time doing a case insensitive comparison for every
5820 dns name every time we do any lookup. Canonicalize the names to
5821 lowercase when you first see them.
5824 - Handle unavailable hidden services better. Handle slow or busy
5825 hidden services better.
5826 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
5827 circ as necessary, if there are any completed ones lying around
5828 when we try to launch one.
5829 - Make hidden services try to establish a rendezvous for 30 seconds
5830 after fetching the descriptor, rather than for n (where n=3)
5831 attempts to build a circuit.
5832 - Adjust maximum skew and age for rendezvous descriptors: let skew
5833 be 48 hours rather than 90 minutes.
5834 - Reject malformed .onion addresses rather then passing them on as
5835 normal web requests.
5838 - More Tor controller support. See
5839 http://tor.eff.org/doc/control-spec.txt for all the new features,
5840 including signals to emulate unix signals from any platform;
5841 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
5842 closestream; closecircuit; etc.
5843 - Encode hashed controller passwords in hex instead of base64,
5844 to make it easier to write controllers.
5845 - Revise control spec and implementation to allow all log messages to
5846 be sent to controller with their severities intact (suggested by
5847 Matt Edman). Disable debug-level logs while delivering a debug-level
5848 log to the controller, to prevent loop. Update TorControl to handle
5849 new log event types.
5851 o New config options/defaults:
5852 - Begin scrubbing sensitive strings from logs by default. Turn off
5853 the config option SafeLogging if you need to do debugging.
5854 - New exit policy: accept most low-numbered ports, rather than
5855 rejecting most low-numbered ports.
5856 - Put a note in the torrc about abuse potential with the default
5858 - Add support for CONNECTing through https proxies, with "HttpsProxy"
5860 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
5861 based on patch from Adam Langley (basic auth only).
5862 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
5863 the fast servers that have been joining lately. (Clients are now
5864 willing to load balance over up to 2 MB of advertised bandwidth
5866 - New config option MaxAdvertisedBandwidth which lets you advertise
5867 a low bandwidthrate (to not attract as many circuits) while still
5868 allowing a higher bandwidthrate in reality.
5869 - Require BandwidthRate to be at least 20kB/s for servers.
5870 - Add a NoPublish config option, so you can be a server (e.g. for
5871 testing running Tor servers in other Tor networks) without
5872 publishing your descriptor to the primary dirservers.
5873 - Add a new AddressMap config directive to rewrite incoming socks
5874 addresses. This lets you, for example, declare an implicit
5875 required exit node for certain sites.
5876 - Add a new TrackHostExits config directive to trigger addressmaps
5877 for certain incoming socks addresses -- for sites that break when
5878 your exit keeps changing (based on patch from Mike Perry).
5879 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
5880 which describes how often we retry making new circuits if current
5881 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
5882 how long we're willing to make use of an already-dirty circuit.
5883 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
5884 a config option "ShutdownWaitLength" (when using kill -INT on
5886 - Fix an edge case in parsing config options: if they say "--"
5887 on the commandline, it's not a config option (thanks weasel).
5888 - New config option DirAllowPrivateAddresses for authdirservers.
5889 Now by default they refuse router descriptors that have non-IP or
5890 private-IP addresses.
5891 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
5892 smart" default value: low for servers and high for clients.
5893 - Some people were putting "Address " in their torrc, and they had
5894 a buggy resolver that resolved " " to 0.0.0.0. Oops.
5895 - If DataDir is ~/.tor, and that expands to /.tor, then default to
5896 LOCALSTATEDIR/tor instead.
5897 - Implement --verify-config command-line option to check if your torrc
5898 is valid without actually launching Tor.
5900 o Logging improvements:
5901 - When dirservers refuse a server descriptor, we now log its
5902 contactinfo, platform, and the poster's IP address.
5903 - Only warn once per nickname from add_nickname_list_to_smartlist()
5904 per failure, so an entrynode or exitnode choice that's down won't
5906 - When we're connecting to an OR and he's got a different nickname/key
5907 than we were expecting, only complain loudly if we're an OP or a
5908 dirserver. Complaining loudly to the OR admins just confuses them.
5909 - Whine at you if you're a server and you don't set your contactinfo.
5910 - Warn when exit policy implicitly allows local addresses.
5911 - Give a better warning when some other server advertises an
5912 ORPort that is actually an apache running ssl.
5913 - If we get an incredibly skewed timestamp from a dirserver mirror
5914 that isn't a verified OR, don't warn -- it's probably him that's
5916 - When a dirserver causes you to give a warn, mention which dirserver
5918 - Initialize libevent later in the startup process, so the logs are
5919 already established by the time we start logging libevent warns.
5920 - Use correct errno on win32 if libevent fails.
5921 - Check and warn about known-bad/slow libevent versions.
5922 - Stop warning about sigpipes in the logs. We're going to
5923 pretend that getting these occassionally is normal and fine.
5925 o New contrib scripts:
5926 - New experimental script tor/contrib/exitlist: a simple python
5927 script to parse directories and find Tor nodes that exit to listed
5929 - New experimental script tor/contrib/ExerciseServer.py (needs more
5930 work) that uses the controller interface to build circuits and
5931 fetch pages over them. This will help us bootstrap servers that
5932 have lots of capacity but haven't noticed it yet.
5933 - New experimental script tor/contrib/PathDemo.py (needs more work)
5934 that uses the controller interface to let you choose whole paths
5936 "<hostname>.<path,separated by dots>.<length of path>.path"
5937 - New contributed script "privoxy-tor-toggle" to toggle whether
5938 Privoxy uses Tor. Seems to be configured for Debian by default.
5939 - Have torctl.in/tor.sh.in check for location of su binary (needed
5943 - chdir() to your datadirectory at the *end* of the daemonize process,
5944 not the beginning. This was a problem because the first time you
5945 run tor, if your datadir isn't there, and you have runasdaemon set
5946 to 1, it will try to chdir to it before it tries to create it. Oops.
5947 - Fix several double-mark-for-close bugs, e.g. where we were finding
5948 a conn for a cell even if that conn is already marked for close.
5949 - Stop most cases of hanging up on a socks connection without sending
5951 - Fix a bug in the RPM package: set home directory for _tor to
5952 something more reasonable when first installing.
5953 - Stop putting nodename in the Platform string in server descriptors.
5954 It doesn't actually help, and it is confusing/upsetting some people.
5955 - When using preferred entry or exit nodes, ignore whether the
5956 circuit wants uptime or capacity. They asked for the nodes, they
5958 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
5959 artificially capped at 500kB.
5960 - Cache local dns resolves correctly even when they're .exit
5962 - If we're hibernating and we get a SIGINT, exit immediately.
5963 - tor-resolve requests were ignoring .exit if there was a working circuit
5964 they could use instead.
5965 - Pay more attention to the ClientOnly config option.
5966 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
5967 installer screens; and don't put stuff into StartupItems unless
5968 the user asks you to.
5971 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
5972 rather than just rejecting it.
5973 - If our clock jumps forward by 100 seconds or more, assume something
5974 has gone wrong with our network and abandon all not-yet-used circs.
5975 - When an application is using socks5, give him the whole variety of
5976 potential socks5 responses (connect refused, host unreachable, etc),
5977 rather than just "success" or "failure".
5978 - A more sane version numbering system. See
5979 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
5980 - Change version parsing logic: a version is "obsolete" if it is not
5981 recommended and (1) there is a newer recommended version in the
5982 same series, or (2) there are no recommended versions in the same
5983 series, but there are some recommended versions in a newer series.
5984 A version is "new" if it is newer than any recommended version in
5986 - Report HTTP reasons to client when getting a response from directory
5987 servers -- so you can actually know what went wrong.
5988 - Reject odd-looking addresses at the client (e.g. addresses that
5989 contain a colon), rather than having the server drop them because
5991 - Stop publishing socksport in the directory, since it's not
5992 actually meant to be public. For compatibility, publish a 0 there
5994 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
5995 cookies to disk and doesn't log each web request to disk. (Thanks
5996 to Brett Carrington for pointing this out.)
5997 - Add OSX uninstall instructions. An actual uninstall script will
5999 - Add "opt hibernating 1" to server descriptor to make it clearer
6000 whether the server is hibernating.
6003 Changes in version 0.0.9.10 - 2005-06-16
6004 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
6005 - Refuse relay cells that claim to have a length larger than the
6006 maximum allowed. This prevents a potential attack that could read
6007 arbitrary memory (e.g. keys) from an exit server's process
6011 Changes in version 0.0.9.9 - 2005-04-23
6012 o Bugfixes on 0.0.9.x:
6013 - If unofficial Tor clients connect and send weird TLS certs, our
6014 Tor server triggers an assert. This release contains a minimal
6015 backport from the broader fix that we put into 0.1.0.4-rc.
6018 Changes in version 0.0.9.8 - 2005-04-07
6019 o Bugfixes on 0.0.9.x:
6020 - We have a bug that I haven't found yet. Sometimes, very rarely,
6021 cpuworkers get stuck in the 'busy' state, even though the cpuworker
6022 thinks of itself as idle. This meant that no new circuits ever got
6023 established. Here's a workaround to kill any cpuworker that's been
6024 busy for more than 100 seconds.
6027 Changes in version 0.0.9.7 - 2005-04-01
6028 o Bugfixes on 0.0.9.x:
6029 - Fix another race crash bug (thanks to Glenn Fink for reporting).
6030 - Compare identity to identity, not to nickname, when extending to
6031 a router not already in the directory. This was preventing us from
6032 extending to unknown routers. Oops.
6033 - Make sure to create OS X Tor user in <500 range, so we aren't
6034 creating actual system users.
6035 - Note where connection-that-hasn't-sent-end was marked, and fix
6036 a few really loud instances of this harmless bug (it's fixed more
6040 Changes in version 0.0.9.6 - 2005-03-24
6041 o Bugfixes on 0.0.9.x (crashes and asserts):
6042 - Add new end stream reasons to maintainance branch. Fix bug where
6043 reason (8) could trigger an assert. Prevent bug from recurring.
6044 - Apparently win32 stat wants paths to not end with a slash.
6045 - Fix assert triggers in assert_cpath_layer_ok(), where we were
6046 blowing away the circuit that conn->cpath_layer points to, then
6047 checking to see if the circ is well-formed. Backport check to make
6048 sure we dont use the cpath on a closed connection.
6049 - Prevent circuit_resume_edge_reading_helper() from trying to package
6050 inbufs for marked-for-close streams.
6051 - Don't crash on hup if your options->address has become unresolvable.
6052 - Some systems (like OS X) sometimes accept() a connection and tell
6053 you the remote host is 0.0.0.0:0. If this happens, due to some
6054 other mis-features, we get confused; so refuse the conn for now.
6056 o Bugfixes on 0.0.9.x (other):
6057 - Fix harmless but scary "Unrecognized content encoding" warn message.
6058 - Add new stream error reason: TORPROTOCOL reason means "you are not
6059 speaking a version of Tor I understand; say bye-bye to your stream."
6060 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
6061 into the future, now that we are more tolerant of skew. This
6062 resolves a bug where a Tor server would refuse to cache a directory
6063 because all the directories it gets are too far in the future;
6064 yet the Tor server never logs any complaints about clock skew.
6065 - Mac packaging magic: make man pages useable, and do not overwrite
6066 existing torrc files.
6067 - Make OS X log happily to /var/log/tor/tor.log
6070 Changes in version 0.0.9.5 - 2005-02-22
6071 o Bugfixes on 0.0.9.x:
6072 - Fix an assert race at exit nodes when resolve requests fail.
6073 - Stop picking unverified dir mirrors--it only leads to misery.
6074 - Patch from Matt Edman to make NT services work better. Service
6075 support is still not compiled into the executable by default.
6076 - Patch from Dmitri Bely so the Tor service runs better under
6077 the win32 SYSTEM account.
6078 - Make tor-resolve actually work (?) on Win32.
6079 - Fix a sign bug when getrlimit claims to have 4+ billion
6080 file descriptors available.
6081 - Stop refusing to start when bandwidthburst == bandwidthrate.
6082 - When create cells have been on the onion queue more than five
6083 seconds, just send back a destroy and take them off the list.
6086 Changes in version 0.0.9.4 - 2005-02-03
6087 o Bugfixes on 0.0.9:
6088 - Fix an assert bug that took down most of our servers: when
6089 a server claims to have 1 GB of bandwidthburst, don't
6091 - Don't crash as badly if we have spawned the max allowed number
6092 of dnsworkers, or we're out of file descriptors.
6093 - Block more file-sharing ports in the default exit policy.
6094 - MaxConn is now automatically set to the hard limit of max
6095 file descriptors we're allowed (ulimit -n), minus a few for
6097 - Give a clearer message when servers need to raise their
6098 ulimit -n when they start running out of file descriptors.
6099 - SGI Compatibility patches from Jan Schaumann.
6100 - Tolerate a corrupt cached directory better.
6101 - When a dirserver hasn't approved your server, list which one.
6102 - Go into soft hibernation after 95% of the bandwidth is used,
6103 not 99%. This is especially important for daily hibernators who
6104 have a small accounting max. Hopefully it will result in fewer
6105 cut connections when the hard hibernation starts.
6106 - Load-balance better when using servers that claim more than
6107 800kB/s of capacity.
6108 - Make NT services work (experimental, only used if compiled in).
6111 Changes in version 0.0.9.3 - 2005-01-21
6112 o Bugfixes on 0.0.9:
6113 - Backport the cpu use fixes from main branch, so busy servers won't
6114 need as much processor time.
6115 - Work better when we go offline and then come back, or when we
6116 run Tor at boot before the network is up. We do this by
6117 optimistically trying to fetch a new directory whenever an
6118 application request comes in and we think we're offline -- the
6119 human is hopefully a good measure of when the network is back.
6120 - Backport some minimal hidserv bugfixes: keep rend circuits open as
6121 long as you keep using them; actually publish hidserv descriptors
6122 shortly after they change, rather than waiting 20-40 minutes.
6123 - Enable Mac startup script by default.
6124 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
6125 - When you update AllowUnverifiedNodes or FirewallPorts via the
6126 controller's setconf feature, we were always appending, never
6128 - When you update HiddenServiceDir via setconf, it was screwing up
6129 the order of reading the lines, making it fail.
6130 - Do not rewrite a cached directory back to the cache; otherwise we
6131 will think it is recent and not fetch a newer one on startup.
6132 - Workaround for webservers that lie about Content-Encoding: Tor
6133 now tries to autodetect compressed directories and compression
6134 itself. This lets us Proxypass dir fetches through apache.
6137 Changes in version 0.0.9.2 - 2005-01-04
6138 o Bugfixes on 0.0.9 (crashes and asserts):
6139 - Fix an assert on startup when the disk is full and you're logging
6141 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
6142 style address, then we'd crash.
6143 - Fix an assert trigger when the running-routers string we get from
6144 a dirserver is broken.
6145 - Make worker threads start and run on win32. Now win32 servers
6147 - Bandaid (not actually fix, but now it doesn't crash) an assert
6148 where the dns worker dies mysteriously and the main Tor process
6149 doesn't remember anything about the address it was resolving.
6151 o Bugfixes on 0.0.9 (Win32):
6152 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
6153 name out of the warning/assert messages.
6154 - Fix a superficial "unhandled error on read" bug on win32.
6155 - The win32 installer no longer requires a click-through for our
6156 license, since our Free Software license grants rights but does not
6158 - Win32: When connecting to a dirserver fails, try another one
6159 immediately. (This was already working for non-win32 Tors.)
6160 - Stop trying to parse $HOME on win32 when hunting for default
6162 - Make tor-resolve.c work on win32 by calling network_init().
6164 o Bugfixes on 0.0.9 (other):
6165 - Make 0.0.9.x build on Solaris again.
6166 - Due to a fencepost error, we were blowing away the \n when reporting
6167 confvalue items in the controller. So asking for multiple config
6168 values at once couldn't work.
6169 - When listing circuits that are pending on an opening OR connection,
6170 if we're an OR we were listing circuits that *end* at us as
6171 being pending on every listener, dns/cpu worker, etc. Stop that.
6172 - Dirservers were failing to create 'running-routers' or 'directory'
6173 strings if we had more than some threshold of routers. Fix them so
6174 they can handle any number of routers.
6175 - Fix a superficial "Duplicate mark for close" bug.
6176 - Stop checking for clock skew for OR connections, even for servers.
6177 - Fix a fencepost error that was chopping off the last letter of any
6178 nickname that is the maximum allowed nickname length.
6179 - Update URLs in log messages so they point to the new website.
6180 - Fix a potential problem in mangling server private keys while
6181 writing to disk (not triggered yet, as far as we know).
6182 - Include the licenses for other free software we include in Tor,
6183 now that we're shipping binary distributions more regularly.
6186 Changes in version 0.0.9.1 - 2004-12-15
6187 o Bugfixes on 0.0.9:
6188 - Make hibernation actually work.
6189 - Make HashedControlPassword config option work.
6190 - When we're reporting event circuit status to a controller,
6191 don't use the stream status code.
6194 Changes in version 0.0.9 - 2004-12-12
6195 o Bugfixes on 0.0.8.1 (Crashes and asserts):
6196 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
6197 write() call will fail and we handle it there.
6198 - When we run out of disk space, or other log writing error, don't
6199 crash. Just stop logging to that log and continue.
6200 - Fix isspace() and friends so they still make Solaris happy
6201 but also so they don't trigger asserts on win32.
6202 - Fix assert failure on malformed socks4a requests.
6203 - Fix an assert bug where a hidden service provider would fail if
6204 the first hop of his rendezvous circuit was down.
6205 - Better handling of size_t vs int, so we're more robust on 64
6208 o Bugfixes on 0.0.8.1 (Win32):
6209 - Make windows sockets actually non-blocking (oops), and handle
6210 win32 socket errors better.
6211 - Fix parse_iso_time on platforms without strptime (eg win32).
6212 - win32: when being multithreaded, leave parent fdarray open.
6213 - Better handling of winsock includes on non-MSV win32 compilers.
6214 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
6216 - Make unit tests work on win32.
6218 o Bugfixes on 0.0.8.1 (Path selection and streams):
6219 - Calculate timeout for waiting for a connected cell from the time
6220 we sent the begin cell, not from the time the stream started. If
6221 it took a long time to establish the circuit, we would time out
6222 right after sending the begin cell.
6223 - Fix router_compare_addr_to_addr_policy: it was not treating a port
6224 of * as always matching, so we were picking reject *:* nodes as
6225 exit nodes too. Oops.
6226 - When read() failed on a stream, we would close it without sending
6227 back an end. So 'connection refused' would simply be ignored and
6228 the user would get no response.
6229 - Stop a sigpipe: when an 'end' cell races with eof from the app,
6230 we shouldn't hold-open-until-flush if the eof arrived first.
6231 - Let resolve conns retry/expire also, rather than sticking around
6233 - Fix more dns related bugs: send back resolve_failed and end cells
6234 more reliably when the resolve fails, rather than closing the
6235 circuit and then trying to send the cell. Also attach dummy resolve
6236 connections to a circuit *before* calling dns_resolve(), to fix
6237 a bug where cached answers would never be sent in RESOLVED cells.
6239 o Bugfixes on 0.0.8.1 (Circuits):
6240 - Finally fix a bug that's been plaguing us for a year:
6241 With high load, circuit package window was reaching 0. Whenever
6242 we got a circuit-level sendme, we were reading a lot on each
6243 socket, but only writing out a bit. So we would eventually reach
6244 eof. This would be noticed and acted on even when there were still
6245 bytes sitting in the inbuf.
6246 - Use identity comparison, not nickname comparison, to choose which
6247 half of circuit-ID-space each side gets to use. This is needed
6248 because sometimes we think of a router as a nickname, and sometimes
6249 as a hex ID, and we can't predict what the other side will do.
6251 o Bugfixes on 0.0.8.1 (Other):
6252 - Fix a whole slew of memory leaks.
6253 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
6254 - If we are using select, make sure we stay within FD_SETSIZE.
6255 - When poll() is interrupted, we shouldn't believe the revents values.
6256 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
6257 and smartlist_len, which are two major profiling offenders.
6258 - If do_hup fails, actually notice.
6259 - Flush the log file descriptor after we print "Tor opening log file",
6260 so we don't see those messages days later.
6261 - Hidden service operators now correctly handle version 1 style
6262 INTRODUCE1 cells (nobody generates them still, so not a critical
6264 - Handle more errnos from accept() without closing the listener.
6265 Some OpenBSD machines were closing their listeners because
6266 they ran out of file descriptors.
6267 - Some people had wrapped their tor client/server in a script
6268 that would restart it whenever it died. This did not play well
6269 with our "shut down if your version is obsolete" code. Now people
6270 don't fetch a new directory if their local cached version is
6272 - Make our autogen.sh work on ksh as well as bash.
6273 - Better torrc example lines for dirbindaddress and orbindaddress.
6274 - Improved bounds checking on parsed ints (e.g. config options and
6275 the ones we find in directories.)
6276 - Stop using separate defaults for no-config-file and
6277 empty-config-file. Now you have to explicitly turn off SocksPort,
6278 if you don't want it open.
6279 - We were starting to daemonize before we opened our logs, so if
6280 there were any problems opening logs, we would complain to stderr,
6281 which wouldn't work, and then mysteriously exit.
6282 - If a verified OR connects to us before he's uploaded his descriptor,
6283 or we verify him and hup but he still has the original TLS
6284 connection, then conn->nickname is still set like he's unverified.
6286 o Code security improvements, inspired by Ilja:
6287 - tor_snprintf wrapper over snprintf with consistent (though not C99)
6289 - Replace sprintf with tor_snprintf. (I think they were all safe, but
6291 - Replace strcpy/strncpy with strlcpy in more places.
6292 - Avoid strcat; use tor_snprintf or strlcat instead.
6294 o Features (circuits and streams):
6295 - New circuit building strategy: keep a list of ports that we've
6296 used in the past 6 hours, and always try to have 2 circuits open
6297 or on the way that will handle each such port. Seed us with port
6298 80 so web users won't complain that Tor is "slow to start up".
6299 - Make kill -USR1 dump more useful stats about circuits.
6300 - When warning about retrying or giving up, print the address, so
6301 the user knows which one it's talking about.
6302 - If you haven't used a clean circuit in an hour, throw it away,
6303 just to be on the safe side. (This means after 6 hours a totally
6304 unused Tor client will have no circuits open.)
6305 - Support "foo.nickname.exit" addresses, to let Alice request the
6306 address "foo" as viewed by exit node "nickname". Based on a patch
6308 - If your requested entry or exit node has advertised bandwidth 0,
6310 - Be more greedy about filling up relay cells -- we try reading again
6311 once we've processed the stuff we read, in case enough has arrived
6312 to fill the last cell completely.
6313 - Refuse application socks connections to port 0.
6314 - Use only 0.0.9pre1 and later servers for resolve cells.
6316 o Features (bandwidth):
6317 - Hibernation: New config option "AccountingMax" lets you
6318 set how many bytes per month (in each direction) you want to
6319 allow your server to consume. Rather than spreading those
6320 bytes out evenly over the month, we instead hibernate for some
6321 of the month and pop up at a deterministic time, work until
6322 the bytes are consumed, then hibernate again. Config option
6323 "MonthlyAccountingStart" lets you specify which day of the month
6324 your billing cycle starts on.
6325 - Implement weekly/monthly/daily accounting: now you specify your
6326 hibernation properties by
6327 AccountingMax N bytes|KB|MB|GB|TB
6328 AccountingStart day|week|month [day] HH:MM
6329 Defaults to "month 1 0:00".
6330 - Let bandwidth and interval config options be specified as 5 bytes,
6331 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
6333 o Features (directories):
6334 - New "router-status" line in directory, to better bind each verified
6335 nickname to its identity key.
6336 - Clients can ask dirservers for /dir.z to get a compressed version
6337 of the directory. Only works for servers running 0.0.9, of course.
6338 - Make clients cache directories and use them to seed their router
6339 lists at startup. This means clients have a datadir again.
6340 - Respond to content-encoding headers by trying to uncompress as
6342 - Clients and servers now fetch running-routers; cache
6343 running-routers; compress running-routers; serve compressed
6345 - Make moria2 advertise a dirport of 80, so people behind firewalls
6346 will be able to get a directory.
6347 - Http proxy support
6348 - Dirservers translate requests for http://%s:%d/x to /x
6349 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
6350 be routed through this host.
6351 - Clients ask for /tor/x rather than /x for new enough dirservers.
6352 This way we can one day coexist peacefully with apache.
6353 - Clients specify a "Host: %s%d" http header, to be compatible
6354 with more proxies, and so running squid on an exit node can work.
6355 - Protect dirservers from overzealous descriptor uploading -- wait
6356 10 seconds after directory gets dirty, before regenerating.
6358 o Features (packages and install):
6359 - Add NSI installer contributed by J Doe.
6360 - Apply NT service patch from Osamu Fujino. Still needs more work.
6361 - Commit VC6 and VC7 workspace/project files.
6362 - Commit a tor.spec for making RPM files, with help from jbash.
6363 - Add contrib/torctl.in contributed by Glenn Fink.
6364 - Make expand_filename handle ~ and ~username.
6365 - Use autoconf to enable largefile support where necessary. Use
6366 ftello where available, since ftell can fail at 2GB.
6367 - Ship src/win32/ in the tarball, so people can use it to build.
6368 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
6371 o Features (ui controller):
6372 - Control interface: a separate program can now talk to your
6373 client/server over a socket, and get/set config options, receive
6374 notifications of circuits and streams starting/finishing/dying,
6375 bandwidth used, etc. The next step is to get some GUIs working.
6376 Let us know if you want to help out. See doc/control-spec.txt .
6377 - Ship a contrib/tor-control.py as an example script to interact
6378 with the control port.
6379 - "tor --hash-password zzyxz" will output a salted password for
6380 use in authenticating to the control interface.
6381 - Implement the control-spec's SAVECONF command, to write your
6382 configuration to torrc.
6383 - Get cookie authentication for the controller closer to working.
6384 - When set_conf changes our server descriptor, upload a new copy.
6385 But don't upload it too often if there are frequent changes.
6387 o Features (config and command-line):
6388 - Deprecate unofficial config option abbreviations, and abbreviations
6389 not on the command line.
6390 - Configuration infrastructure support for warning on obsolete
6392 - Give a slightly more useful output for "tor -h".
6393 - Break DirFetchPostPeriod into:
6394 - DirFetchPeriod for fetching full directory,
6395 - StatusFetchPeriod for fetching running-routers,
6396 - DirPostPeriod for posting server descriptor,
6397 - RendPostPeriod for posting hidden service descriptors.
6398 - New log format in config:
6399 "Log minsev[-maxsev] stdout|stderr|syslog" or
6400 "Log minsev[-maxsev] file /var/foo"
6401 - DirPolicy config option, to let people reject incoming addresses
6402 from their dirserver.
6403 - "tor --list-fingerprint" will list your identity key fingerprint
6405 - Make tor --version --version dump the cvs Id of every file.
6406 - New 'MyFamily nick1,...' config option for a server to
6407 specify other servers that shouldn't be used in the same circuit
6408 with it. Only believed if nick1 also specifies us.
6409 - New 'NodeFamily nick1,nick2,...' config option for a client to
6410 specify nodes that it doesn't want to use in the same circuit.
6411 - New 'Redirectexit pattern address:port' config option for a
6412 server to redirect exit connections, e.g. to a local squid.
6413 - Add "pass" target for RedirectExit, to make it easier to break
6414 out of a sequence of RedirectExit rules.
6415 - Make the dirservers file obsolete.
6416 - Include a dir-signing-key token in directories to tell the
6417 parsing entity which key is being used to sign.
6418 - Remove the built-in bulky default dirservers string.
6419 - New config option "Dirserver %s:%d [fingerprint]", which can be
6420 repeated as many times as needed. If no dirservers specified,
6421 default to moria1,moria2,tor26.
6422 - Make 'Routerfile' config option obsolete.
6423 - Discourage people from setting their dirfetchpostperiod more often
6424 than once per minute.
6427 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
6428 get back to normal.)
6429 - Accept *:706 (silc) in default exit policy.
6430 - Implement new versioning format for post 0.1.
6431 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
6432 log more informatively.
6433 - Check clock skew for verified servers, but allow unverified
6434 servers and clients to have any clock skew.
6435 - Make sure the hidden service descriptors are at a random offset
6436 from each other, to hinder linkability.
6437 - Clients now generate a TLS cert too, in preparation for having
6438 them act more like real nodes.
6439 - Add a pure-C tor-resolve implementation.
6440 - Use getrlimit and friends to ensure we can reach MaxConn (currently
6441 1024) file descriptors.
6442 - Raise the max dns workers from 50 to 100.
6445 Changes in version 0.0.8.1 - 2004-10-13
6447 - Fix a seg fault that can be triggered remotely for Tor
6448 clients/servers with an open dirport.
6449 - Fix a rare assert trigger, where routerinfos for entries in
6450 our cpath would expire while we're building the path.
6451 - Fix a bug in OutboundBindAddress so it (hopefully) works.
6452 - Fix a rare seg fault for people running hidden services on
6453 intermittent connections.
6454 - Fix a bug in parsing opt keywords with objects.
6455 - Fix a stale pointer assert bug when a stream detaches and
6457 - Fix a string format vulnerability (probably not exploitable)
6458 in reporting stats locally.
6459 - Fix an assert trigger: sometimes launching circuits can fail
6460 immediately, e.g. because too many circuits have failed recently.
6461 - Fix a compile warning on 64 bit platforms.
6464 Changes in version 0.0.8 - 2004-08-25
6466 - Made our unit tests compile again on OpenBSD 3.5, and tor
6467 itself compile again on OpenBSD on a sparc64.
6468 - We were neglecting milliseconds when logging on win32, so
6469 everything appeared to happen at the beginning of each second.
6470 - Check directory signature _before_ you decide whether you're
6471 you're running an obsolete version and should exit.
6472 - Check directory signature _before_ you parse the running-routers
6473 list to decide who's running.
6474 - Check return value of fclose while writing to disk, so we don't
6475 end up with broken files when servers run out of disk space.
6476 - Port it to SunOS 5.9 / Athena
6477 - Fix two bugs in saving onion keys to disk when rotating, so
6478 hopefully we'll get fewer people using old onion keys.
6479 - Remove our mostly unused -- and broken -- hex_encode()
6480 function. Use base16_encode() instead. (Thanks to Timo Lindfors
6481 for pointing out this bug.)
6482 - Only pick and establish intro points after we've gotten a
6484 - Fix assert triggers: if the other side returns an address 0.0.0.0,
6485 don't put it into the client dns cache.
6486 - If a begin failed due to exit policy, but we believe the IP
6487 address should have been allowed, switch that router to exitpolicy
6488 reject *:* until we get our next directory.
6491 - 'Extend' relay cell payloads now include the digest of the
6492 intended next hop's identity key. Now we can verify that we're
6493 extending to the right router, and also extend to routers we
6494 hadn't heard of before.
6497 - Tor nodes can now act as relays (with an advertised ORPort)
6498 without being manually verified by the dirserver operators.
6499 - Uploaded descriptors of unverified routers are now accepted
6500 by the dirservers, and included in the directory.
6501 - Verified routers are listed by nickname in the running-routers
6502 list; unverified routers are listed as "$<fingerprint>".
6503 - We now use hash-of-identity-key in most places rather than
6504 nickname or addr:port, for improved security/flexibility.
6505 - AllowUnverifiedNodes config option to let circuits choose no-name
6506 routers in entry,middle,exit,introduction,rendezvous positions.
6507 Allow middle and rendezvous positions by default.
6508 - When picking unverified routers, skip those with low uptime and/or
6509 low bandwidth, depending on what properties you care about.
6510 - ClientOnly option for nodes that never want to become servers.
6511 - Directory caching.
6512 - "AuthoritativeDir 1" option for the official dirservers.
6513 - Now other nodes (clients and servers) will cache the latest
6514 directory they've pulled down.
6515 - They can enable their DirPort to serve it to others.
6516 - Clients will pull down a directory from any node with an open
6517 DirPort, and check the signature/timestamp correctly.
6518 - Authoritative dirservers now fetch directories from other
6519 authdirservers, to stay better synced.
6520 - Running-routers list tells who's down also, along with noting
6521 if they're verified (listed by nickname) or unverified (listed
6523 - Allow dirservers to serve running-router list separately.
6524 This isn't used yet.
6525 - You can now fetch $DIRURL/running-routers to get just the
6526 running-routers line, not the whole descriptor list. (But
6527 clients don't use this yet.)
6528 - Clients choose nodes proportional to advertised bandwidth.
6529 - Clients avoid using nodes with low uptime as introduction points.
6530 - Handle servers with dynamic IP addresses: don't just replace
6531 options->Address with the resolved one at startup, and
6532 detect our address right before we make a routerinfo each time.
6533 - 'FascistFirewall' option to pick dirservers and ORs on specific
6534 ports; plus 'FirewallPorts' config option to tell FascistFirewall
6535 which ports are open. (Defaults to 80,443)
6536 - Try other dirservers immediately if the one you try is down. This
6537 should tolerate down dirservers better now.
6538 - ORs connect-on-demand to other ORs
6539 - If you get an extend cell to an OR you're not connected to,
6540 connect, handshake, and forward the create cell.
6541 - The authoritative dirservers stay connected to everybody,
6542 and everybody stays connected to 0.0.7 servers, but otherwise
6543 clients/servers expire unused connections after 5 minutes.
6544 - When servers get a sigint, they delay 30 seconds (refusing new
6545 connections) then exit. A second sigint causes immediate exit.
6546 - File and name management:
6547 - Look for .torrc if no CONFDIR "torrc" is found.
6548 - If no datadir is defined, then choose, make, and secure ~/.tor
6550 - If torrc not found, exitpolicy reject *:*.
6551 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
6552 - If no nickname is defined, derive default from hostname.
6553 - Rename secret key files, e.g. identity.key -> secret_id_key,
6554 to discourage people from mailing their identity key to tor-ops.
6555 - Refuse to build a circuit before the directory has arrived --
6556 it won't work anyway, since you won't know the right onion keys
6558 - Parse tor version numbers so we can do an is-newer-than check
6559 rather than an is-in-the-list check.
6560 - New socks command 'resolve', to let us shim gethostbyname()
6562 - A 'tor_resolve' script to access the socks resolve functionality.
6563 - A new socks-extensions.txt doc file to describe our
6564 interpretation and extensions to the socks protocols.
6565 - Add a ContactInfo option, which gets published in descriptor.
6566 - Write tor version at the top of each log file
6567 - New docs in the tarball:
6569 - Document that you should proxy your SSL traffic too.
6570 - Log a warning if the user uses an unsafe socks variant, so people
6571 are more likely to learn about privoxy or socat.
6572 - Log a warning if you're running an unverified server, to let you
6573 know you might want to get it verified.
6574 - Change the default exit policy to reject the default edonkey,
6575 kazaa, gnutella ports.
6576 - Add replace_file() to util.[ch] to handle win32's rename().
6577 - Publish OR uptime in descriptor (and thus in directory) too.
6578 - Remember used bandwidth (both in and out), and publish 15-minute
6579 snapshots for the past day into our descriptor.
6580 - Be more aggressive about trying to make circuits when the network
6581 has changed (e.g. when you unsuspend your laptop).
6582 - Check for time skew on http headers; report date in response to
6584 - If the entrynode config line has only one node, don't pick it as
6586 - Add strict{entry|exit}nodes config options. If set to 1, then
6587 we refuse to build circuits that don't include the specified entry
6589 - OutboundBindAddress config option, to bind to a specific
6590 IP address for outgoing connect()s.
6591 - End truncated log entries (e.g. directories) with "[truncated]".
6594 Changes in version 0.0.7.3 - 2004-08-12
6595 o Stop dnsworkers from triggering an assert failure when you
6596 ask them to resolve the host "".
6599 Changes in version 0.0.7.2 - 2004-07-07
6600 o A better fix for the 0.0.0.0 problem, that will hopefully
6601 eliminate the remaining related assertion failures.
6604 Changes in version 0.0.7.1 - 2004-07-04
6605 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
6606 since internally we use 0.0.0.0 to signify "not yet resolved".
6609 Changes in version 0.0.7 - 2004-06-07
6610 o Fixes for crashes and other obnoxious bugs:
6611 - Fix an epipe bug: sometimes when directory connections failed
6612 to connect, we would give them a chance to flush before closing
6614 - When we detached from a circuit because of resolvefailed, we
6615 would immediately try the same circuit twice more, and then
6616 give up on the resolve thinking we'd tried three different
6618 - Limit the number of intro circuits we'll attempt to build for a
6619 hidden service per 15-minute period.
6620 - Check recommended-software string *early*, before actually parsing
6621 the directory. Thus we can detect an obsolete version and exit,
6622 even if the new directory format doesn't parse.
6623 o Fixes for security bugs:
6624 - Remember which nodes are dirservers when you startup, and if a
6625 random OR enables his dirport, don't automatically assume he's
6626 a trusted dirserver.
6628 - Directory connections were asking the wrong poll socket to
6629 start writing, and not asking themselves to start writing.
6630 - When we detached from a circuit because we sent a begin but
6631 didn't get a connected, we would use it again the first time;
6632 but after that we would correctly switch to a different one.
6633 - Stop warning when the first onion decrypt attempt fails; they
6634 will sometimes legitimately fail now that we rotate keys.
6635 - Override unaligned-access-ok check when $host_cpu is ia64 or
6636 arm. Apparently they allow it but the kernel whines.
6637 - Dirservers try to reconnect periodically too, in case connections
6639 - Fix some memory leaks in directory servers.
6640 - Allow backslash in Win32 filenames.
6641 - Made Tor build complain-free on FreeBSD, hopefully without
6642 breaking other BSD builds. We'll see.
6643 - Check directory signatures based on name of signer, not on whom
6644 we got the directory from. This will let us cache directories more
6646 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
6649 - Doxygen markup on all functions and global variables.
6650 - Make directory functions update routerlist, not replace it. So
6651 now directory disagreements are not so critical a problem.
6652 - Remove the upper limit on number of descriptors in a dirserver's
6653 directory (not that we were anywhere close).
6654 - Allow multiple logfiles at different severity ranges.
6655 - Allow *BindAddress to specify ":port" rather than setting *Port
6656 separately. Allow multiple instances of each BindAddress config
6657 option, so you can bind to multiple interfaces if you want.
6658 - Allow multiple exit policy lines, which are processed in order.
6659 Now we don't need that huge line with all the commas in it.
6660 - Enable accept/reject policies on SOCKS connections, so you can bind
6661 to 0.0.0.0 but still control who can use your OP.
6662 - Updated the man page to reflect these features.
6665 Changes in version 0.0.6.2 - 2004-05-16
6666 o Our integrity-checking digest was checking only the most recent cell,
6667 not the previous cells like we'd thought.
6668 Thanks to Stefan Mark for finding the flaw!
6671 Changes in version 0.0.6.1 - 2004-05-06
6672 o Fix two bugs in our AES counter-mode implementation (this affected
6673 onion-level stream encryption, but not TLS-level). It turns
6674 out we were doing something much more akin to a 16-character
6675 polyalphabetic cipher. Oops.
6676 Thanks to Stefan Mark for finding the flaw!
6677 o Retire moria3 as a directory server, and add tor26 as a directory
6681 Changes in version 0.0.6 - 2004-05-02
6683 - Hidden services and rendezvous points are implemented. Go to
6684 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
6685 hidden services. (This only works via a socks4a proxy such as
6686 Privoxy, and currently it's quite slow.)
6687 - We now rotate link (tls context) keys and onion keys.
6688 - CREATE cells now include oaep padding, so you can tell
6689 if you decrypted them correctly.
6690 - Retry stream correctly when we fail to connect because of
6691 exit-policy-reject (should try another) or can't-resolve-address.
6692 - When we hup a dirserver and we've *removed* a server from the
6693 approved-routers list, now we remove that server from the
6694 in-memory directories too.
6695 - Add bandwidthburst to server descriptor.
6696 - Directories now say which dirserver signed them.
6697 - Use a tor_assert macro that logs failed assertions too.
6698 - Since we don't support truncateds much, don't bother sending them;
6699 just close the circ.
6700 - Fetch randomness from /dev/urandom better (not via fopen/fread)
6701 - Better debugging for tls errors
6702 - Set Content-Type on the directory and hidserv descriptor.
6703 - Remove IVs from cipher code, since AES-ctr has none.
6705 - Fix an assert trigger for exit nodes that's been plaguing us since
6706 the days of 0.0.2prexx (thanks weasel!)
6707 - Fix a bug where we were closing tls connections intermittently.
6708 It turns out openssl keeps its errors around -- so if an error
6709 happens, and you don't ask about it, and then another openssl
6710 operation happens and succeeds, and you ask if there was an error,
6711 it tells you about the first error.
6712 - Fix a bug that's been lurking since 27 may 03 (!)
6713 When passing back a destroy cell, we would use the wrong circ id.
6714 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
6715 - Some versions of openssl have an SSL_pending function that erroneously
6716 returns bytes when there is a non-application record pending.
6717 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
6718 o We were using an array of length zero in a few places.
6719 o Win32's gethostbyname can't resolve an IP to an IP.
6720 o Win32's close can't close a socket.
6721 o Handle windows socket errors correctly.
6723 - check for <sys/limits.h> so we build on FreeBSD again, and
6724 <machine/limits.h> for NetBSD.
6727 Changes in version 0.0.5 - 2004-03-30
6728 o Install torrc as torrc.sample -- we no longer clobber your
6730 o Fix mangled-state bug in directory fetching (was causing sigpipes).
6731 o Only build circuits after we've fetched the directory: clients were
6732 using only the directory servers before they'd fetched a directory.
6733 This also means longer startup time; so it goes.
6734 o Fix an assert trigger where an OP would fail to handshake, and we'd
6735 expect it to have a nickname.
6736 o Work around a tsocks bug: do a socks reject when AP connection dies
6737 early, else tsocks goes into an infinite loop.
6738 o Hold socks connection open until reply is flushed (if possible)
6739 o Make exit nodes resolve IPs to IPs immediately, rather than asking
6740 the dns farm to do it.
6741 o Fix c99 aliasing warnings in rephist.c
6742 o Don't include server descriptors that are older than 24 hours in the
6744 o Give socks 'reject' replies their whole 15s to attempt to flush,
6745 rather than seeing the 60s timeout and assuming the flush had failed.
6746 o Clean automake droppings from the cvs repository
6747 o Add in a 'notice' log level for things the operator should hear
6748 but that aren't warnings
6751 Changes in version 0.0.4 - 2004-03-26
6752 o When connecting to a dirserver or OR and the network is down,
6756 Changes in version 0.0.3 - 2004-03-26
6757 o Warn and fail if server chose a nickname with illegal characters
6758 o Port to Solaris and Sparc:
6759 - include missing header fcntl.h
6760 - have autoconf find -lsocket -lnsl automatically
6761 - deal with hardware word alignment
6762 - make uname() work (solaris has a different return convention)
6763 - switch from using signal() to sigaction()
6764 o Preliminary work on reputation system:
6765 - Keep statistics on success/fail of connect attempts; they're published
6766 by kill -USR1 currently.
6767 - Add a RunTesting option to try to learn link state by creating test
6768 circuits, even when SocksPort is off.
6769 - Remove unused open circuits when there are too many.
6772 Changes in version 0.0.2 - 2004-03-19
6773 - Include strlcpy and strlcat for safer string ops
6774 - define INADDR_NONE so we compile (but still not run) on solaris
6777 Changes in version 0.0.2pre27 - 2004-03-14
6779 - Allow internal tor networks (we were rejecting internal IPs,
6780 now we allow them if they're set explicitly).
6781 - And fix a few endian issues.
6784 Changes in version 0.0.2pre26 - 2004-03-14
6786 - If a stream times out after 15s without a connected cell, don't
6787 try that circuit again: try a new one.
6788 - Retry streams at most 4 times. Then give up.
6789 - When a dirserver gets a descriptor from an unknown router, it
6790 logs its fingerprint (so the dirserver operator can choose to
6791 accept it even without mail from the server operator).
6792 - Inform unapproved servers when we reject their descriptors.
6793 - Make tor build on Windows again. It works as a client, who knows
6795 - Clearer instructions in the torrc for how to set up a server.
6796 - Be more efficient about reading fd's when our global token bucket
6797 (used for rate limiting) becomes empty.
6799 - Stop asserting that computers always go forward in time. It's
6801 - When we sent a cell (e.g. destroy) and then marked an OR connection
6802 expired, we might close it before finishing a flush if the other
6803 side isn't reading right then.
6804 - Don't allow dirservers to start if they haven't defined
6806 - We were caching transient dns failures. Oops.
6807 - Prevent servers from publishing an internal IP as their address.
6808 - Address a strcat vulnerability in circuit.c
6811 Changes in version 0.0.2pre25 - 2004-03-04
6813 - Put the OR's IP in its router descriptor, not its fqdn. That way
6814 we'll stop being stalled by gethostbyname for nodes with flaky dns,
6817 - If the user typed in an address that didn't resolve, the server
6821 Changes in version 0.0.2pre24 - 2004-03-03
6823 - Fix an assertion failure in dns.c, where we were trying to dequeue
6824 a pending dns resolve even if it wasn't pending
6825 - Fix a spurious socks5 warning about still trying to write after the
6826 connection is finished.
6827 - Hold certain marked_for_close connections open until they're finished
6828 flushing, rather than losing bytes by closing them too early.
6829 - Correctly report the reason for ending a stream
6830 - Remove some duplicate calls to connection_mark_for_close
6831 - Put switch_id and start_daemon earlier in the boot sequence, so it
6832 will actually try to chdir() to options.DataDirectory
6833 - Make 'make test' exit(1) if a test fails; fix some unit tests
6834 - Make tor fail when you use a config option it doesn't know about,
6835 rather than warn and continue.
6836 - Make --version work
6837 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
6840 Changes in version 0.0.2pre23 - 2004-02-29
6842 - Print a statement when the first circ is finished, so the user
6844 - If a relay cell is unrecognized at the end of the circuit,
6845 send back a destroy. (So attacks to mutate cells are more
6847 - New config option 'excludenodes' to avoid certain nodes for circuits.
6848 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
6849 so you can collect coredumps there.
6851 - Fix a bug in tls flushing where sometimes data got wedged and
6852 didn't flush until more data got sent. Hopefully this bug was
6853 a big factor in the random delays we were seeing.
6854 - Make 'connected' cells include the resolved IP, so the client
6855 dns cache actually gets populated.
6856 - Disallow changing from ORPort=0 to ORPort>0 on hup.
6857 - When we time-out on a stream and detach from the circuit, send an
6858 end cell down it first.
6859 - Only warn about an unknown router (in exitnodes, entrynodes,
6860 excludenodes) after we've fetched a directory.
6863 Changes in version 0.0.2pre22 - 2004-02-26
6865 - Servers publish less revealing uname information in descriptors.
6866 - More memory tracking and assertions, to crash more usefully when
6868 - If the default torrc isn't there, just use some default defaults.
6869 Plus provide an internal dirservers file if they don't have one.
6870 - When the user tries to use Tor as an http proxy, give them an http
6871 501 failure explaining that we're a socks proxy.
6872 - Dump a new router.desc on hup, to help confused people who change
6873 their exit policies and then wonder why router.desc doesn't reflect
6875 - Clean up the generic tor.sh init script that we ship with.
6877 - If the exit stream is pending on the resolve, and a destroy arrives,
6878 then the stream wasn't getting removed from the pending list. I
6879 think this was the one causing recent server crashes.
6880 - Use a more robust poll on OSX 10.3, since their poll is flaky.
6881 - When it couldn't resolve any dirservers, it was useless from then on.
6882 Now it reloads the RouterFile (or default dirservers) if it has no
6884 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
6885 many users don't even *have* a /usr/local/sbin/.
6888 Changes in version 0.0.2pre21 - 2004-02-18
6890 - There's a ChangeLog file that actually reflects the changelog.
6891 - There's a 'torify' wrapper script, with an accompanying
6892 tor-tsocks.conf, that simplifies the process of using tsocks for
6893 tor. It even has a man page.
6894 - The tor binary gets installed to sbin rather than bin now.
6895 - Retry streams where the connected cell hasn't arrived in 15 seconds
6896 - Clean up exit policy handling -- get the default out of the torrc,
6897 so we can update it without forcing each server operator to fix
6899 - Allow imaps and pop3s in default exit policy
6901 - Prevent picking middleman nodes as the last node in the circuit
6904 Changes in version 0.0.2pre20 - 2004-01-30
6906 - We now have a deb package, and it's in debian unstable. Go to
6908 - I've split the TotalBandwidth option into BandwidthRate (how many
6909 bytes per second you want to allow, long-term) and
6910 BandwidthBurst (how many bytes you will allow at once before the cap
6911 kicks in). This better token bucket approach lets you, say, set
6912 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
6913 performance while not exceeding your monthly bandwidth quota.
6914 - Push out a tls record's worth of data once you've got it, rather
6915 than waiting until you've read everything waiting to be read. This
6916 may improve performance by pipelining better. We'll see.
6917 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
6918 from failed circuits (if they haven't been connected yet) and attach
6920 - Expire old streams that haven't managed to connect. Some day we'll
6921 have them reattach to new circuits instead.
6924 - Fix several memory leaks that were causing servers to become bloated
6926 - Fix a few very rare assert triggers. A few more remain.
6927 - Setuid to User _before_ complaining about running as root.
6930 Changes in version 0.0.2pre19 - 2004-01-07
6932 - Fix deadlock condition in dns farm. We were telling a child to die by
6933 closing the parent's file descriptor to him. But newer children were
6934 inheriting the open file descriptor from the parent, and since they
6935 weren't closing it, the socket never closed, so the child never read
6936 eof, so he never knew to exit. Similarly, dns workers were holding
6937 open other sockets, leading to all sorts of chaos.
6938 - New cleaner daemon() code for forking and backgrounding.
6939 - If you log to a file, it now prints an entry at the top of the
6940 logfile so you know it's working.
6941 - The onionskin challenge length was 30 bytes longer than necessary.
6942 - Started to patch up the spec so it's not quite so out of date.
6945 Changes in version 0.0.2pre18 - 2004-01-02
6947 - Fix endian issues with the 'integrity' field in the relay header.
6948 - Fix a potential bug where connections in state
6949 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
6952 Changes in version 0.0.2pre17 - 2003-12-30
6954 - Made --debuglogfile (or any second log file, actually) work.
6955 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
6956 adversary could force us into an infinite loop.
6959 - Each onionskin handshake now includes a hash of the computed key,
6960 to prove the server's identity and help perfect forward secrecy.
6961 - Changed cell size from 256 to 512 bytes (working toward compatibility
6963 - Changed cell length to 2 bytes, and moved it to the relay header.
6964 - Implemented end-to-end integrity checking for the payloads of
6966 - Separated streamid from 'recognized' (otherwise circuits will get
6967 messed up when we try to have streams exit from the middle). We
6968 use the integrity-checking to confirm that a cell is addressed to
6970 - Randomize the initial circid and streamid values, so an adversary who
6971 breaks into a node can't learn how many circuits or streams have
6975 Changes in version 0.0.2pre16 - 2003-12-14
6977 - Fixed a bug that made HUP trigger an assert
6978 - Fixed a bug where a circuit that immediately failed wasn't being
6979 counted as a failed circuit in counting retries.
6982 - Now we close the circuit when we get a truncated cell: otherwise we're
6983 open to an anonymity attack where a bad node in the path truncates
6984 the circuit and then we open streams at him.
6985 - Add port ranges to exit policies
6986 - Add a conservative default exit policy
6987 - Warn if you're running tor as root
6988 - on HUP, retry OR connections and close/rebind listeners
6989 - options.EntryNodes: try these nodes first when picking the first node
6990 - options.ExitNodes: if your best choices happen to include any of
6991 your preferred exit nodes, you choose among just those preferred
6993 - options.ExcludedNodes: nodes that are never picked in path building
6996 Changes in version 0.0.2pre15 - 2003-12-03
6997 o Robustness and bugfixes:
6998 - Sometimes clients would cache incorrect DNS resolves, which would
6999 really screw things up.
7000 - An OP that goes offline would slowly leak all its sockets and stop
7002 - A wide variety of bugfixes in exit node selection, exit policy
7003 handling, and processing pending streams when a new circuit is
7005 - Pick nodes for a path only from those the directory says are up
7006 - Choose randomly from all running dirservers, not always the first one
7007 - Increase allowed http header size for directory fetch.
7008 - Stop writing to stderr (if we're daemonized it will be closed).
7009 - Enable -g always, so cores will be more useful to me.
7010 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
7013 - Wrote a man page. It lists commonly used options.
7016 - Change default loglevel to warn.
7017 - Make PidFile default to null rather than littering in your CWD.
7018 - OnionRouter config option is now obsolete. Instead it just checks
7020 - Moved to a single unified torrc file for both clients and servers.
7023 Changes in version 0.0.2pre14 - 2003-11-29
7024 o Robustness and bugfixes:
7025 - Force the admin to make the DataDirectory himself
7026 - to get ownership/permissions right
7027 - so clients no longer make a DataDirectory and then never use it
7028 - fix bug where a client who was offline for 45 minutes would never
7029 pull down a directory again
7030 - fix (or at least hide really well) the dns assert bug that was
7031 causing server crashes
7032 - warnings and improved robustness wrt clockskew for certs
7033 - use the native daemon(3) to daemonize, when available
7034 - exit if bind() fails
7035 - exit if neither socksport nor orport is defined
7036 - include our own tor_timegm (Win32 doesn't have its own)
7037 - bugfix for win32 with lots of connections
7038 - fix minor bias in PRNG
7039 - make dirserver more robust to corrupt cached directory
7042 - Wrote the design document (woo)
7044 o Circuit building and exit policies:
7045 - Circuits no longer try to use nodes that the directory has told them
7047 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
7048 bitcounts (18.0.0.0/8).
7049 - Make AP connections standby for a circuit if no suitable circuit
7050 exists, rather than failing
7051 - Circuits choose exit node based on addr/port, exit policies, and
7052 which AP connections are standing by
7053 - Bump min pathlen from 2 to 3
7054 - Relay end cells have a payload to describe why the stream ended.
7055 - If the stream failed because of exit policy, try again with a new
7057 - Clients have a dns cache to remember resolved addresses.
7058 - Notice more quickly when we have no working circuits
7061 - APPort is now called SocksPort
7062 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
7064 - RecommendedVersions is now a config variable rather than
7065 hardcoded (for dirservers)
7066 - Reloads config on HUP
7067 - Usage info on -h or --help
7068 - If you set User and Group config vars, it'll setu/gid to them.
7070 Changes in version 0.0.2pre13 - 2003-10-19
7071 o General stability:
7072 - SSL_write no longer fails when it returns WANTWRITE and the number
7073 of bytes in the buf has changed by the next SSL_write call.
7074 - Fix segfault fetching directory when network is down
7075 - Fix a variety of minor memory leaks
7076 - Dirservers reload the fingerprints file on HUP, so I don't have
7077 to take down the network when I approve a new router
7078 - Default server config file has explicit Address line to specify fqdn
7081 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
7082 - Make listener connections not ever alloc bufs
7084 o Autoconf improvements:
7085 - don't clobber an external CFLAGS in ./configure
7086 - Make install now works
7087 - create var/lib/tor on make install
7088 - autocreate a tor.sh initscript to help distribs
7089 - autocreate the torrc and sample-server-torrc with correct paths
7091 o Log files and Daemonizing now work:
7092 - If --DebugLogFile is specified, log to it at -l debug
7093 - If --LogFile is specified, use it instead of commandline
7094 - If --RunAsDaemon is set, tor forks and backgrounds on startup