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