1 Changes in version 0.2.5.9-rc - 2014-10-20
2 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
3 series. It disables SSL3 in response to the recent "POODLE" attack
4 (even though POODLE does not affect Tor). It also works around a crash
5 bug caused by some operating systems' response to the "POODLE" attack
6 (which does affect Tor). It also contains a few miscellaneous fixes.
8 o Major security fixes:
9 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
10 today support TLS 1.0 or later, so we can safely turn off support
11 for this old (and insecure) protocol. Fixes bug 13426.
13 o Major bugfixes (openssl bug workaround):
14 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
16 13471. This is a workaround for an OpenSSL bug.
19 - Disable the sandbox name resolver cache when running tor-resolve:
20 tor-resolve doesn't use the sandbox code, and turning it on was
21 breaking attempts to do tor-resolve on a non-default server on
22 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
25 - Build and run correctly on systems like OpenBSD-current that have
26 patched OpenSSL to remove get_cipher_by_char and/or its
27 implementations. Fixes issue 13325.
29 o Downgraded warnings:
30 - Downgrade the severity of the 'unexpected sendme cell from client'
31 from 'warn' to 'protocol warning'. Closes ticket 8093.
34 Changes in version 0.2.4.25 - 2014-10-20
35 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
36 (even though POODLE does not affect Tor). It also works around a crash
37 bug caused by some operating systems' response to the "POODLE" attack
38 (which does affect Tor).
40 o Major security fixes (also in 0.2.5.9-rc):
41 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
42 today support TLS 1.0 or later, so we can safely turn off support
43 for this old (and insecure) protocol. Fixes bug 13426.
45 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
46 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
47 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
48 13471. This is a workaround for an OpenSSL bug.
51 Changes in version 0.2.5.8-rc - 2014-09-22
52 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
53 series. It fixes a bug that affects consistency and speed when
54 connecting to hidden services, and it updates the location of one of
55 the directory authorities.
58 - Clients now send the correct address for their chosen rendezvous
59 point when trying to access a hidden service. They used to send
60 the wrong address, which would still work some of the time because
61 they also sent the identity digest of the rendezvous point, and if
62 the hidden service happened to try connecting to the rendezvous
63 point from a relay that already had a connection open to it,
64 the relay would reuse that connection. Now connections to hidden
65 services should be more robust and faster. Also, this bug meant
66 that clients were leaking to the hidden service whether they were
67 on a little-endian (common) or big-endian (rare) system, which for
68 some users might have reduced their anonymity. Fixes bug 13151;
69 bugfix on 0.2.1.5-alpha.
71 o Directory authority changes:
72 - Change IP address for gabelmoo (v3 directory authority).
75 Changes in version 0.2.4.24 - 2014-09-22
76 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
77 connecting to hidden services, and it updates the location of one of
78 the directory authorities.
81 - Clients now send the correct address for their chosen rendezvous
82 point when trying to access a hidden service. They used to send
83 the wrong address, which would still work some of the time because
84 they also sent the identity digest of the rendezvous point, and if
85 the hidden service happened to try connecting to the rendezvous
86 point from a relay that already had a connection open to it,
87 the relay would reuse that connection. Now connections to hidden
88 services should be more robust and faster. Also, this bug meant
89 that clients were leaking to the hidden service whether they were
90 on a little-endian (common) or big-endian (rare) system, which for
91 some users might have reduced their anonymity. Fixes bug 13151;
92 bugfix on 0.2.1.5-alpha.
94 o Directory authority changes:
95 - Change IP address for gabelmoo (v3 directory authority).
97 o Minor features (geoip):
98 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
102 Changes in version 0.2.5.7-rc - 2014-09-11
103 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
104 release series, and some long-standing bugs related to ORPort reachability
105 testing and failure to send CREATE cells. It is the first release
106 candidate for the Tor 0.2.5.x series.
108 o Major bugfixes (client, startup):
109 - Start making circuits as soon as DisabledNetwork is turned off.
110 When Tor started with DisabledNetwork set, it would correctly
111 conclude that it shouldn't build circuits, but it would mistakenly
112 cache this conclusion, and continue believing it even when
113 DisableNetwork is set to 0. Fixes the bug introduced by the fix
114 for bug 11200; bugfix on 0.2.5.4-alpha.
115 - Resume expanding abbreviations for command-line options. The fix
116 for bug 4647 accidentally removed our hack from bug 586 that
117 rewrote HashedControlPassword to __HashedControlSessionPassword
118 when it appears on the commandline (which allowed the user to set
119 her own HashedControlPassword in the torrc file while the
120 controller generates a fresh session password for each run). Fixes
121 bug 12948; bugfix on 0.2.5.1-alpha.
122 - Warn about attempts to run hidden services and relays in the same
123 process: that's probably not a good idea. Closes ticket 12908.
125 o Major bugfixes (relay):
126 - Avoid queuing or sending destroy cells for circuit ID zero when we
127 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
128 Found and fixed by "cypherpunks".
129 - Fix ORPort reachability detection on relays running behind a
130 proxy, by correctly updating the "local" mark on the controlling
131 channel when changing the address of an or_connection_t after the
132 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
134 o Minor features (bridge):
135 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
136 cookie file for the ExtORPort g+r by default.
138 o Minor features (geoip):
139 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
142 o Minor bugfixes (logging):
143 - Reduce the log severity of the "Pluggable transport proxy does not
144 provide any needed transports and will not be launched." message,
145 since Tor Browser includes several ClientTransportPlugin lines in
146 its torrc-defaults file, leading every Tor Browser user who looks
147 at her logs to see these notices and wonder if they're dangerous.
148 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
149 - Downgrade "Unexpected onionskin length after decryption" warning
150 to a protocol-warn, since there's nothing relay operators can do
151 about a client that sends them a malformed create cell. Resolves
152 bug 12996; bugfix on 0.0.6rc1.
153 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
154 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
155 - When logging information about an EXTEND2 or EXTENDED2 cell, log
156 their names correctly. Fixes part of bug 12700; bugfix
158 - When logging information about a relay cell whose command we don't
159 recognize, log its command as an integer. Fixes part of bug 12700;
160 bugfix on 0.2.1.10-alpha.
161 - Escape all strings from the directory connection before logging
162 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
164 o Minor bugfixes (controller):
165 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
166 bug 12864; bugfix on 0.2.5.1-alpha.
167 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
168 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
171 o Minor bugfixes (compilation):
172 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
173 bugfix on 0.2.5.5-alpha.
174 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
175 0.2.5.1-alpha. Patch from "NewEraCracker".
176 - In routerlist_assert_ok(), don't take the address of a
177 routerinfo's cache_info member unless that routerinfo is non-NULL.
178 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
179 - Fix a large number of false positive warnings from the clang
180 analyzer static analysis tool. This should make real warnings
181 easier for clang analyzer to find. Patch from "teor". Closes
184 o Distribution (systemd):
185 - Verify configuration file via ExecStartPre in the systemd unit
186 file. Patch from intrigeri; resolves ticket 12730.
187 - Explicitly disable RunAsDaemon in the systemd unit file. Our
188 current systemd unit uses "Type = simple", so systemd does not
189 expect tor to fork. If the user has "RunAsDaemon 1" in their
190 torrc, then things won't work as expected. This is e.g. the case
191 on Debian (and derivatives), since there we pass "--defaults-torrc
192 /usr/share/tor/tor-service-defaults-torrc" (that contains
193 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
197 - Adjust the URLs in the README to refer to the new locations of
198 several documents on the website. Fixes bug 12830. Patch from
200 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
204 Changes in version 0.2.5.6-alpha - 2014-07-28
205 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
206 risk from guard rotation, and fixes a variety of other issues to get
207 us closer to a release candidate.
209 o Major features (also in 0.2.4.23):
210 - Make the number of entry guards configurable via a new
211 NumEntryGuards consensus parameter, and the number of directory
212 guards configurable via a new NumDirectoryGuards consensus
213 parameter. Implements ticket 12688.
215 o Major bugfixes (also in 0.2.4.23):
216 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
217 implementation that caused incorrect results on 32-bit
218 implementations when certain malformed inputs were used along with
219 a small class of private ntor keys. This bug does not currently
220 appear to allow an attacker to learn private keys or impersonate a
221 Tor server, but it could provide a means to distinguish 32-bit Tor
222 implementations from 64-bit Tor implementations. Fixes bug 12694;
223 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
227 - Perform circuit cleanup operations even when circuit
228 construction operations are disabled (because the network is
229 disabled, or because there isn't enough directory information).
230 Previously, when we were not building predictive circuits, we
231 were not closing expired circuits either. Fixes bug 8387; bugfix on
232 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
233 became more strict about when we have "enough directory information
237 - Authorities now assign the Guard flag to the fastest 25% of the
238 network (it used to be the fastest 50%). Also raise the consensus
239 weight that guarantees the Guard flag from 250 to 2000. For the
240 current network, this results in about 1100 guards, down from 2500.
241 This step paves the way for moving the number of entry guards
242 down to 1 (proposal 236) while still providing reasonable expected
243 performance for most users. Implements ticket 12690.
244 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
246 - Slightly enhance the diagnostic message for bug 12184.
248 o Minor bugfixes (also in 0.2.4.23):
249 - Warn and drop the circuit if we receive an inbound 'relay early'
250 cell. Those used to be normal to receive on hidden service circuits
251 due to bug 1038, but the buggy Tor versions are long gone from
252 the network so we can afford to resume watching for them. Resolves
253 the rest of bug 1038; bugfix on 0.2.1.19.
254 - Correct a confusing error message when trying to extend a circuit
255 via the control protocol but we don't know a descriptor or
256 microdescriptor for one of the specified relays. Fixes bug 12718;
257 bugfix on 0.2.3.1-alpha.
260 - Fix compilation when building with bufferevents enabled. (This
261 configuration is still not expected to work, however.)
262 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
263 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
265 - Compile correctly with builds and forks of OpenSSL (such as
266 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
267 0.2.1.1-alpha. Patch from "dhill".
270 Changes in version 0.2.4.23 - 2014-07-28
271 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
272 guard rotation, and also backports several important fixes from the
273 Tor 0.2.5 alpha release series.
276 - Clients now look at the "usecreatefast" consensus parameter to
277 decide whether to use CREATE_FAST or CREATE cells for the first hop
278 of their circuit. This approach can improve security on connections
279 where Tor's circuit handshake is stronger than the available TLS
280 connection security levels, but the tradeoff is more computational
281 load on guard relays. Implements proposal 221. Resolves ticket 9386.
282 - Make the number of entry guards configurable via a new
283 NumEntryGuards consensus parameter, and the number of directory
284 guards configurable via a new NumDirectoryGuards consensus
285 parameter. Implements ticket 12688.
288 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
289 implementation that caused incorrect results on 32-bit
290 implementations when certain malformed inputs were used along with
291 a small class of private ntor keys. This bug does not currently
292 appear to allow an attacker to learn private keys or impersonate a
293 Tor server, but it could provide a means to distinguish 32-bit Tor
294 implementations from 64-bit Tor implementations. Fixes bug 12694;
295 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
299 - Warn and drop the circuit if we receive an inbound 'relay early'
300 cell. Those used to be normal to receive on hidden service circuits
301 due to bug 1038, but the buggy Tor versions are long gone from
302 the network so we can afford to resume watching for them. Resolves
303 the rest of bug 1038; bugfix on 0.2.1.19.
304 - Correct a confusing error message when trying to extend a circuit
305 via the control protocol but we don't know a descriptor or
306 microdescriptor for one of the specified relays. Fixes bug 12718;
307 bugfix on 0.2.3.1-alpha.
308 - Avoid an illegal read from stack when initializing the TLS
309 module using a version of OpenSSL without all of the ciphers
310 used by the v2 link handshake. Fixes bug 12227; bugfix on
311 0.2.4.8-alpha. Found by "starlight".
314 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
318 Changes in version 0.2.5.5-alpha - 2014-06-18
319 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
320 0.2.5.x release series, including a couple of DoS issues, some
321 performance regressions, a large number of bugs affecting the Linux
322 seccomp2 sandbox code, and various other bugfixes. It also adds
323 diagnostic bugfixes for a few tricky issues that we're trying to
326 o Major features (security, traffic analysis resistance):
327 - Several major improvements to the algorithm used to decide when to
328 close TLS connections. Previous versions of Tor closed connections
329 at a fixed interval after the last time a non-padding cell was
330 sent over the connection, regardless of the target of the
331 connection. Now, we randomize the intervals by adding up to 50% of
332 their base value, we measure the length of time since connection
333 last had at least one circuit, and we allow connections to known
334 ORs to remain open a little longer (15 minutes instead of 3
335 minutes minimum). These changes should improve Tor's resistance
336 against some kinds of traffic analysis, and lower some overhead
337 from needlessly closed connections. Fixes ticket 6799.
338 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
340 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
341 - Fix a memory leak that could occur if a microdescriptor parse
342 fails during the tokenizing step. This bug could enable a memory
343 exhaustion attack by directory servers. Fixes bug 11649; bugfix
346 o Major bugfixes (security, directory authorities):
347 - Directory authorities now include a digest of each relay's
348 identity key as a part of its microdescriptor.
350 This is a workaround for bug 11743 (reported by "cypherpunks"),
351 where Tor clients do not support receiving multiple
352 microdescriptors with the same SHA256 digest in the same
353 consensus. When clients receive a consensus like this, they only
354 use one of the relays. Without this fix, a hostile relay could
355 selectively disable some client use of target relays by
356 constructing a router descriptor with a different identity and the
357 same microdescriptor parameters and getting the authorities to
358 list it in a microdescriptor consensus. This fix prevents an
359 attacker from causing a microdescriptor collision, because the
360 router's identity is not forgeable.
362 o Major bugfixes (relay):
363 - Use a direct dirport connection when uploading non-anonymous
364 descriptors to the directory authorities. Previously, relays would
365 incorrectly use tunnel connections under a fairly wide variety of
366 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
367 - When a circuit accidentally has the same circuit ID for its
368 forward and reverse direction, correctly detect the direction of
369 cells using that circuit. Previously, this bug made roughly one
370 circuit in a million non-functional. Fixes bug 12195; this is a
371 bugfix on every version of Tor.
373 o Major bugfixes (client, pluggable transports):
374 - When managing pluggable transports, use OS notification facilities
375 to learn if they have crashed, and don't attempt to kill any
376 process that has already exited. Fixes bug 8746; bugfix
379 o Minor features (diagnostic):
380 - When logging a warning because of bug 7164, additionally check the
381 hash table for consistency (as proposed on ticket 11737). This may
382 help diagnose bug 7164.
383 - When we log a heartbeat, log how many one-hop circuits we have
384 that are at least 30 minutes old, and log status information about
385 a few of them. This is an attempt to track down bug 8387.
386 - When encountering an unexpected CR while writing text to a file on
387 Windows, log the name of the file. Should help diagnosing
389 - Give more specific warnings when a client notices that an onion
390 handshake has failed. Fixes ticket 9635.
391 - Add significant new logging code to attempt to diagnose bug 12184,
392 where relays seem to run out of available circuit IDs.
393 - Improve the diagnostic log message for bug 8387 even further to
394 try to improve our odds of figuring out why one-hop directory
395 circuits sometimes do not get closed.
397 o Minor features (security, memory management):
398 - Memory allocation tricks (mempools and buffer freelists) are now
399 disabled by default. You can turn them back on with
400 --enable-mempools and --enable-buf-freelists respectively. We're
401 disabling these features because malloc performance is good enough
402 on most platforms, and a similar feature in OpenSSL exacerbated
403 exploitation of the Heartbleed attack. Resolves ticket 11476.
405 o Minor features (security):
406 - Apply the secure SipHash-2-4 function to the hash table mapping
407 circuit IDs and channels to circuits. We missed this one when we
408 were converting all the other hash functions to use SipHash back
409 in 0.2.5.3-alpha. Resolves ticket 11750.
411 o Minor features (build):
412 - The configure script has a --disable-seccomp option to turn off
413 support for libseccomp on systems that have it, in case it (or
414 Tor's use of it) is broken. Resolves ticket 11628.
416 o Minor features (other):
417 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
420 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
421 - When running a hidden service, do not allow TunneledDirConns 0;
422 this will keep the hidden service from running, and also
423 make it publish its descriptors directly over HTTP. Fixes bug 10849;
424 bugfix on 0.2.1.1-alpha.
426 o Minor bugfixes (performance):
427 - Avoid a bug where every successful connection made us recompute
428 the flag telling us whether we have sufficient information to
429 build circuits. Previously, we would forget our cached value
430 whenever we successfully opened a channel (or marked a router as
431 running or not running for any other reason), regardless of
432 whether we had previously believed the router to be running. This
433 forced us to run an expensive update operation far too often.
434 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
435 - Avoid using tor_memeq() for checking relay cell integrity. This
436 removes a possible performance bottleneck. Fixes part of bug
437 12169; bugfix on 0.2.1.31.
439 o Minor bugfixes (compilation):
440 - Fix compilation of test_status.c when building with MVSC. Bugfix
441 on 0.2.5.4-alpha. Patch from Gisle Vanem.
442 - Resolve GCC complaints on OpenBSD about discarding constness in
443 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
444 on 0.1.1.23. Patch from Dana Koch.
445 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
446 treatment of long and time_t as comparable types. Fixes part of
447 bug 11633. Patch from Dana Koch.
448 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
449 11623; bugfix on 0.2.5.3-alpha.
450 - When deciding whether to build the 64-bit curve25519
451 implementation, detect platforms where we can compile 128-bit
452 arithmetic but cannot link it. Fixes bug 11729; bugfix on
453 0.2.4.8-alpha. Patch from "conradev".
454 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
455 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
456 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
459 o Minor bugfixes (Directory server):
460 - When sending a compressed set of descriptors or microdescriptors,
461 make sure to finalize the zlib stream. Previously, we would write
462 all the compressed data, but if the last descriptor we wanted to
463 send was missing or too old, we would not mark the stream as
464 finished. This caused problems for decompression tools. Fixes bug
465 11648; bugfix on 0.1.1.23.
467 o Minor bugfixes (Linux seccomp sandbox):
468 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
469 11622; bugfix on 0.2.5.1-alpha.
470 - Avoid crashing when re-opening listener ports with the seccomp
471 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
472 - Avoid crashing with the seccomp sandbox enabled along with
473 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
474 - When we receive a SIGHUP with the sandbox enabled, correctly
475 support rotating our log files. Fixes bug 12032; bugfix
477 - Avoid crash when running with sandboxing enabled and
478 DirReqStatistics not disabled. Fixes bug 12035; bugfix
480 - Fix a "BUG" warning when trying to write bridge-stats files with
481 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
483 - Prevent the sandbox from crashing on startup when run with the
484 --enable-expensive-hardening configuration option. Fixes bug
485 11477; bugfix on 0.2.5.4-alpha.
486 - When running with DirPortFrontPage and sandboxing both enabled,
487 reload the DirPortFrontPage correctly when restarting. Fixes bug
488 12028; bugfix on 0.2.5.1-alpha.
489 - Don't try to enable the sandbox when using the Tor binary to check
490 its configuration, hash a passphrase, or so on. Doing so was
491 crashing on startup for some users. Fixes bug 11609; bugfix
493 - Avoid warnings when running with sandboxing and node statistics
494 enabled at the same time. Fixes part of 12064; bugfix on
495 0.2.5.1-alpha. Patch from Michael Wolf.
496 - Avoid warnings when running with sandboxing enabled at the same
497 time as cookie authentication, hidden services, or directory
498 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
499 - Do not allow options that require calls to exec to be enabled
500 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
501 bug 12043; bugfix on 0.2.5.1-alpha.
502 - Handle failures in getpwnam()/getpwuid() when running with the
503 User option set and the Linux syscall sandbox enabled. Fixes bug
504 11946; bugfix on 0.2.5.1-alpha.
505 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
506 to avoid calling getaddrinfo() after installing the sandbox
507 filters. Previously, it preloaded a cache with the IPv4 address
508 for our hostname, and nothing else. Now, it loads the cache with
509 every address that it used to initialize the Tor process. Fixes
510 bug 11970; bugfix on 0.2.5.1-alpha.
512 o Minor bugfixes (pluggable transports):
513 - Enable the ExtORPortCookieAuthFile option, to allow changing the
514 default location of the authentication token for the extended OR
515 Port as used by sever-side pluggable transports. We had
516 implemented this option before, but the code to make it settable
517 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
518 - Avoid another 60-second delay when starting Tor in a pluggable-
519 transport-using configuration when we already have cached
520 descriptors for our bridges. Fixes bug 11965; bugfix
523 o Minor bugfixes (client):
524 - Avoid "Tried to open a socket with DisableNetwork set" warnings
525 when starting a client with bridges configured and DisableNetwork
526 set. (Tor launcher starts Tor with DisableNetwork set the first
527 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
529 o Minor bugfixes (testing):
530 - The Python parts of the test scripts now work on Python 3 as well
531 as Python 2, so systems where '/usr/bin/python' is Python 3 will
532 no longer have the tests break. Fixes bug 11608; bugfix
534 - When looking for versions of python that we could run the tests
535 with, check for "python2.7" and "python3.3"; previously we were
536 only looking for "python", "python2", and "python3". Patch from
537 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
538 - Fix all valgrind warnings produced by the unit tests. There were
539 over a thousand memory leak warnings previously, mostly produced
540 by forgetting to free things in the unit test code. Fixes bug
541 11618, bugfixes on many versions of Tor.
543 o Minor bugfixes (tor-fw-helper):
544 - Give a correct log message when tor-fw-helper fails to launch.
545 (Previously, we would say something like "tor-fw-helper sent us a
546 string we could not parse".) Fixes bug 9781; bugfix
549 o Minor bugfixes (relay, threading):
550 - Check return code on spawn_func() in cpuworker code, so that we
551 don't think we've spawned a nonworking cpuworker and write junk to
552 it forever. Fix related to bug 4345; bugfix on all released Tor
553 versions. Found by "skruffy".
554 - Use a pthread_attr to make sure that spawn_func() cannot return an
555 error while at the same time launching a thread. Fix related to
556 bug 4345; bugfix on all released Tor versions. Reported
559 o Minor bugfixes (relay, oom prevention):
560 - Correctly detect the total available system memory. We tried to do
561 this in 0.2.5.4-alpha, but the code was set up to always return an
562 error value, even on success. Fixes bug 11805; bugfix
565 o Minor bugfixes (relay, other):
566 - We now drop CREATE cells for already-existent circuit IDs and for
567 zero-valued circuit IDs, regardless of other factors that might
568 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
570 - Avoid an illegal read from stack when initializing the TLS module
571 using a version of OpenSSL without all of the ciphers used by the
572 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
574 - When rejecting DATA cells for stream_id zero, still count them
575 against the circuit's deliver window so that we don't fail to send
576 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
578 o Minor bugfixes (logging):
579 - Fix a misformatted log message about delayed directory fetches.
580 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
581 - Squelch a spurious LD_BUG message "No origin circuit for
582 successful SOCKS stream" in certain hidden service failure cases;
586 - Include a tor.service file in contrib/dist for use with systemd.
587 Some distributions will be able to use this file unmodified;
588 others will need to tweak it, or write their own. Patch from Jamie
589 Nguyen; resolves ticket 8368.
592 - Clean up several option names in the manpage to match their real
593 names, add the missing documentation for a couple of testing and
594 directory authority options, remove the documentation for a
595 V2-directory fetching option that no longer exists. Resolves
597 - Correct the documenation so that it lists the correct directory
598 for the stats files. (They are in a subdirectory called "stats",
600 - In the manpage, move more authority-only options into the
601 directory authority section so that operators of regular directory
602 caches don't get confused.
605 - The contrib directory has been sorted and tidied. Before, it was
606 an unsorted dumping ground for useful and not-so-useful things.
607 Now, it is divided based on functionality, and the items which
608 seemed to be nonfunctional or useless have been removed. Resolves
609 ticket 8966; based on patches from "rl1987".
612 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
613 and MTBF calculations, but that nobody was using. Fixes #11742.
614 - The TunnelDirConns and PreferTunnelledDirConns options no longer
615 exist; tunneled directory connections have been available since
616 0.1.2.5-alpha, and turning them off is not a good idea. This is a
617 brute-force fix for 10849, where "TunnelDirConns 0" would break
621 Changes in version 0.2.4.22 - 2014-05-16
622 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
623 alpha release series. These include blocking all authority signing
624 keys that may have been affected by the OpenSSL "heartbleed" bug,
625 choosing a far more secure set of TLS ciphersuites by default, closing
626 a couple of memory leaks that could be used to run a target relay out
627 of RAM, and several others.
629 o Major features (security, backport from 0.2.5.4-alpha):
630 - Block authority signing keys that were used on authorities
631 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
632 don't have any evidence that these keys _were_ compromised; we're
633 doing this to be prudent.) Resolves ticket 11464.
635 o Major bugfixes (security, OOM):
636 - Fix a memory leak that could occur if a microdescriptor parse
637 fails during the tokenizing step. This bug could enable a memory
638 exhaustion attack by directory servers. Fixes bug 11649; bugfix
641 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
642 - The relay ciphersuite list is now generated automatically based on
643 uniform criteria, and includes all OpenSSL ciphersuites with
644 acceptable strength and forward secrecy. Previously, we had left
645 some perfectly fine ciphersuites unsupported due to omission or
646 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
647 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
648 - Relays now trust themselves to have a better view than clients of
649 which TLS ciphersuites are better than others. (Thanks to bug
650 11513, the relay list is now well-considered, whereas the client
651 list has been chosen mainly for anti-fingerprinting purposes.)
652 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
653 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
654 AES128. Resolves ticket 11528.
655 - Clients now try to advertise the same list of ciphersuites as
656 Firefox 28. This change enables selection of (fast) GCM
657 ciphersuites, disables some strange old ciphers, and stops
658 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
659 Resolves ticket 11438.
661 o Minor bugfixes (configuration, security):
662 - When running a hidden service, do not allow TunneledDirConns 0:
663 trying to set that option together with a hidden service would
664 otherwise prevent the hidden service from running, and also make
665 it publish its descriptors directly over HTTP. Fixes bug 10849;
666 bugfix on 0.2.1.1-alpha.
668 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
669 - Avoid sending a garbage value to the controller when a circuit is
670 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
672 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
673 - Stop leaking memory when we successfully resolve a PTR record.
674 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
676 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
677 - Avoid 60-second delays in the bootstrapping process when Tor is
678 launching for a second time while using bridges. Fixes bug 9229;
679 bugfix on 0.2.0.3-alpha.
681 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
682 - Give the correct URL in the warning message when trying to run a
683 relay on an ancient version of Windows. Fixes bug 9393.
685 o Minor bugfixes (compilation):
686 - Fix a compilation error when compiling with --disable-curve25519.
687 Fixes bug 9700; bugfix on 0.2.4.17-rc.
690 - Downgrade the warning severity for the the "md was still
691 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
692 for trying to diagnose this bug, and the current warning in
693 earlier versions of tor achieves nothing useful. Addresses warning
696 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
697 - When we run out of usable circuit IDs on a channel, log only one
698 warning for the whole channel, and describe how many circuits
699 there were on the channel. Fixes part of ticket 11553.
701 o Minor features (security, backport from 0.2.5.4-alpha):
702 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
703 leave the default at 8GBytes), to better support Raspberry Pi
704 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
706 o Documentation (backport from 0.2.5.4-alpha):
707 - Correctly document that we search for a system torrc file before
708 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
712 Changes in version 0.2.5.4-alpha - 2014-04-25
713 Tor 0.2.5.4-alpha includes several security and performance
714 improvements for clients and relays, including blacklisting authority
715 signing keys that were used while susceptible to the OpenSSL
716 "heartbleed" bug, fixing two expensive functions on busy relays,
717 improved TLS ciphersuite preference lists, support for run-time
718 hardening on compilers that support AddressSanitizer, and more work on
719 the Linux sandbox code.
721 There are also several usability fixes for clients (especially clients
722 that use bridges), two new TransPort protocols supported (one on
723 OpenBSD, one on FreeBSD), and various other bugfixes.
725 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
726 have accumulated many known flaws; everyone should upgrade.
728 o Major features (security):
729 - If you don't specify MaxMemInQueues yourself, Tor now tries to
730 pick a good value based on your total system memory. Previously,
731 the default was always 8 GB. You can still override the default by
732 setting MaxMemInQueues yourself. Resolves ticket 11396.
733 - Block authority signing keys that were used on authorities
734 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
735 don't have any evidence that these keys _were_ compromised; we're
736 doing this to be prudent.) Resolves ticket 11464.
738 o Major features (relay performance):
739 - Speed up server-side lookups of rendezvous and introduction point
740 circuits by using hashtables instead of linear searches. These
741 functions previously accounted between 3 and 7% of CPU usage on
742 some busy relays. Resolves ticket 9841.
743 - Avoid wasting CPU when extending a circuit over a channel that is
744 nearly out of circuit IDs. Previously, we would do a linear scan
745 over possible circuit IDs before finding one or deciding that we
746 had exhausted our possibilities. Now, we try at most 64 random
747 circuit IDs before deciding that we probably won't succeed. Fixes
748 a possible root cause of ticket 11553.
750 o Major features (seccomp2 sandbox, Linux only):
751 - The seccomp2 sandbox can now run a test network for multiple hours
752 without crashing. The sandbox is still experimental, and more bugs
753 will probably turn up. To try it, enable "Sandbox 1" on a Linux
754 host. Resolves ticket 11351.
755 - Strengthen sandbox code: the sandbox can now test the arguments
756 for rename(), and blocks _sysctl() entirely. Resolves another part
758 - When the sandbox blocks a system call, it now tries to log a stack
759 trace before exiting. Resolves ticket 11465.
761 o Major bugfixes (TLS cipher selection):
762 - The relay ciphersuite list is now generated automatically based on
763 uniform criteria, and includes all OpenSSL ciphersuites with
764 acceptable strength and forward secrecy. Previously, we had left
765 some perfectly fine ciphersuites unsupported due to omission or
766 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
767 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
768 - Relays now trust themselves to have a better view than clients of
769 which TLS ciphersuites are better than others. (Thanks to bug
770 11513, the relay list is now well-considered, whereas the client
771 list has been chosen mainly for anti-fingerprinting purposes.)
772 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
773 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
774 AES128. Resolves ticket 11528.
775 - Clients now try to advertise the same list of ciphersuites as
776 Firefox 28. This change enables selection of (fast) GCM
777 ciphersuites, disables some strange old ciphers, and stops
778 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
779 Resolves ticket 11438.
781 o Major bugfixes (bridge client):
782 - Avoid 60-second delays in the bootstrapping process when Tor is
783 launching for a second time while using bridges. Fixes bug 9229;
784 bugfix on 0.2.0.3-alpha.
786 o Minor features (transparent proxy, *BSD):
787 - Support FreeBSD's ipfw firewall interface for TransPort ports on
788 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
789 10267; patch from "yurivict".
790 - Support OpenBSD's divert-to rules with the pf firewall for
791 transparent proxy ports. To enable it, set "TransProxyType
792 pf-divert". This allows Tor to run a TransPort transparent proxy
793 port on OpenBSD 4.4 or later without root privileges. See the
794 pf.conf(5) manual page for information on configuring pf to use
795 divert-to rules. Closes ticket 10896; patch from Dana Koch.
797 o Minor features (security):
798 - New --enable-expensive-hardening option to enable security
799 hardening options that consume nontrivial amounts of CPU and
800 memory. Right now, this includes AddressSanitizer and UbSan, which
801 are supported in newer versions of GCC and Clang. Closes ticket
804 o Minor features (log verbosity):
805 - Demote the message that we give when a flushing connection times
806 out for too long from NOTICE to INFO. It was usually meaningless.
807 Resolves ticket 5286.
808 - Don't log so many notice-level bootstrapping messages at startup
809 about downloading descriptors. Previously, we'd log a notice
810 whenever we learned about more routers. Now, we only log a notice
811 at every 5% of progress. Fixes bug 9963.
812 - Warn less verbosely when receiving a malformed
813 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
814 - When we run out of usable circuit IDs on a channel, log only one
815 warning for the whole channel, and describe how many circuits
816 there were on the channel. Fixes part of ticket 11553.
818 o Minor features (relay):
819 - If a circuit timed out for at least 3 minutes, check if we have a
820 new external IP address, and publish a new descriptor with the new
821 IP address if it changed. Resolves ticket 2454.
823 o Minor features (controller):
824 - Make the entire exit policy available from the control port via
825 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
827 - Because of the fix for ticket 11396, the real limit for memory
828 usage may no longer match the configured MaxMemInQueues value. The
829 real limit is now exposed via GETINFO limits/max-mem-in-queues.
831 o Minor features (bridge client):
832 - Report a more useful failure message when we can't connect to a
833 bridge because we don't have the right pluggable transport
834 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
836 o Minor features (diagnostic):
837 - Add more log messages to diagnose bug 7164, which causes
838 intermittent "microdesc_free() called but md was still referenced"
839 warnings. We now include more information, to figure out why we
840 might be cleaning a microdescriptor for being too old if it's
841 still referenced by a live node_t object.
843 o Minor bugfixes (client, DNSPort):
844 - When using DNSPort, try to respond to AAAA requests with AAAA
845 answers. Previously, we hadn't looked at the request type when
846 deciding which answer type to prefer. Fixes bug 10468; bugfix on
848 - When receiving a DNS query for an unsupported record type, reply
849 with no answer rather than with a NOTIMPL error. This behavior
850 isn't correct either, but it will break fewer client programs, we
851 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
854 o Minor bugfixes (exit relay):
855 - Stop leaking memory when we successfully resolve a PTR record.
856 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
858 o Minor bugfixes (bridge client):
859 - Stop accepting bridge lines containing hostnames. Doing so would
860 cause clients to perform DNS requests on the hostnames, which was
861 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
862 - Avoid a 60-second delay in the bootstrapping process when a Tor
863 client with pluggable transports re-reads its configuration at
864 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
866 o Minor bugfixes (client, logging during bootstrap):
867 - Warn only once if we start logging in an unsafe way. Previously,
868 we complain as many times as we had problems. Fixes bug 9870;
869 bugfix on 0.2.5.1-alpha.
870 - Only report the first fatal bootstrap error on a given OR
871 connection. This stops us from telling the controller bogus error
872 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
873 - Be more helpful when trying to run sandboxed on Linux without
874 libseccomp. Instead of saying "Sandbox is not implemented on this
875 platform", we now explain that we need to be built with
876 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
877 - Avoid generating spurious warnings when starting with
878 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
881 o Minor bugfixes (closing OR connections):
882 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
883 check if it's an or_connection_t and correctly call
884 connection_or_close_for_error() rather than
885 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
887 - When closing all connections on setting DisableNetwork to 1, use
888 connection_or_close_normally() rather than closing OR connections
889 out from under the channel layer. Fixes bug 11306; bugfix on
892 o Minor bugfixes (controller):
893 - Avoid sending a garbage value to the controller when a circuit is
894 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
896 o Minor bugfixes (tor-fw-helper):
897 - Allow tor-fw-helper to build again by adding src/ext to its
898 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
900 o Minor bugfixes (bridges):
901 - Avoid potential crashes or bad behavior when launching a
902 server-side managed proxy with ORPort or ExtORPort temporarily
903 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
905 o Minor bugfixes (platform-specific):
906 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
907 bug 11426; bugfix on 0.2.5.3-alpha.
908 - When dumping a malformed directory object to disk, save it in
909 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
911 - Don't report failures from make_socket_reuseable() on incoming
912 sockets on OSX: this can happen when incoming connections close
913 early. Fixes bug 10081.
915 o Minor bugfixes (trivial memory leaks):
916 - Fix a small memory leak when signing a directory object. Fixes bug
917 11275; bugfix on 0.2.4.13-alpha.
918 - Free placeholder entries in our circuit table at exit; fixes a
919 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
920 - Don't re-initialize a second set of OpenSSL mutexes when starting
921 up. Previously, we'd make one set of mutexes, and then immediately
922 replace them with another. Fixes bug 11726; bugfix on
924 - Resolve some memory leaks found by coverity in the unit tests, on
925 exit in tor-gencert, and on a failure to compute digests for our
926 own keys when generating a v3 networkstatus vote. These leaks
927 should never have affected anyone in practice.
929 o Minor bugfixes (hidden service):
930 - Only retry attempts to connect to a chosen rendezvous point 8
931 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
933 o Minor bugfixes (misc code correctness):
934 - Fix various instances of undefined behavior in channeltls.c,
935 tor_memmem(), and eventdns.c that would cause us to construct
936 pointers to memory outside an allocated object. (These invalid
937 pointers were not accessed, but C does not even allow them to
938 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
939 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
940 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
941 fix some miscellaneous errors in our tests and codebase. Fixes bug
942 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
943 - Always check return values for unlink, munmap, UnmapViewOfFile;
944 check strftime return values more often. In some cases all we can
945 do is report a warning, but this may help prevent deeper bugs from
946 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
948 - Fix numerous warnings from the clang "scan-build" static analyzer.
949 Some of these are programming style issues; some of them are false
950 positives that indicated awkward code; some are undefined behavior
951 cases related to constructing (but not using) invalid pointers;
952 some are assumptions about API behavior; some are (harmlessly)
953 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
954 correct; and one or two are genuine bugs that weren't reachable
955 from the rest of the program. Fixes bug 8793; bugfixes on many,
959 - Build the torify.1 manpage again. Previously, we were only trying
960 to build it when also building tor-fw-helper. That's why we didn't
961 notice that we'd broken the ability to build it. Fixes bug 11321;
962 bugfix on 0.2.5.1-alpha.
963 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
964 11061; bugfix on 0.2.4.7-alpha.
965 - Correctly document that we search for a system torrc file before
966 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
968 - Resolve warnings from Doxygen.
970 o Code simplifications and refactoring:
971 - Remove is_internal_IP() function. Resolves ticket 4645.
972 - Remove unused function circuit_dump_by_chan from circuitlist.c.
973 Closes issue 9107; patch from "marek".
974 - Change our use of the ENUM_BF macro to avoid declarations that
977 o Deprecated versions:
978 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
979 attention for some while. Directory authorities no longer accept
980 descriptors from relays running any version of Tor prior to Tor
981 0.2.3.16-alpha. Resolves ticket 11149.
984 - New macros in test.h to simplify writing mock-functions for unit
985 tests. Part of ticket 11507. Patch from Dana Koch.
986 - Complete tests for the status.c module. Resolves ticket 11507.
987 Patch from Dana Koch.
990 - Remove all code for the long unused v1 directory protocol.
991 Resolves ticket 11070.
994 Changes in version 0.2.5.3-alpha - 2014-03-22
995 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
996 two new anti-DoS features for Tor relays, resolves a bug that kept
997 SOCKS5 support for IPv6 from working, fixes several annoying usability
998 issues for bridge users, and removes more old code for unused
1001 The Tor 0.2.5.x release series is now in patch-freeze: no feature
1002 patches not already written will be considered for inclusion in 0.2.5.x.
1004 o Major features (relay security, DoS-resistance):
1005 - When deciding whether we have run out of memory and we need to
1006 close circuits, also consider memory allocated in buffers for
1007 streams attached to each circuit.
1009 This change, which extends an anti-DoS feature introduced in
1010 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
1011 better resist more memory-based DoS attacks than before. Since the
1012 MaxMemInCellQueues option now applies to all queues, it is renamed
1013 to MaxMemInQueues. This feature fixes bug 10169.
1014 - Avoid hash-flooding denial-of-service attacks by using the secure
1015 SipHash-2-4 hash function for our hashtables. Without this
1016 feature, an attacker could degrade performance of a targeted
1017 client or server by flooding their data structures with a large
1018 number of entries to be stored at the same hash table position,
1019 thereby slowing down the Tor instance. With this feature, hash
1020 table positions are derived from a randomized cryptographic key,
1021 and an attacker cannot predict which entries will collide. Closes
1023 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
1024 the default at 8GBytes), to better support Raspberry Pi users. Fixes
1025 bug 9686; bugfix on 0.2.4.14-alpha.
1027 o Minor features (bridges, pluggable transports):
1028 - Bridges now write the SHA1 digest of their identity key
1029 fingerprint (that is, a hash of a hash of their public key) to
1030 notice-level logs, and to a new hashed-fingerprint file. This
1031 information will help bridge operators look up their bridge in
1032 Globe and similar tools. Resolves ticket 10884.
1033 - Improve the message that Tor displays when running as a bridge
1034 using pluggable transports without an Extended ORPort listener.
1035 Also, log the message in the log file too. Resolves ticket 11043.
1037 o Minor features (other):
1038 - Add a new option, PredictedPortsRelevanceTime, to control how long
1039 after having received a request to connect to a given port Tor
1040 will try to keep circuits ready in anticipation of future requests
1041 for that port. Patch from "unixninja92"; implements ticket 9176.
1042 - Generate a warning if any ports are listed in the SocksPolicy,
1043 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
1044 AuthDirBadExit options. (These options only support address
1045 ranges.) Fixes part of ticket 11108.
1046 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
1049 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
1050 - Build without warnings under clang 3.4. (We have some macros that
1051 define static functions only some of which will get used later in
1052 the module. Starting with clang 3.4, these give a warning unless the
1053 unused attribute is set on them.) Resolves ticket 10904.
1054 - Fix build warnings about missing "a2x" comment when building the
1055 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1056 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1058 o Minor bugfixes (client):
1059 - Improve the log message when we can't connect to a hidden service
1060 because all of the hidden service directory nodes hosting its
1061 descriptor are excluded. Improves on our fix for bug 10722, which
1062 was a bugfix on 0.2.0.10-alpha.
1063 - Raise a control port warning when we fail to connect to all of
1064 our bridges. Previously, we didn't inform the controller, and
1065 the bootstrap process would stall. Fixes bug 11069; bugfix on
1067 - Exit immediately when a process-owning controller exits.
1068 Previously, tor relays would wait for a little while after their
1069 controller exited, as if they had gotten an INT signal -- but this
1070 was problematic, since there was no feedback for the user. To do a
1071 clean shutdown, controllers should send an INT signal and give Tor
1072 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
1073 - Stop attempting to connect to bridges before our pluggable
1074 transports are configured (harmless but resulted in some erroneous
1075 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
1076 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
1077 generating incorrect SOCKS5 responses, and confusing client
1078 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
1080 o Minor bugfixes (relays and bridges):
1081 - Avoid crashing on a malformed resolv.conf file when running a
1082 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
1083 - Non-exit relays no longer launch mock DNS requests to check for
1084 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
1085 non-exit relays stopped servicing DNS requests. Fixes bug 965;
1086 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
1087 - Bridges now report complete directory request statistics. Related
1088 to bug 5824; bugfix on 0.2.2.1-alpha.
1089 - Bridges now never collect statistics that were designed for
1090 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
1091 - Stop giving annoying warning messages when we decide not to launch
1092 a pluggable transport proxy that we don't need (because there are
1093 no bridges configured to use it). Resolves ticket 5018; bugfix
1095 - Give the correct URL in the warning message when trying to run a
1096 relay on an ancient version of Windows. Fixes bug 9393.
1098 o Minor bugfixes (backtrace support):
1099 - Support automatic backtraces on more platforms by using the
1100 "-fasynchronous-unwind-tables" compiler option. This option is
1101 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
1102 is on by default and table generation is not. This doesn't yet
1103 add Windows support; only Linux, OSX, and some BSDs are affected.
1104 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
1105 - Avoid strange behavior if two threads hit failed assertions at the
1106 same time and both try to log backtraces at once. (Previously, if
1107 this had happened, both threads would have stored their intermediate
1108 results in the same buffer, and generated junk outputs.) Reported by
1109 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
1110 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
1111 0.2.5.2-alpha; patch from Nick Hopper.
1113 o Minor bugfixes (unit tests):
1114 - Fix a small bug in the unit tests that might have made the tests
1115 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
1116 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
1119 - Remove all remaining code related to version-0 hidden service
1120 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
1121 the rest of bug 10841.
1124 - Document in the manpage that "KBytes" may also be written as
1125 "kilobytes" or "KB", that "Kbits" may also be written as
1126 "kilobits", and so forth. Closes ticket 9222.
1127 - Document that the ClientOnly config option overrides ORPort.
1128 Our old explanation made ClientOnly sound as though it did
1129 nothing at all. Resolves bug 9059.
1130 - Explain that SocksPolicy, DirPolicy, and similar options don't
1131 take port arguments. Fixes the other part of ticket 11108.
1132 - Fix a comment about the rend_server_descriptor_t.protocols field
1133 to more accurately describe its range. Also, make that field
1134 unsigned, to more accurately reflect its usage. Fixes bug 9099;
1135 bugfix on 0.2.1.5-alpha.
1136 - Fix the manpage's description of HiddenServiceAuthorizeClient:
1137 the maximum client name length is 16, not 19. Fixes bug 11118;
1138 bugfix on 0.2.1.6-alpha.
1140 o Code simplifications and refactoring:
1141 - Get rid of router->address, since in all cases it was just the
1142 string representation of router->addr. Resolves ticket 5528.
1144 o Test infrastructure:
1145 - Update to the latest version of tinytest.
1146 - Improve the tinytest implementation of string operation tests so
1147 that comparisons with NULL strings no longer crash the tests; they
1148 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
1151 Changes in version 0.2.4.21 - 2014-02-28
1152 Tor 0.2.4.21 further improves security against potential adversaries who
1153 find breaking 1024-bit crypto doable, and backports several stability
1154 and robustness patches from the 0.2.5 branch.
1156 o Major features (client security):
1157 - When we choose a path for a 3-hop circuit, make sure it contains
1158 at least one relay that supports the NTor circuit extension
1159 handshake. Otherwise, there is a chance that we're building
1160 a circuit that's worth attacking by an adversary who finds
1161 breaking 1024-bit crypto doable, and that chance changes the game
1162 theory. Implements ticket 9777.
1165 - Do not treat streams that fail with reason
1166 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1167 since it could also indicate an ENETUNREACH connection error. Fixes
1168 part of bug 10777; bugfix on 0.2.4.8-alpha.
1170 o Code simplification and refactoring:
1171 - Remove data structures which were introduced to implement the
1172 CellStatistics option: they are now redundant with the new timestamp
1173 field in the regular packed_cell_t data structure, which we did
1174 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
1177 - Always clear OpenSSL bignums before freeing them -- even bignums
1178 that don't contain secrets. Resolves ticket 10793. Patch by
1180 - Build without warnings under clang 3.4. (We have some macros that
1181 define static functions only some of which will get used later in
1182 the module. Starting with clang 3.4, these give a warning unless the
1183 unused attribute is set on them.) Resolves ticket 10904.
1184 - Update geoip and geoip6 files to the February 7 2014 Maxmind
1185 GeoLite2 Country database.
1188 - Set the listen() backlog limit to the largest actually supported
1189 on the system, not to the value in a header file. Fixes bug 9716;
1190 bugfix on every released Tor.
1191 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1192 exit node as a NOROUTE error, not an INTERNAL error, since they
1193 can apparently happen when trying to connect to the wrong sort
1194 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1195 - Fix build warnings about missing "a2x" comment when building the
1196 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1197 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1198 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1199 not entirely remove it from the connection lists. Fixes bug 9602;
1200 bugfix on 0.2.4.4-alpha.
1201 - Fix a segmentation fault in our benchmark code when running with
1202 Fedora's OpenSSL package, or any other OpenSSL that provides
1203 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1204 - Turn "circuit handshake stats since last time" log messages into a
1205 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1207 o Documentation fixes:
1208 - Document that all but one DirPort entry must have the NoAdvertise
1209 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1212 Changes in version 0.2.5.2-alpha - 2014-02-13
1213 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
1214 like the "poor random number generation" fix and the "building too many
1215 circuits" fix. It also further improves security against potential
1216 adversaries who find breaking 1024-bit crypto doable, and launches
1217 pluggable transports on demand (which gets us closer to integrating
1218 pluggable transport support by default -- not to be confused with Tor
1219 bundles enabling pluggable transports and bridges by default).
1221 o Major features (client security):
1222 - When we choose a path for a 3-hop circuit, make sure it contains
1223 at least one relay that supports the NTor circuit extension
1224 handshake. Otherwise, there is a chance that we're building
1225 a circuit that's worth attacking by an adversary who finds
1226 breaking 1024-bit crypto doable, and that chance changes the game
1227 theory. Implements ticket 9777.
1228 - Clients now look at the "usecreatefast" consensus parameter to
1229 decide whether to use CREATE_FAST or CREATE cells for the first hop
1230 of their circuit. This approach can improve security on connections
1231 where Tor's circuit handshake is stronger than the available TLS
1232 connection security levels, but the tradeoff is more computational
1233 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1235 o Major features (bridges):
1236 - Don't launch pluggable transport proxies if we don't have any
1237 bridges configured that would use them. Now we can list many
1238 pluggable transports, and Tor will dynamically start one when it
1239 hears a bridge address that needs it. Resolves ticket 5018.
1240 - The bridge directory authority now assigns status flags (Stable,
1241 Guard, etc) to bridges based on thresholds calculated over all
1242 Running bridges. Now bridgedb can finally make use of its features
1243 to e.g. include at least one Stable bridge in its answers. Fixes
1246 o Major features (other):
1247 - Extend ORCONN controller event to include an "ID" parameter,
1248 and add four new controller event types CONN_BW, CIRC_BW,
1249 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
1250 The new events are emitted in private Tor networks only, with the
1251 goal of being able to better track performance and load during
1252 full-network simulations. Implements proposal 218 and ticket 7359.
1253 - On some platforms (currently: recent OSX versions, glibc-based
1254 platforms that support the ELF format, and a few other
1255 Unix-like operating systems), Tor can now dump stack traces
1256 when a crash occurs or an assertion fails. By default, traces
1257 are dumped to stderr (if possible) and to any logs that are
1258 reporting errors. Implements ticket 9299.
1261 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1262 not entirely remove it from the connection lists. Fixes bug 9602;
1263 bugfix on 0.2.4.4-alpha.
1264 - Do not treat streams that fail with reason
1265 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1266 since it could also indicate an ENETUNREACH connection error. Fixes
1267 part of bug 10777; bugfix on 0.2.4.8-alpha.
1269 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1270 - Do not allow OpenSSL engines to replace the PRNG, even when
1271 HardwareAccel is set. The only default builtin PRNG engine uses
1272 the Intel RDRAND instruction to replace the entire PRNG, and
1273 ignores all attempts to seed it with more entropy. That's
1274 cryptographically stupid: the right response to a new alleged
1275 entropy source is never to discard all previously used entropy
1276 sources. Fixes bug 10402; works around behavior introduced in
1277 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1279 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1280 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1281 - Avoid launching spurious extra circuits when a stream is pending.
1282 This fixes a bug where any circuit that _wasn't_ unusable for new
1283 streams would be treated as if it were, causing extra circuits to
1284 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1286 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1287 - No longer stop reading or writing on cpuworker connections when
1288 our rate limiting buckets go empty. Now we should handle circuit
1289 handshake requests more promptly. Resolves bug 9731.
1290 - Stop trying to bootstrap all our directory information from
1291 only our first guard. Discovered while fixing bug 9946; bugfix
1294 o Minor features (bridges, pluggable transports):
1295 - Add threshold cutoffs to the networkstatus document created by
1296 the Bridge Authority. Fixes bug 1117.
1297 - On Windows, spawn background processes using the CREATE_NO_WINDOW
1298 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
1299 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
1300 Vidalia set this option for us.) Implements ticket 10297.
1302 o Minor features (security):
1303 - Always clear OpenSSL bignums before freeing them -- even bignums
1304 that don't contain secrets. Resolves ticket 10793. Patch by
1307 o Minor features (config options and command line):
1308 - Add an --allow-missing-torrc commandline option that tells Tor to
1309 run even if the configuration file specified by -f is not available.
1310 Implements ticket 10060.
1311 - Add support for the TPROXY transparent proxying facility on Linux.
1312 See documentation for the new TransProxyType option for more
1313 details. Implementation by "thomo". Closes ticket 10582.
1315 o Minor features (controller):
1316 - Add a new "HS_DESC" controller event that reports activities
1317 related to hidden service descriptors. Resolves ticket 8510.
1318 - New "DROPGUARDS" controller command to forget all current entry
1319 guards. Not recommended for ordinary use, since replacing guards
1320 too frequently makes several attacks easier. Resolves ticket 9934;
1323 o Minor features (build):
1324 - Assume that a user using ./configure --host wants to cross-compile,
1325 and give an error if we cannot find a properly named
1326 tool-chain. Add a --disable-tool-name-check option to proceed
1327 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
1328 - If we run ./configure and the compiler recognizes -fstack-protector
1329 but the linker rejects it, warn the user about a potentially missing
1330 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
1332 o Minor features (testing):
1333 - If Python is installed, "make check" now runs extra tests beyond
1334 the unit test scripts.
1335 - When bootstrapping a test network, sometimes very few relays get
1336 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
1337 specify a set of relays which should be voted Guard regardless of
1338 their uptime or bandwidth. Addresses ticket 9206.
1340 o Minor features (log messages):
1341 - When ServerTransportPlugin is set on a bridge, Tor can write more
1342 useful statistics about bridge use in its extrainfo descriptors,
1343 but only if the Extended ORPort ("ExtORPort") is set too. Add a
1344 log message to inform the user in this case. Resolves ticket 9651.
1345 - When receiving a new controller connection, log the origin address.
1346 Resolves ticket 9698; patch from "sigpipe".
1347 - When logging OpenSSL engine status at startup, log the status of
1348 more engines. Fixes ticket 10043; patch from Joshua Datko.
1349 - Turn "circuit handshake stats since last time" log messages into a
1350 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1352 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1353 - Improve the circuit queue out-of-memory handler. Previously, when
1354 we ran low on memory, we'd close whichever circuits had the most
1355 queued cells. Now, we close those that have the *oldest* queued
1356 cells, on the theory that those are most responsible for us
1357 running low on memory. Based on analysis from a forthcoming paper
1358 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1359 - Generate bootstrapping status update events correctly when fetching
1360 microdescriptors. Fixes bug 9927.
1361 - Update to the October 2 2013 Maxmind GeoLite Country database.
1363 o Minor bugfixes (clients):
1364 - When closing a channel that has already been open, do not close
1365 pending circuits that were waiting to connect to the same relay.
1366 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
1369 o Minor bugfixes (relays):
1370 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1371 exit node as a NOROUTE error, not an INTERNAL error, since they
1372 can apparently happen when trying to connect to the wrong sort
1373 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1375 o Minor bugfixes (bridges):
1376 - Fix a bug where the first connection works to a bridge that uses a
1377 pluggable transport with client-side parameters, but we don't send
1378 the client-side parameters on subsequent connections. (We don't
1379 use any pluggable transports with client-side parameters yet,
1380 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
1381 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
1383 o Minor bugfixes (node selection):
1384 - If ExcludeNodes is set, consider non-excluded hidden service
1385 directory servers before excluded ones. Do not consider excluded
1386 hidden service directory servers at all if StrictNodes is
1387 set. (Previously, we would sometimes decide to connect to those
1388 servers, and then realize before we initiated a connection that
1389 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
1391 - If we set the ExitNodes option but it doesn't include any nodes
1392 that have the Exit flag, we would choose not to bootstrap. Now we
1393 bootstrap so long as ExitNodes includes nodes which can exit to
1394 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
1396 o Minor bugfixes (controller and command-line):
1397 - If changing a config option via "setconf" fails in a recoverable
1398 way, we used to nonetheless write our new control ports to the
1399 file described by the "ControlPortWriteToFile" option. Now we only
1400 write out that file if we successfully switch to the new config
1401 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
1402 - When a command-line option such as --version or --help that
1403 ordinarily implies --hush appears on the command line along with
1404 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
1405 only if it appeared later on the command line. Fixes bug 9578;
1406 bugfix on 0.2.5.1-alpha.
1408 o Minor bugfixes (code correctness):
1409 - Previously we used two temporary files when writing descriptors to
1410 disk; now we only use one. Fixes bug 1376.
1411 - Remove an erroneous (but impossible and thus harmless) pointer
1412 comparison that would have allowed compilers to skip a bounds
1413 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
1414 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
1415 - Fix an always-true assertion in pluggable transports code so it
1416 actually checks what it was trying to check. Fixes bug 10046;
1417 bugfix on 0.2.3.9-alpha. Found by "dcb".
1419 o Minor bugfixes (protocol correctness):
1420 - When receiving a VERSIONS cell with an odd number of bytes, close
1421 the connection immediately since the cell is malformed. Fixes bug
1422 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
1425 o Minor bugfixes (build):
1426 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
1427 turned off (that is, without support for v2 link handshakes). Fixes
1428 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
1429 - Fix compilation warnings and startup issues when running with
1430 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
1432 - Fix compilation on Solaris 9, which didn't like us having an
1433 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
1435 o Minor bugfixes (testing):
1436 - Fix a segmentation fault in our benchmark code when running with
1437 Fedora's OpenSSL package, or any other OpenSSL that provides
1438 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1440 o Minor bugfixes (log messages):
1441 - Fix a bug where clients using bridges would report themselves
1442 as 50% bootstrapped even without a live consensus document.
1443 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
1444 - Suppress a warning where, if there's only one directory authority
1445 in the network, we would complain that votes and signatures cannot
1446 be uploaded to other directory authorities. Fixes bug 10842;
1447 bugfix on 0.2.2.26-beta.
1448 - Report bootstrapping progress correctly when we're downloading
1449 microdescriptors. We had updated our "do we have enough microdescs
1450 to begin building circuits?" logic most recently in 0.2.4.10-alpha
1451 (see bug 5956), but we left the bootstrap status event logic at
1452 "how far through getting 1/4 of them are we?" Fixes bug 9958;
1453 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
1455 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1456 - Avoid a crash bug when starting with a corrupted microdescriptor
1457 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1458 - If we fail to dump a previously cached microdescriptor to disk, avoid
1459 freeing duplicate data later on. Fixes bug 10423; bugfix on
1460 0.2.4.13-alpha. Spotted by "bobnomnom".
1462 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1463 - Correctly log long IPv6 exit policies, instead of truncating them
1464 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1465 - Our default TLS ecdhe groups were backwards: we meant to be using
1466 P224 for relays (for performance win) and P256 for bridges (since
1467 it is more common in the wild). Instead we had it backwards. After
1468 reconsideration, we decided that the default should be P256 on all
1469 hosts, since its security is probably better, and since P224 is
1470 reportedly used quite little in the wild. Found by "skruffy" on
1471 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1472 - Free directory authority certificate download statuses on exit
1473 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1475 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1476 - If the guard we choose first doesn't answer, we would try the
1477 second guard, but once we connected to the second guard we would
1478 abandon it and retry the first one, slowing down bootstrapping.
1479 The fix is to treat all our initially chosen guards as acceptable
1480 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1481 - Fix an assertion failure that would occur when disabling the
1482 ORPort setting on a running Tor process while accounting was
1483 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1484 - When examining the list of network interfaces to find our address,
1485 do not consider non-running or disabled network interfaces. Fixes
1486 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1487 - Avoid an off-by-one error when checking buffer boundaries when
1488 formatting the exit status of a pluggable transport helper.
1489 This is probably not an exploitable bug, but better safe than
1490 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1493 o Removed code and features:
1494 - Clients now reject any directory authority certificates lacking
1495 a dir-key-crosscert element. These have been included since
1496 0.2.1.9-alpha, so there's no real reason for them to be optional
1497 any longer. Completes proposal 157. Resolves ticket 10162.
1498 - Remove all code that existed to support the v2 directory system,
1499 since there are no longer any v2 directory authorities. Resolves
1501 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
1502 options, which were used for designating authorities as "Hidden
1503 service authorities". There has been no use of hidden service
1504 authorities since 0.2.2.1-alpha, when we stopped uploading or
1505 downloading v0 hidden service descriptors. Fixes bug 10881; also
1506 part of a fix for bug 10841.
1508 o Code simplification and refactoring:
1509 - Remove some old fallback code designed to keep Tor clients working
1510 in a network with only two working relays. Elsewhere in the code we
1511 have long since stopped supporting such networks, so there wasn't
1512 much point in keeping it around. Addresses ticket 9926.
1513 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
1514 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
1515 - Remove data structures which were introduced to implement the
1516 CellStatistics option: they are now redundant with the addition
1517 of a timestamp to the regular packed_cell_t data structure, which
1518 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
1521 o Documentation (man page) fixes:
1522 - Update manpage to describe some of the files you can expect to
1523 find in Tor's DataDirectory. Addresses ticket 9839.
1524 - Document that all but one DirPort entry must have the NoAdvertise
1525 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1527 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1528 - Clarify the usage and risks of setting the ContactInfo torrc line
1529 for your relay or bridge. Resolves ticket 9854.
1530 - Add anchors to the manpage so we can link to the html version of
1531 the documentation for specific options. Resolves ticket 9866.
1532 - Replace remaining references to DirServer in man page and
1533 log entries. Resolves ticket 10124.
1536 - Make the "tor-gencert" tool used by directory authority operators
1537 create 2048-bit signing keys by default (rather than 1024-bit, since
1538 1024-bit is uncomfortably small these days). Addresses ticket 10324.
1541 Changes in version 0.2.4.20 - 2013-12-22
1542 Tor 0.2.4.20 fixes potentially poor random number generation for users
1543 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
1544 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
1545 and 4) have no state file in their DataDirectory (as would happen on
1546 first start). Users who generated relay or hidden service identity
1547 keys in such a situation should discard them and generate new ones.
1549 This release also fixes a logic error that caused Tor clients to build
1550 many more preemptive circuits than they actually need.
1553 - Do not allow OpenSSL engines to replace the PRNG, even when
1554 HardwareAccel is set. The only default builtin PRNG engine uses
1555 the Intel RDRAND instruction to replace the entire PRNG, and
1556 ignores all attempts to seed it with more entropy. That's
1557 cryptographically stupid: the right response to a new alleged
1558 entropy source is never to discard all previously used entropy
1559 sources. Fixes bug 10402; works around behavior introduced in
1560 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1562 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1563 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1564 - Avoid launching spurious extra circuits when a stream is pending.
1565 This fixes a bug where any circuit that _wasn't_ unusable for new
1566 streams would be treated as if it were, causing extra circuits to
1567 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1570 - Avoid a crash bug when starting with a corrupted microdescriptor
1571 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1572 - If we fail to dump a previously cached microdescriptor to disk, avoid
1573 freeing duplicate data later on. Fixes bug 10423; bugfix on
1574 0.2.4.13-alpha. Spotted by "bobnomnom".
1577 Changes in version 0.2.4.19 - 2013-12-11
1578 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
1579 (1986-2013). Aaron worked on diverse projects including helping to guide
1580 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
1581 transparency to the U.S government's PACER documents, and contributing
1582 design and development for Tor and Tor2Web. Aaron was one of the latest
1583 martyrs in our collective fight for civil liberties and human rights,
1584 and his death is all the more painful because he was one of us.
1586 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
1587 a new circuit handshake and link encryption that use ECC to provide
1588 better security and efficiency; makes relays better manage circuit
1589 creation requests; uses "directory guards" to reduce client enumeration
1590 risks; makes bridges collect and report statistics about the pluggable
1591 transports they support; cleans up and improves our geoip database;
1592 gets much closer to IPv6 support for clients, bridges, and relays; makes
1593 directory authorities use measured bandwidths rather than advertised
1594 ones when computing flags and thresholds; disables client-side DNS
1595 caching to reduce tracking risks; and fixes a big bug in bridge
1596 reachability testing. This release introduces two new design
1597 abstractions in the code: a new "channel" abstraction between circuits
1598 and or_connections to allow for implementing alternate relay-to-relay
1599 transports, and a new "circuitmux" abstraction storing the queue of
1600 circuits for a channel. The release also includes many stability,
1601 security, and privacy fixes.
1604 Changes in version 0.2.4.18-rc - 2013-11-16
1605 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
1606 series. It takes a variety of fixes from the 0.2.5.x branch to improve
1607 stability, performance, and better handling of edge cases.
1610 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1611 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1612 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1613 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1614 them to solve bug 6033.)
1617 - No longer stop reading or writing on cpuworker connections when
1618 our rate limiting buckets go empty. Now we should handle circuit
1619 handshake requests more promptly. Resolves bug 9731.
1620 - If we are unable to save a microdescriptor to the journal, do not
1621 drop it from memory and then reattempt downloading it. Fixes bug
1622 9645; bugfix on 0.2.2.6-alpha.
1623 - Stop trying to bootstrap all our directory information from
1624 only our first guard. Discovered while fixing bug 9946; bugfix
1626 - The new channel code sometimes lost track of in-progress circuits,
1627 causing long-running clients to stop building new circuits. The
1628 fix is to always call circuit_n_chan_done(chan, 0) from
1629 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1631 o Minor bugfixes (on 0.2.4.x):
1632 - Correctly log long IPv6 exit policies, instead of truncating them
1633 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1634 - Our default TLS ecdhe groups were backwards: we meant to be using
1635 P224 for relays (for performance win) and P256 for bridges (since
1636 it is more common in the wild). Instead we had it backwards. After
1637 reconsideration, we decided that the default should be P256 on all
1638 hosts, since its security is probably better, and since P224 is
1639 reportedly used quite little in the wild. Found by "skruffy" on
1640 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1641 - Free directory authority certificate download statuses on exit
1642 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1644 o Minor bugfixes (on 0.2.3.x and earlier):
1645 - If the guard we choose first doesn't answer, we would try the
1646 second guard, but once we connected to the second guard we would
1647 abandon it and retry the first one, slowing down bootstrapping.
1648 The fix is to treat all our initially chosen guards as acceptable
1649 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1650 - Fix an assertion failure that would occur when disabling the
1651 ORPort setting on a running Tor process while accounting was
1652 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1653 - When examining the list of network interfaces to find our address,
1654 do not consider non-running or disabled network interfaces. Fixes
1655 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1656 - Avoid an off-by-one error when checking buffer boundaries when
1657 formatting the exit status of a pluggable transport helper.
1658 This is probably not an exploitable bug, but better safe than
1659 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1662 o Minor features (protecting client timestamps):
1663 - Clients no longer send timestamps in their NETINFO cells. These were
1664 not used for anything, and they provided one small way for clients
1665 to be distinguished from each other as they moved from network to
1666 network or behind NAT. Implements part of proposal 222.
1667 - Clients now round timestamps in INTRODUCE cells down to the nearest
1668 10 minutes. If a new Support022HiddenServices option is set to 0, or
1669 if it's set to "auto" and the feature is disabled in the consensus,
1670 the timestamp is sent as 0 instead. Implements part of proposal 222.
1671 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1672 a big deal from a security point of view, but it achieves no actual
1673 good purpose, and isn't needed. Implements part of proposal 222.
1674 - Reduce down accuracy of timestamps in hidden service descriptors.
1675 Implements part of proposal 222.
1677 o Minor features (other):
1678 - Improve the circuit queue out-of-memory handler. Previously, when
1679 we ran low on memory, we'd close whichever circuits had the most
1680 queued cells. Now, we close those that have the *oldest* queued
1681 cells, on the theory that those are most responsible for us
1682 running low on memory. Based on analysis from a forthcoming paper
1683 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1684 - Generate bootstrapping status update events correctly when fetching
1685 microdescriptors. Fixes bug 9927.
1686 - Update to the October 2 2013 Maxmind GeoLite Country database.
1688 o Documentation fixes:
1689 - Clarify the usage and risks of setting the ContactInfo torrc line
1690 for your relay or bridge. Resolves ticket 9854.
1691 - Add anchors to the manpage so we can link to the html version of
1692 the documentation for specific options. Resolves ticket 9866.
1693 - Replace remaining references to DirServer in man page and
1694 log entries. Resolves ticket 10124.
1697 Changes in version 0.2.5.1-alpha - 2013-10-02
1698 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
1699 on Linux, allows bridges that offer pluggable transports to report usage
1700 statistics, fixes many issues to make testing easier, and provides
1701 a pile of minor features and bugfixes that have been waiting for a
1702 release of the new branch.
1704 This is the first alpha release in a new series, so expect there to
1705 be bugs. Users who would rather test out a more stable branch should
1706 stay with 0.2.4.x for now.
1708 o Major features (security):
1709 - Use the seccomp2 syscall filtering facility on Linux to limit
1710 which system calls Tor can invoke. This is an experimental,
1711 Linux-only feature to provide defense-in-depth against unknown
1712 attacks. To try turning it on, set "Sandbox 1" in your torrc
1713 file. Please be ready to report bugs. We hope to add support
1714 for better sandboxing in the future, including more fine-grained
1715 filters, better division of responsibility, and support for more
1716 platforms. This work has been done by Cristian-Matei Toader for
1717 Google Summer of Code.
1718 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1719 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1720 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1721 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1722 them to solve bug 6033.)
1724 o Major features (other):
1725 - Add support for passing arguments to managed pluggable transport
1726 proxies. Implements ticket 3594.
1727 - Bridges now track GeoIP information and the number of their users
1728 even when pluggable transports are in use, and report usage
1729 statistics in their extra-info descriptors. Resolves tickets 4773
1731 - Make testing Tor networks bootstrap better: lower directory fetch
1732 retry schedules and maximum interval without directory requests,
1733 and raise maximum download tries. Implements ticket 6752.
1734 - Add make target 'test-network' to run tests on a Chutney network.
1735 Implements ticket 8530.
1736 - The ntor handshake is now on-by-default, no matter what the
1737 directory authorities recommend. Implements ticket 8561.
1740 - Instead of writing destroy cells directly to outgoing connection
1741 buffers, queue them and intersperse them with other outgoing cells.
1742 This can prevent a set of resource starvation conditions where too
1743 many pending destroy cells prevent data cells from actually getting
1744 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
1745 bugfix on 0.2.0.1-alpha.
1746 - If we are unable to save a microdescriptor to the journal, do not
1747 drop it from memory and then reattempt downloading it. Fixes bug
1748 9645; bugfix on 0.2.2.6-alpha.
1749 - The new channel code sometimes lost track of in-progress circuits,
1750 causing long-running clients to stop building new circuits. The
1751 fix is to always call circuit_n_chan_done(chan, 0) from
1752 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1755 - Tor now builds each source file in two modes: a mode that avoids
1756 exposing identifiers needlessly, and another mode that exposes
1757 more identifiers for testing. This lets the compiler do better at
1758 optimizing the production code, while enabling us to take more
1759 radical measures to let the unit tests test things.
1760 - The production builds no longer include functions used only in
1761 the unit tests; all functions exposed from a module only for
1762 unit-testing are now static in production builds.
1763 - Add an --enable-coverage configuration option to make the unit
1764 tests (and a new src/or/tor-cov target) to build with gcov test
1768 - We now have rudimentary function mocking support that our unit
1769 tests can use to test functions in isolation. Function mocking
1770 lets the tests temporarily replace a function's dependencies with
1771 stub functions, so that the tests can check the function without
1772 invoking the other functions it calls.
1773 - Add more unit tests for the <circid,channel>->circuit map, and
1774 the destroy-cell-tracking code to fix bug 7912.
1775 - Unit tests for failing cases of the TAP onion handshake.
1776 - More unit tests for address-manipulation functions.
1778 o Minor features (protecting client timestamps):
1779 - Clients no longer send timestamps in their NETINFO cells. These were
1780 not used for anything, and they provided one small way for clients
1781 to be distinguished from each other as they moved from network to
1782 network or behind NAT. Implements part of proposal 222.
1783 - Clients now round timestamps in INTRODUCE cells down to the nearest
1784 10 minutes. If a new Support022HiddenServices option is set to 0, or
1785 if it's set to "auto" and the feature is disabled in the consensus,
1786 the timestamp is sent as 0 instead. Implements part of proposal 222.
1787 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1788 a big deal from a security point of view, but it achieves no actual
1789 good purpose, and isn't needed. Implements part of proposal 222.
1790 - Reduce down accuracy of timestamps in hidden service descriptors.
1791 Implements part of proposal 222.
1793 o Minor features (config options):
1794 - Config (torrc) lines now handle fingerprints which are missing
1795 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
1796 - Support a --dump-config option to print some or all of the
1797 configured options. Mainly useful for debugging the command-line
1798 option parsing code. Helps resolve ticket 4647.
1799 - Raise awareness of safer logging: notify user of potentially
1800 unsafe config options, like logging more verbosely than severity
1801 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
1802 - Add a new configuration option TestingV3AuthVotingStartOffset
1803 that bootstraps a network faster by changing the timing for
1804 consensus votes. Addresses ticket 8532.
1805 - Add a new torrc option "ServerTransportOptions" that allows
1806 bridge operators to pass configuration parameters to their
1807 pluggable transports. Resolves ticket 8929.
1808 - The config (torrc) file now accepts bandwidth and space limits in
1809 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
1810 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
1813 o Minor features (build):
1814 - Add support for `--library-versions` flag. Implements ticket 6384.
1815 - Return the "unexpected sendme" warnings to a warn severity, but make
1816 them rate limited, to help diagnose ticket 8093.
1817 - Detect a missing asciidoc, and warn the user about it, during
1818 configure rather than at build time. Fixes issue 6506. Patch from
1821 o Minor features (other):
1822 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
1823 sockets in a single system call. Implements ticket 5129.
1824 - Log current accounting state (bytes sent and received + remaining
1825 time for the current accounting period) in the relay's heartbeat
1826 message. Implements ticket 5526; patch from Peter Retzlaff.
1827 - Implement the TRANSPORT_LAUNCHED control port event that
1828 notifies controllers about new launched pluggable
1829 transports. Resolves ticket 5609.
1830 - If we're using the pure-C 32-bit curve25519_donna implementation
1831 of curve25519, build it with the -fomit-frame-pointer option to
1832 make it go faster on register-starved hosts. This improves our
1833 handshake performance by about 6% on i386 hosts without nacl.
1835 - Update to the September 4 2013 Maxmind GeoLite Country database.
1838 - Set the listen() backlog limit to the largest actually supported
1839 on the system, not to the value in a header file. Fixes bug 9716;
1840 bugfix on every released Tor.
1841 - No longer accept malformed http headers when parsing urls from
1842 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
1843 bugfix on 0.0.6pre1.
1844 - In munge_extrainfo_into_routerinfo(), check the return value of
1845 memchr(). This would have been a serious issue if we ever passed
1846 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
1848 - On the chance that somebody manages to build Tor on a
1849 platform where time_t is unsigned, correct the way that
1850 microdesc_add_to_cache() handles negative time arguments.
1851 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
1852 - Reject relative control socket paths and emit a warning. Previously,
1853 single-component control socket paths would be rejected, but Tor
1854 would not log why it could not validate the config. Fixes bug 9258;
1855 bugfix on 0.2.3.16-alpha.
1857 o Minor bugfixes (command line):
1858 - Use a single command-line parser for parsing torrc options on the
1859 command line and for finding special command-line options to avoid
1860 inconsistent behavior for torrc option arguments that have the same
1861 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
1863 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
1864 9573; bugfix on 0.0.9pre5.
1866 o Minor fixes (build, auxiliary programs):
1867 - Stop preprocessing the "torify" script with autoconf, since
1868 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
1870 - The tor-fw-helper program now follows the standard convention and
1871 exits with status code "0" on success. Fixes bug 9030; bugfix on
1872 0.2.3.1-alpha. Patch by Arlo Breault.
1873 - Corrected ./configure advice for what openssl dev package you should
1874 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
1876 o Minor code improvements:
1877 - Remove constants and tests for PKCS1 padding; it's insecure and
1878 shouldn't be used for anything new. Fixes bug 8792; patch
1880 - Remove instances of strcpy() from the unit tests. They weren't
1881 hurting anything, since they were only in the unit tests, but it's
1882 embarassing to have strcpy() in the code at all, and some analysis
1883 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
1884 0.2.3.8-alpha. Patch from Arlo Breault.
1887 - Remove migration code from when we renamed the "cached-routers"
1888 file to "cached-descriptors" back in 0.2.0.8-alpha. This
1889 incidentally resolves ticket 6502 by cleaning up the related code
1890 a bit. Patch from Akshay Hebbar.
1892 o Code simplification and refactoring:
1893 - Extract the common duplicated code for creating a subdirectory
1894 of the data directory and writing to a file in it. Fixes ticket
1895 4282; patch from Peter Retzlaff.
1896 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
1897 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
1898 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
1899 - Add a set of accessor functions for the circuit timeout data
1900 structure. Fixes ticket 6153; patch from "piet".
1901 - Clean up exit paths from connection_listener_new(). Closes ticket
1902 8789. Patch from Arlo Breault.
1903 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
1904 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
1905 - Use a doubly-linked list to implement the global circuit list.
1906 Resolves ticket 9108. Patch from Marek Majkowski.
1907 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
1910 Changes in version 0.2.4.17-rc - 2013-09-05
1911 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
1912 series. It adds an emergency step to help us tolerate the massive
1913 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
1914 circuit-level handshakes now effectively jump the queue compared to
1915 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
1916 big bug hindering bridge reachability tests.
1919 - Relays now process the new "NTor" circuit-level handshake requests
1920 with higher priority than the old "TAP" circuit-level handshake
1921 requests. We still process some TAP requests to not totally starve
1922 0.2.3 clients when NTor becomes popular. A new consensus parameter
1923 "NumNTorsPerTAP" lets us tune the balance later if we need to.
1924 Implements ticket 9574.
1927 - If the circuit build timeout logic is disabled (via the consensus,
1928 or because we are an authority), then don't build testing circuits.
1929 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
1930 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
1931 previously they did not, which prevented them from receiving
1932 successful connections from relays for self-test or bandwidth
1933 testing. Also, when a relay is extending a circuit to a bridge,
1934 it needs to send a NETINFO cell, even when the bridge hasn't sent
1935 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
1936 - If the time to download the next old-style networkstatus is in
1937 the future, do not decline to consider whether to download the
1938 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
1942 - Avoid double-closing the listener socket in our socketpair()
1943 replacement (used on Windows) in the case where the addresses on
1944 our opened sockets don't match what we expected. Fixes bug 9400;
1945 bugfix on 0.0.2pre7. Found by Coverity.
1947 o Minor fixes (config options):
1948 - Avoid overflows when the user sets MaxCircuitDirtiness to a
1949 ridiculously high value, by imposing a (ridiculously high) 30-day
1950 maximum on MaxCircuitDirtiness.
1951 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
1952 message is logged at notice, not at info.
1953 - Warn and fail if a server is configured not to advertise any
1954 ORPorts at all. (We need *something* to put in our descriptor,
1955 or we just won't work.)
1958 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1959 and how many we complete, and log it every hour to help relay
1960 operators follow trends in network load. Addresses ticket 9658.
1961 - Update to the August 7 2013 Maxmind GeoLite Country database.
1964 Changes in version 0.2.4.16-rc - 2013-08-10
1965 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
1966 series. It fixes several crash bugs in the 0.2.4 branch.
1969 - Fix a bug in the voting algorithm that could yield incorrect results
1970 when a non-naming authority declared too many flags. Fixes bug 9200;
1971 bugfix on 0.2.0.3-alpha.
1972 - Fix an uninitialized read that could in some cases lead to a remote
1973 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
1974 Anybody running a hidden service on the experimental 0.2.4.x
1975 branch should upgrade. (This is, so far as we know, unrelated to
1977 - Avoid an assertion failure when processing DNS replies without the
1978 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
1979 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
1980 0.2.4.15-rc. Found by stem integration tests.
1983 - Fix an invalid memory read that occured when a pluggable
1984 transport proxy failed its configuration protocol.
1985 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
1986 - When evaluating whether to use a connection that we haven't
1987 decided is canonical using a recent link protocol version,
1988 decide that it's canonical only if it used address _does_
1989 match the desired address. Fixes bug 9309; bugfix on
1990 0.2.4.4-alpha. Reported by skruffy.
1991 - Make the default behavior of NumDirectoryGuards be to track
1992 NumEntryGuards. Now a user who changes only NumEntryGuards will get
1993 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
1994 - Fix a spurious compilation warning with some older versions of
1995 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
1998 - Update to the July 3 2013 Maxmind GeoLite Country database.
2001 Changes in version 0.2.4.15-rc - 2013-07-01
2002 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
2003 series. It fixes a few smaller bugs, but generally appears stable.
2004 Please test it and let us know whether it is!
2007 - When receiving a new configuration file via the control port's
2008 LOADCONF command, do not treat the defaults file as absent.
2009 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
2012 - Issue a warning when running with the bufferevents backend enabled.
2013 It's still not stable, and people should know that they're likely
2014 to hit unexpected problems. Closes ticket 9147.
2017 Changes in version 0.2.4.14-alpha - 2013-06-18
2018 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
2019 present in 0.2.4.13-alpha.
2022 - When we have too much memory queued in circuits (according to a new
2023 MaxMemInCellQueues option), close the circuits consuming the most
2024 memory. This prevents us from running out of memory as a relay if
2025 circuits fill up faster than they can be drained. Fixes bug 9063;
2026 bugfix on the 54th commit of Tor. This bug is a further fix beyond
2027 bug 6252, whose fix was merged into 0.2.3.21-rc.
2029 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
2030 where we tried to solve this issue simply by imposing an upper limit
2031 on the number of queued cells for a single circuit. That approach
2032 proved to be problematic, since there are ways to provoke clients to
2033 send a number of cells in excess of any such reasonable limit. Fixes
2034 bug 9072; bugfix on 0.2.4.13-alpha.
2036 - Limit hidden service descriptors to at most ten introduction
2037 points, to slow one kind of guard enumeration. Fixes bug 9002;
2038 bugfix on 0.1.1.11-alpha.
2041 Changes in version 0.2.4.13-alpha - 2013-06-14
2042 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
2043 vulnerabilities, makes socks5 username/password circuit isolation
2044 actually actually work (this time for sure!), and cleans up a bunch
2045 of other issues in preparation for a release candidate.
2047 o Major bugfixes (robustness):
2048 - Close any circuit that has too many cells queued on it. Fixes
2049 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
2050 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
2051 - Prevent the get_freelists() function from running off the end of
2052 the list of freelists if it somehow gets an unrecognized
2053 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
2055 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
2056 when an exit connection with optimistic data succeeds immediately
2057 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
2059 - Fix a directory authority crash bug when building a consensus
2060 using an older consensus as its basis. Fixes bug 8833. Bugfix
2064 - Avoid a memory leak where we would leak a consensus body when we
2065 find that a consensus which we couldn't previously verify due to
2066 missing certificates is now verifiable. Fixes bug 8719; bugfix
2068 - We used to always request authority certificates by identity digest,
2069 meaning we'd get the newest one even when we wanted one with a
2070 different signing key. Then we would complain about being given
2071 a certificate we already had, and never get the one we really
2072 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
2073 resource to request the one we want. Fixes bug 5595; bugfix on
2075 - Follow the socks5 protocol when offering username/password
2076 authentication. The fix for bug 8117 exposed this bug, and it
2077 turns out real-world applications like Pidgin do care. Bugfix on
2078 0.2.3.2-alpha; fixes bug 8879.
2079 - Prevent failures on Windows Vista and later when rebuilding the
2080 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
2081 bugfix on 0.2.4.12-alpha.
2084 - Fix an impossible buffer overrun in the AES unit tests. Fixes
2085 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
2086 - If for some reason we fail to write a microdescriptor while
2087 rebuilding the cache, do not let the annotations from that
2088 microdescriptor linger in the cache file, and do not let the
2089 microdescriptor stay recorded as present in its old location.
2090 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
2091 - Fix a memory leak that would occur whenever a configuration
2092 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
2093 - Paste the description for PathBias parameters from the man
2094 page into or.h, so the code documents them too. Fixes bug 7982;
2095 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
2096 - Relays now treat a changed IPv6 ORPort as sufficient reason to
2097 publish an updated descriptor. Fixes bug 6026; bugfix on
2099 - When launching a resolve request on behalf of an AF_UNIX control
2100 socket, omit the address field of the new entry connection, used in
2101 subsequent controller events, rather than letting tor_dup_addr()
2102 set it to "<unknown address type>". Fixes bug 8639; bugfix on
2105 o Minor bugfixes (log messages):
2106 - Fix a scaling issue in the path bias accounting code that
2107 resulted in "Bug:" log messages from either
2108 pathbias_scale_close_rates() or pathbias_count_build_success().
2109 This represents a bugfix on a previous bugfix: the original fix
2110 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
2112 - Give a less useless error message when the user asks for an IPv4
2113 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
2117 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
2118 to tolerate bug 8093 for now.
2119 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
2120 in directory authority votes to describe whether they have enough
2121 measured bandwidths to ignore advertised (relay descriptor)
2122 bandwidth claims. Resolves ticket 8711.
2123 - Update to the June 5 2013 Maxmind GeoLite Country database.
2125 o Removed documentation:
2126 - Remove some of the older contents of doc/ as obsolete; move others
2127 to torspec.git. Fixes bug 8965.
2129 o Code simplification and refactoring:
2130 - Avoid using character buffers when constructing most directory
2131 objects: this approach was unwieldy and error-prone. Instead,
2132 build smartlists of strings, and concatenate them when done.
2135 Changes in version 0.2.4.12-alpha - 2013-04-18
2136 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
2137 process for lengthening the guard rotation period, makes directory
2138 authority opinions in the consensus a bit less gameable, makes socks5
2139 username/password circuit isolation actually work, and fixes a wide
2140 variety of other issues.
2143 - Raise the default time that a client keeps an entry guard from
2144 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
2145 2012 paper. (We would make it even longer, but we need better client
2146 load balancing first.) Also, make the guard lifetime controllable
2147 via a new GuardLifetime torrc option and a GuardLifetime consensus
2148 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
2149 - Directory authorities now prefer using measured bandwidths to
2150 advertised ones when computing flags and thresholds. Resolves
2152 - Directory authorities that have more than a threshold number
2153 of relays with measured bandwidths now treat relays with unmeasured
2154 bandwidths as having bandwidth 0. Resolves ticket 8435.
2156 o Major bugfixes (assert / resource use):
2157 - Avoid a bug where our response to TLS renegotiation under certain
2158 network conditions could lead to a busy-loop, with 100% CPU
2159 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
2160 - Avoid an assertion when we discover that we'd like to write a cell
2161 onto a closing connection: just discard the cell. Fixes another
2162 case of bug 7350; bugfix on 0.2.4.4-alpha.
2164 o Major bugfixes (client-side privacy):
2165 - When we mark a circuit as unusable for new circuits, have it
2166 continue to be unusable for new circuits even if MaxCircuitDirtiness
2167 is increased too much at the wrong time, or the system clock jumps
2168 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
2169 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
2170 which have resolved to internal addresses") is set, apply that
2171 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
2172 - When an exit relay rejects a stream with reason "exit policy", but
2173 we only know an exit policy summary (e.g. from the microdesc
2174 consensus) for it, do not mark the relay as useless for all exiting.
2175 Instead, mark just the circuit as unsuitable for that particular
2176 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
2177 - Allow applications to get proper stream isolation with
2178 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
2179 username/password authentication also offer "no authentication". Tor
2180 had previously preferred "no authentication", so the applications
2181 never actually sent Tor their auth details. Now Tor selects
2182 username/password authentication if it's offered. You can disable
2183 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
2184 bug 8117; bugfix on 0.2.3.3-alpha.
2186 o Major bugfixes (other):
2187 - When unable to find any working directory nodes to use as a
2188 directory guard, give up rather than adding the same non-working
2189 nodes to the directory guard list over and over. Fixes bug 8231;
2190 bugfix on 0.2.4.8-alpha.
2193 - Reject as invalid most directory objects containing a NUL.
2194 Belt-and-suspender fix for bug 8037.
2195 - In our testsuite, create temporary directories with a bit more
2196 entropy in their name to make name collisions less likely. Fixes
2198 - Add CACHED keyword to ADDRMAP events in the control protocol
2199 to indicate whether a DNS result will be cached or not. Resolves
2201 - Update to the April 3 2013 Maxmind GeoLite Country database.
2203 o Minor features (build):
2204 - Detect and reject attempts to build Tor with threading support
2205 when OpenSSL has been compiled without threading support.
2207 - Clarify that when autoconf is checking for nacl, it is checking
2208 specifically for nacl with a fast curve25519 implementation.
2210 - Warn if building on a platform with an unsigned time_t: there
2211 are too many places where Tor currently assumes that time_t can
2212 hold negative values. We'd like to fix them all, but probably
2215 o Minor bugfixes (build):
2216 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
2217 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
2218 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
2219 - Add the old src/or/micro-revision.i filename to CLEANFILES.
2220 On the off chance that somebody has one, it will go away as soon
2221 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
2222 - Build Tor correctly on 32-bit platforms where the compiler can build
2223 but not run code using the "uint128_t" construction. Fixes bug 8587;
2224 bugfix on 0.2.4.8-alpha.
2225 - Fix compilation warning with some versions of clang that would
2226 prefer the -Wswitch-enum compiler flag to warn about switch
2227 statements with missing enum values, even if those switch
2228 statements have a "default:" statement. Fixes bug 8598; bugfix
2231 o Minor bugfixes (protocol):
2232 - Fix the handling of a TRUNCATE cell when it arrives while the
2233 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
2234 - Fix a misframing issue when reading the version numbers in a
2235 VERSIONS cell. Previously we would recognize [00 01 00 02] as
2236 'version 1, version 2, and version 0x100', when it should have
2237 only included versions 1 and 2. Fixes bug 8059; bugfix on
2238 0.2.0.10-alpha. Reported pseudonymously.
2239 - Make the format and order of STREAM events for DNS lookups
2240 consistent among the various ways to launch DNS lookups. Fixes
2241 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
2242 - Correct our check for which versions of Tor support the EXTEND2
2243 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
2244 later, when support was really added in version 0.2.4.8-alpha.
2245 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
2247 o Minor bugfixes (other):
2248 - Correctly store microdescriptors and extrainfo descriptors with
2249 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
2250 Bug reported by "cypherpunks".
2251 - Increase the width of the field used to remember a connection's
2252 link protocol version to two bytes. Harmless for now, since the
2253 only currently recognized versions are one byte long. Reported
2254 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
2255 - If the state file's path bias counts are invalid (presumably from a
2256 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
2257 additional checks and log messages to the scaling of Path Bias
2258 counts, in case there still are remaining issues with scaling.
2259 Should help resolve bug 8235.
2260 - Eliminate several instances where we use "Nickname=ID" to refer to
2261 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
2262 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
2263 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
2265 o Minor bugfixes (syscalls):
2266 - Always check the return values of functions fcntl() and
2267 setsockopt(). We don't believe these are ever actually failing in
2268 practice, but better safe than sorry. Also, checking these return
2269 values should please analysis tools like Coverity. Patch from
2270 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
2271 - Use direct writes rather than stdio when building microdescriptor
2272 caches, in an attempt to mitigate bug 8031, or at least make it
2275 o Minor bugfixes (config):
2276 - When rejecting a configuration because we were unable to parse a
2277 quoted string, log an actual error message. Fixes bug 7950; bugfix
2279 - Behave correctly when the user disables LearnCircuitBuildTimeout
2280 but doesn't tell us what they would like the timeout to be. Fixes
2281 bug 6304; bugfix on 0.2.2.14-alpha.
2282 - When autodetecting the number of CPUs, use the number of available
2283 CPUs in preference to the number of configured CPUs. Inform the
2284 user if this reduces the number of available CPUs. Fixes bug 8002;
2285 bugfix on 0.2.3.1-alpha.
2286 - Make it an error when you set EntryNodes but disable UseGuardNodes,
2287 since it will (surprisingly to some users) ignore EntryNodes. Fixes
2288 bug 8180; bugfix on 0.2.3.11-alpha.
2289 - Allow TestingTorNetworks to override the 4096-byte minimum for
2290 the Fast threshold. Otherwise they can't bootstrap until they've
2291 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
2292 - Fix some logic errors when the user manually overrides the
2293 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
2296 o Minor bugfixes (log messages to help diagnose bugs):
2297 - If we fail to free a microdescriptor because of bug 7164, log
2298 the filename and line number from which we tried to free it.
2299 - Add another diagnostic to the heartbeat message: track and log
2300 overhead that TLS is adding to the data we write. If this is
2301 high, we are sending too little data to SSL_write at a time.
2302 Diagnostic for bug 7707.
2303 - Add more detail to a log message about relaxed timeouts, to help
2305 - Warn more aggressively when flushing microdescriptors to a
2306 microdescriptor cache fails, in an attempt to mitigate bug 8031,
2307 or at least make it more diagnosable.
2308 - Improve debugging output to help track down bug 8185 ("Bug:
2309 outgoing relay cell has n_chan==NULL. Dropping.")
2310 - Log the purpose of a path-bias testing circuit correctly.
2311 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
2313 o Minor bugfixes (0.2.4.x log messages that were too noisy):
2314 - Don't attempt to relax the timeout of already opened 1-hop circuits.
2315 They might never timeout. This should eliminate some/all cases of
2316 the relaxed timeout log message.
2317 - Use circuit creation time for network liveness evaluation. This
2318 should eliminate warning log messages about liveness caused
2319 by changes in timeout evaluation. Fixes bug 6572; bugfix on
2321 - Reduce a path bias length check from notice to info. The message
2322 is triggered when creating controller circuits. Fixes bug 8196;
2323 bugfix on 0.2.4.8-alpha.
2324 - Fix a path state issue that triggered a notice during relay startup.
2325 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
2326 - Reduce occurrences of warns about circuit purpose in
2327 connection_ap_expire_building(). Fixes bug 8477; bugfix on
2330 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
2331 - If we encounter a write failure on a SOCKS connection before we
2332 finish our SOCKS handshake, don't warn that we closed the
2333 connection before we could send a SOCKS reply. Fixes bug 8427;
2334 bugfix on 0.1.0.1-rc.
2335 - Correctly recognize that [::1] is a loopback address. Fixes
2336 bug 8377; bugfix on 0.2.1.3-alpha.
2337 - Fix a directory authority warn caused when we have a large amount
2338 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
2339 - Don't log inappropriate heartbeat messages when hibernating: a
2340 hibernating node is _expected_ to drop out of the consensus,
2341 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
2342 bugfix on 0.2.3.1-alpha.
2343 - Don't complain about bootstrapping problems while hibernating.
2344 These complaints reflect a general code problem, but not one
2345 with any problematic effects (no connections are actually
2346 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
2348 o Documentation fixes:
2349 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
2350 names match. Fixes bug 7768.
2351 - Make the torify manpage no longer refer to tsocks; torify hasn't
2352 supported tsocks since 0.2.3.14-alpha.
2353 - Make the tor manpage no longer reference tsocks.
2354 - Fix the GeoIPExcludeUnknown documentation to refer to
2355 ExcludeExitNodes rather than the currently nonexistent
2356 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
2359 - The tor-tsocks.conf is no longer distributed or installed. We
2360 recommend that tsocks users use torsocks instead. Resolves
2364 Changes in version 0.2.4.11-alpha - 2013-03-11
2365 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
2366 more robust, makes hidden service authentication work again, and
2367 resolves a DPI fingerprint for Tor's SSL transport.
2369 o Major features (directory authorities):
2370 - Directory authorities now support a new consensus method (17)
2371 where they cap the published bandwidth of servers for which
2372 insufficient bandwidth measurements exist. Fixes part of bug 2286.
2373 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
2374 serve any v2 directory information. Now we can test disabling the
2375 old deprecated v2 directory format, and see whether doing so has
2376 any effect on network load. Begins to fix bug 6783.
2377 - Directory authorities now include inside each vote a statement of
2378 the performance thresholds they used when assigning flags.
2379 Implements ticket 8151.
2381 o Major bugfixes (directory authorities):
2382 - Stop marking every relay as having been down for one hour every
2383 time we restart a directory authority. These artificial downtimes
2384 were messing with our Stable and Guard flag calculations. Fixes
2385 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
2387 o Major bugfixes (hidden services):
2388 - Allow hidden service authentication to succeed again. When we
2389 refactored the hidden service introduction code back
2390 in 0.2.4.1-alpha, we didn't update the code that checks
2391 whether authentication information is present, causing all
2392 authentication checks to return "false". Fix for bug 8207; bugfix
2393 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
2395 o Minor features (relays, bridges):
2396 - Make bridge relays check once a minute for whether their IP
2397 address has changed, rather than only every 15 minutes. Resolves
2399 - Refactor resolve_my_address() so it returns the method by which we
2400 decided our public IP address (explicitly configured, resolved from
2401 explicit hostname, guessed from interfaces, learned by gethostname).
2402 Now we can provide more helpful log messages when a relay guesses
2403 its IP address incorrectly (e.g. due to unexpected lines in
2404 /etc/hosts). Resolves ticket 2267.
2405 - Teach bridge-using clients to avoid 0.2.2 bridges when making
2406 microdescriptor-related dir requests, and only fall back to normal
2407 descriptors if none of their bridges can handle microdescriptors
2408 (as opposed to the fix in ticket 4013, which caused them to fall
2409 back to normal descriptors if *any* of their bridges preferred
2410 them). Resolves ticket 4994.
2411 - Randomize the lifetime of our SSL link certificate, so censors can't
2412 use the static value for filtering Tor flows. Resolves ticket 8443;
2413 related to ticket 4014 which was included in 0.2.2.33.
2414 - Support a new version of the link protocol that allows 4-byte circuit
2415 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
2416 a possible resource exhaustion issue. Closes ticket 7351; implements
2419 o Minor features (portability):
2420 - Tweak the curve25519-donna*.c implementations to tolerate systems
2421 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
2422 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
2423 the signs of types during autoconf. This is better than our old
2424 approach, which didn't work when cross-compiling.
2425 - Detect the sign of enum values, rather than assuming that MSC is the
2426 only compiler where enum types are all signed. Fixes bug 7727;
2427 bugfix on 0.2.4.10-alpha.
2429 o Minor features (other):
2430 - Say "KBytes" rather than "KB" in the man page (for various values
2431 of K), to further reduce confusion about whether Tor counts in
2432 units of memory or fractions of units of memory. Resolves ticket 7054.
2433 - Clear the high bit on curve25519 public keys before passing them to
2434 our backend, in case we ever wind up using a backend that doesn't do
2435 so itself. If we used such a backend, and *didn't* clear the high bit,
2436 we could wind up in a situation where users with such backends would
2437 be distinguishable from users without. Fixes bug 8121; bugfix on
2439 - Update to the March 6 2013 Maxmind GeoLite Country database.
2441 o Minor bugfixes (clients):
2442 - When we receive a RELAY_END cell with the reason DONE, or with no
2443 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
2444 status as "connection refused". Previously we reported these cases
2445 as success but then immediately closed the connection. Fixes bug
2446 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
2447 - Downgrade an assertion in connection_ap_expire_beginning to an
2448 LD_BUG message. The fix for bug 8024 should prevent this message
2449 from displaying, but just in case, a warn that we can diagnose
2450 is better than more assert crashes. Fixes bug 8065; bugfix on
2452 - Lower path use bias thresholds to .80 for notice and .60 for warn.
2453 Also make the rate limiting flags for the path use bias log messages
2454 independent from the original path bias flags. Fixes bug 8161;
2455 bugfix on 0.2.4.10-alpha.
2457 o Minor bugfixes (relays):
2458 - Stop trying to resolve our hostname so often (e.g. every time we
2459 think about doing a directory fetch). Now we reuse the cached
2460 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
2461 and 2410 (bugfix on 0.1.2.2-alpha).
2462 - Stop sending a stray "(null)" in some cases for the server status
2463 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
2465 - When choosing which stream on a formerly stalled circuit to wake
2466 first, make better use of the platform's weak RNG. Previously,
2467 we had been using the % ("modulo") operator to try to generate a
2468 1/N chance of picking each stream, but this behaves badly with
2469 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
2471 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
2472 Irix's random() only return 15 bits; Solaris's random() returns more
2473 bits but its RAND_MAX says it only returns 15, and so on. Motivated
2474 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
2476 o Minor bugfixes (directory authorities):
2477 - Directory authorities now use less space when formatting identical
2478 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
2481 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
2482 - Avoid leaking memory if we fail to compute a consensus signature
2483 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
2484 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
2486 - Fix a memory leak during safe-cookie controller authentication.
2487 Bugfix on 0.2.3.13-alpha.
2488 - Avoid memory leak of IPv6 policy content if we fail to format it into
2489 a router descriptor. Bugfix on 0.2.4.7-alpha.
2491 o Minor bugfixes (other code correctness issues):
2492 - Avoid a crash if we fail to generate an extrainfo descriptor.
2493 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
2495 - When detecting the largest possible file descriptor (in order to
2496 close all file descriptors when launching a new program), actually
2497 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
2498 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
2500 - Fix a copy-and-paste error when adding a missing A1 to a routerset
2501 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
2502 Bugfix on 0.2.4.10-alpha.
2503 - Fix an impossible-to-trigger integer overflow when estimating how
2504 long our onionskin queue would take. (This overflow would require us
2505 to accept 4 million onionskins before processing 100 of them.) Fixes
2506 bug 8210; bugfix on 0.2.4.10-alpha.
2508 o Code simplification and refactoring:
2509 - Add a wrapper function for the common "log a message with a
2513 Changes in version 0.2.4.10-alpha - 2013-02-04
2514 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
2515 certain attacks that flood the network with relays; changes the queue
2516 for circuit create requests from a sized-based limit to a time-based
2517 limit; resumes building with MSVC on Windows; and fixes a wide variety
2520 o Major bugfixes (directory authority):
2521 - When computing directory thresholds, ignore any rejected-as-sybil
2522 nodes during the computation so that they can't influence Fast,
2523 Guard, etc. (We should have done this for proposal 109.) Fixes
2525 - When marking a node as a likely sybil, reset its uptime metrics
2526 to zero, so that it cannot time towards getting marked as Guard,
2527 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
2531 - When a TLS write is partially successful but incomplete, remember
2532 that the flushed part has been flushed, and notice that bytes were
2533 actually written. Reported and fixed pseudonymously. Fixes bug
2534 7708; bugfix on Tor 0.1.0.5-rc.
2535 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
2536 ID: these could be used to create unexpected streams and circuits
2537 which would count as "present" to some parts of Tor but "absent"
2538 to others, leading to zombie circuits and streams or to a bandwidth
2539 denial-of-service. Fixes bug 7889; bugfix on every released version
2540 of Tor. Reported by "oftc_must_be_destroyed".
2541 - Rename all macros in our local copy of queue.h to begin with "TOR_".
2542 This change seems the only good way to permanently prevent conflicts
2543 with queue.h on various operating systems. Fixes bug 8107; bugfix
2546 o Major features (relay):
2547 - Instead of limiting the number of queued onionskins (aka circuit
2548 create requests) to a fixed, hard-to-configure number, we limit
2549 the size of the queue based on how many we expect to be able to
2550 process in a given amount of time. We estimate the time it will
2551 take to process an onionskin based on average processing time
2552 of previous onionskins. Closes ticket 7291. You'll never have to
2553 configure MaxOnionsPending again.
2555 o Major features (portability):
2556 - Resume building correctly with MSVC and Makefile.nmake. This patch
2557 resolves numerous bugs and fixes reported by ultramage, including
2558 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
2559 - Make the ntor and curve25519 code build correctly with MSVC.
2560 Fix on 0.2.4.8-alpha.
2563 - When directory authorities are computing thresholds for flags,
2564 never let the threshold for the Fast flag fall below 4096
2565 bytes. Also, do not consider nodes with extremely low bandwidths
2566 when deciding thresholds for various directory flags. This change
2567 should raise our threshold for Fast relays, possibly in turn
2568 improving overall network performance; see ticket 1854. Resolves
2570 - The Tor client now ignores sub-domain components of a .onion
2571 address. This change makes HTTP "virtual" hosting
2572 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
2573 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
2574 hosted on the same hidden service. Implements proposal 204.
2575 - We compute the overhead from passing onionskins back and forth to
2576 cpuworkers, and report it when dumping statistics in response to
2577 SIGUSR1. Supports ticket 7291.
2579 o Minor features (path selection):
2580 - When deciding whether we have enough descriptors to build circuits,
2581 instead of looking at raw relay counts, look at which fraction
2582 of (bandwidth-weighted) paths we're able to build. This approach
2583 keeps clients from building circuits if their paths are likely to
2584 stand out statistically. The default fraction of paths needed is
2585 taken from the consensus directory; you can override it with the
2586 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
2587 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
2588 and we have GeoIP information, also exclude all nodes with unknown
2589 countries "??" and "A1". This behavior is controlled by the
2590 new GeoIPExcludeUnknown option: you can make such nodes always
2591 excluded with "GeoIPExcludeUnknown 1", and disable the feature
2592 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
2593 gets you the default behavior. Implements feature 7706.
2594 - Path Use Bias: Perform separate accounting for successful circuit
2595 use. Keep separate statistics on stream attempt rates versus stream
2596 success rates for each guard. Provide configurable thresholds to
2597 determine when to emit log messages or disable use of guards that
2598 fail too many stream attempts. Resolves ticket 7802.
2600 o Minor features (log messages):
2601 - When learning a fingerprint for a bridge, log its corresponding
2602 transport type. Implements ticket 7896.
2603 - Improve the log message when "Bug/attack: unexpected sendme cell
2604 from client" occurs, to help us track bug 8093.
2607 - Remove a couple of extraneous semicolons that were upsetting the
2608 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
2609 bugfix on 0.2.2.1-alpha.
2610 - Remove a source of rounding error during path bias count scaling;
2611 don't count cannibalized circuits as used for path bias until we
2612 actually try to use them; and fix a circuit_package_relay_cell()
2613 warning message about n_chan==NULL. Fixes bug 7802.
2614 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
2615 actually link against nacl when we're configured to use it. Fixes
2616 bug 7972; bugfix on 0.2.4.8-alpha.
2617 - Compile correctly with the --disable-curve25519 option. Fixes
2618 bug 8153; bugfix on 0.2.4.8-alpha.
2620 o Build improvements:
2621 - Do not report status verbosely from autogen.sh unless the -v flag
2622 is specified. Fixes issue 4664. Patch from Onizuka.
2623 - Replace all calls to snprintf() outside of src/ext with
2624 tor_snprintf(). Also remove the #define to replace snprintf with
2625 _snprintf on Windows; they have different semantics, and all of
2626 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
2627 - Try to detect if we are ever building on a platform where
2628 memset(...,0,...) does not set the value of a double to 0.0. Such
2629 platforms are permitted by the C standard, though in practice
2630 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
2631 currently support them, but it's better to detect them and fail
2632 than to perform erroneously.
2635 - Stop exporting estimates of v2 and v3 directory traffic shares
2636 in extrainfo documents. They were unneeded and sometimes inaccurate.
2637 Also stop exporting any v2 directory request statistics. Resolves
2639 - Drop support for detecting and warning about versions of Libevent
2640 before 1.3e. Nothing reasonable ships with them any longer;
2641 warning the user about them shouldn't be needed. Resolves ticket
2644 o Code simplifications and refactoring:
2645 - Rename "isin" functions to "contains", for grammar. Resolves
2647 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
2648 with the natural logarithm function from the system libm. Resolves
2652 Changes in version 0.2.4.9-alpha - 2013-01-15
2653 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
2657 - Fix backward compatibility logic when receiving an embedded ntor
2658 handshake tunneled in a CREATE cell. This clears up the "Bug:
2659 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
2663 Changes in version 0.2.4.8-alpha - 2013-01-14
2664 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
2665 risks, adds a new stronger and faster circuit handshake, and offers
2666 stronger and faster link encryption when both sides support it.
2669 - Preliminary support for directory guards (proposal 207): when
2670 possible, clients now use their entry guards for non-anonymous
2671 directory requests. This can help prevent client enumeration. Note
2672 that this behavior only works when we have a usable consensus
2673 directory, and when options about what to download are more or less
2674 standard. In the future we should re-bootstrap from our guards,
2675 rather than re-bootstrapping from the preconfigured list of
2676 directory sources that ships with Tor. Resolves ticket 6526.
2677 - Tor relays and clients now support a better CREATE/EXTEND cell
2678 format, allowing the sender to specify multiple address, identity,
2679 and handshake types. Implements Robert Ransom's proposal 200;
2682 o Major features (new circuit handshake):
2683 - Tor now supports a new circuit extension handshake designed by Ian
2684 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
2685 circuit extension handshake, later called "TAP", was a bit slow
2686 (especially on the relay side), had a fragile security proof, and
2687 used weaker keys than we'd now prefer. The new circuit handshake
2688 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
2689 function, making it significantly more secure than the older
2690 handshake, and significantly faster. Tor can use one of two built-in
2691 pure-C curve25519-donna implementations by Adam Langley, or it
2692 can link against the "nacl" library for a tuned version if present.
2694 The built-in version is very fast for 64-bit systems when building
2695 with GCC. The built-in 32-bit version is still faster than the
2696 old TAP protocol, but using libnacl is better on most such hosts.
2698 Clients don't currently use this protocol by default, since
2699 comparatively few clients support it so far. To try it, set
2700 UseNTorHandshake to 1.
2702 Implements proposal 216; closes ticket 7202.
2704 o Major features (better link encryption):
2705 - Relays can now enable the ECDHE TLS ciphersuites when available
2706 and appropriate. These ciphersuites let us negotiate forward-secure
2707 TLS secret keys more safely and more efficiently than with our
2708 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
2709 public relays prefer the (faster) P224 group, and bridges prefer
2710 the (more common) P256 group; you can override this with the
2713 Enabling these ciphers was a little tricky, since for a long time,
2714 clients had been claiming to support them without actually doing
2715 so, in order to foil fingerprinting. But with the client-side
2716 implementation of proposal 198 in 0.2.3.17-beta, clients can now
2717 match the ciphers from recent Firefox versions *and* list the
2718 ciphers they actually mean, so relays can believe such clients
2719 when they advertise ECDHE support in their TLS ClientHello messages.
2721 This feature requires clients running 0.2.3.17-beta or later,
2722 and requires both sides to be running OpenSSL 1.0.0 or later
2723 with ECC support. OpenSSL 1.0.1, with the compile-time option
2724 "enable-ec_nistp_64_gcc_128", is highly recommended.
2726 Implements the relay side of proposal 198; closes ticket 7200.
2729 - Avoid crashing when, as a relay without IPv6-exit support, a
2730 client insists on getting an IPv6 address or nothing. Fixes bug
2731 7814; bugfix on 0.2.4.7-alpha.
2734 - Improve circuit build timeout handling for hidden services.
2735 In particular: adjust build timeouts more accurately depending
2736 upon the number of hop-RTTs that a particular circuit type
2737 undergoes. Additionally, launch intro circuits in parallel
2738 if they timeout, and take the first one to reply as valid.
2739 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
2740 separate error codes; or at least, don't break for that reason.
2741 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
2742 - Update to the January 2 2013 Maxmind GeoLite Country database.
2744 o Minor features (testing):
2745 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
2746 (P-256) Diffie-Hellman handshakes to src/or/bench.
2747 - Add benchmark functions to test onion handshake performance.
2749 o Minor features (path bias detection):
2750 - Alter the Path Bias log messages to be more descriptive in terms
2751 of reporting timeouts and other statistics.
2752 - Create three levels of Path Bias log messages, as opposed to just
2753 two. These are configurable via consensus as well as via the torrc
2754 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
2755 The default values are 0.70, 0.50, and 0.30 respectively.
2756 - Separate the log message levels from the decision to drop guards,
2757 which also is available via torrc option PathBiasDropGuards.
2758 PathBiasDropGuards still defaults to 0 (off).
2759 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
2760 in combination with PathBiasExtremeRate.
2761 - Increase the default values for PathBiasScaleThreshold and
2762 PathBiasCircThreshold from (200, 20) to (300, 150).
2763 - Add in circuit usage accounting to path bias. If we try to use a
2764 built circuit but fail for any reason, it counts as path bias.
2765 Certain classes of circuits where the adversary gets to pick your
2766 destination node are exempt from this accounting. Usage accounting
2767 can be specifically disabled via consensus parameter or torrc.
2768 - Convert all internal path bias state to double-precision floating
2769 point, to avoid roundoff error and other issues.
2770 - Only record path bias information for circuits that have completed
2771 *two* hops. Assuming end-to-end tagging is the attack vector, this
2772 makes us more resilient to ambient circuit failure without any
2773 detection capability loss.
2775 o Minor bugfixes (log messages):
2776 - Rate-limit the "No circuits are opened. Relaxed timeout for a
2777 circuit with channel state open..." message to once per hour to
2778 keep it from filling the notice logs. Mitigates bug 7799 but does
2779 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
2780 - Avoid spurious warnings when configuring multiple client ports of
2781 which only some are nonlocal. Previously, we had claimed that some
2782 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
2785 o Code simplifications and refactoring:
2786 - Get rid of a couple of harmless clang warnings, where we compared
2787 enums to ints. These warnings are newly introduced in clang 3.2.
2788 - Split the onion.c file into separate modules for the onion queue
2789 and the different handshakes it supports.
2790 - Remove the marshalling/unmarshalling code for sending requests to
2791 cpuworkers over a socket, and instead just send structs. The
2792 recipient will always be the same Tor binary as the sender, so
2793 any encoding is overkill.
2796 Changes in version 0.2.4.7-alpha - 2012-12-24
2797 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
2798 directory mirrors for more robust bootstrapping; fixes more issues where
2799 clients with changing network conditions refuse to make any circuits;
2800 adds initial support for exiting to IPv6 addresses; resumes being able
2801 to update our GeoIP database, and includes the geoip6 file this time;
2802 turns off the client-side DNS cache by default due to privacy risks;
2803 and fixes a variety of other issues.
2805 o Major features (client resilience):
2806 - Add a new "FallbackDir" torrc option to use when we can't use
2807 a directory mirror from the consensus (either because we lack a
2808 consensus, or because they're all down). Currently, all authorities
2809 are fallbacks by default, and there are no other default fallbacks,
2810 but that will change. This option will allow us to give clients a
2811 longer list of servers to try to get a consensus from when first
2812 connecting to the Tor network, and thereby reduce load on the
2813 directory authorities. Implements proposal 206, "Preconfigured
2814 directory sources for bootstrapping". We also removed the old
2815 "FallbackNetworkstatus" option, since we never got it working well
2816 enough to use it. Closes bug 572.
2817 - If we have no circuits open, use a relaxed timeout (the
2818 95-percentile cutoff) until a circuit succeeds. This heuristic
2819 should allow Tor to succeed at building circuits even when the
2820 network connection drastically changes. Should help with bug 3443.
2822 o Major features (IPv6):
2823 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
2824 connectivity, then set the IPv6Exit flag to 1. Also make sure your
2825 exit policy reads as you would like: the address * applies to all
2826 address families, whereas *4 is IPv4 address only, and *6 is IPv6
2827 addresses only. On the client side, you'll need to wait until the
2828 authorities have upgraded, wait for enough exits to support IPv6,
2829 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
2830 ticket 5547, implements proposal 117 as revised in proposal 208.
2832 We DO NOT recommend that clients with actual anonymity needs start
2833 using IPv6 over Tor yet, since not enough exits support it yet.
2835 o Major features (geoip database):
2836 - Maxmind began labelling Tor relays as being in country "A1",
2837 which breaks by-country node selection inside Tor. Now we use a
2838 script to replace "A1" ("Anonymous Proxy") entries in our geoip
2839 file with real country codes. This script fixes about 90% of "A1"
2840 entries automatically and uses manual country code assignments to
2841 fix the remaining 10%. See src/config/README.geoip for details.
2842 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
2843 Country database, as modified above.
2845 o Major bugfixes (client-side DNS):
2846 - Turn off the client-side DNS cache by default. Updating and using
2847 the DNS cache is now configurable on a per-client-port
2848 level. SOCKSPort, DNSPort, etc lines may now contain
2849 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
2850 cache these types of DNS answers when we receive them from an
2851 exit node in response to an application request on this port, and
2852 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
2853 cached DNS answers of these types, we shouldn't use them. It's
2854 potentially risky to use cached DNS answers at the client, since
2855 doing so can indicate to one exit what answers we've gotten
2856 for DNS lookups in the past. With IPv6, this becomes especially
2857 problematic. Using cached DNS answers for requests on the same
2858 circuit would present less linkability risk, since all traffic
2859 on a circuit is already linkable, but it would also provide
2860 little performance benefit: the exit node caches DNS replies
2861 too. Implements a simplified version of Proposal 205. Implements
2864 o Major bugfixes (other):
2865 - Alter circuit build timeout measurement to start at the point
2866 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
2867 initialization). This should make our timeout measurements more
2868 uniform. Previously, we were sometimes including ORconn setup time
2869 in our circuit build time measurements. Should resolve bug 3443.
2870 - Fix an assertion that could trigger in hibernate_go_dormant() when
2871 closing an or_connection_t: call channel_mark_for_close() rather
2872 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
2874 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
2875 7655; bugfix on 0.2.4.6-alpha.
2878 - Add a new torrc option "ServerTransportListenAddr" to let bridge
2879 operators select the address where their pluggable transports will
2880 listen for connections. Resolves ticket 7013.
2881 - Allow an optional $ before the node identity digest in the
2882 controller command GETINFO ns/id/<identity>, for consistency with
2883 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
2884 - Log packaged cell fullness as part of the heartbeat message.
2885 Diagnosis to try to determine the extent of bug 7743.
2887 o Minor features (IPv6):
2888 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
2889 prefer to hand out virtual IPv6 addresses, since there are more of
2890 them and we can't run out. To override this behavior and make IPv4
2891 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
2892 or DNSPort you're using for resolving. Implements ticket 7571.
2893 - AutomapHostsOnResolve responses are now randomized, to avoid
2894 annoying situations where Tor is restarted and applications
2895 connect to the wrong addresses.
2896 - Never try more than 1000 times to pick a new virtual address when
2897 AutomapHostsOnResolve is set. That's good enough so long as we
2898 aren't close to handing out our entire virtual address space;
2899 if you're getting there, it's best to switch to IPv6 virtual
2903 - The ADDRMAP command can no longer generate an ill-formed error
2904 code on a failed MAPADDRESS. It now says "internal" rather than
2905 an English sentence fragment with spaces in the middle. Bugfix on
2907 - Fix log messages and comments to avoid saying "GMT" when we mean
2908 "UTC". Fixes bug 6113.
2909 - Compile on win64 using mingw64. Fixes bug 7260; patches from
2911 - Fix a crash when debugging unit tests on Windows: deallocate a
2912 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
2913 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
2916 - The DirServer option is now DirAuthority, for consistency with
2917 current naming patterns. You can still use the old DirServer form.
2919 o Code simplification and refactoring:
2920 - Move the client-side address-map/virtual-address/DNS-cache code
2921 out of connection_edge.c into a new addressmap.c module.
2922 - Remove unused code for parsing v1 directories and "running routers"
2923 documents. Fixes bug 6887.
2926 Changes in version 0.2.3.25 - 2012-11-19
2927 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
2928 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
2929 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
2930 programmer, and friend. Unstinting in his dedication to the cause of
2931 freedom, he inspired and helped many of us as we began our work on
2932 anonymity, and inspires us still. Please honor his memory by writing
2933 software to protect people's freedoms, and by helping others to do so.
2935 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
2936 significantly reduced directory overhead (via microdescriptors),
2937 enormous crypto performance improvements for fast relays on new
2938 enough hardware, a new v3 TLS handshake protocol that can better
2939 resist fingerprinting, support for protocol obfuscation plugins (aka
2940 pluggable transports), better scalability for hidden services, IPv6
2941 support for bridges, performance improvements like allowing clients
2942 to skip the first round-trip on the circuit ("optimistic data") and
2943 refilling token buckets more often, a new "stream isolation" design
2944 to isolate different applications on different circuits, and many
2945 stability, security, and privacy fixes.
2948 - Tor tries to wipe potentially sensitive data after using it, so
2949 that if some subsequent security failure exposes Tor's memory,
2950 the damage will be limited. But we had a bug where the compiler
2951 was eliminating these wipe operations when it decided that the
2952 memory was no longer visible to a (correctly running) program,
2953 hence defeating our attempt at defense in depth. We fix that
2954 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2955 is unlikely to optimize away. Future versions of Tor may use
2956 a less ridiculously heavy approach for this. Fixes bug 7352.
2957 Reported in an article by Andrey Karpov.
2960 - Fix a harmless bug when opting against publishing a relay descriptor
2961 because DisableNetwork is set. Fixes bug 7464; bugfix on
2965 Changes in version 0.2.4.6-alpha - 2012-11-13
2966 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
2967 makes our defense-in-depth memory wiping more reliable, and begins to
2968 count IPv6 addresses in bridge statistics,
2971 - Fix an assertion failure that could occur when closing a connection
2972 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
2974 - Tor tries to wipe potentially sensitive data after using it, so
2975 that if some subsequent security failure exposes Tor's memory,
2976 the damage will be limited. But we had a bug where the compiler
2977 was eliminating these wipe operations when it decided that the
2978 memory was no longer visible to a (correctly running) program,
2979 hence defeating our attempt at defense in depth. We fix that
2980 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2981 is unlikely to optimize away. Future versions of Tor may use
2982 a less ridiculously heavy approach for this. Fixes bug 7352.
2983 Reported in an article by Andrey Karpov.
2986 - Add GeoIP database for IPv6 addresses. The new config option
2988 - Bridge statistics now count bridge clients connecting over IPv6:
2989 bridge statistics files now list "bridge-ip-versions" and
2990 extra-info documents list "geoip6-db-digest". The control protocol
2991 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
2992 implementation by "shkoo", addressing ticket 5055.
2995 - Warn when we are binding low ports when hibernation is enabled;
2996 previously we had warned when we were _advertising_ low ports with
2997 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
2998 - Fix a harmless bug when opting against publishing a relay descriptor
2999 because DisableNetwork is set. Fixes bug 7464; bugfix on
3001 - Add warning message when a managed proxy dies during configuration.
3002 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
3003 - Fix a linking error when building tor-fw-helper without miniupnp.
3004 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
3005 - Check for closing an or_connection_t without going through correct
3006 channel functions; emit a warning and then call
3007 connection_or_close_for_error() so we don't assert as in bugs 7212
3009 - Compile correctly on compilers without C99 designated initializer
3010 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
3011 - Avoid a possible assert that can occur when channel_send_destroy() is
3012 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
3013 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
3014 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
3015 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
3016 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
3018 o Code simplification and refactoring:
3019 - Start using OpenBSD's implementation of queue.h, so that we don't
3020 need to hand-roll our own pointer and list structures whenever we
3021 need them. (We can't rely on a sys/queue.h, since some operating
3022 systems don't have them, and the ones that do have them don't all
3023 present the same extensions.)
3026 Changes in version 0.2.4.5-alpha - 2012-10-25
3027 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
3028 two important security vulnerabilities that could lead to remotely
3029 triggerable relay crashes, fix a major bug that was preventing clients
3030 from choosing suitable exit nodes, and refactor some of our code.
3032 o Major bugfixes (security, also in 0.2.3.24-rc):
3033 - Fix a group of remotely triggerable assertion failures related to
3034 incorrect link protocol negotiation. Found, diagnosed, and fixed
3035 by "some guy from France". Fix for CVE-2012-2250; bugfix on
3037 - Fix a denial of service attack by which any directory authority
3038 could crash all the others, or by which a single v2 directory
3039 authority could crash everybody downloading v2 directory
3040 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3042 o Major bugfixes (also in 0.2.3.24-rc):
3043 - When parsing exit policy summaries from microdescriptors, we had
3044 previously been ignoring the last character in each one, so that
3045 "accept 80,443,8080" would be treated by clients as indicating
3046 a node that allows access to ports 80, 443, and 808. That would
3047 lead to clients attempting connections that could never work,
3048 and ignoring exit nodes that would support their connections. Now
3049 clients parse these exit policy summaries correctly. Fixes bug 7192;
3050 bugfix on 0.2.3.1-alpha.
3052 o Minor bugfixes (also in 0.2.3.24-rc):
3053 - Clients now consider the ClientRejectInternalAddresses config option
3054 when using a microdescriptor consensus stanza to decide whether
3055 an exit relay would allow exiting to an internal address. Fixes
3056 bug 7190; bugfix on 0.2.3.1-alpha.
3059 - Only disable TLS session ticket support when running as a TLS
3060 server. Now clients will blend better with regular Firefox
3061 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
3063 o Code simplification and refactoring:
3064 - Start using OpenBSD's implementation of queue.h (originally by
3066 - Move the entry node code from circuitbuild.c to its own file.
3067 - Move the circuit build timeout tracking code from circuitbuild.c
3071 Changes in version 0.2.3.24-rc - 2012-10-25
3072 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
3073 could lead to remotely triggerable relay crashes, and fixes
3074 a major bug that was preventing clients from choosing suitable exit
3077 o Major bugfixes (security):
3078 - Fix a group of remotely triggerable assertion failures related to
3079 incorrect link protocol negotiation. Found, diagnosed, and fixed
3080 by "some guy from France". Fix for CVE-2012-2250; bugfix on
3082 - Fix a denial of service attack by which any directory authority
3083 could crash all the others, or by which a single v2 directory
3084 authority could crash everybody downloading v2 directory
3085 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3088 - When parsing exit policy summaries from microdescriptors, we had
3089 previously been ignoring the last character in each one, so that
3090 "accept 80,443,8080" would be treated by clients as indicating
3091 a node that allows access to ports 80, 443, and 808. That would
3092 lead to clients attempting connections that could never work,
3093 and ignoring exit nodes that would support their connections. Now
3094 clients parse these exit policy summaries correctly. Fixes bug 7192;
3095 bugfix on 0.2.3.1-alpha.
3098 - Clients now consider the ClientRejectInternalAddresses config option
3099 when using a microdescriptor consensus stanza to decide whether
3100 an exit relay would allow exiting to an internal address. Fixes
3101 bug 7190; bugfix on 0.2.3.1-alpha.
3104 Changes in version 0.2.4.4-alpha - 2012-10-20
3105 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
3106 vulnerability introduced by a change in OpenSSL, fixes a remotely
3107 triggerable assert, and adds new channel_t and circuitmux_t abstractions
3108 that will make it easier to test new connection transport and cell
3109 scheduling algorithms.
3111 o New directory authorities (also in 0.2.3.23-rc):
3112 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3113 authority. Closes ticket 5749.
3115 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
3116 - Disable TLS session tickets. OpenSSL's implementation was giving
3117 our TLS session keys the lifetime of our TLS context objects, when
3118 perfect forward secrecy would want us to discard anything that
3119 could decrypt a link connection as soon as the link connection
3120 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3121 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3122 - Discard extraneous renegotiation attempts once the V3 link
3123 protocol has been initiated. Failure to do so left us open to
3124 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3125 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3127 o Internal abstraction features:
3128 - Introduce new channel_t abstraction between circuits and
3129 or_connection_t to allow for implementing alternate OR-to-OR
3130 transports. A channel_t is an abstract object which can either be a
3131 cell-bearing channel, which is responsible for authenticating and
3132 handshaking with the remote OR and transmitting cells to and from
3133 it, or a listening channel, which spawns new cell-bearing channels
3134 at the request of remote ORs. Implements part of ticket 6465.
3135 - Also new is the channel_tls_t subclass of channel_t, adapting it
3136 to the existing or_connection_t code. The V2/V3 protocol handshaking
3137 code which formerly resided in command.c has been moved below the
3138 channel_t abstraction layer and may be found in channeltls.c now.
3139 Implements the rest of ticket 6465.
3140 - Introduce new circuitmux_t storing the queue of circuits for
3141 a channel; this encapsulates and abstracts the queue logic and
3142 circuit selection policy, and allows the latter to be overridden
3143 easily by switching out a policy object. The existing EWMA behavior
3144 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
3146 o Required libraries:
3147 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
3148 strongly recommended.
3151 - Warn users who run hidden services on a Tor client with
3152 UseEntryGuards disabled that their hidden services will be
3153 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
3154 attack which motivated Tor to support entry guards in the first
3155 place). Resolves ticket 6889.
3156 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
3157 dhill. Resolves ticket 6982.
3158 - Option OutboundBindAddress can be specified multiple times and
3159 accepts IPv6 addresses. Resolves ticket 6876.
3161 o Minor bugfixes (also in 0.2.3.23-rc):
3162 - Don't serve or accept v2 hidden service descriptors over a
3163 relay's DirPort. It's never correct to do so, and disabling it
3164 might make it more annoying to exploit any bugs that turn up in the
3165 descriptor-parsing code. Fixes bug 7149.
3166 - Fix two cases in src/or/transports.c where we were calling
3167 fmt_addr() twice in a parameter list. Bug found by David
3168 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3169 - Fix memory leaks whenever we logged any message about the "path
3170 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3171 - When relays refuse a "create" cell because their queue of pending
3172 create cells is too big (typically because their cpu can't keep up
3173 with the arrival rate), send back reason "resource limit" rather
3174 than reason "internal", so network measurement scripts can get a
3175 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
3178 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
3179 - Free some more still-in-use memory at exit, to make hunting for
3180 memory leaks easier. Resolves bug 7029.
3181 - When a Tor client gets a "truncated" relay cell, the first byte of
3182 its payload specifies why the circuit was truncated. We were
3183 ignoring this 'reason' byte when tearing down the circuit, resulting
3184 in the controller not being told why the circuit closed. Now we
3185 pass the reason from the truncated cell to the controller. Bugfix
3186 on 0.1.2.3-alpha; fixes bug 7039.
3187 - Downgrade "Failed to hand off onionskin" messages to "debug"
3188 severity, since they're typically redundant with the "Your computer
3189 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
3190 - Make clients running with IPv6 bridges connect over IPv6 again,
3191 even without setting new config options ClientUseIPv6 and
3192 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
3193 - Use square brackets around IPv6 addresses in numerous places
3194 that needed them, including log messages, HTTPS CONNECT proxy
3195 requests, TransportProxy statefile entries, and pluggable transport
3196 extra-info lines. Fixes bug 7011; patch by David Fifield.
3198 o Code refactoring and cleanup:
3199 - Source files taken from other packages now reside in src/ext;
3200 previously they were scattered around the rest of Tor.
3201 - Avoid use of reserved identifiers in our C code. The C standard
3202 doesn't like us declaring anything that starts with an
3203 underscore, so let's knock it off before we get in trouble. Fix
3204 for bug 1031; bugfix on the first Tor commit.
3207 Changes in version 0.2.3.23-rc - 2012-10-20
3208 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
3209 vulnerability introduced by a change in OpenSSL, and fixes a variety
3210 of smaller bugs in preparation for the release.
3212 o New directory authorities:
3213 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3214 authority. Closes ticket 5749.
3216 o Major bugfixes (security/privacy):
3217 - Disable TLS session tickets. OpenSSL's implementation was giving
3218 our TLS session keys the lifetime of our TLS context objects, when
3219 perfect forward secrecy would want us to discard anything that
3220 could decrypt a link connection as soon as the link connection
3221 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3222 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3223 - Discard extraneous renegotiation attempts once the V3 link
3224 protocol has been initiated. Failure to do so left us open to
3225 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3226 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3229 - Fix a possible crash bug when checking for deactivated circuits
3230 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3231 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3233 o Minor bugfixes (on 0.2.3.x):
3234 - Fix two cases in src/or/transports.c where we were calling
3235 fmt_addr() twice in a parameter list. Bug found by David
3236 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3237 - Convert an assert in the pathbias code to a log message. The assert
3238 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3239 bugfix on 0.2.3.17-beta.
3240 - Fix memory leaks whenever we logged any message about the "path
3241 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3243 o Minor bugfixes (on 0.2.2.x and earlier):
3244 - Don't serve or accept v2 hidden service descriptors over a relay's
3245 DirPort. It's never correct to do so, and disabling it might
3246 make it more annoying to exploit any bugs that turn up in the
3247 descriptor-parsing code. Fixes bug 7149.
3248 - When relays refuse a "create" cell because their queue of pending
3249 create cells is too big (typically because their cpu can't keep up
3250 with the arrival rate), send back reason "resource limit" rather
3251 than reason "internal", so network measurement scripts can get a
3252 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
3253 - Correct file sizes when reading binary files on Cygwin, to avoid
3254 a bug where Tor would fail to read its state file. Fixes bug 6844;
3255 bugfix on 0.1.2.7-alpha.
3256 - Avoid undefined behaviour when parsing the list of supported
3257 rendezvous/introduction protocols in a hidden service descriptor.
3258 Previously, Tor would have confused (as-yet-unused) protocol version
3259 numbers greater than 32 with lower ones on many platforms. Fixes
3260 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3262 o Documentation fixes:
3263 - Clarify that hidden services are TCP only. Fixes bug 6024.
3266 Changes in version 0.2.4.3-alpha - 2012-09-22
3267 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
3268 assertion, resumes letting relays test reachability of their DirPort,
3269 and cleans up a bunch of smaller bugs.
3272 - Fix an assertion failure in tor_timegm() that could be triggered
3273 by a badly formatted directory object. Bug found by fuzzing with
3274 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3277 - Fix a possible crash bug when checking for deactivated circuits
3278 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3279 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3280 - Allow routers to detect that their own DirPorts are running. When
3281 we removed support for versions_supports_begindir, we also
3282 accidentally removed the mechanism we used to self-test our
3283 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
3284 bugfix on 0.2.4.2-alpha.
3286 o Security features:
3287 - Switch to a completely time-invariant approach for picking nodes
3288 weighted by bandwidth. Our old approach would run through the
3289 part of the loop after it had made its choice slightly slower
3290 than it ran through the part of the loop before it had made its
3291 choice. Addresses ticket 6538.
3292 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
3293 by tor2web clients allows hidden services to identify tor2web
3294 clients through their repeated selection of the same rendezvous
3295 and introduction point circuit endpoints (their guards). Resolves
3299 - Enable Tor to read configuration, state, and key information from
3300 a FIFO. Previously Tor would only read from files with a positive
3301 stat.st_size. Code from meejah; fixes bug 6044.
3304 - Correct file sizes when reading binary files on Cygwin, to avoid
3305 a bug where Tor would fail to read its state file. Fixes bug 6844;
3306 bugfix on 0.1.2.7-alpha.
3307 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
3308 bugfix on 0.2.0.3-alpha.
3309 - When complaining about a client port on a public address, log
3310 which address we're complaining about. Fixes bug 4020; bugfix on
3311 0.2.3.3-alpha. Patch by Tom Fitzhenry.
3312 - Convert an assert in the pathbias code to a log message. The assert
3313 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3314 bugfix on 0.2.3.17-beta.
3315 - Our new buildsystem was overzealous about rebuilding manpages: it
3316 would rebuild them all whenever any one of them changed. Now our
3317 dependency checking should be correct. Fixes bug 6843; bugfix on
3319 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
3320 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
3321 - Correct log printout about which address family is preferred
3322 when connecting to a bridge with both an IPv4 and IPv6 OR port.
3323 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
3325 o Minor bugfixes (code cleanliness):
3326 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
3327 with large values. This situation was untriggered, but nevertheless
3328 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
3329 - Reject consensus votes with more than 64 known-flags. We aren't even
3330 close to that limit yet, and our code doesn't handle it correctly.
3331 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
3332 - Avoid undefined behaviour when parsing the list of supported
3333 rendezvous/introduction protocols in a hidden service descriptor.
3334 Previously, Tor would have confused (as-yet-unused) protocol version
3335 numbers greater than 32 with lower ones on many platforms. Fixes
3336 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3337 - Fix handling of rendezvous client authorization types over 8.
3338 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
3339 - Fix building with older versions of GCC (2.95, for one) that don't
3340 like preprocessor directives inside macro arguments. Found by
3341 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
3342 - Switch weighted node selection rule from using a list of doubles
3343 to using a list of int64_t. This change should make the process
3344 slightly easier to debug and maintain. Needed to finish ticket 6538.
3346 o Code simplification and refactoring:
3347 - Move the generic "config" code into a new file, and have "config.c"
3348 hold only torrc- and state-related code. Resolves ticket 6823.
3349 - Move the core of our "choose a weighted element at random" logic
3350 into its own function, and give it unit tests. Now the logic is
3351 testable, and a little less fragile too.
3352 - Removed the testing_since field of node_t, which hasn't been used
3353 for anything since 0.2.0.9-alpha.
3355 o Documentation fixes:
3356 - Clarify that hidden services are TCP only. Fixes bug 6024.
3357 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
3361 Changes in version 0.2.3.22-rc - 2012-09-11
3362 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
3366 - Fix an assertion failure in tor_timegm() that could be triggered
3367 by a badly formatted directory object. Bug found by fuzzing with
3368 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3371 - Avoid segfault when starting up having run with an extremely old
3372 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3376 Changes in version 0.2.2.39 - 2012-09-11
3377 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
3381 - Fix an assertion failure in tor_timegm() that could be triggered
3382 by a badly formatted directory object. Bug found by fuzzing with
3383 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3384 - Do not crash when comparing an address with port value 0 to an
3385 address policy. This bug could have been used to cause a remote
3386 assertion failure by or against directory authorities, or to
3387 allow some applications to crash clients. Fixes bug 6690; bugfix
3391 Changes in version 0.2.4.2-alpha - 2012-09-10
3392 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
3393 raises the default rate limiting even more, and makes the bootstrapping
3394 log messages less noisy.
3397 - Automatically forward the TCP ports of pluggable transport
3398 proxies using tor-fw-helper if PortForwarding is enabled. Implements
3402 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
3403 to 1GB/1GB. The previous defaults were intended to be "basically
3404 infinite", but it turns out they're now limiting our 100mbit+
3405 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
3406 last time we raised it).
3409 - Detect when we're running with a version of OpenSSL other than the
3410 one we compiled with. This has occasionally given people hard-to-
3412 - Log fewer lines at level "notice" about our OpenSSL and Libevent
3413 versions and capabilities when everything is going right. Resolves
3414 part of ticket 6736.
3415 - Directory authorities no long accept descriptors for any version of
3416 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
3417 These versions are insecure, unsupported, or both. Implements
3421 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
3422 to start with a triple-underscore so the controller won't touch it.
3423 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
3424 - Avoid segfault when starting up having run with an extremely old
3425 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3427 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
3428 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
3429 - Don't follow the NULL pointer if microdescriptor generation fails.
3430 (This does not appear to be triggerable, but it's best to be safe.)
3431 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
3432 - Fix mis-declared dependencies on src/common/crypto.c and
3433 src/or/tor_main.c that could break out-of-tree builds under some
3434 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
3435 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
3436 6778; bugfix on 0.2.4.1-alpha.
3437 - Fix a harmless (in this case) build warning for implicitly
3438 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
3441 - Now that all versions before 0.2.2.x are disallowed, we no longer
3442 need to work around their missing features. Thus we can remove a
3443 bunch of compatibility code.
3446 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
3447 TCP ports to forward. In the past it only accepted two ports:
3448 the ORPort and the DirPort.
3451 Changes in version 0.2.4.1-alpha - 2012-09-05
3452 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
3453 bridgedb; lets relays use IPv6 addresses and directory authorities
3454 advertise them; and switches to a cleaner build interface.
3456 This is the first alpha release in a new series, so expect there to
3457 be bugs. Users who would rather test out a more stable branch should
3458 stay with 0.2.3.x for now.
3460 o Major features (bridges):
3461 - Bridges now report the pluggable transports they support to the
3462 bridge authority, so it can pass the supported transports on to
3463 bridgedb and/or eventually do reachability testing. Implements
3466 o Major features (IPv6):
3467 - Bridge authorities now accept IPv6 bridge addresses and include
3468 them in network status documents. Implements ticket 5534.
3469 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
3470 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
3471 to happen. Implements ticket 5535.
3472 - All kind of relays, not just bridges, can now advertise an IPv6
3473 OR port. Implements ticket 6362.
3474 - Directory authorities vote on IPv6 OR ports using the new consensus
3475 method 14. Implements ticket 6363.
3477 o Major features (build):
3478 - Switch to a nonrecursive Makefile structure. Now instead of each
3479 Makefile.am invoking other Makefile.am's, there is a master
3480 Makefile.am that includes the others. This change makes our build
3481 process slightly more maintainable, and improves parallelism for
3482 building with make -j. Original patch by Stewart Smith; various
3483 fixes by Jim Meyering.
3484 - Where available, we now use automake's "silent" make rules by
3485 default, so that warnings are easier to spot. You can get the old
3486 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
3488 o Minor features (code security and spec conformance):
3489 - Clear keys and key-derived material left on the stack in
3490 rendservice.c and rendclient.c. Check return value of
3491 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
3492 These fixes should make us more forward-secure against cold-boot
3493 attacks and the like. Fixes bug 2385.
3494 - Reject EXTEND cells sent to nonexistent streams. According to the
3495 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
3496 we were only checking for stream IDs that were currently in use.
3497 Found while hunting for more instances of bug 6271. Bugfix on
3498 0.0.2pre8, which introduced incremental circuit construction.
3500 o Minor features (streamlining);
3501 - No longer include the "opt" prefix when generating routerinfos
3502 or v2 directories: it has been needless since Tor 0.1.2. Closes
3504 - Remove some now-needless code that tried to aggressively flush
3505 OR connections as data was added to them. Since 0.2.0.1-alpha, our
3506 cell queue logic has saved us from the failure mode that this code
3507 was supposed to prevent. Removing this code will limit the number
3508 of baroque control flow paths through Tor's network logic. Reported
3509 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
3511 o Minor features (controller):
3512 - Add a "GETINFO signal/names" control port command. Implements
3514 - Provide default values for all options via "GETINFO config/defaults".
3515 Implements ticket 4971.
3517 o Minor features (IPv6):
3518 - New config option "AuthDirHasIPv6Connectivity 1" that directory
3519 authorities should set if they have IPv6 connectivity and want to
3520 do reachability tests for IPv6 relays. Implements feature 5974.
3521 - A relay with an IPv6 OR port now sends that address in NETINFO
3522 cells (in addition to its other address). Implements ticket 6364.
3524 o Minor features (log messages):
3525 - Omit the first heartbeat log message, because it never has anything
3526 useful to say, and it clutters up the bootstrapping messages.
3527 Resolves ticket 6758.
3528 - Don't log about reloading the microdescriptor cache at startup. Our
3529 bootstrap warnings are supposed to tell the user when there's a
3530 problem, and our bootstrap notices say when there isn't. Resolves
3531 ticket 6759; bugfix on 0.2.2.6-alpha.
3532 - Don't log "I learned some more directory information" when we're
3533 reading cached directory information. Reserve it for when new
3534 directory information arrives in response to a fetch. Resolves
3536 - Prevent rounding error in path bias counts when scaling
3537 them down, and use the correct scale factor default. Also demote
3538 some path bias related log messages down a level and make others
3539 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
3540 - We no longer warn so much when generating manpages from their
3543 o Code simplifications and refactoring:
3544 - Enhance our internal sscanf replacement so that we can eliminate
3545 the last remaining uses of the system sscanf. (Though those uses
3546 of sscanf were safe, sscanf itself is generally error prone, so
3547 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
3549 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
3550 - Move last_reachable and testing_since from routerinfo_t to node_t.
3551 Implements ticket 5529.
3552 - Add replaycache_t structure, functions and unit tests, then refactor
3553 rend_service_introduce() to be more clear to read, improve, debug,
3554 and test. Resolves bug 6177.
3555 - Finally remove support for malloc_good_size and malloc_usable_size.
3556 We had hoped that these functions would let us eke a little more
3557 memory out of our malloc implementation. Unfortunately, the only
3558 implementations that provided these functions are also ones that
3559 are already efficient about not overallocation: they never got us
3560 more than 7 or so bytes per allocation. Removing them saves us a
3561 little code complexity and a nontrivial amount of build complexity.
3564 - Tor maintainers now require Automake version 1.9 or later to build
3565 Tor from the Git repository. (Automake is not required when building
3566 from a source distribution.)
3569 Changes in version 0.2.3.21-rc - 2012-09-05
3570 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
3571 series. It fixes a trio of potential security bugs, fixes a bug where
3572 we were leaving some of the fast relays out of the microdescriptor
3573 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
3574 and cleans up other smaller issues.
3576 o Major bugfixes (security):
3577 - Tear down the circuit if we get an unexpected SENDME cell. Clients
3578 could use this trick to make their circuits receive cells faster
3579 than our flow control would have allowed, or to gum up the network,
3580 or possibly to do targeted memory denial-of-service attacks on
3581 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
3582 from July 2002, before the release of Tor 0.0.0. We had committed
3583 this patch previously, but we had to revert it because of bug 6271.
3584 Now that 6271 is fixed, this patch appears to work.
3585 - Reject any attempt to extend to an internal address. Without
3586 this fix, a router could be used to probe addresses on an internal
3587 network to see whether they were accepting connections. Fixes bug
3588 6710; bugfix on 0.0.8pre1.
3589 - Do not crash when comparing an address with port value 0 to an
3590 address policy. This bug could have been used to cause a remote
3591 assertion failure by or against directory authorities, or to
3592 allow some applications to crash clients. Fixes bug 6690; bugfix
3596 - Remove the upper bound on microdescriptor length. We were hitting
3597 the limit for routers with complex exit policies or family
3598 declarations, causing clients to not use them. Fixes the first
3599 piece of bug 6404; fix on 0.2.2.6-alpha.
3600 - Detect "ORPort 0" as meaning, uniformly, that we're not running
3601 as a relay. Previously, some of our code would treat the presence
3602 of any ORPort line as meaning that we should act like a relay,
3603 even though our new listener code would correctly not open any
3604 ORPorts for ORPort 0. Similar bugs in other Port options are also
3605 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
3608 - Avoid a pair of double-free and use-after-mark bugs that can
3609 occur with certain timings in canceled and re-received DNS
3610 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
3611 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
3612 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
3613 - Allow one-hop directory fetching circuits the full "circuit build
3614 timeout" period, rather than just half of it, before failing them
3615 and marking the relay down. This fix should help reduce cases where
3616 clients declare relays (or worse, bridges) unreachable because
3617 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
3618 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
3620 - Authorities no longer include any router in their microdescriptor
3621 consensuses for which they couldn't generate or agree on a
3622 microdescriptor. Fixes the second piece of bug 6404; fix on
3624 - Detect and reject attempts to specify both "FooPort" and
3625 "FooPort 0" in the same configuration domain. (It's still okay
3626 to have a FooPort in your configuration file, and use "FooPort 0"
3627 on the command line to disable it.) Fixes the second half of bug
3628 6507; bugfix on 0.2.3.3-alpha.
3629 - Make wildcarded addresses (that is, ones beginning with "*.") work
3630 when provided via the controller's MapAddress command. Previously,
3631 they were accepted, but we never actually noticed that they were
3632 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
3633 - Avoid crashing on a malformed state file where EntryGuardPathBias
3634 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
3635 - Add a (probably redundant) memory clear between iterations of
3636 the router status voting loop, to prevent future coding errors
3637 where data might leak between iterations of the loop. Resolves
3640 o Minor bugfixes (log messages):
3641 - Downgrade "set buildtimeout to low value" messages to "info"
3642 severity; they were never an actual problem, there was never
3643 anything reasonable to do about them, and they tended to spam logs
3644 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
3645 - Downgrade path-bias warning messages to "info". We'll try to get
3646 them working better in 0.2.4. Add internal circuit construction
3647 state to protect against the noisy warn message "Unexpectedly high
3648 circuit_successes". Also add some additional rate-limited notice
3649 messages to help determine the root cause of the warn. Fixes bug
3650 6475. Bugfix against 0.2.3.17-beta.
3651 - Move log message when unable to find a microdesc in a routerstatus
3652 entry to parse time. Previously we'd spam this warning every time
3653 we tried to figure out which microdescriptors to download. Fixes
3654 the third piece of bug 6404; fix on 0.2.3.18-rc.
3657 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
3658 change when the authority is deciding whether to accept a newly
3659 uploaded descriptor. Implements ticket 6423.
3660 - Add missing documentation for consensus and microdesc files.
3661 Resolves ticket 6732.
3664 Changes in version 0.2.2.38 - 2012-08-12
3665 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
3666 attack that could in theory leak path information.
3669 - Avoid an uninitialized memory read when reading a vote or consensus
3670 document that has an unrecognized flavor name. This read could
3671 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3672 - Try to leak less information about what relays a client is
3673 choosing to a side-channel attacker. Previously, a Tor client would
3674 stop iterating through the list of available relays as soon as it
3675 had chosen one, thus finishing a little earlier when it picked
3676 a router earlier in the list. If an attacker can recover this
3677 timing information (nontrivial but not proven to be impossible),
3678 they could learn some coarse-grained information about which relays
3679 a client was picking (middle nodes in particular are likelier to
3680 be affected than exits). The timing attack might be mitigated by
3681 other factors (see bug 6537 for some discussion), but it's best
3682 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3685 Changes in version 0.2.3.20-rc - 2012-08-05
3686 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
3687 series. It fixes a pair of code security bugs and a potential anonymity
3688 issue, updates our RPM spec files, and cleans up other smaller issues.
3691 - Avoid read-from-freed-memory and double-free bugs that could occur
3692 when a DNS request fails while launching it. Fixes bug 6480;
3693 bugfix on 0.2.0.1-alpha.
3694 - Avoid an uninitialized memory read when reading a vote or consensus
3695 document that has an unrecognized flavor name. This read could
3696 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3697 - Try to leak less information about what relays a client is
3698 choosing to a side-channel attacker. Previously, a Tor client would
3699 stop iterating through the list of available relays as soon as it
3700 had chosen one, thus finishing a little earlier when it picked
3701 a router earlier in the list. If an attacker can recover this
3702 timing information (nontrivial but not proven to be impossible),
3703 they could learn some coarse-grained information about which relays
3704 a client was picking (middle nodes in particular are likelier to
3705 be affected than exits). The timing attack might be mitigated by
3706 other factors (see bug 6537 for some discussion), but it's best
3707 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3710 - Try to make the warning when giving an obsolete SOCKSListenAddress
3711 a little more useful.
3712 - Terminate active server managed proxies if Tor stops being a
3713 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
3714 - Provide a better error message about possible OSX Asciidoc failure
3715 reasons. Fixes bug 6436.
3716 - Warn when Tor is configured to use accounting in a way that can
3717 link a hidden service to some other hidden service or public
3718 address. Resolves ticket 6490.
3721 - Check return value of fputs() when writing authority certificate
3722 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
3723 - Ignore ServerTransportPlugin lines when Tor is not configured as
3724 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
3725 - When disabling guards for having too high a proportion of failed
3726 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
3730 - Update our default RPM spec files to work with mock and rpmbuild
3731 on RHEL/Fedora. They have an updated set of dependencies and
3732 conflicts, a fix for an ancient typo when creating the "_tor"
3733 user, and better instructions. Thanks to Ondrej Mikle for the
3734 patch series. Fixes bug 6043.
3737 - Make it possible to set the TestingTorNetwork configuration
3738 option using AlternateDirAuthority and AlternateBridgeAuthority
3739 as an alternative to setting DirServer. Addresses ticket 6377.
3742 - Clarify the documentation for the Alternate*Authority options.
3744 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
3746 o Code simplification and refactoring:
3747 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
3748 10 lines. Also, don't nest them. Doing so in the past has
3749 led to hard-to-debug code. The new style is to use the
3750 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
3753 Changes in version 0.2.3.19-rc - 2012-07-06
3754 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
3755 series. It fixes the compile on Windows, reverts to a GeoIP database
3756 that isn't as broken, and fixes a flow control bug that has been around
3757 since the beginning of Tor.
3760 - Fix a bug handling SENDME cells on nonexistent streams that could
3761 result in bizarre window values. Report and patch contributed
3762 pseudonymously. Fixes part of bug 6271. This bug was introduced
3763 before the first Tor release, in svn commit r152.
3764 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
3765 June 2012 database, Maxmind marked many Tor relays as country "A1",
3766 which will cause risky behavior for clients that set EntryNodes
3767 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
3768 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
3769 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
3772 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
3773 bugfix on 0.2.1.10-alpha.
3776 Changes in version 0.2.3.18-rc - 2012-06-28
3777 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
3778 series. It fixes a few smaller bugs, but generally appears stable.
3779 Please test it and let us know whether it is!
3782 - Allow wildcarded mapaddress targets to be specified on the
3783 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
3784 - Make our linker option detection code more robust against linkers
3785 such as on FreeBSD 8, where a bad combination of options completes
3786 successfully but makes an unrunnable binary. Fixes bug 6173;
3787 bugfix on 0.2.3.17-beta.
3789 o Minor bugfixes (on 0.2.2.x and earlier):
3790 - Avoid a false positive in the util/threads unit test by increasing
3791 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
3792 - Replace "Sending publish request" log messages with "Launching
3793 upload", so that they no longer confusingly imply that we're
3794 sending something to a directory we might not even be connected
3795 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
3796 - Make sure to set *socket_error in all error cases in
3797 connection_connect(), so it can't produce a warning about
3798 errno being zero from errno_to_orconn_end_reason(). Bugfix on
3799 0.2.1.1-alpha; resolves ticket 6028.
3800 - Downgrade "Got a certificate, but we already have it" log messages
3801 from warning to info, except when we're a dirauth. Fixes bug 5238;
3802 bugfix on 0.2.1.7-alpha.
3803 - When checking for requested signatures on the latest consensus
3804 before serving it to a client, make sure to check the right
3805 consensus flavor. Bugfix on 0.2.2.6-alpha.
3806 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
3807 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
3809 o Minor bugfixes (on 0.2.3.x):
3810 - Make format_helper_exit_status() avoid unnecessary space padding
3811 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
3813 - Downgrade a message about cleaning the microdescriptor cache to
3814 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
3815 - Log a BUG message at severity INFO if we have a networkstatus with
3816 a missing entry for some microdescriptor. Continues on a patch
3818 - Improve the log message when a managed proxy fails to launch. Fixes
3819 bug 5099; bugfix on 0.2.3.6-alpha.
3820 - Don't do DNS lookups when parsing corrupted managed proxy protocol
3821 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
3822 - When formatting wildcarded address mappings for the controller,
3823 be sure to include "*." as appropriate. Partially fixes bug 6244;
3824 bugfix on 0.2.3.9-alpha.
3825 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
3826 Bugfix on 0.2.3.13-alpha.
3827 - Stop logging messages about running with circuit timeout learning
3828 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
3829 - Disable a spurious warning about reading on a marked and flushing
3830 connection. We shouldn't be doing that, but apparently we
3831 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
3832 - Fix a bug that stopped AllowDotExit from working on addresses
3833 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
3836 o Code simplification, refactoring, unit tests:
3837 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
3838 Libevent's notion of cached time when possible.
3839 - Remove duplicate code for invoking getrlimit() from control.c.
3840 - Add a unit test for the environment_variable_names_equal function.
3843 - Document the --defaults-torrc option, and the new (in 0.2.3)
3844 semantics for overriding, extending, and clearing lists of
3845 options. Closes bug 4748.
3848 Changes in version 0.2.3.17-beta - 2012-06-15
3849 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
3850 gets our TLS handshake back on track for being able to blend in with
3851 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
3852 with Vidalia, and otherwise continues to get us closer to a release
3856 - Enable gcc and ld hardening by default. Resolves ticket 5210.
3857 - Update TLS cipher list to match Firefox 8 and later. Resolves
3859 - Implement the client side of proposal 198: remove support for
3860 clients falsely claiming to support standard ciphersuites that
3861 they can actually provide. As of modern OpenSSL versions, it's not
3862 necessary to fake any standard ciphersuite, and doing so prevents
3863 us from using better ciphersuites in the future, since servers
3864 can't know whether an advertised ciphersuite is really supported or
3865 not. Some hosts -- notably, ones with very old versions of OpenSSL
3866 or where OpenSSL has been built with ECC disabled -- will stand
3867 out because of this change; TBB users should not be affected.
3870 - Change the default value for DynamicDHGroups (introduced in
3871 0.2.3.9-alpha) to 0. This feature can make Tor relays less
3872 identifiable by their use of the mod_ssl DH group, but at
3873 the cost of some usability (#4721) and bridge tracing (#6087)
3874 regressions. Resolves ticket 5598.
3875 - Send a CRLF at the end of each STATUS_* control protocol event. This
3876 bug tickled a bug in Vidalia which would make it freeze. Fixes
3877 bug 6094; bugfix on 0.2.3.16-alpha.
3880 - Disable writing on marked-for-close connections when they are
3881 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
3882 bug 5263; bugfix on 0.0.2pre13, where we first added a special
3883 case for flushing marked connections.
3884 - Detect SSL handshake even when the initial attempt to write the
3885 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
3886 - Change the AllowDotExit rules so they should actually work.
3887 We now enforce AllowDotExit only immediately after receiving an
3888 address via SOCKS or DNSPort: other sources are free to provide
3889 .exit addresses after the resolution occurs. Fixes bug 3940;
3890 bugfix on 0.2.2.1-alpha.
3891 - Fix a (harmless) integer overflow in cell statistics reported by
3892 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
3893 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
3894 right places and never depends on the consensus parameters or
3895 computes adaptive timeouts when it is disabled. Fixes bug 5049;
3896 bugfix on 0.2.2.14-alpha.
3897 - When building Tor on Windows with -DUNICODE (not default), ensure
3898 that error messages, filenames, and DNS server names are always
3899 NUL-terminated when we convert them to a single-byte encoding.
3900 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
3901 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
3902 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
3903 - Fix an edge case where TestingTorNetwork is set but the authorities
3904 and relays all have an uptime of zero, where the private Tor network
3905 could briefly lack support for hidden services. Fixes bug 3886;
3906 bugfix on 0.2.2.18-alpha.
3907 - Correct the manpage's descriptions for the default values of
3908 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
3910 - Fix the documentation for the --hush and --quiet command line
3911 options, which changed their behavior back in 0.2.3.3-alpha.
3912 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
3916 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
3917 more information to it, so that we can track it down in case it
3918 returns again. Mitigates bug 5235.
3919 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
3920 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
3921 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
3922 - Warn the user when HTTPProxy, but no other proxy type, is
3923 configured. This can cause surprising behavior: it doesn't send
3924 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
3925 directory traffic only. Resolves ticket 4663.
3926 - Issue a notice if a guard completes less than 40% of your circuits.
3927 Threshold is configurable by torrc option PathBiasNoticeRate and
3928 consensus parameter pb_noticepct. There is additional, off-by-
3929 default code to disable guards which fail too many circuits.
3930 Addresses ticket 5458.
3931 - Update to the June 6 2012 Maxmind GeoLite Country database.
3933 o Code simplifications and refactoring:
3934 - Remove validate_pluggable_transports_config(): its warning
3935 message is now handled by connection_or_connect().
3938 Changes in version 0.2.2.37 - 2012-06-06
3939 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
3940 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3944 - Work around a bug in OpenSSL that broke renegotiation with TLS
3945 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3946 the v2 Tor connection protocol when both sides were using OpenSSL
3947 1.0.1 would fail. Resolves ticket 6033.
3948 - When waiting for a client to renegotiate, don't allow it to add
3949 any bytes to the input buffer. This fixes a potential DoS issue.
3950 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3951 - Fix an edge case where if we fetch or publish a hidden service
3952 descriptor, we might build a 4-hop circuit and then use that circuit
3953 for exiting afterwards -- even if the new last hop doesn't obey our
3954 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3957 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3958 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3961 - Tell GCC and Clang to check for any errors in format strings passed
3962 to the tor_v*(print|scan)f functions.
3965 Changes in version 0.2.3.16-alpha - 2012-06-05
3966 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
3967 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3968 currently). It also fixes a variety of smaller bugs and other cleanups
3969 that get us closer to a release candidate.
3971 o Major bugfixes (general):
3972 - Work around a bug in OpenSSL that broke renegotiation with TLS
3973 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3974 the v2 Tor connection protocol when both sides were using OpenSSL
3975 1.0.1 would fail. Resolves ticket 6033.
3976 - When waiting for a client to renegotiate, don't allow it to add
3977 any bytes to the input buffer. This fixes a potential DoS issue.
3978 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3979 - Pass correct OR address to managed proxies (like obfsproxy),
3980 even when ORListenAddress is used. Fixes bug 4865; bugfix on
3982 - The advertised platform of a router now includes only its operating
3983 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
3984 service pack level (for Windows) or its CPU architecture (for Unix).
3985 We also no longer include the "git-XYZ" tag in the version. Resolves
3988 o Major bugfixes (clients):
3989 - If we are unable to find any exit that supports our predicted ports,
3990 stop calling them predicted, so that we don't loop and build
3991 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
3992 which introduced predicted ports.
3993 - Fix an edge case where if we fetch or publish a hidden service
3994 descriptor, we might build a 4-hop circuit and then use that circuit
3995 for exiting afterwards -- even if the new last hop doesn't obey our
3996 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3997 - Check at each new consensus whether our entry guards were picked
3998 long enough ago that we should rotate them. Previously, we only
3999 did this check at startup, which could lead to us holding a guard
4000 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
4001 - When fetching a bridge descriptor from a bridge authority,
4002 always do so anonymously, whether we have been able to open
4003 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
4004 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
4005 but we'll need to wait for bug 6010 before it's actually usable.
4007 o Major bugfixes (directory authorities):
4008 - When computing weight parameters, behave more robustly in the
4009 presence of a bad bwweightscale value. Previously, the authorities
4010 would crash if they agreed on a sufficiently broken weight_scale
4011 value: now, they use a reasonable default and carry on. Partial
4012 fix for 5786; bugfix on 0.2.2.17-alpha.
4013 - Check more thoroughly to prevent a rogue authority from
4014 double-voting on any consensus directory parameter. Previously,
4015 authorities would crash in this case if the total number of
4016 votes for any parameter exceeded the number of active voters,
4017 but would let it pass otherwise. Partial fix for bug 5786; bugfix
4021 - Rate-limit log messages when asked to connect anonymously to
4022 a private address. When these hit, they tended to hit fast and
4023 often. Also, don't bother trying to connect to addresses that we
4024 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
4025 reply makes us think we have been lied to, even when the address the
4026 client tried to connect to was "localhost." Resolves ticket 2822.
4027 - Allow packagers to insert an extra string in server descriptor
4028 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
4029 Resolves the rest of ticket 2988.
4030 - Raise the threshold of server descriptors needed (75%) and exit
4031 server descriptors needed (50%) before we will declare ourselves
4032 bootstrapped. This will make clients start building circuits a
4033 little later, but makes the initially constructed circuits less
4034 skewed and less in conflict with further directory fetches. Fixes
4036 - Close any connection that sends unrecognized junk before the
4037 handshake. Solves an issue noted in bug 4369.
4038 - Improve log messages about managed transports. Resolves ticket 5070.
4039 - Tag a bridge's descriptor as "never to be sent unencrypted".
4040 This shouldn't matter, since bridges don't open non-anonymous
4041 connections to the bridge authority and don't allow unencrypted
4042 directory connections from clients, but we might as well make
4043 sure. Closes bug 5139.
4044 - Expose our view of whether we have gone dormant to the controller,
4045 via a new "GETINFO dormant" value. Torbutton and other controllers
4046 can use this to avoid doing periodic requests through Tor while
4047 it's dormant (bug 4718). Fixes bug 5954.
4048 - Tell GCC and Clang to check for any errors in format strings passed
4049 to the tor_v*(print|scan)f functions.
4050 - Update to the May 1 2012 Maxmind GeoLite Country database.
4052 o Minor bugfixes (already included in 0.2.2.36):
4053 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4054 Fixes bug 5346; bugfix on 0.0.8pre3.
4055 - Correct parsing of certain date types in parse_http_time().
4056 Without this patch, If-Modified-Since would behave
4057 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4058 Esteban Manchado Velázques.
4059 - Make our number-parsing functions always treat too-large values
4060 as an error, even when those values exceed the width of the
4061 underlying type. Previously, if the caller provided these
4062 functions with minima or maxima set to the extreme values of the
4063 underlying integer type, these functions would return those
4064 values on overflow rather than treating overflow as an error.
4065 Fixes part of bug 5786; bugfix on 0.0.9.
4066 - If we hit the error case where routerlist_insert() replaces an
4067 existing (old) server descriptor, make sure to remove that
4068 server descriptor from the old_routers list. Fix related to bug
4069 1776. Bugfix on 0.2.2.18-alpha.
4070 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4071 circuits. Fixes issue 5259.
4073 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
4074 - Prevent a null-pointer dereference when receiving a data cell
4075 for a nonexistent stream when the circuit in question has an
4076 empty deliver window. We don't believe this is triggerable,
4077 since we don't currently allow deliver windows to become empty,
4078 but the logic is tricky enough that it's better to make the code
4079 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
4080 - Fix a memory leak when trying to launch a DNS request when the
4081 network is disabled or the nameservers are unconfigurable. Fixes
4082 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
4083 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
4084 - Don't hold a Windows file handle open for every file mapping;
4085 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
4087 - Avoid O(n^2) performance characteristics when parsing a large
4088 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
4089 - Format more doubles with %f, not %lf. Patch from grarpamp to make
4090 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
4092 - Make our replacement implementation of strtok_r() compatible with
4093 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
4094 bugfix on 0.2.2.1-alpha.
4095 - Fix a NULL-pointer dereference on a badly formed
4096 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
4097 bugfix on 0.2.2.9-alpha.
4098 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
4099 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
4100 - Defensively refactor rend_mid_rendezvous() so that protocol
4101 violations and length checks happen in the beginning. Fixes
4103 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
4104 that IPv6 stuff will compile on MSVC, and compilation issues
4105 will be easier to track down. Fixes bug 5861.
4107 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
4108 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
4109 resource exhaustion, so that clients can adjust their load to
4110 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
4111 started using END_STREAM_REASON_RESOURCELIMIT.
4112 - Don't check for whether the address we're using for outbound
4113 connections has changed until after the outbound connection has
4114 completed. On Windows, getsockname() doesn't succeed until the
4115 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
4116 - If the configuration tries to set MyFamily on a bridge, refuse to
4117 do so, and warn about the security implications. Fixes bug 4657;
4118 bugfix on 0.2.0.3-alpha.
4119 - If the client fails to set a reasonable set of ciphersuites
4120 during its v2 handshake renegotiation, allow the renegotiation to
4121 continue nevertheless (i.e. send all the required certificates).
4122 Fixes bug 4591; bugfix on 0.2.0.20-rc.
4123 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
4124 option is set to 0 (which Vidalia version 0.2.16 now does when
4125 a SAVECONF attempt fails), perform other actions that SIGHUP
4126 usually causes (like reopening the logs). Fixes bug 5095; bugfix
4128 - If we fail to write a microdescriptor to the disk cache, do not
4129 continue replacing the old microdescriptor file. Fixes bug 2954;
4130 bugfix on 0.2.2.6-alpha.
4131 - Exit nodes don't need to fetch certificates for authorities that
4132 they don't recognize; only directory authorities, bridges,
4133 and caches need to do that. Fixes part of bug 2297; bugfix on
4135 - Correctly handle checking the permissions on the parent
4136 directory of a control socket in the root directory. Bug found
4137 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
4139 - When told to add a bridge with the same digest as a preexisting
4140 bridge but a different addr:port, change the addr:port as
4141 requested. Previously we would not notice the change. Fixes half
4142 of bug 5603; fix on 0.2.2.26-beta.
4143 - End AUTHCHALLENGE error messages (in the control protocol) with
4144 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
4146 o Minor bugfixes (on 0.2.3.x):
4147 - Turn an assertion (that the number of handshakes received as a
4148 server is not < 1) into a warning. Fixes bug 4873; bugfix on
4150 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
4151 we had reversed them when the answer was cached.) Fixes bug
4152 5723; bugfix on 0.2.3.1-alpha.
4153 - Work correctly on Linux systems with accept4 support advertised in
4154 their headers, but without accept4 support in the kernel. Fix
4155 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
4156 - When told to add a bridge with the same addr:port as a preexisting
4157 bridge but a different transport, change the transport as
4158 requested. Previously we would not notice the change. Fixes half
4159 of bug 5603; fix on 0.2.3.2-alpha.
4160 - Avoid a "double-reply" warning when replying to a SOCKS request
4161 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
4162 bugfix on 0.2.3.4-alpha.
4163 - Fix a bug where a bridge authority crashes if it has seen no
4164 directory requests when it's time to write statistics to disk.
4165 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
4167 - Don't try to open non-control listeners when DisableNetwork is set.
4168 Previously, we'd open all listeners, then immediately close them.
4169 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
4170 - Don't abort the managed proxy protocol if the managed proxy
4171 sends us an unrecognized line; ignore it instead. Fixes bug
4172 5910; bugfix on 0.2.3.9-alpha.
4173 - Fix a compile warning in crypto.c when compiling with clang 3.1.
4174 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
4175 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
4176 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
4177 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
4178 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
4179 - Resolve numerous small warnings and build issues with MSVC. Resolves
4182 o Documentation fixes:
4183 - Improve the manual's documentation for the NT Service command-line
4184 options. Addresses ticket 3964.
4185 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
4186 - Document the changes to the ORPort and DirPort options, and the
4187 fact that {OR/Dir}ListenAddress is now unnecessary (and
4188 therefore deprecated). Resolves ticket 5597.
4191 - Remove the torrc.bridge file: we don't use it for anything, and
4192 it had become badly desynchronized from torrc.sample. Resolves
4196 Changes in version 0.2.2.36 - 2012-05-24
4197 Tor 0.2.2.36 updates the addresses for two of the eight directory
4198 authorities, fixes some potential anonymity and security issues,
4199 and fixes several crash bugs.
4201 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
4202 known flaws, and nobody should be using them. You should upgrade. If
4203 you're using a Linux or BSD and its packages are obsolete, stop using
4204 those packages and upgrade anyway.
4206 o Directory authority changes:
4207 - Change IP address for maatuska (v3 directory authority).
4208 - Change IP address for ides (v3 directory authority), and rename
4212 - When building or running with any version of OpenSSL earlier
4213 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4214 versions have a bug (CVE-2011-4576) in which their block cipher
4215 padding includes uninitialized data, potentially leaking sensitive
4216 information to any peer with whom they make a SSLv3 connection. Tor
4217 does not use SSL v3 by default, but a hostile client or server
4218 could force an SSLv3 connection in order to gain information that
4219 they shouldn't have been able to get. The best solution here is to
4220 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4221 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4222 to make sure that the bug can't happen.
4223 - Never use a bridge or a controller-supplied node as an exit, even
4224 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4225 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4226 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4227 - Only build circuits if we have a sufficient threshold of the total
4228 descriptors that are marked in the consensus with the "Exit"
4229 flag. This mitigates an attack proposed by wanoskarnet, in which
4230 all of a client's bridges collude to restrict the exit nodes that
4231 the client knows about. Fixes bug 5343.
4232 - Provide controllers with a safer way to implement the cookie
4233 authentication mechanism. With the old method, if another locally
4234 running program could convince a controller that it was the Tor
4235 process, then that program could trick the controller into telling
4236 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4237 authentication method uses a challenge-response approach to prevent
4238 this attack. Fixes bug 5185; implements proposal 193.
4241 - Avoid logging uninitialized data when unable to decode a hidden
4242 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4243 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4244 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4246 - Fix builds when the path to sed, openssl, or sha1sum contains
4247 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4249 - Correct our replacements for the timeradd() and timersub() functions
4250 on platforms that lack them (for example, Windows). The timersub()
4251 function is used when expiring circuits, while timeradd() is
4252 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4253 bugfix on 0.2.2.24-alpha.
4254 - Fix the SOCKET_OK test that we use to tell when socket
4255 creation fails so that it works on Win64. Fixes part of bug 4533;
4256 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4259 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4260 Fixes bug 5346; bugfix on 0.0.8pre3.
4261 - Make our number-parsing functions always treat too-large values
4262 as an error, even when those values exceed the width of the
4263 underlying type. Previously, if the caller provided these
4264 functions with minima or maxima set to the extreme values of the
4265 underlying integer type, these functions would return those
4266 values on overflow rather than treating overflow as an error.
4267 Fixes part of bug 5786; bugfix on 0.0.9.
4268 - Older Linux kernels erroneously respond to strange nmap behavior
4269 by having accept() return successfully with a zero-length
4270 socket. When this happens, just close the connection. Previously,
4271 we would try harder to learn the remote address: but there was
4272 no such remote address to learn, and our method for trying to
4273 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4274 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4275 - Correct parsing of certain date types in parse_http_time().
4276 Without this patch, If-Modified-Since would behave
4277 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4278 Esteban Manchado Velázques.
4279 - Change the BridgePassword feature (part of the "bridge community"
4280 design, which is not yet implemented) to use a time-independent
4281 comparison. The old behavior might have allowed an adversary
4282 to use timing to guess the BridgePassword value. Fixes bug 5543;
4283 bugfix on 0.2.0.14-alpha.
4284 - Detect and reject certain misformed escape sequences in
4285 configuration values. Previously, these values would cause us
4286 to crash if received in a torrc file or over an authenticated
4287 control port. Bug found by Esteban Manchado Velázquez, and
4288 independently by Robert Connolly from Matta Consulting who further
4289 noted that it allows a post-authentication heap overflow. Patch
4290 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4291 bugfix on 0.2.0.16-alpha.
4292 - Fix a compile warning when using the --enable-openbsd-malloc
4293 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4294 - During configure, detect when we're building with clang version
4295 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4296 CFLAGS. clang doesn't support them yet.
4297 - When sending an HTTP/1.1 proxy request, include a Host header.
4298 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4299 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
4300 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
4301 - If we hit the error case where routerlist_insert() replaces an
4302 existing (old) server descriptor, make sure to remove that
4303 server descriptor from the old_routers list. Fix related to bug
4304 1776. Bugfix on 0.2.2.18-alpha.
4306 o Minor bugfixes (documentation and log messages):
4307 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4308 Fixes bug 4856; bugfix on Tor 0.0.6.
4309 - Update "ClientOnly" man page entry to explain that there isn't
4310 really any point to messing with it. Resolves ticket 5005.
4311 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4312 directory authority option (introduced in Tor 0.2.2.34).
4313 - Downgrade the "We're missing a certificate" message from notice
4314 to info: people kept mistaking it for a real problem, whereas it
4315 is seldom the problem even when we are failing to bootstrap. Fixes
4316 bug 5067; bugfix on 0.2.0.10-alpha.
4317 - Correctly spell "connect" in a log message on failure to create a
4318 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
4319 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4320 circuits. Fixes issue 5259.
4323 - Directory authorities now reject versions of Tor older than
4324 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4325 inclusive. These versions accounted for only a small fraction of
4326 the Tor network, and have numerous known security issues. Resolves
4328 - Update to the May 1 2012 Maxmind GeoLite Country database.
4331 - When sending or relaying a RELAY_EARLY cell, we used to convert
4332 it to a RELAY cell if the connection was using the v1 link
4333 protocol. This was a workaround for older versions of Tor, which
4334 didn't handle RELAY_EARLY cells properly. Now that all supported
4335 versions can handle RELAY_EARLY cells, and now that we're enforcing
4336 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4337 remove this workaround. Addresses bug 4786.
4340 Changes in version 0.2.3.15-alpha - 2012-04-30
4341 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
4342 the development branch build on Windows again.
4344 o Minor bugfixes (on 0.2.2.x and earlier):
4345 - Make sure that there are no unhandled pending TLS errors before
4346 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
4347 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
4348 Bugfix on 0.1.0.5-rc; fixes bug 4528.
4349 - Fix an assert that directory authorities could trigger on sighup
4350 during some configuration state transitions. We now don't treat
4351 it as a fatal error when the new descriptor we just generated in
4352 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
4353 - After we pick a directory mirror, we would refuse to use it if
4354 it's in our ExcludeExitNodes list, resulting in mysterious failures
4355 to bootstrap for people who just wanted to avoid exiting from
4356 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
4357 - When building with --enable-static-tor on OpenBSD, do not
4358 erroneously attempt to link -lrt. Fixes bug 5103.
4360 o Minor bugfixes (on 0.2.3.x):
4361 - When Tor is built with kernel headers from a recent (last few
4362 years) Linux kernel, do not fail to run on older (pre-2.6.28
4363 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
4364 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
4366 - Fix compilation with miniupnpc version 1.6; patch from
4367 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
4368 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
4369 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
4370 - Fix compilation on platforms without unistd.h, or where environ
4371 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
4374 - Directory authorities are now a little more lenient at accepting
4375 older router descriptors, or newer router descriptors that don't
4376 make big changes. This should help ameliorate past and future
4377 issues where routers think they have uploaded valid descriptors,
4378 but the authorities don't think so. Fix for ticket 2479.
4379 - Make the code that clients use to detect an address change be
4380 IPv6-aware, so that it won't fill clients' logs with error
4381 messages when trying to get the IPv4 address of an IPv6
4382 connection. Implements ticket 5537.
4385 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
4386 authorities needed to use it for a while to keep the network working
4387 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
4388 that was six months ago. As of now, it should no longer be needed
4392 Changes in version 0.2.3.14-alpha - 2012-04-23
4393 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
4394 candidate. It also dramatically speeds up AES: fast relays should
4395 consider switching to the newer OpenSSL library.
4397 o Directory authority changes:
4398 - Change IP address for ides (v3 directory authority), and rename
4402 - Avoid logging uninitialized data when unable to decode a hidden
4403 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4404 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4405 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4407 - If authorities are unable to get a v2 consensus document from other
4408 directory authorities, they no longer fall back to fetching
4409 them from regular directory caches. Fixes bug 5635; bugfix on
4410 0.2.2.26-beta, where routers stopped downloading v2 consensus
4412 - When we start a Tor client with a normal consensus already cached,
4413 be willing to download a microdescriptor consensus. Fixes bug 4011;
4414 fix on 0.2.3.1-alpha.
4416 o Major features (performance):
4417 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
4418 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
4419 vectorized AES implementations as appropriate. These can be much,
4420 much faster than other AES implementations.
4422 o Minor bugfixes (0.2.2.x and earlier):
4423 - Don't launch more than 10 service-side introduction-point circuits
4424 for a hidden service in five minutes. Previously, we would consider
4425 launching more introduction-point circuits if at least one second
4426 had passed without any introduction-point circuits failing. Fixes
4427 bug 4607; bugfix on 0.0.7pre1.
4428 - Change the BridgePassword feature (part of the "bridge community"
4429 design, which is not yet implemented) to use a time-independent
4430 comparison. The old behavior might have allowed an adversary
4431 to use timing to guess the BridgePassword value. Fixes bug 5543;
4432 bugfix on 0.2.0.14-alpha.
4433 - Enforce correct return behavior of tor_vsscanf() when the '%%'
4434 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
4435 - When sending an HTTP/1.1 proxy request, include a Host header.
4436 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4437 - Don't log that we have "decided to publish new relay descriptor"
4438 unless we are actually publishing a descriptor. Fixes bug 3942;
4439 bugfix on 0.2.2.28-beta.
4441 o Minor bugfixes (0.2.3.x):
4442 - Fix a bug where a bridge authority crashes (on a failed assert)
4443 if it has seen no directory requests when it's time to write
4444 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
4445 - Fix bug stomping on ORPort option NoListen and ignoring option
4446 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
4447 - In the testsuite, provide a large enough buffer in the tor_sscanf
4448 unit test. Otherwise we'd overrun that buffer and crash during
4449 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
4451 - Make sure we create the keys directory if it doesn't exist and we're
4452 about to store the dynamic Diffie-Hellman parameters. Fixes bug
4453 5572; bugfix on 0.2.3.13-alpha.
4454 - Fix a small memory leak when trying to decode incorrect base16
4455 authenticator during SAFECOOKIE authentication. Found by
4456 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
4459 - Add more information to a log statement that might help track down
4460 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
4461 non-IP address" messages (or any Bug messages, for that matter!),
4462 please let us know about it.
4463 - Relays now understand an IPv6 address when they get one from a
4464 directory server. Resolves ticket 4875.
4465 - Resolve IPv6 addresses in bridge and entry statistics to country
4466 code "??" which means we at least count them. Resolves ticket 5053;
4467 improves on 0.2.3.9-alpha.
4468 - Update to the April 3 2012 Maxmind GeoLite Country database.
4469 - Begin a doc/state-contents.txt file to explain the contents of
4470 the Tor state file. Fixes bug 2987.
4472 o Default torrc changes:
4473 - Stop listing "socksport 9050" in torrc.sample. We open a socks
4474 port on 9050 by default anyway, so this should not change anything
4476 - Stop mentioning the deprecated *ListenAddress options in
4477 torrc.sample. Fixes bug 5438.
4478 - Document unit of bandwidth related options in sample torrc.
4482 - The "torify" script no longer supports the "tsocks" socksifier
4483 tool, since tsocks doesn't support DNS and UDP right for Tor.
4484 Everyone should be using torsocks instead. Fixes bugs 3530 and
4485 5180. Based on a patch by "ugh".
4488 - Change the symmetric cipher interface so that creating and
4489 initializing a stream cipher are no longer separate functions.
4490 - Remove all internal support for unpadded RSA. We never used it, and
4491 it would be a bad idea to start.
4494 Changes in version 0.2.3.13-alpha - 2012-03-26
4495 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
4496 in managed pluggable transports, as well as providing other cleanups
4497 that get us closer to a release candidate.
4499 o Directory authority changes:
4500 - Change IP address for maatuska (v3 directory authority).
4503 - Provide controllers with a safer way to implement the cookie
4504 authentication mechanism. With the old method, if another locally
4505 running program could convince a controller that it was the Tor
4506 process, then that program could trick the controller into telling
4507 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4508 authentication method uses a challenge-response approach to prevent
4509 this attack. Fixes bug 5185, implements proposal 193.
4510 - Never use a bridge or a controller-supplied node as an exit, even
4511 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4512 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4513 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4514 - Only build circuits if we have a sufficient threshold of the total
4515 descriptors that are marked in the consensus with the "Exit"
4516 flag. This mitigates an attack proposed by wanoskarnet, in which
4517 all of a client's bridges collude to restrict the exit nodes that
4518 the client knows about. Fixes bug 5343.
4520 o Major bugfixes (on Tor 0.2.3.x):
4521 - Avoid an assert when managed proxies like obfsproxy are configured,
4522 and we receive HUP signals or setconf attempts too rapidly. This
4523 situation happens most commonly when Vidalia tries to attach to
4524 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
4525 bugfix on 0.2.3.6-alpha.
4526 - Fix a relay-side pluggable transports bug where managed proxies were
4527 unreachable from the Internet, because Tor asked them to bind on
4528 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
4529 - Stop discarding command-line arguments when TestingTorNetwork
4530 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
4531 0.2.3.9-alpha, where task 4552 added support for two layers of
4533 - Resume allowing the unit tests to run in gdb. This was accidentally
4534 made impossible when the DisableDebuggerAttachment option was
4535 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
4536 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
4537 0.2.3.11-alpha. Reported by Anthony G. Basile.
4539 o Minor bugfixes (on 0.2.2.x and earlier):
4540 - Ensure we don't cannibalize circuits that are longer than three hops
4541 already, so we don't end up making circuits with 5 or more
4542 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
4543 0.1.0.1-rc which introduced cannibalization.
4544 - Detect and reject certain misformed escape sequences in
4545 configuration values. Previously, these values would cause us
4546 to crash if received in a torrc file or over an authenticated
4547 control port. Bug found by Esteban Manchado Velázquez, and
4548 independently by Robert Connolly from Matta Consulting who further
4549 noted that it allows a post-authentication heap overflow. Patch
4550 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4551 bugfix on 0.2.0.16-alpha.
4552 - Fix a compile warning when using the --enable-openbsd-malloc
4553 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4554 - Directory caches no longer refuse to clean out descriptors because
4555 of missing v2 networkstatus documents, unless they're configured
4556 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
4557 0.2.2.26-beta. Patch by Daniel Bryg.
4558 - Update to the latest version of the tinytest unit testing framework.
4559 This includes a couple of bugfixes that can be relevant for
4560 running forked unit tests on Windows, and removes all reserved
4563 o Minor bugfixes (on 0.2.3.x):
4564 - On a failed pipe() call, don't leak file descriptors. Fixes bug
4565 4296; bugfix on 0.2.3.1-alpha.
4566 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
4567 until after we have received a CERTS cell. Fixes bug 4361; bugfix
4568 on 0.2.3.6-alpha. Patch by "frosty".
4569 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
4570 option, so that the IP stack doesn't decide to use it for IPv4
4571 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
4572 - Ensure that variables set in Tor's environment cannot override
4573 environment variables that Tor passes to a managed
4574 pluggable-transport proxy. Previously, Tor would pass every
4575 variable in its environment to managed proxies along with the new
4576 ones, in such a way that on many operating systems, the inherited
4577 environment variables would override those which Tor tried to
4578 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
4579 bugfix on 0.2.3.9-alpha for Windows.
4582 - A wide variety of new unit tests by Esteban Manchado Velázquez.
4583 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
4584 - Update to the March 6 2012 Maxmind GeoLite Country database.
4587 Changes in version 0.2.3.12-alpha - 2012-02-13
4588 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
4589 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
4590 when Tor is configured to use a pluggable transport like obfsproxy.
4593 - Fix builds when the path to sed, openssl, or sha1sum contains
4594 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4596 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
4597 connections. This change should allow busy exit relays to stop
4598 running out of available sockets as quickly. Fixes bug 4950;
4599 bugfix on 0.2.2.26-beta.
4600 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
4601 would ask the bridge for microdescriptors, which are only supported
4602 in 0.2.3.x, and then fail to bootstrap when it didn't get the
4603 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
4604 - Properly set up obfsproxy's environment when in managed mode. The
4605 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
4606 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
4607 5076 and 5082; bugfix on 0.2.3.6-alpha.
4610 - Use the dead_strip option when building Tor on OS X. This reduces
4611 binary size by almost 19% when linking openssl and libevent
4612 statically, which we do for Tor Browser Bundle.
4613 - Fix broken URLs in the sample torrc file, and tell readers about
4614 the OutboundBindAddress, ExitPolicyRejectPrivate, and
4615 PublishServerDescriptor options. Addresses bug 4652.
4616 - Update to the February 7 2012 Maxmind GeoLite Country database.
4619 - Downgrade the "We're missing a certificate" message from notice
4620 to info: people kept mistaking it for a real problem, whereas it
4621 is seldom the problem even when we are failing to bootstrap. Fixes
4622 bug 5067; bugfix on 0.2.0.10-alpha.
4623 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
4624 managed pluggable transport server proxy's environment.
4625 Previously, we would put it there, even though Tor doesn't
4626 implement an 'extended server port' yet, and even though Tor
4627 almost certainly isn't listening at that address. For now, we set
4628 it to an empty string to avoid crashing older obfsproxies. Bugfix
4630 - Log the heartbeat message every HeartbeatPeriod seconds, not every
4631 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
4632 0.2.3.1-alpha. Bug reported by Scott Bennett.
4633 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
4634 bugfix on 0.2.3.11-alpha.
4635 - Update "ClientOnly" man page entry to explain that there isn't
4636 really any point to messing with it. Resolves ticket 5005.
4637 - Use the correct CVE number for CVE-2011-4576 in our comments and
4638 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
4641 o Code simplifications and refactoring:
4642 - Use the _WIN32 macro throughout our code to detect Windows.
4643 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
4647 Changes in version 0.2.3.11-alpha - 2012-01-22
4648 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
4649 the last step of the plan to limit maximum circuit length, includes
4650 a wide variety of hidden service performance and correctness fixes,
4651 works around an OpenSSL security flaw if your distro is too stubborn
4652 to upgrade, and fixes a bunch of smaller issues.
4655 - Now that Tor 0.2.0.x is completely deprecated, enable the final
4656 part of "Proposal 110: Avoiding infinite length circuits" by
4657 refusing all circuit-extend requests that do not use a relay_early
4658 cell. This change helps Tor resist a class of denial-of-service
4659 attacks by limiting the maximum circuit length.
4660 - Adjust the number of introduction points that a hidden service
4661 will try to maintain based on how long its introduction points
4662 remain in use and how many introductions they handle. Fixes
4664 - Try to use system facilities for enumerating local interface
4665 addresses, before falling back to our old approach (which was
4666 binding a UDP socket, and calling getsockname() on it). That
4667 approach was scaring OS X users whose draconian firewall
4668 software warned about binding to UDP sockets, regardless of
4669 whether packets were sent. Now we try to use getifaddrs(),
4670 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
4671 system supports. Resolves ticket 1827.
4673 o Major security workaround:
4674 - When building or running with any version of OpenSSL earlier
4675 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4676 versions have a bug (CVE-2011-4576) in which their block cipher
4677 padding includes uninitialized data, potentially leaking sensitive
4678 information to any peer with whom they make a SSLv3 connection. Tor
4679 does not use SSL v3 by default, but a hostile client or server
4680 could force an SSLv3 connection in order to gain information that
4681 they shouldn't have been able to get. The best solution here is to
4682 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4683 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4684 to make sure that the bug can't happen.
4687 - Fix the SOCKET_OK test that we use to tell when socket
4688 creation fails so that it works on Win64. Fixes part of bug 4533;
4689 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4690 - Correct our replacements for the timeradd() and timersub() functions
4691 on platforms that lack them (for example, Windows). The timersub()
4692 function is used when expiring circuits, while timeradd() is
4693 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4694 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
4695 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
4696 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
4697 bug at runtime, not compile time, because some distributions hack
4698 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
4699 on 0.2.3.9-alpha. Found by Pascal.
4701 o Minor features (controller):
4702 - Use absolute path names when reporting the torrc filename in the
4703 control protocol, so a controller can more easily find the torrc
4704 file. Resolves bug 1101.
4705 - Extend the control protocol to report flags that control a circuit's
4706 path selection in CIRC events and in replies to 'GETINFO
4707 circuit-status'. Implements part of ticket 2411.
4708 - Extend the control protocol to report the hidden service address
4709 and current state of a hidden-service-related circuit in CIRC
4710 events and in replies to 'GETINFO circuit-status'. Implements part
4712 - When reporting the path to the cookie file to the controller,
4713 give an absolute path. Resolves ticket 4881.
4714 - Allow controllers to request an event notification whenever a
4715 circuit is cannibalized or its purpose is changed. Implements
4716 part of ticket 3457.
4717 - Include the creation time of a circuit in CIRC and CIRC2
4718 control-port events and the list produced by the 'GETINFO
4719 circuit-status' control-port command.
4721 o Minor features (directory authorities):
4722 - Directory authorities now reject versions of Tor older than
4723 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4724 inclusive. These versions accounted for only a small fraction of
4725 the Tor network, and have numerous known security issues. Resolves
4727 - Authority operators can now vote for all relays in a given
4728 set of countries to be BadDir/BadExit/Invalid/Rejected.
4729 - Provide two consensus parameters (FastFlagMinThreshold and
4730 FastFlagMaxThreshold) to control the range of allowable bandwidths
4731 for the Fast directory flag. These allow authorities to run
4732 experiments on appropriate requirements for being a "Fast" node.
4733 The AuthDirFastGuarantee config value still applies. Implements
4735 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4736 directory authority option (introduced in Tor 0.2.2.34).
4738 o Minor features (other):
4739 - Don't disable the DirPort when we cannot exceed our AccountingMax
4740 limit during this interval because the effective bandwidthrate is
4741 low enough. This is useful in a situation where AccountMax is only
4742 used as an additional safeguard or to provide statistics.
4743 - Prepend an informative header to generated dynamic_dh_params files.
4744 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
4745 EntryNodes will have no effect. Resolves issue 2571.
4746 - Log more useful messages when we fail to disable debugger
4748 - Log which authority we're missing votes from when we go to fetch
4749 them from the other auths.
4750 - Log (at debug level) whenever a circuit's purpose is changed.
4751 - Add missing documentation for the MaxClientCircuitsPending,
4752 UseMicrodescriptors, UserspaceIOCPBuffers, and
4753 _UseFilteringSSLBufferevents options, all introduced during
4755 - Update to the January 3 2012 Maxmind GeoLite Country database.
4757 o Minor bugfixes (hidden services):
4758 - Don't close hidden service client circuits which have almost
4759 finished connecting to their destination when they reach
4760 the normal circuit-build timeout. Previously, we would close
4761 introduction circuits which are waiting for an acknowledgement
4762 from the introduction point, and rendezvous circuits which have
4763 been specified in an INTRODUCE1 cell sent to a hidden service,
4764 after the normal CBT. Now, we mark them as 'timed out', and launch
4765 another rendezvous attempt in parallel. This behavior change can
4766 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
4767 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
4768 - Don't close hidden-service-side rendezvous circuits when they
4769 reach the normal circuit-build timeout. This behaviour change can
4770 be disabled using the new
4771 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
4772 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
4773 - Make sure we never mark the wrong rendezvous circuit as having
4774 had its introduction cell acknowleged by the introduction-point
4775 relay. Previously, when we received an INTRODUCE_ACK cell on a
4776 client-side hidden-service introduction circuit, we might have
4777 marked a rendezvous circuit other than the one we specified in
4778 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
4779 a warning message and interfered with the hidden service
4780 connection-establishment process. Fixes bug 4759; bugfix on
4781 0.2.3.3-alpha, when we added the stream-isolation feature which
4782 might cause Tor to open multiple rendezvous circuits for the same
4784 - Don't trigger an assertion failure when we mark a new client-side
4785 hidden-service introduction circuit for close during the process
4786 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
4789 o Minor bugfixes (log messages):
4790 - Correctly spell "connect" in a log message on failure to create a
4791 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
4793 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4794 Fixes bug 4856; bugfix on Tor 0.0.6.
4795 - Fix the log message describing how we work around discovering
4796 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
4797 4837; bugfix on 0.2.2.9-alpha.
4798 - When logging about a disallowed .exit name, do not also call it
4799 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
4801 o Minor bugfixes (build fixes):
4802 - During configure, detect when we're building with clang version
4803 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4804 CFLAGS. clang doesn't support them yet.
4805 - During configure, search for library containing cos function as
4806 libm lives in libcore on some platforms (BeOS/Haiku). Linking
4807 against libm was hard-coded before. Fixes the first part of bug
4808 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
4810 - Detect attempts to build Tor on (as yet hypothetical) versions
4811 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
4812 fix for bug 4533. Bugfix on 0.2.2.28-beta.
4813 - Preprocessor directives should not be put inside the arguments
4814 of a macro. This would break compilation with GCC releases prior
4815 to version 3.3. We would never recommend such an old GCC version,
4816 but it is apparently required for binary compatibility on some
4817 platforms (namely, certain builds of Haiku). Fixes the other part
4818 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
4821 o Minor bugfixes (other):
4822 - Older Linux kernels erroneously respond to strange nmap behavior
4823 by having accept() return successfully with a zero-length
4824 socket. When this happens, just close the connection. Previously,
4825 we would try harder to learn the remote address: but there was
4826 no such remote address to learn, and our method for trying to
4827 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4828 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4829 - Fix null-pointer access that could occur if TLS allocation failed.
4830 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
4831 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
4832 accidentally been reverted.
4833 - Fix our implementation of crypto_random_hostname() so it can't
4834 overflow on ridiculously large inputs. (No Tor version has ever
4835 provided this kind of bad inputs, but let's be correct in depth.)
4836 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
4837 - Find more places in the code that should have been testing for
4838 invalid sockets using the SOCKET_OK macro. Required for a fix
4839 for bug 4533. Bugfix on 0.2.2.28-beta.
4840 - Fix an assertion failure when, while running with bufferevents, a
4841 connection finishes connecting after it is marked for close, but
4842 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
4843 - test_util_spawn_background_ok() hardcoded the expected value
4844 for ENOENT to 2. This isn't portable as error numbers are
4845 platform specific, and particularly the hurd has ENOENT at
4846 0x40000002. Construct expected string at runtime, using the correct
4847 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
4848 - Reject attempts to disable DisableDebuggerAttachment while Tor is
4849 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
4850 - Use an appropriate-width type for sockets in tor-fw-helper on
4851 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
4854 - When sending or relaying a RELAY_EARLY cell, we used to convert
4855 it to a RELAY cell if the connection was using the v1 link
4856 protocol. This was a workaround for older versions of Tor, which
4857 didn't handle RELAY_EARLY cells properly. Now that all supported
4858 versions can handle RELAY_EARLY cells, and now that we're enforcing
4859 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4860 remove this workaround. Addresses bug 4786.
4862 o Code simplifications and refactoring:
4863 - Use OpenSSL's built-in SSL_state_string_long() instead of our
4864 own homebrewed ssl_state_to_string() replacement. Patch from
4865 Emile Snyder. Fixes bug 4653.
4866 - Use macros to indicate OpenSSL versions, so we don't need to worry
4867 about accidental hexadecimal bit shifts.
4868 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
4870 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
4871 - Use the smartlist_add_asprintf() alias more consistently.
4872 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
4873 invalid value, rather than just -1.
4874 - Rename a handful of old identifiers, mostly related to crypto
4875 structures and crypto functions. By convention, our "create an
4876 object" functions are called "type_new()", our "free an object"
4877 functions are called "type_free()", and our types indicate that
4878 they are types only with a final "_t". But a handful of older
4879 types and functions broke these rules, with function names like
4880 "type_create" or "subsystem_op_type", or with type names like
4884 Changes in version 0.2.3.10-alpha - 2011-12-16
4885 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
4886 Tor's buffers code. Absolutely everybody should upgrade.
4888 The bug relied on an incorrect calculation when making data continuous
4889 in one of our IO buffers, if the first chunk of the buffer was
4890 misaligned by just the wrong amount. The miscalculation would allow an
4891 attacker to overflow a piece of heap-allocated memory. To mount this
4892 attack, the attacker would need to either open a SOCKS connection to
4893 Tor's SocksPort (usually restricted to localhost), or target a Tor
4894 instance configured to make its connections through a SOCKS proxy
4895 (which Tor does not do by default).
4897 Good security practice requires that all heap-overflow bugs should be
4898 presumed to be exploitable until proven otherwise, so we are treating
4899 this as a potential code execution attack. Please upgrade immediately!
4900 This bug does not affect bufferevents-based builds of Tor. Special
4901 thanks to "Vektor" for reporting this issue to us!
4903 This release also contains a few minor bugfixes for issues discovered
4907 - Fix a heap overflow bug that could occur when trying to pull
4908 data into the first chunk of a buffer, when that chunk had
4909 already had some data drained from it. Fixes CVE-2011-2778;
4910 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4913 - If we can't attach streams to a rendezvous circuit when we
4914 finish connecting to a hidden service, clear the rendezvous
4915 circuit's stream-isolation state and try to attach streams
4916 again. Previously, we cleared rendezvous circuits' isolation
4917 state either too early (if they were freshly built) or not at all
4918 (if they had been built earlier and were cannibalized). Bugfix on
4919 0.2.3.3-alpha; fixes bug 4655.
4920 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
4921 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
4922 - Fix an assertion failure when a relay with accounting enabled
4923 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
4926 - Update to the December 6 2011 Maxmind GeoLite Country database.
4929 Changes in version 0.2.2.35 - 2011-12-16
4930 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
4931 buffers code. Absolutely everybody should upgrade.
4933 The bug relied on an incorrect calculation when making data continuous
4934 in one of our IO buffers, if the first chunk of the buffer was
4935 misaligned by just the wrong amount. The miscalculation would allow an
4936 attacker to overflow a piece of heap-allocated memory. To mount this
4937 attack, the attacker would need to either open a SOCKS connection to
4938 Tor's SocksPort (usually restricted to localhost), or target a Tor
4939 instance configured to make its connections through a SOCKS proxy
4940 (which Tor does not do by default).
4942 Good security practice requires that all heap-overflow bugs should be
4943 presumed to be exploitable until proven otherwise, so we are treating
4944 this as a potential code execution attack. Please upgrade immediately!
4945 This bug does not affect bufferevents-based builds of Tor. Special
4946 thanks to "Vektor" for reporting this issue to us!
4948 Tor 0.2.2.35 also fixes several bugs in previous versions, including
4949 crash bugs for unusual configurations, and a long-term bug that
4950 would prevent Tor from starting on Windows machines with draconian
4953 With this release, we remind everyone that 0.2.0.x has reached its
4954 formal end-of-life. Those Tor versions have many known flaws, and
4955 nobody should be using them. You should upgrade -- ideally to the
4956 0.2.2.x series. If you're using a Linux or BSD and its packages are
4957 obsolete, stop using those packages and upgrade anyway.
4959 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
4960 longer receive support after some time in early 2012.
4963 - Fix a heap overflow bug that could occur when trying to pull
4964 data into the first chunk of a buffer, when that chunk had
4965 already had some data drained from it. Fixes CVE-2011-2778;
4966 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4967 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4968 that it doesn't attempt to allocate a socketpair. This could cause
4969 some problems on Windows systems with overzealous firewalls. Fix for
4970 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4972 - If we mark an OR connection for close based on a cell we process,
4973 don't process any further cells on it. We already avoid further
4974 reads on marked-for-close connections, but now we also discard the
4975 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4976 which was the first version where we might mark a connection for
4977 close based on processing a cell on it.
4978 - Correctly sanity-check that we don't underflow on a memory
4979 allocation (and then assert) for hidden service introduction
4980 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4981 bugfix on 0.2.1.5-alpha.
4982 - Fix a memory leak when we check whether a hidden service
4983 descriptor has any usable introduction points left. Fixes bug
4984 4424. Bugfix on 0.2.2.25-alpha.
4985 - Don't crash when we're running as a relay and don't have a GeoIP
4986 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
4987 we've had in the 0.2.3.x branch already.
4988 - When running as a client, do not print a misleading (and plain
4989 wrong) log message that we're collecting "directory request"
4990 statistics: clients don't collect statistics. Also don't create a
4991 useless (because empty) stats file in the stats/ directory. Fixes
4992 bug 4353; bugfix on 0.2.2.34.
4995 - Detect failure to initialize Libevent. This fix provides better
4996 detection for future instances of bug 4457.
4997 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4998 function. This was eating up hideously large amounts of time on some
4999 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5000 - Resolve an integer overflow bug in smartlist_ensure_capacity().
5001 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
5003 - Don't warn about unused log_mutex in log.c when building with
5004 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5005 0.1.0.6-rc which introduced --disable-threads.
5006 - When configuring, starting, or stopping an NT service, stop
5007 immediately after the service configuration attempt has succeeded
5008 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5009 - When sending a NETINFO cell, include the original address
5010 received for the other side, not its canonical address. Found
5011 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5012 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
5013 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
5014 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5015 occurred when a client tried to fetch a descriptor for a bridge
5016 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5017 - Backport fixes for a pair of compilation warnings on Windows.
5018 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
5019 - If we had ever tried to call tor_addr_to_str on an address of
5020 unknown type, we would have done a strdup on an uninitialized
5021 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5022 Reported by "troll_un".
5023 - Correctly detect and handle transient lookup failures from
5024 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5025 Reported by "troll_un".
5026 - Fix null-pointer access that could occur if TLS allocation failed.
5027 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5028 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5029 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5032 - Add two new config options for directory authorities:
5033 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5034 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5035 that is always sufficient to satisfy the bandwidth requirement for
5036 the Guard flag. Now it will be easier for researchers to simulate
5037 Tor networks with different values. Resolves ticket 4484.
5038 - When Tor ignores a hidden service specified in its configuration,
5039 include the hidden service's directory in the warning message.
5040 Previously, we would only tell the user that some hidden service
5041 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5042 - Update to the December 6 2011 Maxmind GeoLite Country database.
5044 o Packaging changes:
5045 - Make it easier to automate expert package builds on Windows,
5046 by removing an absolute path from makensis.exe command.
5049 Changes in version 0.2.1.32 - 2011-12-16
5050 Tor 0.2.1.32 backports important security and privacy fixes for
5051 oldstable. This release is intended only for package maintainers and
5052 others who cannot use the 0.2.2 stable series. All others should be
5053 using Tor 0.2.2.x or newer.
5055 The Tor 0.2.1.x series will reach formal end-of-life some time in
5056 early 2012; we will stop releasing patches for it then.
5058 o Major bugfixes (also included in 0.2.2.x):
5059 - Correctly sanity-check that we don't underflow on a memory
5060 allocation (and then assert) for hidden service introduction
5061 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5062 bugfix on 0.2.1.5-alpha.
5063 - Fix a heap overflow bug that could occur when trying to pull
5064 data into the first chunk of a buffer, when that chunk had
5065 already had some data drained from it. Fixes CVE-2011-2778;
5066 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5069 - Update to the December 6 2011 Maxmind GeoLite Country database.
5072 Changes in version 0.2.3.9-alpha - 2011-12-08
5073 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
5074 a "DisableNetwork" security feature that bundles can use to avoid
5075 touching the network until bridges are configured, moves forward on
5076 the pluggable transport design, fixes a flaw in the hidden service
5077 design that unnecessarily prevented clients with wrong clocks from
5078 reaching hidden services, and fixes a wide variety of other issues.
5081 - Clients can now connect to private bridges over IPv6. Bridges
5082 still need at least one IPv4 address in order to connect to
5083 other relays. Note that we don't yet handle the case where the
5084 user has two bridge lines for the same bridge (one IPv4, one
5085 IPv6). Implements parts of proposal 186.
5086 - New "DisableNetwork" config option to prevent Tor from launching any
5087 connections or accepting any connections except on a control port.
5088 Bundles and controllers can set this option before letting Tor talk
5089 to the rest of the network, for example to prevent any connections
5090 to a non-bridge address. Packages like Orbot can also use this
5091 option to instruct Tor to save power when the network is off.
5092 - Clients and bridges can now be configured to use a separate
5093 "transport" proxy. This approach makes the censorship arms race
5094 easier by allowing bridges to use protocol obfuscation plugins. It
5095 implements the "managed proxy" part of proposal 180 (ticket 3472).
5096 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
5097 implementation. It makes AES_CTR about 7% faster than our old one
5098 (which was about 10% faster than the one OpenSSL used to provide).
5099 Resolves ticket 4526.
5100 - Add a "tor2web mode" for clients that want to connect to hidden
5101 services non-anonymously (and possibly more quickly). As a safety
5102 measure to try to keep users from turning this on without knowing
5103 what they are doing, tor2web mode must be explicitly enabled at
5104 compile time, and a copy of Tor compiled to run in tor2web mode
5105 cannot be used as a normal Tor client. Implements feature 2553.
5106 - Add experimental support for running on Windows with IOCP and no
5107 kernel-space socket buffers. This feature is controlled by a new
5108 "UserspaceIOCPBuffers" config option (off by default), which has
5109 no effect unless Tor has been built with support for bufferevents,
5110 is running on Windows, and has enabled IOCP. This may, in the long
5111 run, help solve or mitigate bug 98.
5112 - Use a more secure consensus parameter voting algorithm. Now at
5113 least three directory authorities or a majority of them must
5114 vote on a given parameter before it will be included in the
5115 consensus. Implements proposal 178.
5118 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
5119 They used to check that the timestamp was within 30 minutes
5120 of their system clock, so they could cap the size of their
5121 replay-detection cache, but that approach unnecessarily refused
5122 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
5123 the v3 intro-point protocol (the first one which sent a timestamp
5124 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
5125 - Only use the EVP interface when AES acceleration is enabled,
5126 to avoid a 5-7% performance regression. Resolves issue 4525;
5127 bugfix on 0.2.3.8-alpha.
5129 o Privacy/anonymity features (bridge detection):
5130 - Make bridge SSL certificates a bit more stealthy by using random
5131 serial numbers, in the same fashion as OpenSSL when generating
5132 self-signed certificates. Implements ticket 4584.
5133 - Introduce a new config option "DynamicDHGroups", enabled by
5134 default, which provides each bridge with a unique prime DH modulus
5135 to be used during SSL handshakes. This option attempts to help
5136 against censors who might use the Apache DH modulus as a static
5137 identifier for bridges. Addresses ticket 4548.
5139 o Minor features (new/different config options):
5140 - New configuration option "DisableDebuggerAttachment" (on by default)
5141 to prevent basic debugging attachment attempts by other processes.
5142 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
5143 - Allow MapAddress directives to specify matches against super-domains,
5144 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
5145 Implements issue 933.
5146 - Slightly change behavior of "list" options (that is, config
5147 options that can appear more than once) when they appear both in
5148 torrc and on the command line. Previously, the command-line options
5149 would be appended to the ones from torrc. Now, the command-line
5150 options override the torrc options entirely. This new behavior
5151 allows the user to override list options (like exit policies and
5152 ports to listen on) from the command line, rather than simply
5153 appending to the list.
5154 - You can get the old (appending) command-line behavior for "list"
5155 options by prefixing the option name with a "+".
5156 - You can remove all the values for a "list" option from the command
5157 line without adding any new ones by prefixing the option name
5159 - Add experimental support for a "defaults" torrc file to be parsed
5160 before the regular torrc. Torrc options override the defaults file's
5161 options in the same way that the command line overrides the torrc.
5162 The SAVECONF controller command saves only those options which
5163 differ between the current configuration and the defaults file. HUP
5164 reloads both files. (Note: This is an experimental feature; its
5165 behavior will probably be refined in future 0.2.3.x-alpha versions
5166 to better meet packagers' needs.) Implements task 4552.
5169 - Try to make the introductory warning message that Tor prints on
5170 startup more useful for actually finding help and information.
5171 Resolves ticket 2474.
5172 - Running "make version" now displays the version of Tor that
5173 we're about to build. Idea from katmagic; resolves issue 4400.
5174 - Expire old or over-used hidden service introduction points.
5175 Required by fix for bug 3460.
5176 - Move the replay-detection cache for the RSA-encrypted parts of
5177 INTRODUCE2 cells to the introduction point data structures.
5178 Previously, we would use one replay-detection cache per hidden
5179 service. Required by fix for bug 3460.
5180 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
5181 public key replay-detection cache from 60 minutes to 5 minutes. This
5182 replay-detection cache is now used only to detect multiple
5183 INTRODUCE2 cells specifying the same rendezvous point, so we can
5184 avoid launching multiple simultaneous attempts to connect to it.
5186 o Minor bugfixes (on Tor 0.2.2.x and earlier):
5187 - Resolve an integer overflow bug in smartlist_ensure_capacity().
5188 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
5190 - Fix a minor formatting issue in one of tor-gencert's error messages.
5192 - Prevent a false positive from the check-spaces script, by disabling
5193 the "whitespace between function name and (" check for functions
5195 - Fix a log message suggesting that people contact a non-existent
5196 email address. Fixes bug 3448.
5197 - Fix null-pointer access that could occur if TLS allocation failed.
5198 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5199 - Report a real bootstrap problem to the controller on router
5200 identity mismatch. Previously we just said "foo", which probably
5201 made a lot of sense at the time. Fixes bug 4169; bugfix on
5203 - If we had ever tried to call tor_addr_to_str() on an address of
5204 unknown type, we would have done a strdup() on an uninitialized
5205 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5206 Reported by "troll_un".
5207 - Correctly detect and handle transient lookup failures from
5208 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5209 Reported by "troll_un".
5210 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5211 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5212 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
5213 bug 4532; found by "troll_un".
5215 o Minor bugfixes (on Tor 0.2.3.x):
5216 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
5218 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
5219 circuit for use as a hidden service client's rendezvous point.
5220 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
5221 with help from wanoskarnet.
5222 - Restore behavior of overriding SocksPort, ORPort, and similar
5223 options from the command line. Bugfix on 0.2.3.3-alpha.
5226 - Properly handle the case where the build-tree is not the same
5227 as the source tree when generating src/common/common_sha1.i,
5228 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
5229 bugfix on 0.2.0.1-alpha.
5231 o Code simplifications, cleanups, and refactorings:
5232 - Remove the pure attribute from all functions that used it
5233 previously. In many cases we assigned it incorrectly, because the
5234 functions might assert or call impure functions, and we don't have
5235 evidence that keeping the pure attribute is worthwhile. Implements
5236 changes suggested in ticket 4421.
5237 - Remove some dead code spotted by coverity. Fixes cid 432.
5238 Bugfix on 0.2.3.1-alpha, closes bug 4637.
5241 Changes in version 0.2.3.8-alpha - 2011-11-22
5242 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
5243 socketpair-related bug that has been bothering Windows users. It adds
5244 support to serve microdescriptors to controllers, so Vidalia's network
5245 map can resume listing relays (once Vidalia implements its side),
5246 and adds better support for hardware AES acceleration. Finally, it
5247 starts the process of adjusting the bandwidth cutoff for getting the
5248 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
5249 that tiny relays harm performance more than they help network capacity.
5252 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5253 that it doesn't attempt to allocate a socketpair. This could cause
5254 some problems on Windows systems with overzealous firewalls. Fix for
5255 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5257 - Correctly sanity-check that we don't underflow on a memory
5258 allocation (and then assert) for hidden service introduction
5259 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5260 bugfix on 0.2.1.5-alpha.
5261 - Remove the artificially low cutoff of 20KB to guarantee the Fast
5262 flag. In the past few years the average relay speed has picked
5263 up, and while the "top 7/8 of the network get the Fast flag" and
5264 "all relays with 20KB or more of capacity get the Fast flag" rules
5265 used to have the same result, now the top 7/8 of the network has
5266 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
5267 - Fix a rare assertion failure when checking whether a v0 hidden
5268 service descriptor has any usable introduction points left, and
5269 we don't have enough information to build a circuit to the first
5270 intro point named in the descriptor. The HS client code in
5271 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
5272 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
5273 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
5274 - Make bridge authorities not crash when they are asked for their own
5275 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
5276 - When running as a client, do not print a misleading (and plain
5277 wrong) log message that we're collecting "directory request"
5278 statistics: clients don't collect statistics. Also don't create a
5279 useless (because empty) stats file in the stats/ directory. Fixes
5280 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
5283 - Allow Tor controllers like Vidalia to obtain the microdescriptor
5284 for a relay by identity digest or nickname. Previously,
5285 microdescriptors were only available by their own digests, so a
5286 controller would have to ask for and parse the whole microdescriptor
5287 consensus in order to look up a single relay's microdesc. Fixes
5288 bug 3832; bugfix on 0.2.3.1-alpha.
5289 - Use OpenSSL's EVP interface for AES encryption, so that all AES
5290 operations can use hardware acceleration (if present). Resolves
5293 o Minor bugfixes (on 0.2.2.x and earlier):
5294 - Detect failure to initialize Libevent. This fix provides better
5295 detection for future instances of bug 4457.
5296 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
5297 function. This was eating up hideously large amounts of time on some
5298 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5299 - Don't warn about unused log_mutex in log.c when building with
5300 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5301 0.1.0.6-rc which introduced --disable-threads.
5302 - Allow manual 'authenticate' commands to the controller interface
5303 from netcat (nc) as well as telnet. We were rejecting them because
5304 they didn't come with the expected whitespace at the end of the
5305 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
5306 - Fix some (not actually triggerable) buffer size checks in usage of
5307 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
5309 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
5310 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
5311 - When configuring, starting, or stopping an NT service, stop
5312 immediately after the service configuration attempt has succeeded
5313 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5314 - When sending a NETINFO cell, include the original address
5315 received for the other side, not its canonical address. Found
5316 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5317 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
5318 can pick them up when the tests aren't disabled. Bugfix on
5319 0.2.2.4-alpha which introduced tinytest.
5320 - Fix a memory leak when we check whether a hidden service
5321 descriptor has any usable introduction points left. Fixes bug
5322 4424. Bugfix on 0.2.2.25-alpha.
5323 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5324 occurred when a client tried to fetch a descriptor for a bridge
5325 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5327 o Minor bugfixes (on 0.2.3.x):
5328 - Make util unit tests build correctly with MSVC. Bugfix on
5329 0.2.3.3-alpha. Patch by Gisle Vanem.
5330 - Successfully detect AUTH_CHALLENGE cells with no recognized
5331 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
5333 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
5334 it should still send a NETINFO cell to allow the connection to
5335 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
5337 - Log less loudly when we get an invalid authentication certificate
5338 from a source other than a directory authority: it's not unusual
5339 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
5341 - Tolerate servers with more clock skew in their authentication
5342 certificates than previously. Fixes bug 4371; bugfix on
5344 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
5345 on 0.2.3.4-alpha and 0.2.3.6-alpha.
5348 - Add two new config options for directory authorities:
5349 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5350 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5351 that is always sufficient to satisfy the bandwidth requirement for
5352 the Guard flag. Now it will be easier for researchers to simulate
5353 Tor networks with different values. Resolves ticket 4484.
5354 - When Tor ignores a hidden service specified in its configuration,
5355 include the hidden service's directory in the warning message.
5356 Previously, we would only tell the user that some hidden service
5357 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5358 - When we fail to initialize Libevent, retry with IOCP disabled so we
5359 don't need to turn on multi-threading support in Libevent, which in
5360 turn requires a working socketpair(). This is a workaround for bug
5361 4457, which affects Libevent versions from 2.0.1-alpha through
5363 - Detect when we try to build on a platform that doesn't define
5364 AF_UNSPEC to 0. We don't work there, so refuse to compile.
5365 - Update to the November 1 2011 Maxmind GeoLite Country database.
5367 o Packaging changes:
5368 - Make it easier to automate expert package builds on Windows,
5369 by removing an absolute path from makensis.exe command.
5371 o Code simplifications and refactoring:
5372 - Remove some redundant #include directives throughout the code.
5373 Patch from Andrea Gelmini.
5374 - Unconditionally use OpenSSL's AES implementation instead of our
5375 old built-in one. OpenSSL's AES has been better for a while, and
5376 relatively few servers should still be on any version of OpenSSL
5377 that doesn't have good optimized assembly AES.
5378 - Use the name "CERTS" consistently to refer to the new cell type;
5379 we were calling it CERT in some places and CERTS in others.
5382 - Numerous new unit tests for functions in util.c and address.c by
5384 - The long-disabled benchmark tests are now split into their own
5385 ./src/test/bench binary.
5386 - The benchmark tests can now use more accurate timers than
5387 gettimeofday() when such timers are available.
5390 Changes in version 0.2.3.7-alpha - 2011-10-30
5391 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
5392 the new v3 handshake. It also resolves yet another bridge address
5396 - If we mark an OR connection for close based on a cell we process,
5397 don't process any further cells on it. We already avoid further
5398 reads on marked-for-close connections, but now we also discard the
5399 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
5400 which was the first version where we might mark a connection for
5401 close based on processing a cell on it.
5402 - Fix a double-free bug that would occur when we received an invalid
5403 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
5404 bugfix on 0.2.3.6-alpha.
5405 - Bridges no longer include their address in NETINFO cells on outgoing
5406 OR connections, to allow them to blend in better with clients.
5407 Removes another avenue for enumerating bridges. Reported by
5408 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
5409 cells were introduced.
5412 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
5413 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
5416 Changes in version 0.2.3.6-alpha - 2011-10-26
5417 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
5418 anonymity vulnerability where an attacker can deanonymize Tor
5419 users. Everybody should upgrade.
5421 This release also features support for a new v3 connection handshake
5422 protocol, and fixes to make hidden service connections more robust.
5425 - Implement a new handshake protocol (v3) for authenticating Tors to
5426 each other over TLS. It should be more resistant to fingerprinting
5427 than previous protocols, and should require less TLS hacking for
5428 future Tor implementations. Implements proposal 176.
5429 - Allow variable-length padding cells to disguise the length of
5430 Tor's TLS records. Implements part of proposal 184.
5432 o Privacy/anonymity fixes (clients):
5433 - Clients and bridges no longer send TLS certificate chains on
5434 outgoing OR connections. Previously, each client or bridge would
5435 use the same cert chain for all outgoing OR connections until
5436 its IP address changes, which allowed any relay that the client
5437 or bridge contacted to determine which entry guards it is using.
5438 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5439 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5440 no longer considers that connection as suitable for satisfying a
5441 circuit EXTEND request. Now relays can protect clients from the
5442 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5443 - Directory authorities no longer assign the Guard flag to relays
5444 that haven't upgraded to the above "refuse EXTEND requests
5445 to client connections" fix. Now directory authorities can
5446 protect clients from the CVE-2011-2768 issue even if neither
5447 the clients nor the relays have upgraded yet. There's a new
5448 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5449 to let us transition smoothly, else tomorrow there would be no
5452 o Major bugfixes (hidden services):
5453 - Improve hidden service robustness: when an attempt to connect to
5454 a hidden service ends, be willing to refetch its hidden service
5455 descriptors from each of the HSDir relays responsible for them
5456 immediately. Previously, we would not consider refetching the
5457 service's descriptors from each HSDir for 15 minutes after the last
5458 fetch, which was inconvenient if the hidden service was not running
5459 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
5460 - When one of a hidden service's introduction points appears to be
5461 unreachable, stop trying it. Previously, we would keep trying
5462 to build circuits to the introduction point until we lost the
5463 descriptor, usually because the user gave up and restarted Tor.
5464 Partly fixes bug 3825.
5465 - Don't launch a useless circuit after failing to use one of a
5466 hidden service's introduction points. Previously, we would
5467 launch a new introduction circuit, but not set the hidden service
5468 which that circuit was intended to connect to, so it would never
5469 actually be used. A different piece of code would then create a
5470 new introduction circuit correctly. Bug reported by katmagic and
5471 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5473 o Major bugfixes (other):
5474 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5475 that they initiated. Relays could distinguish incoming bridge
5476 connections from client connections, creating another avenue for
5477 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5478 Found by "frosty_un".
5479 - Don't update the AccountingSoftLimitHitAt state file entry whenever
5480 tor gets started. This prevents a wrong average bandwidth
5481 estimate, which would cause relays to always start a new accounting
5482 interval at the earliest possible moment. Fixes bug 2003; bugfix
5483 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
5484 immensely in tracking this bug down.
5485 - Fix a crash bug when changing node restrictions while a DNS lookup
5486 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5489 o Minor bugfixes (on 0.2.2.x and earlier):
5490 - When a hidden service turns an extra service-side introduction
5491 circuit into a general-purpose circuit, free the rend_data and
5492 intro_key fields first, so we won't leak memory if the circuit
5493 is cannibalized for use as another service-side introduction
5494 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5495 - Rephrase the log message emitted if the TestSocks check is
5496 successful. Patch from Fabian Keil; fixes bug 4094.
5497 - Bridges now skip DNS self-tests, to act a little more stealthily.
5498 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5499 bridges. Patch by "warms0x".
5500 - Remove a confusing dollar sign from the example fingerprint in the
5501 man page, and also make the example fingerprint a valid one. Fixes
5502 bug 4309; bugfix on 0.2.1.3-alpha.
5503 - Fix internal bug-checking logic that was supposed to catch
5504 failures in digest generation so that it will fail more robustly
5505 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5506 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5507 - Report any failure in init_keys() calls launched because our
5508 IP address has changed. Spotted by Coverity Scan. Bugfix on
5509 0.1.1.4-alpha; fixes CID 484.
5511 o Minor bugfixes (on 0.2.3.x):
5512 - Fix a bug in configure.in that kept it from building a configure
5513 script with autoconf versions earlier than 2.61. Fixes bug 2430;
5514 bugfix on 0.2.3.1-alpha.
5515 - Don't warn users that they are exposing a client port to the
5516 Internet if they have specified an RFC1918 address. Previously,
5517 we would warn if the user had specified any non-loopback
5518 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
5519 - Fix memory leaks in the failing cases of the new SocksPort and
5520 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
5521 fixes coverity CIDs 485, 486, and 487.
5524 - When a hidden service's introduction point times out, consider
5525 trying it again during the next attempt to connect to the
5526 HS. Previously, we would not try it again unless a newly fetched
5527 descriptor contained it. Required by fixes for bugs 1297 and 3825.
5528 - The next version of Windows will be called Windows 8, and it has
5529 a major version of 6, minor version of 2. Correctly identify that
5530 version instead of calling it "Very recent version". Resolves
5531 ticket 4153; reported by funkstar.
5532 - The Bridge Authority now writes statistics on how many bridge
5533 descriptors it gave out in total, and how many unique descriptors
5534 it gave out. It also lists how often the most and least commonly
5535 fetched descriptors were given out, as well as the median and
5536 25th/75th percentile. Implements tickets 4200 and 4294.
5537 - Update to the October 4 2011 Maxmind GeoLite Country database.
5539 o Code simplifications and refactoring:
5540 - Remove some old code to remember statistics about which descriptors
5541 we've served as a directory mirror. The feature wasn't used and
5542 is outdated now that microdescriptors are around.
5543 - Rename Tor functions that turn strings into addresses, so that
5544 "parse" indicates that no hostname resolution occurs, and
5545 "lookup" indicates that hostname resolution may occur. This
5546 should help prevent mistakes in the future. Fixes bug 3512.
5549 Changes in version 0.2.2.34 - 2011-10-26
5550 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
5551 can deanonymize Tor users. Everybody should upgrade.
5553 The attack relies on four components: 1) Clients reuse their TLS cert
5554 when talking to different relays, so relays can recognize a user by
5555 the identity key in her cert. 2) An attacker who knows the client's
5556 identity key can probe each guard relay to see if that identity key
5557 is connected to that guard relay right now. 3) A variety of active
5558 attacks in the literature (starting from "Low-Cost Traffic Analysis
5559 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
5560 discover the guard relays that a Tor user visiting the website is using.
5561 4) Clients typically pick three guards at random, so the set of guards
5562 for a given user could well be a unique fingerprint for her. This
5563 release fixes components #1 and #2, which is enough to block the attack;
5564 the other two remain as open research problems. Special thanks to
5565 "frosty_un" for reporting the issue to us!
5567 Clients should upgrade so they are no longer recognizable by the TLS
5568 certs they present. Relays should upgrade so they no longer allow a
5569 remote attacker to probe them to test whether unpatched clients are
5570 currently connected to them.
5572 This release also fixes several vulnerabilities that allow an attacker
5573 to enumerate bridge relays. Some bridge enumeration attacks still
5574 remain; see for example proposal 188.
5576 o Privacy/anonymity fixes (clients):
5577 - Clients and bridges no longer send TLS certificate chains on
5578 outgoing OR connections. Previously, each client or bridge would
5579 use the same cert chain for all outgoing OR connections until
5580 its IP address changes, which allowed any relay that the client
5581 or bridge contacted to determine which entry guards it is using.
5582 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5583 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5584 no longer considers that connection as suitable for satisfying a
5585 circuit EXTEND request. Now relays can protect clients from the
5586 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5587 - Directory authorities no longer assign the Guard flag to relays
5588 that haven't upgraded to the above "refuse EXTEND requests
5589 to client connections" fix. Now directory authorities can
5590 protect clients from the CVE-2011-2768 issue even if neither
5591 the clients nor the relays have upgraded yet. There's a new
5592 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5593 to let us transition smoothly, else tomorrow there would be no
5596 o Privacy/anonymity fixes (bridge enumeration):
5597 - Bridge relays now do their directory fetches inside Tor TLS
5598 connections, like all the other clients do, rather than connecting
5599 directly to the DirPort like public relays do. Removes another
5600 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5601 - Bridges relays now build circuits for themselves in a more similar
5602 way to how clients build them. Removes another avenue for
5603 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5604 when bridges were introduced.
5605 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5606 that they initiated. Relays could distinguish incoming bridge
5607 connections from client connections, creating another avenue for
5608 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5609 Found by "frosty_un".
5612 - Fix a crash bug when changing node restrictions while a DNS lookup
5613 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5615 - Don't launch a useless circuit after failing to use one of a
5616 hidden service's introduction points. Previously, we would
5617 launch a new introduction circuit, but not set the hidden service
5618 which that circuit was intended to connect to, so it would never
5619 actually be used. A different piece of code would then create a
5620 new introduction circuit correctly. Bug reported by katmagic and
5621 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5624 - Change an integer overflow check in the OpenBSD_Malloc code so
5625 that GCC is less likely to eliminate it as impossible. Patch
5626 from Mansour Moufid. Fixes bug 4059.
5627 - When a hidden service turns an extra service-side introduction
5628 circuit into a general-purpose circuit, free the rend_data and
5629 intro_key fields first, so we won't leak memory if the circuit
5630 is cannibalized for use as another service-side introduction
5631 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5632 - Bridges now skip DNS self-tests, to act a little more stealthily.
5633 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5634 bridges. Patch by "warms0x".
5635 - Fix internal bug-checking logic that was supposed to catch
5636 failures in digest generation so that it will fail more robustly
5637 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5638 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5639 - Report any failure in init_keys() calls launched because our
5640 IP address has changed. Spotted by Coverity Scan. Bugfix on
5641 0.1.1.4-alpha; fixes CID 484.
5643 o Minor bugfixes (log messages and documentation):
5644 - Remove a confusing dollar sign from the example fingerprint in the
5645 man page, and also make the example fingerprint a valid one. Fixes
5646 bug 4309; bugfix on 0.2.1.3-alpha.
5647 - The next version of Windows will be called Windows 8, and it has
5648 a major version of 6, minor version of 2. Correctly identify that
5649 version instead of calling it "Very recent version". Resolves
5650 ticket 4153; reported by funkstar.
5651 - Downgrade log messages about circuit timeout calibration from
5652 "notice" to "info": they don't require or suggest any human
5653 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5654 bugfix on 0.2.2.14-alpha.
5657 - Turn on directory request statistics by default and include them in
5658 extra-info descriptors. Don't break if we have no GeoIP database.
5659 Backported from 0.2.3.1-alpha; implements ticket 3951.
5660 - Update to the October 4 2011 Maxmind GeoLite Country database.
5663 Changes in version 0.2.1.31 - 2011-10-26
5664 Tor 0.2.1.31 backports important security and privacy fixes for
5665 oldstable. This release is intended only for package maintainers and
5666 others who cannot use the 0.2.2 stable series. All others should be
5667 using Tor 0.2.2.x or newer.
5669 o Security fixes (also included in 0.2.2.x):
5670 - Replace all potentially sensitive memory comparison operations
5671 with versions whose runtime does not depend on the data being
5672 compared. This will help resist a class of attacks where an
5673 adversary can use variations in timing information to learn
5674 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5675 implementation by Robert Ransom based partially on code by DJB.)
5676 - Fix an assert in parsing router descriptors containing IPv6
5677 addresses. This one took down the directory authorities when
5678 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5680 o Privacy/anonymity fixes (also included in 0.2.2.x):
5681 - Clients and bridges no longer send TLS certificate chains on
5682 outgoing OR connections. Previously, each client or bridge would
5683 use the same cert chain for all outgoing OR connections until
5684 its IP address changes, which allowed any relay that the client
5685 or bridge contacted to determine which entry guards it is using.
5686 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5687 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5688 no longer considers that connection as suitable for satisfying a
5689 circuit EXTEND request. Now relays can protect clients from the
5690 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5691 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5692 that they initiated. Relays could distinguish incoming bridge
5693 connections from client connections, creating another avenue for
5694 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5695 Found by "frosty_un".
5696 - When receiving a hidden service descriptor, check that it is for
5697 the hidden service we wanted. Previously, Tor would store any
5698 hidden service descriptors that a directory gave it, whether it
5699 wanted them or not. This wouldn't have let an attacker impersonate
5700 a hidden service, but it did let directories pre-seed a client
5701 with descriptors that it didn't want. Bugfix on 0.0.6.
5702 - Avoid linkability based on cached hidden service descriptors: forget
5703 all hidden service descriptors cached as a client when processing a
5704 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5705 - Make the bridge directory authority refuse to answer directory
5706 requests for "all" descriptors. It used to include bridge
5707 descriptors in its answer, which was a major information leak.
5708 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5709 - Don't attach new streams to old rendezvous circuits after SIGNAL
5710 NEWNYM. Previously, we would keep using an existing rendezvous
5711 circuit if it remained open (i.e. if it were kept open by a
5712 long-lived stream, or if a new stream were attached to it before
5713 Tor could notice that it was old and no longer in use). Bugfix on
5714 0.1.1.15-rc; fixes bug 3375.
5716 o Minor bugfixes (also included in 0.2.2.x):
5717 - When we restart our relay, we might get a successful connection
5718 from the outside before we've started our reachability tests,
5719 triggering a warning: "ORPort found reachable, but I have no
5720 routerinfo yet. Failing to inform controller of success." This
5721 bug was harmless unless Tor is running under a controller
5722 like Vidalia, in which case the controller would never get a
5723 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5725 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5726 enabled. Fixes bug 1526.
5727 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5728 anything since 0.2.1.16-rc.
5729 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5730 None of the cases where we did this before were wrong, but by making
5731 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5732 - Fix a rare crash bug that could occur when a client was configured
5733 with a large number of bridges. Fixes bug 2629; bugfix on
5734 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5735 - Correct the warning displayed when a rendezvous descriptor exceeds
5736 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5738 - Fix an uncommon assertion failure when running with DNSPort under
5739 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5740 - When warning about missing zlib development packages during compile,
5741 give the correct package names. Bugfix on 0.2.0.1-alpha.
5742 - Require that introduction point keys and onion keys have public
5743 exponent 65537. Bugfix on 0.2.0.10-alpha.
5744 - Do not crash when our configuration file becomes unreadable, for
5745 example due to a permissions change, between when we start up
5746 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5748 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5750 - Always NUL-terminate the sun_path field of a sockaddr_un before
5751 passing it to the kernel. (Not a security issue: kernels are
5752 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5753 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5754 - Don't stack-allocate the list of supplementary GIDs when we're
5755 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5756 could take up to 256K, which is way too much stack. Found by
5757 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5759 o Minor bugfixes (only in 0.2.1.x):
5760 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
5761 rely on them. Bugfix on 0.2.1.30.
5762 - Use git revisions instead of svn revisions when generating our
5763 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5765 o Minor features (also included in 0.2.2.x):
5766 - Adjust the expiration time on our SSL session certificates to
5767 better match SSL certs seen in the wild. Resolves ticket 4014.
5768 - Allow nameservers with IPv6 address. Resolves bug 2574.
5769 - Update to the October 4 2011 Maxmind GeoLite Country database.
5772 Changes in version 0.2.3.5-alpha - 2011-09-28
5773 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
5774 bridge relays; fixes an assertion error that many users started hitting
5775 today; and adds the ability to refill token buckets more often than
5776 once per second, allowing significant performance improvements.
5779 - Bridge relays now do their directory fetches inside Tor TLS
5780 connections, like all the other clients do, rather than connecting
5781 directly to the DirPort like public relays do. Removes another
5782 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5783 - Bridges relays now build circuits for themselves in a more similar
5784 way to how clients build them. Removes another avenue for
5785 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5786 when bridges were introduced.
5789 - Fix an "Assertion md->held_by_node == 1 failed" error that could
5790 occur when the same microdescriptor was referenced by two node_t
5791 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
5793 o Major features (networking):
5794 - Add a new TokenBucketRefillInterval option to refill token buckets
5795 more frequently than once per second. This should improve network
5796 performance, alleviate queueing problems, and make traffic less
5797 bursty. Implements proposal 183; closes ticket 3630. Design by
5798 Florian Tschorsch and Björn Scheuermann; implementation by
5802 - Change an integer overflow check in the OpenBSD_Malloc code so
5803 that GCC is less likely to eliminate it as impossible. Patch
5804 from Mansour Moufid. Fixes bug 4059.
5806 o Minor bugfixes (usability):
5807 - Downgrade log messages about circuit timeout calibration from
5808 "notice" to "info": they don't require or suggest any human
5809 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5810 bugfix on 0.2.2.14-alpha.
5812 o Minor features (diagnostics):
5813 - When the system call to create a listener socket fails, log the
5814 error message explaining why. This may help diagnose bug 4027.
5817 Changes in version 0.2.3.4-alpha - 2011-09-13
5818 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
5819 tweak to Tor's TLS handshake that makes relays and bridges that run
5820 this new version reachable from Iran again. It also fixes a few new
5821 bugs in 0.2.3.x, and teaches relays to recognize when they're not
5822 listed in the network consensus and republish.
5824 o Major bugfixes (also part of 0.2.2.33):
5825 - Avoid an assertion failure when reloading a configuration with
5826 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5827 3923; bugfix on 0.2.2.25-alpha.
5829 o Minor features (security, also part of 0.2.2.33):
5830 - Check for replays of the public-key encrypted portion of an
5831 INTRODUCE1 cell, in addition to the current check for replays of
5832 the g^x value. This prevents a possible class of active attacks
5833 by an attacker who controls both an introduction point and a
5834 rendezvous point, and who uses the malleability of AES-CTR to
5835 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5836 that these attacks are infeasible (requiring the attacker to send
5837 on the order of zettabytes of altered cells in a short interval),
5838 but we'd rather block them off in case there are any classes of
5839 this attack that we missed. Reported by Willem Pinckaers.
5841 o Minor features (also part of 0.2.2.33):
5842 - Adjust the expiration time on our SSL session certificates to
5843 better match SSL certs seen in the wild. Resolves ticket 4014.
5844 - Change the default required uptime for a relay to be accepted as
5845 a HSDir (hidden service directory) from 24 hours to 25 hours.
5846 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5847 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5848 authorities to abstain from voting on assignment of the HSDir
5849 consensus flag. Related to bug 2649.
5850 - Update to the September 6 2011 Maxmind GeoLite Country database.
5852 o Minor bugfixes (also part of 0.2.2.33):
5853 - Demote the 'replay detected' log message emitted when a hidden
5854 service receives the same Diffie-Hellman public key in two different
5855 INTRODUCE2 cells to info level. A normal Tor client can cause that
5856 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5857 fixes part of bug 2442.
5858 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5859 level. There is nothing that a hidden service's operator can do
5860 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5862 - Clarify a log message specifying the characters permitted in
5863 HiddenServiceAuthorizeClient client names. Previously, the log
5864 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5865 given the impression that every ASCII character between "+" and "_"
5866 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5868 o Build fixes (also part of 0.2.2.33):
5869 - Clean up some code issues that prevented Tor from building on older
5870 BSDs. Fixes bug 3894; reported by "grarpamp".
5871 - Search for a platform-specific version of "ar" when cross-compiling.
5872 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5875 - Fix a bug where the SocksPort option (for example) would get
5876 ignored and replaced by the default if a SocksListenAddress
5877 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
5881 - Relays now try regenerating and uploading their descriptor more
5882 frequently if they are not listed in the consensus, or if the
5883 version of their descriptor listed in the consensus is too
5884 old. This fix should prevent situations where a server declines
5885 to re-publish itself because it has done so too recently, even
5886 though the authorities decided not to list its recent-enough
5887 descriptor. Fix for bug 3327.
5890 - Relays now include a reason for regenerating their descriptors
5891 in an HTTP header when uploading to the authorities. This will
5892 make it easier to debug descriptor-upload issues in the future.
5893 - When starting as root and then changing our UID via the User
5894 control option, and we have a ControlSocket configured, make sure
5895 that the ControlSocket is owned by the same account that Tor will
5896 run under. Implements ticket 3421; fix by Jérémy Bobbio.
5899 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
5900 utility function used in the control-port code). This shouldn't
5901 ever happen unless Tor is completely out of memory, but if it did
5902 happen and Tor somehow recovered from it, Tor could have sent a log
5903 message to a control port in the middle of a reply to a controller
5904 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
5905 - Make 'FetchUselessDescriptors' cause all descriptor types and
5906 all consensus types (including microdescriptors) to get fetched.
5907 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
5910 - Make a new "entry connection" struct as an internal subtype of "edge
5911 connection", to simplify the code and make exit connections smaller.
5914 Changes in version 0.2.2.33 - 2011-09-13
5915 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
5916 TLS handshake that makes relays and bridges that run this new version
5917 reachable from Iran again.
5920 - Avoid an assertion failure when reloading a configuration with
5921 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5922 3923; bugfix on 0.2.2.25-alpha.
5924 o Minor features (security):
5925 - Check for replays of the public-key encrypted portion of an
5926 INTRODUCE1 cell, in addition to the current check for replays of
5927 the g^x value. This prevents a possible class of active attacks
5928 by an attacker who controls both an introduction point and a
5929 rendezvous point, and who uses the malleability of AES-CTR to
5930 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5931 that these attacks are infeasible (requiring the attacker to send
5932 on the order of zettabytes of altered cells in a short interval),
5933 but we'd rather block them off in case there are any classes of
5934 this attack that we missed. Reported by Willem Pinckaers.
5937 - Adjust the expiration time on our SSL session certificates to
5938 better match SSL certs seen in the wild. Resolves ticket 4014.
5939 - Change the default required uptime for a relay to be accepted as
5940 a HSDir (hidden service directory) from 24 hours to 25 hours.
5941 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5942 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5943 authorities to abstain from voting on assignment of the HSDir
5944 consensus flag. Related to bug 2649.
5945 - Update to the September 6 2011 Maxmind GeoLite Country database.
5947 o Minor bugfixes (documentation and log messages):
5948 - Correct the man page to explain that HashedControlPassword and
5949 CookieAuthentication can both be set, in which case either method
5950 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5951 when we decided to allow these config options to both be set. Issue
5953 - Demote the 'replay detected' log message emitted when a hidden
5954 service receives the same Diffie-Hellman public key in two different
5955 INTRODUCE2 cells to info level. A normal Tor client can cause that
5956 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5957 fixes part of bug 2442.
5958 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5959 level. There is nothing that a hidden service's operator can do
5960 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5962 - Clarify a log message specifying the characters permitted in
5963 HiddenServiceAuthorizeClient client names. Previously, the log
5964 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5965 given the impression that every ASCII character between "+" and "_"
5966 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5969 - Provide a substitute implementation of lround() for MSVC, which
5970 apparently lacks it. Patch from Gisle Vanem.
5971 - Clean up some code issues that prevented Tor from building on older
5972 BSDs. Fixes bug 3894; reported by "grarpamp".
5973 - Search for a platform-specific version of "ar" when cross-compiling.
5974 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5977 Changes in version 0.2.3.3-alpha - 2011-09-01
5978 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
5979 security, and provides client-side support for the microdescriptor
5980 and optimistic data features introduced earlier in the 0.2.3.x
5981 series. It also includes numerous critical bugfixes in the (optional)
5982 bufferevent-based networking backend.
5984 o Major features (stream isolation):
5985 - You can now configure Tor so that streams from different
5986 applications are isolated on different circuits, to prevent an
5987 attacker who sees your streams as they leave an exit node from
5988 linking your sessions to one another. To do this, choose some way
5989 to distinguish the applications: have them connect to different
5990 SocksPorts, or have one of them use SOCKS4 while the other uses
5991 SOCKS5, or have them pass different authentication strings to the
5992 SOCKS proxy. Then, use the new SocksPort syntax to configure the
5993 degree of isolation you need. This implements Proposal 171.
5994 - There's a new syntax for specifying multiple client ports (such as
5995 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
5996 multiple *Port entries with full addr:port syntax on each.
5997 The old *ListenAddress format is still supported, but you can't
5998 mix it with the new *Port syntax.
6000 o Major features (other):
6001 - Enable microdescriptor fetching by default for clients. This allows
6002 clients to download a much smaller amount of directory information.
6003 To disable it (and go back to the old-style consensus and
6004 descriptors), set "UseMicrodescriptors 0" in your torrc file.
6005 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
6006 "PortForwarding" config option), now supports Windows.
6007 - When using an exit relay running 0.2.3.x, clients can now
6008 "optimistically" send data before the exit relay reports that
6009 the stream has opened. This saves a round trip when starting
6010 connections where the client speaks first (such as web browsing).
6011 This behavior is controlled by a consensus parameter (currently
6012 disabled). To turn it on or off manually, use the "OptimisticData"
6013 torrc option. Implements proposal 181; code by Ian Goldberg.
6015 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
6016 - When using IOCP on Windows, we need to enable Libevent windows
6018 - The IOCP backend now works even when the user has not specified
6019 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
6020 Fixes part of bug 3752.
6021 - Correctly record the bytes we've read and written when using
6022 bufferevents, so that we can include them in our bandwidth history
6023 and advertised bandwidth. Fixes bug 3803.
6024 - Apply rate-limiting only at the bottom of a chain of filtering
6025 bufferevents. This prevents us from filling up internal read
6026 buffers and violating rate-limits when filtering bufferevents
6027 are enabled. Fixes part of bug 3804.
6028 - Add high-watermarks to the output buffers for filtered
6029 bufferevents. This prevents us from filling up internal write
6030 buffers and wasting CPU cycles when filtering bufferevents are
6031 enabled. Fixes part of bug 3804.
6032 - Correctly notice when data has been written from a bufferevent
6033 without flushing it completely. Fixes bug 3805.
6034 - Fix a bug where server-side tunneled bufferevent-based directory
6035 streams would get closed prematurely. Fixes bug 3814.
6036 - Fix a use-after-free error with per-connection rate-limiting
6037 buckets. Fixes bug 3888.
6039 o Major bugfixes (also part of 0.2.2.31-rc):
6040 - If we're configured to write our ControlPorts to disk, only write
6041 them after switching UID and creating the data directory. This way,
6042 we don't fail when starting up with a nonexistent DataDirectory
6043 and a ControlPortWriteToFile setting based on that directory. Fixes
6044 bug 3747; bugfix on Tor 0.2.2.26-beta.
6047 - Added a new CONF_CHANGED event so that controllers can be notified
6048 of any configuration changes made by other controllers, or by the
6049 user. Implements ticket 1692.
6050 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
6051 leak when using bufferevents, and lets Libevent worry about how to
6052 best copy data out of a buffer.
6053 - Replace files in stats/ rather than appending to them. Now that we
6054 include statistics in extra-info descriptors, it makes no sense to
6055 keep old statistics forever. Implements ticket 2930.
6057 o Minor features (build compatibility):
6058 - Limited, experimental support for building with nmake and MSVC.
6059 - Provide a substitute implementation of lround() for MSVC, which
6060 apparently lacks it. Patch from Gisle Vanem.
6062 o Minor features (also part of 0.2.2.31-rc):
6063 - Update to the August 2 2011 Maxmind GeoLite Country database.
6065 o Minor bugfixes (on 0.2.3.x-alpha):
6066 - Fix a spurious warning when parsing SOCKS requests with
6067 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
6068 - Get rid of a harmless warning that could happen on relays running
6069 with bufferevents. The warning was caused by someone doing an http
6070 request to a relay's orport. Also don't warn for a few related
6071 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
6073 o Minor bugfixes (on 2.2.x and earlier):
6074 - Correct the man page to explain that HashedControlPassword and
6075 CookieAuthentication can both be set, in which case either method
6076 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
6077 when we decided to allow these config options to both be set. Issue
6079 - The "--quiet" and "--hush" options now apply not only to Tor's
6080 behavior before logs are configured, but also to Tor's behavior in
6081 the absense of configured logs. Fixes bug 3550; bugfix on
6084 o Minor bugfixes (also part of 0.2.2.31-rc):
6085 - Write several files in text mode, on OSes that distinguish text
6086 mode from binary mode (namely, Windows). These files are:
6087 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6088 that collect those statistics; 'client_keys' and 'hostname' for
6089 hidden services that use authentication; and (in the tor-gencert
6090 utility) newly generated identity and signing keys. Previously,
6091 we wouldn't specify text mode or binary mode, leading to an
6092 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6093 the DirRecordUsageByCountry option which would have triggered
6094 the assertion failure was added), although this assertion failure
6095 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6096 - Selectively disable deprecation warnings on OS X because Lion
6097 started deprecating the shipped copy of openssl. Fixes bug 3643.
6098 - Remove an extra pair of quotation marks around the error
6099 message in control-port STATUS_GENERAL BUG events. Bugfix on
6100 0.1.2.6-alpha; fixes bug 3732.
6101 - When unable to format an address as a string, report its value
6102 as "???" rather than reusing the last formatted address. Bugfix
6105 o Code simplifications and refactoring:
6106 - Rewrite the listener-selection logic so that parsing which ports
6107 we want to listen on is now separate from binding to the ports
6111 - Building Tor with bufferevent support now requires Libevent
6112 2.0.13-stable or later. Previous versions of Libevent had bugs in
6113 SSL-related bufferevents and related issues that would make Tor
6114 work badly with bufferevents. Requiring 2.0.13-stable also allows
6115 Tor with bufferevents to take advantage of Libevent APIs
6116 introduced after 2.0.8-rc.
6119 Changes in version 0.2.2.32 - 2011-08-27
6120 The Tor 0.2.2 release series is dedicated to the memory of Andreas
6121 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
6122 a founder of the PETS community, a leader in our field, a mentor,
6123 and a friend. He left us with these words: "I had the possibility
6124 to contribute to this world that is not as it should be. I hope I
6125 could help in some areas to make the world a better place, and that
6126 I could also encourage other people to be engaged in improving the
6127 world. Please, stay engaged. This world needs you, your love, your
6128 initiative -- now I cannot be part of that anymore."
6130 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
6131 ready. More than two years in the making, this release features improved
6132 client performance and hidden service reliability, better compatibility
6133 for Android, correct behavior for bridges that listen on more than
6134 one address, more extensible and flexible directory object handling,
6135 better reporting of network statistics, improved code security, and
6136 many many other features and bugfixes.
6139 Changes in version 0.2.2.31-rc - 2011-08-17
6140 Tor 0.2.2.31-rc is the second and hopefully final release candidate
6141 for the Tor 0.2.2.x series.
6144 - Remove an extra pair of quotation marks around the error
6145 message in control-port STATUS_GENERAL BUG events. Bugfix on
6146 0.1.2.6-alpha; fixes bug 3732.
6147 - If we're configured to write our ControlPorts to disk, only write
6148 them after switching UID and creating the data directory. This way,
6149 we don't fail when starting up with a nonexistent DataDirectory
6150 and a ControlPortWriteToFile setting based on that directory. Fixes
6151 bug 3747; bugfix on Tor 0.2.2.26-beta.
6154 - Update to the August 2 2011 Maxmind GeoLite Country database.
6157 - Allow GETINFO fingerprint to return a fingerprint even when
6158 we have not yet built a router descriptor. Fixes bug 3577;
6159 bugfix on 0.2.0.1-alpha.
6160 - Write several files in text mode, on OSes that distinguish text
6161 mode from binary mode (namely, Windows). These files are:
6162 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6163 that collect those statistics; 'client_keys' and 'hostname' for
6164 hidden services that use authentication; and (in the tor-gencert
6165 utility) newly generated identity and signing keys. Previously,
6166 we wouldn't specify text mode or binary mode, leading to an
6167 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6168 the DirRecordUsageByCountry option which would have triggered
6169 the assertion failure was added), although this assertion failure
6170 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6171 - Selectively disable deprecation warnings on OS X because Lion
6172 started deprecating the shipped copy of openssl. Fixes bug 3643.
6173 - When unable to format an address as a string, report its value
6174 as "???" rather than reusing the last formatted address. Bugfix
6178 Changes in version 0.2.3.2-alpha - 2011-07-18
6179 Tor 0.2.3.2-alpha introduces two new experimental features:
6180 microdescriptors and pluggable transports. It also continues cleaning
6181 up a variety of recently introduced features.
6184 - Clients can now use microdescriptors instead of regular descriptors
6185 to build circuits. Microdescriptors are authority-generated
6186 summaries of regular descriptors' contents, designed to change
6187 very rarely (see proposal 158 for details). This feature is
6188 designed to save bandwidth, especially for clients on slow internet
6189 connections. It's off by default for now, since nearly no caches
6190 support it, but it will be on-by-default for clients in a future
6191 version. You can use the UseMicrodescriptors option to turn it on.
6192 - Tor clients using bridges can now be configured to use a separate
6193 'transport' proxy for each bridge. This approach helps to resist
6194 censorship by allowing bridges to use protocol obfuscation
6195 plugins. It implements part of proposal 180. Implements ticket 2841.
6196 - While we're trying to bootstrap, record how many TLS connections
6197 fail in each state, and report which states saw the most failures
6198 in response to any bootstrap failures. This feature may speed up
6199 diagnosis of censorship events. Implements ticket 3116.
6201 o Major bugfixes (on 0.2.3.1-alpha):
6202 - When configuring a large set of nodes in EntryNodes (as with
6203 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
6204 random subset to be guards, and choose them in random
6205 order. Fixes bug 2798.
6206 - Tor could crash when remembering a consensus in a non-used consensus
6207 flavor without having a current consensus set. Fixes bug 3361.
6208 - Comparing an unknown address to a microdescriptor's shortened exit
6209 policy would always give a "rejected" result. Fixes bug 3599.
6210 - Using microdescriptors as a client no longer prevents Tor from
6211 uploading and downloading hidden service descriptors. Fixes
6215 - Allow nameservers with IPv6 address. Resolves bug 2574.
6216 - Accept attempts to include a password authenticator in the
6217 handshake, as supported by SOCKS5. This handles SOCKS clients that
6218 don't know how to omit a password when authenticating. Resolves
6220 - When configuring a large set of nodes in EntryNodes, and there are
6221 enough of them listed as Guard so that we don't need to consider
6222 the non-guard entries, prefer the ones listed with the Guard flag.
6223 - Check for and recover from inconsistency in the microdescriptor
6224 cache. This will make it harder for us to accidentally free a
6225 microdescriptor without removing it from the appropriate data
6226 structures. Fixes issue 3135; issue noted by "wanoskarnet".
6227 - Log SSL state transitions at log level DEBUG, log domain
6228 HANDSHAKE. This can be useful for debugging censorship events.
6229 Implements ticket 3264.
6230 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
6231 implements ticket 3439.
6233 o Minor bugfixes (on 0.2.3.1-alpha):
6234 - Do not free all general-purpose regular descriptors just
6235 because microdescriptor use is enabled. Fixes bug 3113.
6236 - Correctly link libevent_openssl when --enable-static-libevent
6237 is passed to configure. Fixes bug 3118.
6238 - Bridges should not complain during their heartbeat log messages that
6239 they are unlisted in the consensus: that's more or less the point
6240 of being a bridge. Fixes bug 3183.
6241 - Report a SIGNAL event to controllers when acting on a delayed
6242 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
6243 event to the controller if we acted on a SIGNAL NEWNYM command
6244 immediately, and otherwise not report a SIGNAL event for the
6245 command at all. Fixes bug 3349.
6246 - Fix a crash when handling the SIGNAL controller command or
6247 reporting ERR-level status events with bufferevents enabled. Found
6248 by Robert Ransom. Fixes bug 3367.
6249 - Always ship the tor-fw-helper manpage in our release tarballs.
6250 Fixes bug 3389. Reported by Stephen Walker.
6251 - Fix a class of double-mark-for-close bugs when bufferevents
6252 are enabled. Fixes bug 3403.
6253 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
6254 - Add SIGNAL to the list returned by the 'GETINFO events/names'
6255 control-port command. Fixes part of bug 3465.
6256 - Prevent using negative indices during unit test runs when read_all()
6257 fails. Spotted by coverity.
6258 - Fix a rare memory leak when checking the nodelist without it being
6259 present. Found by coverity.
6260 - Only try to download a microdescriptor-flavored consensus from
6261 a directory cache that provides them.
6263 o Minor bugfixes (on 0.2.2.x and earlier):
6264 - Assert that hidden-service-related operations are not performed
6265 using single-hop circuits. Previously, Tor would assert that
6266 client-side streams are not attached to single-hop circuits,
6267 but not that other sensitive operations on the client and service
6268 side are not performed using single-hop circuits. Fixes bug 3332;
6270 - Don't publish a new relay descriptor when we reload our onion key,
6271 unless the onion key has actually changed. Fixes bug 3263 and
6272 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
6273 - Allow GETINFO fingerprint to return a fingerprint even when
6274 we have not yet built a router descriptor. Fixes bug 3577;
6275 bugfix on 0.2.0.1-alpha.
6276 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
6277 on 0.2.2.4-alpha; fixes bug 3427.
6279 o Code simplification and refactoring:
6280 - Use tor_sscanf() in place of scanf() in more places through the
6281 code. This makes us a little more locale-independent, and
6282 should help shut up code-analysis tools that can't tell
6283 a safe sscanf string from a dangerous one.
6284 - Use tt_assert(), not tor_assert(), for checking for test failures.
6285 This makes the unit tests more able to go on in the event that
6287 - Split connection_about_to_close() into separate functions for each
6291 - On Windows, we now define the _WIN32_WINNT macros only if they
6292 are not already defined. This lets the person building Tor decide,
6293 if they want, to require a later version of Windows.
6296 Changes in version 0.2.2.30-rc - 2011-07-07
6297 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
6298 series. It fixes a few smaller bugs, but generally appears stable.
6299 Please test it and let us know whether it is!
6302 - Send a SUCCEEDED stream event to the controller when a reverse
6303 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
6304 discovered by katmagic.
6305 - Always NUL-terminate the sun_path field of a sockaddr_un before
6306 passing it to the kernel. (Not a security issue: kernels are
6307 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6308 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6309 - Don't stack-allocate the list of supplementary GIDs when we're
6310 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6311 could take up to 256K, which is way too much stack. Found by
6312 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6313 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
6314 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
6315 fixes part of bug 3465.
6316 - Fix a memory leak when receiving a descriptor for a hidden
6317 service we didn't ask for. Found by Coverity; CID #30. Bugfix
6321 - Update to the July 1 2011 Maxmind GeoLite Country database.
6324 Changes in version 0.2.2.29-beta - 2011-06-20
6325 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
6326 have bridge lines in their torrc but don't want to use them; gets
6327 us closer to having the control socket feature working on Debian;
6328 and fixes a variety of smaller bugs.
6331 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
6332 When we changed the default behavior to "use bridges if any
6333 are listed in the torrc", we surprised users who had bridges
6334 in their torrc files but who didn't actually want to use them.
6335 Partial resolution for bug 3354.
6338 - Don't attach new streams to old rendezvous circuits after SIGNAL
6339 NEWNYM. Previously, we would keep using an existing rendezvous
6340 circuit if it remained open (i.e. if it were kept open by a
6341 long-lived stream, or if a new stream were attached to it before
6342 Tor could notice that it was old and no longer in use). Bugfix on
6343 0.1.1.15-rc; fixes bug 3375.
6346 - Fix a bug when using ControlSocketsGroupWritable with User. The
6347 directory's group would be checked against the current group, not
6348 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
6349 bugfix on 0.2.2.26-beta.
6350 - Make connection_printf_to_buf()'s behaviour sane. Its callers
6351 expect it to emit a CRLF iff the format string ends with CRLF;
6352 it actually emitted a CRLF iff (a) the format string ended with
6353 CRLF or (b) the resulting string was over 1023 characters long or
6354 (c) the format string did not end with CRLF *and* the resulting
6355 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
6356 fixes part of bug 3407.
6357 - Make send_control_event_impl()'s behaviour sane. Its callers
6358 expect it to always emit a CRLF at the end of the string; it
6359 might have emitted extra control characters as well. Bugfix on
6360 0.1.1.9-alpha; fixes another part of bug 3407.
6361 - Make crypto_rand_int() check the value of its input correctly.
6362 Previously, it accepted values up to UINT_MAX, but could return a
6363 negative number if given a value above INT_MAX+1. Found by George
6364 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
6365 - Avoid a segfault when reading a malformed circuit build state
6366 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
6368 - When asked about a DNS record type we don't support via a
6369 client DNSPort, reply with NOTIMPL rather than an empty
6370 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
6371 - Fix a rare memory leak during stats writing. Found by coverity.
6374 - Update to the June 1 2011 Maxmind GeoLite Country database.
6376 o Code simplifications and refactoring:
6377 - Remove some dead code as indicated by coverity.
6378 - Remove a few dead assignments during router parsing. Found by
6380 - Add some forgotten return value checks during unit tests. Found
6382 - Don't use 1-bit wide signed bit fields. Found by coverity.
6385 Changes in version 0.2.2.28-beta - 2011-06-04
6386 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
6387 fixed a big bug in whether relays stay in the consensus consistently,
6388 we moved closer to handling bridges and hidden services correctly,
6389 and we started the process of better handling the dreaded "my Vidalia
6390 died, and now my Tor demands a password when I try to reconnect to it"
6394 - Don't decide to make a new descriptor when receiving a HUP signal.
6395 This bug has caused a lot of 0.2.2.x relays to disappear from the
6396 consensus periodically. Fixes the most common case of triggering
6397 bug 1810; bugfix on 0.2.2.7-alpha.
6398 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
6399 - Don't try to build descriptors if "ORPort auto" is set and we
6400 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
6402 - Resolve a crash that occurred when setting BridgeRelay to 1 with
6403 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
6404 - Apply circuit timeouts to opened hidden-service-related circuits
6405 based on the correct start time. Previously, we would apply the
6406 circuit build timeout based on time since the circuit's creation;
6407 it was supposed to be applied based on time since the circuit
6408 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
6409 - Use the same circuit timeout for client-side introduction
6410 circuits as for other four-hop circuits, rather than the timeout
6411 for single-hop directory-fetch circuits; the shorter timeout may
6412 have been appropriate with the static circuit build timeout in
6413 0.2.1.x and earlier, but caused many hidden service access attempts
6414 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
6415 on 0.2.2.2-alpha; fixes another part of bug 1297.
6416 - In ticket 2511 we fixed a case where you could use an unconfigured
6417 bridge if you had configured it as a bridge the last time you ran
6418 Tor. Now fix another edge case: if you had configured it as a bridge
6419 but then switched to a different bridge via the controller, you
6420 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
6424 - Add an __OwningControllerProcess configuration option and a
6425 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
6426 that when it exits, Tor will shut down. Implements feature 3049.
6427 - If "UseBridges 1" is set and no bridges are configured, Tor will
6428 now refuse to build any circuits until some bridges are set.
6429 If "UseBridges auto" is set, Tor will use bridges if they are
6430 configured and we are not running as a server, but otherwise will
6431 make circuits as usual. The new default is "auto". Patch by anonym,
6432 so the Tails LiveCD can stop automatically revealing you as a Tor
6436 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6437 - Remove a trailing asterisk from "exit-policy/default" in the
6438 output of the control port command "GETINFO info/names". Bugfix
6440 - Use a wide type to hold sockets when built for 64-bit Windows builds.
6442 - Warn when the user configures two HiddenServiceDir lines that point
6443 to the same directory. Bugfix on 0.0.6 (the version introducing
6444 HiddenServiceDir); fixes bug 3289.
6445 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
6446 part of bug 2748; bugfix on 0.2.0.10-alpha.
6447 - Log malformed requests for rendezvous descriptors as protocol
6448 warnings, not warnings. Also, use a more informative log message
6449 in case someone sees it at log level warning without prior
6450 info-level messages. Fixes the other part of bug 2748; bugfix
6452 - Clear the table recording the time of the last request for each
6453 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
6454 Previously, we would clear our HS descriptor cache on SIGNAL
6455 NEWNYM, but if we had previously retrieved a descriptor (or tried
6456 to) from every directory responsible for it, we would refuse to
6457 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
6459 - Fix a log message that said "bits" while displaying a value in
6460 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
6462 - When checking for 1024-bit keys, check for 1024 bits, not 128
6463 bytes. This allows Tor to correctly discard keys of length 1017
6464 through 1023. Bugfix on 0.0.9pre5.
6467 - Relays now log the reason for publishing a new relay descriptor,
6468 so we have a better chance of hunting down instances of bug 1810.
6469 Resolves ticket 3252.
6470 - Revise most log messages that refer to nodes by nickname to
6471 instead use the "$key=nickname at address" format. This should be
6472 more useful, especially since nicknames are less and less likely
6473 to be unique. Resolves ticket 3045.
6474 - Log (at info level) when purging pieces of hidden-service-client
6475 state because of SIGNAL NEWNYM.
6478 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6479 anything since 0.2.1.16-rc.
6482 Changes in version 0.2.2.27-beta - 2011-05-18
6483 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
6484 release, and also adds a few more general bugfixes.
6487 - Fix a crash bug when changing bridges in a running Tor process.
6488 Fixes bug 3213; bugfix on 0.2.2.26-beta.
6489 - When the controller configures a new bridge, don't wait 10 to 60
6490 seconds before trying to fetch its descriptor. Bugfix on
6491 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
6494 - Require that onion keys have exponent 65537 in microdescriptors too.
6495 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
6496 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
6497 Changed the limit to 512 characters by removing base64 newlines.
6498 Fixes bug 2752. Fix by Michael Yakubovich.
6499 - When a client starts or stops using bridges, never use a circuit
6500 that was built before the configuration change. This behavior could
6501 put at risk a user who uses bridges to ensure that her traffic
6502 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
6506 Changes in version 0.2.2.26-beta - 2011-05-17
6507 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
6508 also introduces a new "socksport auto" approach that should make it
6509 easier to run multiple Tors on the same system, and does a lot of
6510 cleanup to get us closer to a release candidate.
6512 o Security/privacy fixes:
6513 - Replace all potentially sensitive memory comparison operations
6514 with versions whose runtime does not depend on the data being
6515 compared. This will help resist a class of attacks where an
6516 adversary can use variations in timing information to learn
6517 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6518 implementation by Robert Ransom based partially on code by DJB.)
6519 - When receiving a hidden service descriptor, check that it is for
6520 the hidden service we wanted. Previously, Tor would store any
6521 hidden service descriptors that a directory gave it, whether it
6522 wanted them or not. This wouldn't have let an attacker impersonate
6523 a hidden service, but it did let directories pre-seed a client
6524 with descriptors that it didn't want. Bugfix on 0.0.6.
6525 - On SIGHUP, do not clear out all TrackHostExits mappings, client
6526 DNS cache entries, and virtual address mappings: that's what
6527 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
6530 - The options SocksPort, ControlPort, and so on now all accept a
6531 value "auto" that opens a socket on an OS-selected port. A
6532 new ControlPortWriteToFile option tells Tor to write its
6533 actual control port or ports to a chosen file. If the option
6534 ControlPortFileGroupReadable is set, the file is created as
6535 group-readable. Now users can run two Tor clients on the same
6536 system without needing to manually mess with parameters. Resolves
6537 part of ticket 3076.
6538 - Set SO_REUSEADDR on all sockets, not just listeners. This should
6539 help busy exit nodes avoid running out of useable ports just
6540 because all the ports have been used in the near past. Resolves
6544 - New "GETINFO net/listeners/(type)" controller command to return
6545 a list of addresses and ports that are bound for listeners for a
6546 given connection type. This is useful when the user has configured
6547 "SocksPort auto" and the controller needs to know which port got
6548 chosen. Resolves another part of ticket 3076.
6549 - Add a new ControlSocketsGroupWritable configuration option: when
6550 it is turned on, ControlSockets are group-writeable by the default
6551 group of the current user. Patch by Jérémy Bobbio; implements
6553 - Tor now refuses to create a ControlSocket in a directory that is
6554 world-readable (or group-readable if ControlSocketsGroupWritable
6555 is 0). This is necessary because some operating systems do not
6556 enforce permissions on an AF_UNIX sockets. Permissions on the
6557 directory holding the socket, however, seems to work everywhere.
6558 - Rate-limit a warning about failures to download v2 networkstatus
6559 documents. Resolves part of bug 1352.
6560 - Backport code from 0.2.3.x that allows directory authorities to
6561 clean their microdescriptor caches. Needed to resolve bug 2230.
6562 - When an HTTPS proxy reports "403 Forbidden", we now explain
6563 what it means rather than calling it an unexpected status code.
6564 Closes bug 2503. Patch from Michael Yakubovich.
6565 - Update to the May 1 2011 Maxmind GeoLite Country database.
6568 - Authorities now clean their microdesc cache periodically and when
6569 reading from disk initially, not only when adding new descriptors.
6570 This prevents a bug where we could lose microdescriptors. Bugfix
6571 on 0.2.2.6-alpha. Fixes bug 2230.
6572 - Do not crash when our configuration file becomes unreadable, for
6573 example due to a permissions change, between when we start up
6574 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6576 - Avoid a bug that would keep us from replacing a microdescriptor
6577 cache on Windows. (We would try to replace the file while still
6578 holding it open. That's fine on Unix, but Windows doesn't let us
6579 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
6580 - Add missing explanations for the authority-related torrc options
6581 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
6582 man page. Resolves issue 2379.
6583 - As an authority, do not upload our own vote or signature set to
6584 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
6585 it would get flagged as a duplicate. Resolves bug 3026.
6586 - Accept hidden service descriptors if we think we might be a hidden
6587 service directory, regardless of what our consensus says. This
6588 helps robustness, since clients and hidden services can sometimes
6589 have a more up-to-date view of the network consensus than we do,
6590 and if they think that the directory authorities list us a HSDir,
6591 we might actually be one. Related to bug 2732; bugfix on
6593 - When a controller changes TrackHostExits, remove mappings for
6594 hosts that should no longer have their exits tracked. Bugfix on
6596 - When a controller changes VirtualAddrNetwork, remove any mappings
6597 for hosts that were automapped to the old network. Bugfix on
6599 - When a controller changes one of the AutomapHosts* options, remove
6600 any mappings for hosts that should no longer be automapped. Bugfix
6602 - Do not reset the bridge descriptor download status every time we
6603 re-parse our configuration or get a configuration change. Fixes
6604 bug 3019; bugfix on 0.2.0.3-alpha.
6606 o Minor bugfixes (code cleanup):
6607 - When loading the microdesc journal, remember its current size.
6608 In 0.2.2, this helps prevent the microdesc journal from growing
6609 without limit on authorities (who are the only ones to use it in
6610 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6611 Fix posted by "cypherpunks."
6612 - The microdesc journal is supposed to get rebuilt only if it is
6613 at least _half_ the length of the store, not _twice_ the length
6614 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6615 - Fix a potential null-pointer dereference while computing a
6616 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
6618 - Avoid a possible null-pointer dereference when rebuilding the mdesc
6619 cache without actually having any descriptors to cache. Bugfix on
6620 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
6621 - If we fail to compute the identity digest of a v3 legacy keypair,
6622 warn, and don't use a buffer-full of junk instead. Bugfix on
6623 0.2.1.1-alpha; fixes bug 3106.
6624 - Resolve an untriggerable issue in smartlist_string_num_isin(),
6625 where if the function had ever in the future been used to check
6626 for the presence of a too-large number, it would have given an
6627 incorrect result. (Fortunately, we only used it for 16-bit
6628 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
6629 - Require that introduction point keys and onion handshake keys
6630 have a public exponent of 65537. Starts to fix bug 3207; bugfix
6634 - Caches no longer download and serve v2 networkstatus documents
6635 unless FetchV2Networkstatus flag is set: these documents haven't
6636 haven't been used by clients or relays since 0.2.0.x. Resolves
6640 Changes in version 0.2.3.1-alpha - 2011-05-05
6641 Tor 0.2.3.1-alpha adds some new experimental features, including support
6642 for an improved network IO backend, IOCP networking on Windows,
6643 microdescriptor caching, "fast-start" support for streams, and automatic
6644 home router configuration. There are also numerous internal improvements
6645 to try to make the code easier for developers to work with.
6647 This is the first alpha release in a new series, so expect there to be
6648 bugs. Users who would rather test out a more stable branch should
6649 stay with 0.2.2.x for now.
6652 - Tor can now optionally build with the "bufferevents" buffered IO
6653 backend provided by Libevent 2. To use this feature, make sure you
6654 have the latest possible version of Libevent, and pass the
6655 --enable-bufferevents flag to configure when building Tor from
6656 source. This feature will make our networking code more flexible,
6657 let us stack layers on each other, and let us use more efficient
6658 zero-copy transports where available.
6659 - As an experimental feature, Tor can use IOCP for networking on Windows.
6660 Once this code is tuned and optimized, it promises much better
6661 performance than the select-based backend we've used in the past. To
6662 try this feature, you must build Tor with Libevent 2, configure Tor
6663 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
6664 your torrc. There are known bugs here: only try this if you can help
6665 debug it as it breaks.
6666 - The EntryNodes option can now include country codes like {de} or IP
6667 addresses or network masks. Previously we had disallowed these options
6668 because we didn't have an efficient way to keep the list up to
6669 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
6670 - Exit nodes now accept and queue data on not-yet-connected streams.
6671 Previously, the client wasn't allowed to send data until the stream was
6672 connected, which slowed down all connections. This change will enable
6673 clients to perform a "fast-start" on streams and send data without
6674 having to wait for a confirmation that the stream has opened. (Patch
6675 from Ian Goldberg; implements the server side of Proposal 174.)
6676 - Tor now has initial support for automatic port mapping on the many
6677 home routers that support NAT-PMP or UPnP. (Not yet supported on
6678 Windows). To build the support code, you'll need to have libnatpnp
6679 library and/or the libminiupnpc library, and you'll need to enable the
6680 feature specifically by passing "--enable-upnp" and/or
6681 "--enable-natpnp" to configure. To turn it on, use the new
6682 PortForwarding option.
6683 - Caches now download, cache, and serve multiple "flavors" of the
6684 consensus, including a flavor that describes microdescriptors.
6685 - Caches now download, cache, and serve microdescriptors -- small
6686 summaries of router descriptors that are authenticated by all of the
6687 directory authorities. Once enough caches are running this code,
6688 clients will be able to save significant amounts of directory bandwidth
6689 by downloading microdescriptors instead of router descriptors.
6692 - Make logging resolution configurable with a new LogTimeGranularity
6693 option, and change the default from 1 millisecond to 1 second.
6694 Implements enhancement 1668.
6695 - We log which torrc file we're using on startup. Implements ticket
6697 - Ordinarily, Tor does not count traffic from private addresses (like
6698 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
6699 There is now a new option, CountPrivateBandwidth, to disable this
6700 behavior. Patch from Daniel Cagara.
6701 - New --enable-static-tor configure option for building Tor as
6702 statically as possible. Idea, general hackery and thoughts from
6703 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
6705 - If you set the NumCPUs option to 0, Tor will now try to detect how
6706 many CPUs you have. This is the new default behavior.
6707 - Turn on directory request statistics by default and include them in
6708 extra-info descriptors. Don't break if we have no GeoIP database.
6709 - Relays that set "ConnDirectionStatistics 1" write statistics on the
6710 bidirectional use of connections to disk every 24 hours.
6711 - Add a GeoIP file digest to the extra-info descriptor. Implements
6713 - The NodeFamily option -- which let you declare that you want to
6714 consider nodes to be part of a family whether they list themselves
6715 that way or not -- now allows IP address ranges and country codes.
6716 - Add a new 'Heartbeat' log message type to periodically log a message
6717 describing Tor's status at level Notice. This feature is meant for
6718 operators who log at notice, and want to make sure that their Tor
6719 server is still working. Implementation by George Kadianakis.
6721 o Minor bugfixes (on 0.2.2.25-alpha):
6722 - When loading the microdesc journal, remember its current size.
6723 In 0.2.2, this helps prevent the microdesc journal from growing
6724 without limit on authorities (who are the only ones to use it in
6725 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6726 Fix posted by "cypherpunks."
6727 - The microdesc journal is supposed to get rebuilt only if it is
6728 at least _half_ the length of the store, not _twice_ the length
6729 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6730 - If as an authority we fail to compute the identity digest of a v3
6731 legacy keypair, warn, and don't use a buffer-full of junk instead.
6732 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
6733 - Authorities now clean their microdesc cache periodically and when
6734 reading from disk initially, not only when adding new descriptors.
6735 This prevents a bug where we could lose microdescriptors. Bugfix
6738 o Minor features (controller):
6739 - Add a new SIGNAL event to the controller interface so that
6740 controllers can be notified when Tor handles a signal. Resolves
6741 issue 1955. Patch by John Brooks.
6742 - Add a new GETINFO option to get total bytes read and written. Patch
6743 from pipe, revised by atagar. Resolves ticket 2345.
6744 - Implement some GETINFO controller fields to provide information about
6745 the Tor process's pid, euid, username, and resource limits.
6748 - Our build system requires automake 1.6 or later to create the
6749 Makefile.in files. Previously, you could have used 1.4.
6750 This only affects developers and people building Tor from git;
6751 people who build Tor from the source distribution without changing
6752 the Makefile.am files should be fine.
6753 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
6754 so on. This is more robust against some of the failure modes
6755 associated with running the autotools pieces on their own.
6757 o Minor packaging issues:
6758 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
6759 already created. Patch from Andreas Stieger. Fixes bug 2573.
6761 o Code simplifications and refactoring:
6762 - A major revision to our internal node-selecting and listing logic.
6763 Tor already had at least two major ways to look at the question of
6764 "which Tor servers do we know about": a list of router descriptors,
6765 and a list of entries in the current consensus. With
6766 microdescriptors, we're adding a third. Having so many systems
6767 without an abstraction layer over them was hurting the codebase.
6768 Now, we have a new "node_t" abstraction that presents a consistent
6769 interface to a client's view of a Tor node, and holds (nearly) all
6770 of the mutable state formerly in routerinfo_t and routerstatus_t.
6771 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
6772 no longer link against Libevent: they never used it, but
6773 our library structure used to force them to link it.
6776 - Remove some old code to work around even older versions of Tor that
6777 used forked processes to handle DNS requests. Such versions of Tor
6778 are no longer in use as servers.
6780 o Documentation fixes:
6781 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
6782 - Add missing documentation for the authority-related torrc options
6783 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
6787 Changes in version 0.2.2.25-alpha - 2011-04-29
6788 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
6789 robust, routers no longer overreport their bandwidth, Win7 should crash
6790 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
6791 now prevents hidden service-related activity from being linkable. It
6792 provides more information to Vidalia so you can see if your bridge is
6793 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
6794 StrictNodes configuration options to make them more reliable, more
6795 understandable, and more regularly applied. If you use those options,
6796 please see the revised documentation for them in the manual page.
6799 - Relays were publishing grossly inflated bandwidth values because
6800 they were writing their state files wrong--now they write the
6801 correct value. Also, resume reading bandwidth history from the
6802 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
6803 - Improve hidden service robustness: When we find that we have
6804 extended a hidden service's introduction circuit to a relay not
6805 listed as an introduction point in the HS descriptor we currently
6806 have, retry with an introduction point from the current
6807 descriptor. Previously we would just give up. Fixes bugs 1024 and
6808 1930; bugfix on 0.2.0.10-alpha.
6809 - Clients now stop trying to use an exit node associated with a given
6810 destination by TrackHostExits if they fail to reach that exit node.
6811 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
6812 - Fix crash bug on platforms where gmtime and localtime can return
6813 NULL. Windows 7 users were running into this one. Fixes part of bug
6814 2077. Bugfix on all versions of Tor. Found by boboper.
6816 o Security and stability fixes:
6817 - Don't double-free a parsable, but invalid, microdescriptor, even if
6818 it is followed in the blob we're parsing by an unparsable
6819 microdescriptor. Fixes an issue reported in a comment on bug 2954.
6820 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
6821 - If the Nickname configuration option isn't given, Tor would pick a
6822 nickname based on the local hostname as the nickname for a relay.
6823 Because nicknames are not very important in today's Tor and the
6824 "Unnamed" nickname has been implemented, this is now problematic
6825 behavior: It leaks information about the hostname without being
6826 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
6827 introduced the Unnamed nickname. Reported by tagnaq.
6828 - Fix an uncommon assertion failure when running with DNSPort under
6829 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6830 - Avoid linkability based on cached hidden service descriptors: forget
6831 all hidden service descriptors cached as a client when processing a
6832 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6835 - Export GeoIP information on bridge usage to controllers even if we
6836 have not yet been running for 24 hours. Now Vidalia bridge operators
6837 can get more accurate and immediate feedback about their
6838 contributions to the network.
6840 o Major features and bugfixes (node selection):
6841 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
6842 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
6843 options. Previously, we had been ambiguous in describing what
6844 counted as an "exit" node, and what operations exactly "StrictNodes
6845 0" would permit. This created confusion when people saw nodes built
6846 through unexpected circuits, and made it hard to tell real bugs from
6847 surprises. Now the intended behavior is:
6848 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
6849 a node that delivers user traffic outside the Tor network.
6850 . "Entry", in the context of EntryNodes, means a node used as the
6851 first hop of a multihop circuit. It doesn't include direct
6852 connections to directory servers.
6853 . "ExcludeNodes" applies to all nodes.
6854 . "StrictNodes" changes the behavior of ExcludeNodes only. When
6855 StrictNodes is set, Tor should avoid all nodes listed in
6856 ExcludeNodes, even when it will make user requests fail. When
6857 StrictNodes is *not* set, then Tor should follow ExcludeNodes
6858 whenever it can, except when it must use an excluded node to
6859 perform self-tests, connect to a hidden service, provide a
6860 hidden service, fulfill a .exit request, upload directory
6861 information, or fetch directory information.
6862 Collectively, the changes to implement the behavior fix bug 1090.
6863 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
6864 a node is listed in both, it's treated as excluded.
6865 - ExcludeNodes now applies to directory nodes -- as a preference if
6866 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
6867 Don't exclude all the directory authorities and set StrictNodes to 1
6868 unless you really want your Tor to break.
6869 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
6870 - ExcludeExitNodes now overrides .exit requests.
6871 - We don't use bridges listed in ExcludeNodes.
6872 - When StrictNodes is 1:
6873 . We now apply ExcludeNodes to hidden service introduction points
6874 and to rendezvous points selected by hidden service users. This
6875 can make your hidden service less reliable: use it with caution!
6876 . If we have used ExcludeNodes on ourself, do not try relay
6877 reachability self-tests.
6878 . If we have excluded all the directory authorities, we will not
6879 even try to upload our descriptor if we're a relay.
6880 . Do not honor .exit requests to an excluded node.
6881 - Remove a misfeature that caused us to ignore the Fast/Stable flags
6882 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
6883 - When the set of permitted nodes changes, we now remove any mappings
6884 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
6886 - We never cannibalize a circuit that had excluded nodes on it, even
6887 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
6888 - Revert a change where we would be laxer about attaching streams to
6889 circuits than when building the circuits. This was meant to prevent
6890 a set of bugs where streams were never attachable, but our improved
6891 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
6892 - Keep track of how many times we launch a new circuit to handle a
6893 given stream. Too many launches could indicate an inconsistency
6894 between our "launch a circuit to handle this stream" logic and our
6895 "attach this stream to one of the available circuits" logic.
6896 - Improve log messages related to excluded nodes.
6899 - Fix a spurious warning when moving from a short month to a long
6900 month on relays with month-based BandwidthAccounting. Bugfix on
6901 0.2.2.17-alpha; fixes bug 3020.
6902 - When a client finds that an origin circuit has run out of 16-bit
6903 stream IDs, we now mark it as unusable for new streams. Previously,
6904 we would try to close the entire circuit. Bugfix on 0.0.6.
6905 - Add a forgotten cast that caused a compile warning on OS X 10.6.
6906 Bugfix on 0.2.2.24-alpha.
6907 - Be more careful about reporting the correct error from a failed
6908 connect() system call. Under some circumstances, it was possible to
6909 look at an incorrect value for errno when sending the end reason.
6910 Bugfix on 0.1.0.1-rc.
6911 - Correctly handle an "impossible" overflow cases in connection byte
6912 counting, where we write or read more than 4GB on an edge connection
6913 in a single second. Bugfix on 0.1.2.8-beta.
6914 - Correct the warning displayed when a rendezvous descriptor exceeds
6915 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6917 - Clients and hidden services now use HSDir-flagged relays for hidden
6918 service descriptor downloads and uploads even if the relays have no
6919 DirPort set and the client has disabled TunnelDirConns. This will
6920 eventually allow us to give the HSDir flag to relays with no
6921 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
6922 - Downgrade "no current certificates known for authority" message from
6923 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
6924 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
6925 2917. Bugfix on 0.1.1.1-alpha.
6926 - Only limit the lengths of single HS descriptors, even when multiple
6927 HS descriptors are published to an HSDir relay in a single POST
6928 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
6929 - Write the current time into the LastWritten line in our state file,
6930 rather than the time from the previous write attempt. Also, stop
6931 trying to use a time of -1 in our log statements. Fixes bug 3039;
6932 bugfix on 0.2.2.14-alpha.
6933 - Be more consistent in our treatment of file system paths. "~" should
6934 get expanded to the user's home directory in the Log config option.
6935 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
6936 feature for the -f and --DataDirectory options.
6939 - Make sure every relay writes a state file at least every 12 hours.
6940 Previously, a relay could go for weeks without writing its state
6941 file, and on a crash could lose its bandwidth history, capacity
6942 estimates, client country statistics, and so on. Addresses bug 3012.
6943 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
6944 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
6945 clients are already deprecated because of security bugs.
6946 - Don't allow v0 hidden service authorities to act as clients.
6947 Required by fix for bug 3000.
6948 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
6949 by fix for bug 3000.
6950 - Ensure that no empty [dirreq-](read|write)-history lines are added
6951 to an extrainfo document. Implements ticket 2497.
6953 o Code simplification and refactoring:
6954 - Remove workaround code to handle directory responses from servers
6955 that had bug 539 (they would send HTTP status 503 responses _and_
6956 send a body too). Since only server versions before
6957 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
6958 keep the workaround in place.
6959 - Remove the old 'fuzzy time' logic. It was supposed to be used for
6960 handling calculations where we have a known amount of clock skew and
6961 an allowed amount of unknown skew. But we only used it in three
6962 places, and we never adjusted the known/unknown skew values. This is
6963 still something we might want to do someday, but if we do, we'll
6964 want to do it differently.
6965 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6966 None of the cases where we did this before were wrong, but by making
6967 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6968 - Use GetTempDir to find the proper temporary directory location on
6969 Windows when generating temporary files for the unit tests. Patch by
6973 Changes in version 0.2.2.24-alpha - 2011-04-08
6974 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
6975 prevented Tor clients from effectively using "multihomed" bridges,
6976 that is, bridges that listen on multiple ports or IP addresses so users
6977 can continue to use some of their addresses even if others get blocked.
6980 - Fix a bug where bridge users who configure the non-canonical
6981 address of a bridge automatically switch to its canonical
6982 address. If a bridge listens at more than one address, it should be
6983 able to advertise those addresses independently and any non-blocked
6984 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
6986 - If you configured Tor to use bridge A, and then quit and
6987 configured Tor to use bridge B instead, it would happily continue
6988 to use bridge A if it's still reachable. While this behavior is
6989 a feature if your goal is connectivity, in some scenarios it's a
6990 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
6991 - Directory authorities now use data collected from their own
6992 uptime observations when choosing whether to assign the HSDir flag
6993 to relays, instead of trusting the uptime value the relay reports in
6994 its descriptor. This change helps prevent an attack where a small
6995 set of nodes with frequently-changing identity keys can blackhole
6996 a hidden service. (Only authorities need upgrade; others will be
6997 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
7000 - When we restart our relay, we might get a successful connection
7001 from the outside before we've started our reachability tests,
7002 triggering a warning: "ORPort found reachable, but I have no
7003 routerinfo yet. Failing to inform controller of success." This
7004 bug was harmless unless Tor is running under a controller
7005 like Vidalia, in which case the controller would never get a
7006 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7008 - Make directory authorities more accurate at recording when
7009 relays that have failed several reachability tests became
7010 unreachable, so we can provide more accuracy at assigning Stable,
7011 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
7012 - Fix an issue that prevented static linking of libevent on
7013 some platforms (notably Linux). Fixes bug 2698; bugfix on
7014 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
7015 the --with-static-libevent configure option).
7016 - We now ask the other side of a stream (the client or the exit)
7017 for more data on that stream when the amount of queued data on
7018 that stream dips low enough. Previously, we wouldn't ask the
7019 other side for more data until either it sent us more data (which
7020 it wasn't supposed to do if it had exhausted its window!) or we
7021 had completely flushed all our queued data. This flow control fix
7022 should improve throughput. Fixes bug 2756; bugfix on the earliest
7023 released versions of Tor (svn commit r152).
7024 - Avoid a double-mark-for-free warning when failing to attach a
7025 transparent proxy connection. (We thought we had fixed this in
7026 0.2.2.23-alpha, but it turns out our fix was checking the wrong
7027 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
7028 bug) and 0.2.2.23-alpha (the incorrect fix).
7029 - When warning about missing zlib development packages during compile,
7030 give the correct package names. Bugfix on 0.2.0.1-alpha.
7033 - Directory authorities now log the source of a rejected POSTed v3
7035 - Make compilation with clang possible when using
7036 --enable-gcc-warnings by removing two warning options that clang
7037 hasn't implemented yet and by fixing a few warnings. Implements
7039 - When expiring circuits, use microsecond timers rather than
7040 one-second timers. This can avoid an unpleasant situation where a
7041 circuit is launched near the end of one second and expired right
7042 near the beginning of the next, and prevent fluctuations in circuit
7044 - Use computed circuit-build timeouts to decide when to launch
7045 parallel introduction circuits for hidden services. (Previously,
7046 we would retry after 15 seconds.)
7047 - Update to the April 1 2011 Maxmind GeoLite Country database.
7050 - Create the /var/run/tor directory on startup on OpenSUSE if it is
7051 not already created. Patch from Andreas Stieger. Fixes bug 2573.
7053 o Documentation changes:
7054 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
7055 - Resolve all doxygen warnings except those for missing documentation.
7057 - Add doxygen documentation for more functions, fields, and types.
7060 Changes in version 0.2.2.23-alpha - 2011-03-08
7061 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
7062 they restart they don't lose their bandwidth capacity estimate. This
7063 release also fixes a diverse set of user-facing bugs, ranging from
7064 relays overrunning their rate limiting to clients falsely warning about
7065 clock skew to bridge descriptor leaks by our bridge directory authority.
7068 - Stop sending a CLOCK_SKEW controller status event whenever
7069 we fetch directory information from a relay that has a wrong clock.
7070 Instead, only inform the controller when it's a trusted authority
7071 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7072 the rest of bug 1074.
7073 - Fix an assert in parsing router descriptors containing IPv6
7074 addresses. This one took down the directory authorities when
7075 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7076 - Make the bridge directory authority refuse to answer directory
7077 requests for "all" descriptors. It used to include bridge
7078 descriptors in its answer, which was a major information leak.
7079 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7080 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7081 Tor would ignore their RelayBandwidthBurst setting,
7082 potentially using more bandwidth than expected. Bugfix on
7083 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7084 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7085 hidserv" in her torrc. The 'hidserv' argument never controlled
7086 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7089 - Relays now save observed peak bandwidth throughput rates to their
7090 state file (along with total usage, which was already saved)
7091 so that they can determine their correct estimated bandwidth on
7092 restart. Resolves bug 1863, where Tor relays would reset their
7093 estimated bandwidth to 0 after restarting.
7094 - Directory authorities now take changes in router IP address and
7095 ORPort into account when determining router stability. Previously,
7096 if a router changed its IP or ORPort, the authorities would not
7097 treat it as having any downtime for the purposes of stability
7098 calculation, whereas clients would experience downtime since the
7099 change could take a while to propagate to them. Resolves issue 1035.
7100 - Enable Address Space Layout Randomization (ASLR) and Data Execution
7101 Prevention (DEP) by default on Windows to make it harder for
7102 attackers to exploit vulnerabilities. Patch from John Brooks.
7104 o Minor bugfixes (on 0.2.1.x and earlier):
7105 - Fix a rare crash bug that could occur when a client was configured
7106 with a large number of bridges. Fixes bug 2629; bugfix on
7107 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7108 - Avoid a double mark-for-free warning when failing to attach a
7109 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
7111 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
7112 found by "cypherpunks". This bug was introduced before the first
7113 Tor release, in svn commit r110.
7114 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
7115 don't mention them in the manpage. Fixes bug 2450; issue
7116 spotted by keb and G-Lo.
7117 - Fix a bug in bandwidth history state parsing that could have been
7118 triggered if a future version of Tor ever changed the timing
7119 granularity at which bandwidth history is measured. Bugfix on
7121 - When a relay decides that its DNS is too broken for it to serve
7122 as an exit server, it advertised itself as a non-exit, but
7123 continued to act as an exit. This could create accidental
7124 partitioning opportunities for users. Instead, if a relay is
7125 going to advertise reject *:* as its exit policy, it should
7126 really act with exit policy "reject *:*". Fixes bug 2366.
7127 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
7128 - In the special case where you configure a public exit relay as your
7129 bridge, Tor would be willing to use that exit relay as the last
7130 hop in your circuit as well. Now we fail that circuit instead.
7131 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
7132 - Fix a bug with our locking implementation on Windows that couldn't
7133 correctly detect when a file was already locked. Fixes bug 2504,
7134 bugfix on 0.2.1.6-alpha.
7135 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
7136 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
7138 - Set target port in get_interface_address6() correctly. Bugfix
7139 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
7140 - Directory authorities are now more robust to hops back in time
7141 when calculating router stability. Previously, if a run of uptime
7142 or downtime appeared to be negative, the calculation could give
7143 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
7145 - Fix an assert that got triggered when using the TestingTorNetwork
7146 configuration option and then issuing a GETINFO config-text control
7147 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
7149 o Minor bugfixes (on 0.2.2.x):
7150 - Clients should not weight BadExit nodes as Exits in their node
7151 selection. Similarly, directory authorities should not count BadExit
7152 bandwidth as Exit bandwidth when computing bandwidth-weights.
7153 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
7154 - Correctly clear our dir_read/dir_write history when there is an
7155 error parsing any bw history value from the state file. Bugfix on
7157 - Resolve a bug in verifying signatures of directory objects
7158 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
7159 Fixes bug 2409. Found by "piebeer".
7160 - Bridge authorities no longer crash on SIGHUP when they try to
7161 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
7165 - Log less aggressively about circuit timeout changes, and improve
7166 some other circuit timeout messages. Resolves bug 2004.
7167 - Log a little more clearly about the times at which we're no longer
7168 accepting new connections. Resolves bug 2181.
7169 - Reject attempts at the client side to open connections to private
7170 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
7171 a randomly chosen exit node. Attempts to do so are always
7172 ill-defined, generally prevented by exit policies, and usually
7173 in error. This will also help to detect loops in transparent
7174 proxy configurations. You can disable this feature by setting
7175 "ClientRejectInternalAddresses 0" in your torrc.
7176 - Always treat failure to allocate an RSA key as an unrecoverable
7178 - Update to the March 1 2011 Maxmind GeoLite Country database.
7180 o Minor features (log subsystem):
7181 - Add documentation for configuring logging at different severities in
7182 different log domains. We've had this feature since 0.2.1.1-alpha,
7183 but for some reason it never made it into the manpage. Fixes
7185 - Make it simpler to specify "All log domains except for A and B".
7186 Previously you needed to say "[*,~A,~B]". Now you can just say
7188 - Add a "LogMessageDomains 1" option to include the domains of log
7189 messages along with the messages. Without this, there's no way
7190 to use log domains without reading the source or doing a lot
7193 o Packaging changes:
7194 - Stop shipping the Tor specs files and development proposal documents
7195 in the tarball. They are now in a separate git repository at
7196 git://git.torproject.org/torspec.git
7199 Changes in version 0.2.1.30 - 2011-02-23
7200 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
7201 change is a slight tweak to Tor's TLS handshake that makes relays
7202 and bridges that run this new version reachable from Iran again.
7203 We don't expect this tweak will win the arms race long-term, but it
7204 buys us time until we roll out a better solution.
7207 - Stop sending a CLOCK_SKEW controller status event whenever
7208 we fetch directory information from a relay that has a wrong clock.
7209 Instead, only inform the controller when it's a trusted authority
7210 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7211 the rest of bug 1074.
7212 - Fix a bounds-checking error that could allow an attacker to
7213 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7215 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7216 Tor would ignore their RelayBandwidthBurst setting,
7217 potentially using more bandwidth than expected. Bugfix on
7218 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7219 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7220 hidserv" in her torrc. The 'hidserv' argument never controlled
7221 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7224 - Adjust our TLS Diffie-Hellman parameters to match those used by
7226 - Update to the February 1 2011 Maxmind GeoLite Country database.
7229 - Check for and reject overly long directory certificates and
7230 directory tokens before they have a chance to hit any assertions.
7231 Bugfix on 0.2.1.28. Found by "doorss".
7232 - Bring the logic that gathers routerinfos and assesses the
7233 acceptability of circuits into line. This prevents a Tor OP from
7234 getting locked in a cycle of choosing its local OR as an exit for a
7235 path (due to a .exit request) and then rejecting the circuit because
7236 its OR is not listed yet. It also prevents Tor clients from using an
7237 OR running in the same instance as an exit (due to a .exit request)
7238 if the OR does not meet the same requirements expected of an OR
7239 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7241 o Packaging changes:
7242 - Stop shipping the Tor specs files and development proposal documents
7243 in the tarball. They are now in a separate git repository at
7244 git://git.torproject.org/torspec.git
7245 - Do not include Git version tags as though they are SVN tags when
7246 generating a tarball from inside a repository that has switched
7247 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7250 Changes in version 0.2.2.22-alpha - 2011-01-25
7251 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
7252 main other change is a slight tweak to Tor's TLS handshake that makes
7253 relays and bridges that run this new version reachable from Iran again.
7254 We don't expect this tweak will win the arms race long-term, but it
7255 will buy us a bit more time until we roll out a better solution.
7258 - Fix a bounds-checking error that could allow an attacker to
7259 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7261 - Don't assert when changing from bridge to relay or vice versa
7262 via the controller. The assert happened because we didn't properly
7263 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
7264 bug 2433. Reported by bastik.
7267 - Adjust our TLS Diffie-Hellman parameters to match those used by
7269 - Provide a log message stating which geoip file we're parsing
7270 instead of just stating that we're parsing the geoip file.
7271 Implements ticket 2432.
7274 - Check for and reject overly long directory certificates and
7275 directory tokens before they have a chance to hit any assertions.
7276 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
7279 Changes in version 0.2.2.21-alpha - 2011-01-15
7280 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
7281 continues our recent code security audit work. The main fix resolves
7282 a remote heap overflow vulnerability that can allow remote code
7283 execution (CVE-2011-0427). Other fixes address a variety of assert
7284 and crash bugs, most of which we think are hard to exploit remotely.
7286 o Major bugfixes (security), also included in 0.2.1.29:
7287 - Fix a heap overflow bug where an adversary could cause heap
7288 corruption. This bug probably allows remote code execution
7289 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7291 - Prevent a denial-of-service attack by disallowing any
7292 zlib-compressed data whose compression factor is implausibly
7293 high. Fixes part of bug 2324; reported by "doorss".
7294 - Zero out a few more keys in memory before freeing them. Fixes
7295 bug 2384 and part of bug 2385. These key instances found by
7296 "cypherpunks", based on Andrew Case's report about being able
7297 to find sensitive data in Tor's memory space if you have enough
7298 permissions. Bugfix on 0.0.2pre9.
7300 o Major bugfixes (crashes), also included in 0.2.1.29:
7301 - Prevent calls to Libevent from inside Libevent log handlers.
7302 This had potential to cause a nasty set of crashes, especially
7303 if running Libevent with debug logging enabled, and running
7304 Tor with a controller watching for low-severity log messages.
7305 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7306 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7307 underflow errors there too. Fixes the other part of bug 2324.
7308 - Fix a bug where we would assert if we ever had a
7309 cached-descriptors.new file (or another file read directly into
7310 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7311 on 0.2.1.25. Found by doorss.
7312 - Fix some potential asserts and parsing issues with grossly
7313 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7316 o Minor bugfixes (other), also included in 0.2.1.29:
7317 - Fix a bug with handling misformed replies to reverse DNS lookup
7318 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7319 bug reported by doorss.
7320 - Fix compilation on mingw when a pthreads compatibility library
7321 has been installed. (We don't want to use it, so we shouldn't
7322 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7323 - Fix a bug where we would declare that we had run out of virtual
7324 addresses when the address space was only half-exhausted. Bugfix
7326 - Correctly handle the case where AutomapHostsOnResolve is set but
7327 no virtual addresses are available. Fixes bug 2328; bugfix on
7328 0.1.2.1-alpha. Bug found by doorss.
7329 - Correctly handle wrapping around when we run out of virtual
7330 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
7332 o Minor features, also included in 0.2.1.29:
7333 - Update to the January 1 2011 Maxmind GeoLite Country database.
7334 - Introduce output size checks on all of our decryption functions.
7336 o Build changes, also included in 0.2.1.29:
7337 - Tor does not build packages correctly with Automake 1.6 and earlier;
7338 added a check to Makefile.am to make sure that we're building with
7339 Automake 1.7 or later.
7340 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7341 because we built it with a too-old version of automake. Thus that
7342 release broke ./configure --enable-openbsd-malloc, which is popular
7343 among really fast exit relays on Linux.
7345 o Major bugfixes, new in 0.2.2.21-alpha:
7346 - Prevent crash/heap corruption when the cbtnummodes consensus
7347 parameter is set to 0 or large values. Fixes bug 2317; bugfix
7350 o Major features, new in 0.2.2.21-alpha:
7351 - Introduce minimum/maximum values that clients will believe
7352 from the consensus. Now we'll have a better chance to avoid crashes
7353 or worse when a consensus param has a weird value.
7355 o Minor features, new in 0.2.2.21-alpha:
7356 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
7357 used on bridges, and it makes bridge scanning somewhat easier.
7358 - If writing the state file to disk fails, wait up to an hour before
7359 retrying again, rather than trying again each second. Fixes bug
7360 2346; bugfix on Tor 0.1.1.3-alpha.
7361 - Make Libevent log messages get delivered to controllers later,
7362 and not from inside the Libevent log handler. This prevents unsafe
7363 reentrant Libevent calls while still letting the log messages
7365 - Detect platforms that brokenly use a signed size_t, and refuse to
7366 build there. Found and analyzed by doorss and rransom.
7367 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
7370 o Minor bugfixes, new in 0.2.2.21-alpha:
7371 - Handle SOCKS messages longer than 128 bytes long correctly, rather
7372 than waiting forever for them to finish. Fixes bug 2330; bugfix
7373 on 0.2.0.16-alpha. Found by doorss.
7374 - Add assertions to check for overflow in arguments to
7375 base32_encode() and base32_decode(); fix a signed-unsigned
7376 comparison there too. These bugs are not actually reachable in Tor,
7377 but it's good to prevent future errors too. Found by doorss.
7378 - Correctly detect failures to create DNS requests when using Libevent
7379 versions before v2. (Before Libevent 2, we used our own evdns
7380 implementation. Its return values for Libevent's evdns_resolve_*()
7381 functions are not consistent with those from Libevent.) Fixes bug
7382 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
7384 o Documentation, new in 0.2.2.21-alpha:
7385 - Document the default socks host and port (127.0.0.1:9050) for
7389 Changes in version 0.2.1.29 - 2011-01-15
7390 Tor 0.2.1.29 continues our recent code security audit work. The main
7391 fix resolves a remote heap overflow vulnerability that can allow remote
7392 code execution. Other fixes address a variety of assert and crash bugs,
7393 most of which we think are hard to exploit remotely.
7395 o Major bugfixes (security):
7396 - Fix a heap overflow bug where an adversary could cause heap
7397 corruption. This bug probably allows remote code execution
7398 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7400 - Prevent a denial-of-service attack by disallowing any
7401 zlib-compressed data whose compression factor is implausibly
7402 high. Fixes part of bug 2324; reported by "doorss".
7403 - Zero out a few more keys in memory before freeing them. Fixes
7404 bug 2384 and part of bug 2385. These key instances found by
7405 "cypherpunks", based on Andrew Case's report about being able
7406 to find sensitive data in Tor's memory space if you have enough
7407 permissions. Bugfix on 0.0.2pre9.
7409 o Major bugfixes (crashes):
7410 - Prevent calls to Libevent from inside Libevent log handlers.
7411 This had potential to cause a nasty set of crashes, especially
7412 if running Libevent with debug logging enabled, and running
7413 Tor with a controller watching for low-severity log messages.
7414 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7415 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7416 underflow errors there too. Fixes the other part of bug 2324.
7417 - Fix a bug where we would assert if we ever had a
7418 cached-descriptors.new file (or another file read directly into
7419 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7420 on 0.2.1.25. Found by doorss.
7421 - Fix some potential asserts and parsing issues with grossly
7422 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7425 o Minor bugfixes (other):
7426 - Fix a bug with handling misformed replies to reverse DNS lookup
7427 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7428 bug reported by doorss.
7429 - Fix compilation on mingw when a pthreads compatibility library
7430 has been installed. (We don't want to use it, so we shouldn't
7431 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7432 - Fix a bug where we would declare that we had run out of virtual
7433 addresses when the address space was only half-exhausted. Bugfix
7435 - Correctly handle the case where AutomapHostsOnResolve is set but
7436 no virtual addresses are available. Fixes bug 2328; bugfix on
7437 0.1.2.1-alpha. Bug found by doorss.
7438 - Correctly handle wrapping around to when we run out of virtual
7439 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
7440 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7441 because we built it with a too-old version of automake. Thus that
7442 release broke ./configure --enable-openbsd-malloc, which is popular
7443 among really fast exit relays on Linux.
7446 - Update to the January 1 2011 Maxmind GeoLite Country database.
7447 - Introduce output size checks on all of our decryption functions.
7450 - Tor does not build packages correctly with Automake 1.6 and earlier;
7451 added a check to Makefile.am to make sure that we're building with
7452 Automake 1.7 or later.
7455 Changes in version 0.2.2.20-alpha - 2010-12-17
7456 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
7457 exploitable bugs. We also fix a variety of other significant bugs,
7458 change the IP address for one of our directory authorities, and update
7459 the minimum version that Tor relays must run to join the network.
7462 - Fix a remotely exploitable bug that could be used to crash instances
7463 of Tor remotely by overflowing on the heap. Remote-code execution
7464 hasn't been confirmed, but can't be ruled out. Everyone should
7465 upgrade. Bugfix on the 0.1.1 series and later.
7466 - Fix a bug that could break accounting on 64-bit systems with large
7467 time_t values, making them hibernate for impossibly long intervals.
7468 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
7469 - Fix a logic error in directory_fetches_from_authorities() that
7470 would cause all _non_-exits refusing single-hop-like circuits
7471 to fetch from authorities, when we wanted to have _exits_ fetch
7472 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
7474 - Fix a stream fairness bug that would cause newer streams on a given
7475 circuit to get preference when reading bytes from the origin or
7476 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
7477 introduced before the first Tor release, in svn revision r152.
7479 o Directory authority changes:
7480 - Change IP address and ports for gabelmoo (v3 directory authority).
7483 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
7484 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
7485 - Fix an off-by-one error in calculating some controller command
7486 argument lengths. Fortunately, this mistake is harmless since
7487 the controller code does redundant NUL termination too. Found by
7488 boboper. Bugfix on 0.1.1.1-alpha.
7489 - Do not dereference NULL if a bridge fails to build its
7490 extra-info descriptor. Found by an anonymous commenter on
7491 Trac. Bugfix on 0.2.2.19-alpha.
7494 - Update to the December 1 2010 Maxmind GeoLite Country database.
7495 - Directory authorities now reject relays running any versions of
7496 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
7497 known bugs that keep RELAY_EARLY cells from working on rendezvous
7498 circuits. Followup to fix for bug 2081.
7499 - Directory authorities now reject relays running any version of Tor
7500 older than 0.2.0.26-rc. That version is the earliest that fetches
7501 current directory information correctly. Fixes bug 2156.
7502 - Report only the top 10 ports in exit-port stats in order not to
7503 exceed the maximum extra-info descriptor length of 50 KB. Implements
7507 Changes in version 0.2.1.28 - 2010-12-17
7508 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
7509 exploitable bugs. We also took this opportunity to change the IP address
7510 for one of our directory authorities, and to update the geoip database
7514 - Fix a remotely exploitable bug that could be used to crash instances
7515 of Tor remotely by overflowing on the heap. Remote-code execution
7516 hasn't been confirmed, but can't be ruled out. Everyone should
7517 upgrade. Bugfix on the 0.1.1 series and later.
7519 o Directory authority changes:
7520 - Change IP address and ports for gabelmoo (v3 directory authority).
7523 - Update to the December 1 2010 Maxmind GeoLite Country database.
7526 Changes in version 0.2.1.27 - 2010-11-23
7527 Yet another OpenSSL security patch broke its compatibility with Tor:
7528 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
7529 also took this opportunity to fix several crash bugs, integrate a new
7530 directory authority, and update the bundled GeoIP database.
7533 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7534 No longer set the tlsext_host_name extension on server SSL objects;
7535 but continue to set it on client SSL objects. Our goal in setting
7536 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7537 bugfix on 0.2.1.1-alpha.
7538 - Do not log messages to the controller while shrinking buffer
7539 freelists. Doing so would sometimes make the controller connection
7540 try to allocate a buffer chunk, which would mess up the internals
7541 of the freelist and cause an assertion failure. Fixes bug 1125;
7542 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7543 - Learn our external IP address when we're a relay or bridge, even if
7544 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7545 where we introduced bridge relays that don't need to publish to
7546 be useful. Fixes bug 2050.
7547 - Do even more to reject (and not just ignore) annotations on
7548 router descriptors received anywhere but from the cache. Previously
7549 we would ignore such annotations at first, but cache them to disk
7550 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7551 - When you're using bridges and your network goes away and your
7552 bridges get marked as down, recover when you attempt a new socks
7553 connection (if the network is back), rather than waiting up to an
7554 hour to try fetching new descriptors for your bridges. Bugfix on
7555 0.2.0.3-alpha; fixes bug 1981.
7558 - Move to the November 2010 Maxmind GeoLite country db (rather
7559 than the June 2009 ip-to-country GeoIP db) for our statistics that
7560 count how many users relays are seeing from each country. Now we'll
7561 have more accurate data, especially for many African countries.
7563 o New directory authorities:
7564 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7568 - Fix an assertion failure that could occur in directory caches or
7569 bridge users when using a very short voting interval on a testing
7570 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
7572 - Enforce multiplicity rules when parsing annotations. Bugfix on
7573 0.2.0.8-alpha. Found by piebeer.
7574 - Allow handshaking OR connections to take a full KeepalivePeriod
7575 seconds to handshake. Previously, we would close them after
7576 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7577 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7579 - When building with --enable-gcc-warnings on OpenBSD, disable
7580 warnings in system headers. This makes --enable-gcc-warnings
7581 pass on OpenBSD 4.8.
7584 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7585 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7586 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7587 Servers can start sending this code when enough clients recognize
7588 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
7589 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7590 Patch from mingw-san.
7593 - Remove the old debian/ directory from the main Tor distribution.
7594 The official Tor-for-debian git repository lives at the URL
7595 https://git.torproject.org/debian/tor.git
7596 - Stop shipping the old doc/website/ directory in the tarball. We
7597 changed the website format in late 2010, and what we shipped in
7598 0.2.1.26 really wasn't that useful anyway.
7601 Changes in version 0.2.2.19-alpha - 2010-11-22
7602 Yet another OpenSSL security patch broke its compatibility with Tor:
7603 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
7606 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7607 No longer set the tlsext_host_name extension on server SSL objects;
7608 but continue to set it on client SSL objects. Our goal in setting
7609 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7610 bugfix on 0.2.1.1-alpha.
7613 - Try harder not to exceed the maximum length of 50 KB when writing
7614 statistics to extra-info descriptors. This bug was triggered by very
7615 fast relays reporting exit-port, entry, and dirreq statistics.
7616 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
7617 - Publish a router descriptor even if generating an extra-info
7618 descriptor fails. Previously we would not publish a router
7619 descriptor without an extra-info descriptor; this can cause fast
7620 exit relays collecting exit-port statistics to drop from the
7621 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
7624 Changes in version 0.2.2.18-alpha - 2010-11-16
7625 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
7626 us lately, makes unpublished bridge relays able to detect their IP
7627 address, and fixes a wide variety of other bugs to get us much closer
7628 to a stable release.
7631 - Do even more to reject (and not just ignore) annotations on
7632 router descriptors received anywhere but from the cache. Previously
7633 we would ignore such annotations at first, but cache them to disk
7634 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7635 - Do not log messages to the controller while shrinking buffer
7636 freelists. Doing so would sometimes make the controller connection
7637 try to allocate a buffer chunk, which would mess up the internals
7638 of the freelist and cause an assertion failure. Fixes bug 1125;
7639 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7640 - Learn our external IP address when we're a relay or bridge, even if
7641 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7642 where we introduced bridge relays that don't need to publish to
7643 be useful. Fixes bug 2050.
7644 - Maintain separate TLS contexts and certificates for incoming and
7645 outgoing connections in bridge relays. Previously we would use the
7646 same TLS contexts and certs for incoming and outgoing connections.
7647 Bugfix on 0.2.0.3-alpha; addresses bug 988.
7648 - Maintain separate identity keys for incoming and outgoing TLS
7649 contexts in bridge relays. Previously we would use the same
7650 identity keys for incoming and outgoing TLS contexts. Bugfix on
7651 0.2.0.3-alpha; addresses the other half of bug 988.
7652 - Avoid an assertion failure when we as an authority receive a
7653 duplicate upload of a router descriptor that we already have,
7654 but which we previously considered an obsolete descriptor.
7655 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
7656 - Avoid a crash bug triggered by looking at a dangling pointer while
7657 setting the network status consensus. Found by Robert Ransom.
7658 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
7659 - Fix a logic error where servers that _didn't_ act as exits would
7660 try to keep their server lists more aggressively up to date than
7661 exits, when it was supposed to be the other way around. Bugfix
7664 o Minor bugfixes (on Tor 0.2.1.x and earlier):
7665 - When we're trying to guess whether we know our IP address as
7666 a relay, we would log various ways that we failed to guess
7667 our address, but never log that we ended up guessing it
7668 successfully. Now add a log line to help confused and anxious
7669 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
7670 - Bring the logic that gathers routerinfos and assesses the
7671 acceptability of circuits into line. This prevents a Tor OP from
7672 getting locked in a cycle of choosing its local OR as an exit for a
7673 path (due to a .exit request) and then rejecting the circuit because
7674 its OR is not listed yet. It also prevents Tor clients from using an
7675 OR running in the same instance as an exit (due to a .exit request)
7676 if the OR does not meet the same requirements expected of an OR
7677 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7678 - Correctly describe errors that occur when generating a TLS object.
7679 Previously we would attribute them to a failure while generating a
7680 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
7682 - Enforce multiplicity rules when parsing annotations. Bugfix on
7683 0.2.0.8-alpha. Found by piebeer.
7684 - Fix warnings that newer versions of autoconf produced during
7685 ./autogen.sh. These warnings appear to be harmless in our case,
7686 but they were extremely verbose. Fixes bug 2020.
7688 o Minor bugfixes (on Tor 0.2.2.x):
7689 - Enable protection of small arrays whenever we build with gcc
7690 hardening features, not only when also building with warnings
7691 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
7694 - Make hidden services work better in private Tor networks by not
7695 requiring any uptime to join the hidden service descriptor
7696 DHT. Implements ticket 2088.
7697 - Rate-limit the "your application is giving Tor only an IP address"
7698 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
7699 - When AllowSingleHopExits is set, print a warning to explain to the
7700 relay operator why most clients are avoiding her relay.
7701 - Update to the November 1 2010 Maxmind GeoLite Country database.
7703 o Code simplifications and refactoring:
7704 - When we fixed bug 1038 we had to put in a restriction not to send
7705 RELAY_EARLY cells on rend circuits. This was necessary as long
7706 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
7707 active. Now remove this obsolete check. Resolves bug 2081.
7708 - Some options used different conventions for uppercasing of acronyms
7709 when comparing manpage and source. Fix those in favor of the
7710 manpage, as it makes sense to capitalize acronyms.
7711 - Remove the torrc.complete file. It hasn't been kept up to date
7712 and users will have better luck checking out the manpage.
7713 - Remove the obsolete "NoPublish" option; it has been flagged
7714 as obsolete and has produced a warning since 0.1.1.18-rc.
7715 - Remove everything related to building the expert bundle for OS X.
7716 It has confused many users, doesn't work right on OS X 10.6,
7717 and is hard to get rid of once installed. Resolves bug 1274.
7720 Changes in version 0.2.2.17-alpha - 2010-09-30
7721 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
7722 to use one-hop circuits (which can put the exit relays at higher risk,
7723 plus unbalance the network); fixes a big bug in bandwidth accounting
7724 for relays that want to limit their monthly bandwidth use; fixes a
7725 big pile of bugs in how clients tolerate temporary network failure;
7726 and makes our adaptive circuit build timeout feature (which improves
7727 client performance if your network is fast while not breaking things
7728 if your network is slow) better handle bad networks.
7731 - Exit relays now try harder to block exit attempts from unknown
7732 relays, to make it harder for people to use them as one-hop proxies
7733 a la tortunnel. Controlled by the refuseunknownexits consensus
7734 parameter (currently enabled), or you can override it on your
7735 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
7737 o Major bugfixes (0.2.1.x and earlier):
7738 - Fix a bug in bandwidth accounting that could make us use twice
7739 the intended bandwidth when our interval start changes due to
7740 daylight saving time. Now we tolerate skew in stored vs computed
7741 interval starts: if the start of the period changes by no more than
7742 50% of the period's duration, we remember bytes that we transferred
7743 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
7744 - Always search the Windows system directory for system DLLs, and
7745 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
7746 - When you're using bridges and your network goes away and your
7747 bridges get marked as down, recover when you attempt a new socks
7748 connection (if the network is back), rather than waiting up to an
7749 hour to try fetching new descriptors for your bridges. Bugfix on
7750 0.2.0.3-alpha; fixes bug 1981.
7752 o Major bugfixes (on 0.2.2.x):
7753 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
7755 - Fix a segfault that could happen when operating a bridge relay with
7756 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
7757 - The consensus bandwidth-weights (used by clients to choose fast
7758 relays) entered an unexpected edge case in September where
7759 Exits were much scarcer than Guards, resulting in bad weight
7760 recommendations. Now we compute them using new constraints that
7761 should succeed in all cases. Also alter directory authorities to
7762 not include the bandwidth-weights line if they fail to produce
7763 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
7764 - When weighting bridges during path selection, we used to trust
7765 the bandwidths they provided in their descriptor, only capping them
7766 at 10MB/s. This turned out to be problematic for two reasons:
7767 Bridges could claim to handle a lot more traffic then they
7768 actually would, thus making more clients pick them and have a
7769 pretty effective DoS attack. The other issue is that new bridges
7770 that might not have a good estimate for their bw capacity yet
7771 would not get used at all unless no other bridges are available
7772 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
7774 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
7775 - Ignore cannibalized circuits when recording circuit build times.
7776 This should provide for a minor performance improvement for hidden
7777 service users using 0.2.2.14-alpha, and should remove two spurious
7778 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
7779 - Simplify the logic that causes us to decide if the network is
7780 unavailable for purposes of recording circuit build times. If we
7781 receive no cells whatsoever for the entire duration of a circuit's
7782 full measured lifetime, the network is probably down. Also ignore
7783 one-hop directory fetching circuit timeouts when calculating our
7784 circuit build times. These changes should hopefully reduce the
7785 cases where we see ridiculous circuit build timeouts for people
7786 with spotty wireless connections. Fixes part of bug 1772; bugfix
7788 - Prevent the circuit build timeout from becoming larger than
7789 the maximum build time we have ever seen. Also, prevent the time
7790 period for measurement circuits from becoming larger than twice that
7791 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
7794 - When we run out of directory information such that we can't build
7795 circuits, but then get enough that we can build circuits, log when
7796 we actually construct a circuit, so the user has a better chance of
7797 knowing what's going on. Fixes bug 1362.
7798 - Be more generous with how much bandwidth we'd use up (with
7799 accounting enabled) before entering "soft hibernation". Previously,
7800 we'd refuse new connections and circuits once we'd used up 95% of
7801 our allotment. Now, we use up 95% of our allotment, AND make sure
7802 that we have no more than 500MB (or 3 hours of expected traffic,
7803 whichever is lower) remaining before we enter soft hibernation.
7804 - If we've configured EntryNodes and our network goes away and/or all
7805 our entrynodes get marked down, optimistically retry them all when
7806 a new socks application request appears. Fixes bug 1882.
7807 - Add some more defensive programming for architectures that can't
7808 handle unaligned integer accesses. We don't know of any actual bugs
7809 right now, but that's the best time to fix them. Fixes bug 1943.
7810 - Support line continuations in the torrc config file. If a line
7811 ends with a single backslash character, the newline is ignored, and
7812 the configuration value is treated as continuing on the next line.
7815 o Minor bugfixes (on 0.2.1.x and earlier):
7816 - For bandwidth accounting, calculate our expected bandwidth rate
7817 based on the time during which we were active and not in
7818 soft-hibernation during the last interval. Previously, we were
7819 also considering the time spent in soft-hibernation. If this
7820 was a long time, we would wind up underestimating our bandwidth
7821 by a lot, and skewing our wakeup time towards the start of the
7822 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
7824 o Minor bugfixes (on 0.2.2.x):
7825 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
7826 which were disabled by the circuit build timeout changes in
7827 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
7828 - Make sure we don't warn about missing bandwidth weights when
7829 choosing bridges or other relays not in the consensus. Bugfix on
7830 0.2.2.10-alpha; fixes bug 1805.
7831 - In our logs, do not double-report signatures from unrecognized
7832 authorities both as "from unknown authority" and "not
7833 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
7836 Changes in version 0.2.2.16-alpha - 2010-09-17
7837 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
7838 evident at exit relays), and also continues to resolve all the little
7839 bugs that have been filling up trac lately.
7841 o Major bugfixes (stream-level fairness):
7842 - When receiving a circuit-level SENDME for a blocked circuit, try
7843 to package cells fairly from all the streams that had previously
7844 been blocked on that circuit. Previously, we had started with the
7845 oldest stream, and allowed each stream to potentially exhaust
7846 the circuit's package window. This gave older streams on any
7847 given circuit priority over newer ones. Fixes bug 1937. Detected
7848 originally by Camilo Viecco. This bug was introduced before the
7849 first Tor release, in svn commit r152: it is the new winner of
7850 the longest-lived bug prize.
7851 - When the exit relay got a circuit-level sendme cell, it started
7852 reading on the exit streams, even if had 500 cells queued in the
7853 circuit queue already, so the circuit queue just grew and grew in
7854 some cases. We fix this by not re-enabling reading on receipt of a
7855 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
7856 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
7858 - Newly created streams were allowed to read cells onto circuits,
7859 even if the circuit's cell queue was blocked and waiting to drain.
7860 This created potential unfairness, as older streams would be
7861 blocked, but newer streams would gladly fill the queue completely.
7862 We add code to detect this situation and prevent any stream from
7863 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
7867 - Update to the September 1 2010 Maxmind GeoLite Country database.
7868 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
7869 not. This would lead to a cookie that is still not group readable.
7870 Closes bug 1843. Suggested by katmagic.
7871 - When logging a rate-limited warning, we now mention how many messages
7872 got suppressed since the last warning.
7873 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
7874 do individual connection-level rate limiting of clients. The torrc
7875 config options with the same names trump the consensus params, if
7876 both are present. Replaces the old "bwconnrate" and "bwconnburst"
7877 consensus params which were broken from 0.2.2.7-alpha through
7878 0.2.2.14-alpha. Closes bug 1947.
7879 - When a router changes IP address or port, authorities now launch
7880 a new reachability test for it. Implements ticket 1899.
7881 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
7882 2 no signature, 4 required" messages about consensus signatures
7883 easier to read, and make sure they get logged at the same severity
7884 as the messages explaining which keys are which. Fixes bug 1290.
7885 - Don't warn when we have a consensus that we can't verify because
7886 of missing certificates, unless those certificates are ones
7887 that we have been trying and failing to download. Fixes bug 1145.
7888 - If you configure your bridge with a known identity fingerprint,
7889 and the bridge authority is unreachable (as it is in at least
7890 one country now), fall back to directly requesting the descriptor
7891 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
7893 - When building with --enable-gcc-warnings on OpenBSD, disable
7894 warnings in system headers. This makes --enable-gcc-warnings
7895 pass on OpenBSD 4.8.
7897 o Minor bugfixes (on 0.2.1.x and earlier):
7898 - Authorities will now attempt to download consensuses if their
7899 own efforts to make a live consensus have failed. This change
7900 means authorities that restart will fetch a valid consensus, and
7901 it means authorities that didn't agree with the current consensus
7902 will still fetch and serve it if it has enough signatures. Bugfix
7903 on 0.2.0.9-alpha; fixes bug 1300.
7904 - Ensure DNS requests launched by "RESOLVE" commands from the
7905 controller respect the __LeaveStreamsUnattached setconf options. The
7906 same goes for requests launched via DNSPort or transparent
7907 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
7908 - Allow handshaking OR connections to take a full KeepalivePeriod
7909 seconds to handshake. Previously, we would close them after
7910 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7911 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7913 - Rate-limit "Failed to hand off onionskin" warnings.
7914 - Never relay a cell for a circuit we have already destroyed.
7915 Between marking a circuit as closeable and finally closing it,
7916 it may have been possible for a few queued cells to get relayed,
7917 even though they would have been immediately dropped by the next
7918 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
7919 - Never queue a cell for a circuit that's already been marked
7921 - Never vote for a server as "Running" if we have a descriptor for
7922 it claiming to be hibernating, and that descriptor was published
7923 more recently than our last contact with the server. Bugfix on
7924 0.2.0.3-alpha; fixes bug 911.
7925 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
7928 o Minor bugfixes (on 0.2.2.x):
7929 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
7930 down if a directory fetch fails and you've configured either
7931 bridges or EntryNodes. The intent was to mark the relay as down
7932 _unless_ you're using bridges or EntryNodes, since if you are
7933 then you could quickly run out of entry points.
7934 - Fix the Windows directory-listing code. A bug introduced in
7935 0.2.2.14-alpha could make Windows directory servers forget to load
7936 some of their cached v2 networkstatus files.
7937 - Really allow clients to use relays as bridges. Fixes bug 1776;
7938 bugfix on 0.2.2.15-alpha.
7939 - Demote a warn to info that happens when the CellStatistics option
7940 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
7941 Reported by Moritz Bartl.
7942 - On Windows, build correctly either with or without Unicode support.
7943 This is necessary so that Tor can support fringe platforms like
7944 Windows 98 (which has no Unicode), or Windows CE (which has no
7945 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
7948 - Add a unit test for cross-platform directory-listing code.
7951 Changes in version 0.2.2.15-alpha - 2010-08-18
7952 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
7953 fixes a variety of other bugs that were preventing performance
7954 experiments from moving forward, fixes several bothersome memory leaks,
7955 and generally closes a lot of smaller bugs that have been filling up
7959 - Stop assigning the HSDir flag to relays that disable their
7960 DirPort (and thus will refuse to answer directory requests). This
7961 fix should dramatically improve the reachability of hidden services:
7962 hidden services and hidden service clients pick six HSDir relays
7963 to store and retrieve the hidden service descriptor, and currently
7964 about half of the HSDir relays will refuse to work. Bugfix on
7965 0.2.0.10-alpha; fixes part of bug 1693.
7966 - The PerConnBWRate and Burst config options, along with the
7967 bwconnrate and bwconnburst consensus params, initialized each conn's
7968 token bucket values only when the connection is established. Now we
7969 update them if the config options change, and update them every time
7970 we get a new consensus. Otherwise we can encounter an ugly edge
7971 case where we initialize an OR conn to client-level bandwidth,
7972 but then later the relay joins the consensus and we leave it
7973 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
7974 - Fix a regression that caused Tor to rebind its ports if it receives
7975 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
7978 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
7979 should give us approximately 40-50% more Guard-flagged nodes,
7980 improving the anonymity the Tor network can provide and also
7981 decreasing the dropoff in throughput that relays experience when
7982 they first get the Guard flag.
7983 - Allow enabling or disabling the *Statistics config options while
7987 - Update to the August 1 2010 Maxmind GeoLite Country database.
7988 - Have the controller interface give a more useful message than
7989 "Internal Error" in response to failed GETINFO requests.
7990 - Warn when the same option is provided more than once in a torrc
7991 file, on the command line, or in a single SETCONF statement, and
7992 the option is one that only accepts a single line. Closes bug 1384.
7993 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7994 Patch from mingw-san.
7995 - Add support for the country code "{??}" in torrc options like
7996 ExcludeNodes, to indicate all routers of unknown country. Closes
7998 - Relays report the number of bytes spent on answering directory
7999 requests in extra-info descriptors similar to {read,write}-history.
8000 Implements enhancement 1790.
8002 o Minor bugfixes (on 0.2.1.x and earlier):
8003 - Complain if PublishServerDescriptor is given multiple arguments that
8004 include 0 or 1. This configuration will be rejected in the future.
8005 Bugfix on 0.2.0.1-alpha; closes bug 1107.
8006 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
8007 Bugfix on 0.2.0.13-alpha; closes bug 928.
8008 - Change "Application request when we're believed to be offline."
8009 notice to "Application request when we haven't used client
8010 functionality lately.", to clarify that it's not an error. Bugfix
8011 on 0.0.9.3; fixes bug 1222.
8012 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
8013 would return "551 Internal error" rather than "552 Unrecognized key
8014 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
8015 - Users can't configure a regular relay to be their bridge. It didn't
8016 work because when Tor fetched the bridge descriptor, it found
8017 that it already had it, and didn't realize that the purpose of the
8018 descriptor had changed. Now we replace routers with a purpose other
8019 than bridge with bridge descriptors when fetching them. Bugfix on
8020 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
8021 refetch the descriptor with router purpose 'general', disabling
8023 - Fix a rare bug in rend_fn unit tests: we would fail a test when
8024 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
8025 on 0.2.0.10-alpha; fixes bug 1808.
8026 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8027 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8028 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8029 Servers can start sending this code when enough clients recognize
8030 it. Also update the spec to reflect this new reason. Bugfix on
8031 0.1.0.1-rc; fixes part of bug 1793.
8032 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
8033 when we switch from being a public relay to a bridge. Otherwise
8034 there will still be clients that see the relay in their consensus,
8035 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
8037 - Instead of giving an assertion failure on an internal mismatch
8038 on estimated freelist size, just log a BUG warning and try later.
8039 Mitigates but does not fix bug 1125.
8040 - Fix an assertion failure that could occur in caches or bridge users
8041 when using a very short voting interval on a testing network.
8042 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
8044 o Minor bugfixes (on 0.2.2.x):
8045 - Alter directory authorities to always consider Exit-flagged nodes
8046 as potential Guard nodes in their votes. The actual decision to
8047 use Exits as Guards is done in the consensus bandwidth weights.
8048 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
8049 - When the controller is reporting the purpose of circuits that
8050 didn't finish building before the circuit build timeout, it was
8051 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
8052 - Our libevent version parsing code couldn't handle versions like
8053 1.4.14b-stable and incorrectly warned the user about using an
8054 old and broken version of libevent. Treat 1.4.14b-stable like
8055 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
8057 - Don't use substitution references like $(VAR:MOD) when
8058 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
8059 '$(:x)' to 'x' rather than the empty string. This bites us in
8060 doc/ when configured with --disable-asciidoc. Bugfix on
8061 0.2.2.9-alpha; fixes bug 1773.
8062 - Remove a spurious hidden service server-side log notice about
8063 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
8065 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
8067 - Correctly report written bytes on linked connections. Found while
8068 implementing 1790. Bugfix on 0.2.2.4-alpha.
8069 - Fix three memory leaks: one in circuit_build_times_parse_state(),
8070 one in dirvote_add_signatures_to_pending_consensus(), and one every
8071 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
8072 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
8074 o Code simplifications and refactoring:
8075 - Take a first step towards making or.h smaller by splitting out
8076 function definitions for all source files in src/or/. Leave
8077 structures and defines in or.h for now.
8078 - Remove a bunch of unused function declarations as well as a block of
8079 #if 0'd code from the unit tests. Closes bug 1824.
8080 - New unit tests for exit-port history statistics; refactored exit
8081 statistics code to be more easily tested.
8082 - Remove the old debian/ directory from the main Tor distribution.
8083 The official Tor-for-debian git repository lives at the URL
8084 https://git.torproject.org/debian/tor.git
8087 Changes in version 0.2.2.14-alpha - 2010-07-12
8088 Tor 0.2.2.14-alpha greatly improves client-side handling of
8089 circuit build timeouts, which are used to estimate speed and improve
8090 performance. We also move to a much better GeoIP database, port Tor to
8091 Windows CE, introduce new compile flags that improve code security,
8092 add an eighth v3 directory authority, and address a lot of more
8096 - Tor directory authorities no longer crash when started with a
8097 cached-microdesc-consensus file in their data directory. Bugfix
8098 on 0.2.2.6-alpha; fixes bug 1532.
8099 - Treat an unset $HOME like an empty $HOME rather than triggering an
8100 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
8101 - Ignore negative and large circuit build timeout values that can
8102 happen during a suspend or hibernate. These values caused various
8103 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
8104 - Alter calculation of Pareto distribution parameter 'Xm' for
8105 Circuit Build Timeout learning to use the weighted average of the
8106 top N=3 modes (because we have three entry guards). Considering
8107 multiple modes should improve the timeout calculation in some cases,
8108 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
8110 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
8111 right censored distribution model. This approach improves over the
8112 synthetic timeout generation approach that was producing insanely
8113 high timeout values. Now we calculate build timeouts using truncated
8114 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
8115 - Do not close circuits that are under construction when they reach
8116 the circuit build timeout. Instead, leave them building (but do not
8117 use them) for up until the time corresponding to the 95th percentile
8118 on the Pareto CDF or 60 seconds, whichever is greater. This is done
8119 to provide better data for the new Pareto model. This percentile
8120 can be controlled by the consensus.
8123 - Move to the June 2010 Maxmind GeoLite country db (rather than the
8124 June 2009 ip-to-country GeoIP db) for our statistics that count
8125 how many users relays are seeing from each country. Now we have
8126 more accurate data for many African countries.
8127 - Port Tor to build and run correctly on Windows CE systems, using
8128 the wcecompat library. Contributed by Valerio Lupi.
8129 - New "--enable-gcc-hardening" ./configure flag (off by default)
8130 to turn on gcc compile time hardening options. It ensures
8131 that signed ints have defined behavior (-fwrapv), enables
8132 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
8133 with canaries (-fstack-protector-all), turns on ASLR protection if
8134 supported by the kernel (-fPIE, -pie), and adds additional security
8135 related warnings. Verified to work on Mac OS X and Debian Lenny.
8136 - New "--enable-linker-hardening" ./configure flag (off by default)
8137 to turn on ELF specific hardening features (relro, now). This does
8138 not work with Mac OS X or any other non-ELF binary format.
8140 o New directory authorities:
8141 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8145 - New config option "WarnUnsafeSocks 0" disables the warning that
8146 occurs whenever Tor receives a socks handshake using a version of
8147 the socks protocol that can only provide an IP address (rather
8148 than a hostname). Setups that do DNS locally over Tor are fine,
8149 and we shouldn't spam the logs in that case.
8150 - Convert the HACKING file to asciidoc, and add a few new sections
8151 to it, explaining how we use Git, how we make changelogs, and
8152 what should go in a patch.
8153 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
8154 event, to give information on the current rate of circuit timeouts
8155 over our stored history.
8156 - Add ability to disable circuit build time learning via consensus
8157 parameter and via a LearnCircuitBuildTimeout config option. Also
8158 automatically disable circuit build time calculation if we are
8159 either a AuthoritativeDirectory, or if we fail to write our state
8160 file. Fixes bug 1296.
8161 - More gracefully handle corrupt state files, removing asserts
8162 in favor of saving a backup and resetting state.
8163 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
8167 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8169 - When a2x fails, mention that the user could disable manpages instead
8170 of trying to fix their asciidoc installation.
8171 - Where available, use Libevent 2.0's periodic timers so that our
8172 once-per-second cleanup code gets called even more closely to
8173 once per second than it would otherwise. Fixes bug 943.
8174 - If you run a bridge that listens on multiple IP addresses, and
8175 some user configures a bridge address that uses a different IP
8176 address than your bridge writes in its router descriptor, and the
8177 user doesn't specify an identity key, their Tor would discard the
8178 descriptor because "it isn't one of our configured bridges", and
8179 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
8180 Bugfix on 0.2.0.3-alpha.
8181 - If OpenSSL fails to make a duplicate of a private or public key, log
8182 an error message and try to exit cleanly. May help with debugging
8183 if bug 1209 ever remanifests.
8184 - Save a couple bytes in memory allocation every time we escape
8185 certain characters in a string. Patch from Florian Zumbiehl.
8186 - Make it explicit that we don't cannibalize one-hop circuits. This
8187 happens in the wild, but doesn't turn out to be a problem because
8188 we fortunately don't use those circuits. Many thanks to outofwords
8189 for the initial analysis and to swissknife who confirmed that
8190 two-hop circuits are actually created.
8191 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
8192 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
8193 - Eliminate a case where a circuit build time warning was displayed
8194 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
8197 Changes in version 0.2.1.26 - 2010-05-02
8198 Tor 0.2.1.26 addresses the recent connection and memory overload
8199 problems we've been seeing on relays, especially relays with their
8200 DirPort open. If your relay has been crashing, or you turned it off
8201 because it used too many resources, give this release a try.
8203 This release also fixes yet another instance of broken OpenSSL libraries
8204 that was causing some relays to drop out of the consensus.
8207 - Teach relays to defend themselves from connection overload. Relays
8208 now close idle circuits early if it looks like they were intended
8209 for directory fetches. Relays are also more aggressive about closing
8210 TLS connections that have no circuits on them. Such circuits are
8211 unlikely to be re-used, and tens of thousands of them were piling
8212 up at the fast relays, causing the relays to run out of sockets
8213 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8214 their directory fetches over TLS).
8215 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8216 that claim to be earlier than 0.9.8m, but which have in reality
8217 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8218 behavior. Possible fix for some cases of bug 1346.
8219 - Directory mirrors were fetching relay descriptors only from v2
8220 directory authorities, rather than v3 authorities like they should.
8221 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8222 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8225 - Finally get rid of the deprecated and now harmful notion of "clique
8226 mode", where directory authorities maintain TLS connections to
8230 - In the util/threads test, no longer free the test_mutex before all
8231 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8232 - The master thread could starve the worker threads quite badly on
8233 certain systems, causing them to run only partially in the allowed
8234 window. This resulted in test failures. Now the master thread sleeps
8235 occasionally for a few microseconds while the two worker-threads
8236 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8239 Changes in version 0.2.2.13-alpha - 2010-04-24
8240 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
8241 problems we've been seeing on relays, especially relays with their
8242 DirPort open. If your relay has been crashing, or you turned it off
8243 because it used too many resources, give this release a try.
8246 - Teach relays to defend themselves from connection overload. Relays
8247 now close idle circuits early if it looks like they were intended
8248 for directory fetches. Relays are also more aggressive about closing
8249 TLS connections that have no circuits on them. Such circuits are
8250 unlikely to be re-used, and tens of thousands of them were piling
8251 up at the fast relays, causing the relays to run out of sockets
8252 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8253 their directory fetches over TLS).
8256 - Finally get rid of the deprecated and now harmful notion of "clique
8257 mode", where directory authorities maintain TLS connections to
8259 - Directory authorities now do an immediate reachability check as soon
8260 as they hear about a new relay. This change should slightly reduce
8261 the time between setting up a relay and getting listed as running
8262 in the consensus. It should also improve the time between setting
8263 up a bridge and seeing use by bridge users.
8264 - Directory authorities no longer launch a TLS connection to every
8265 relay as they startup. Now that we have 2k+ descriptors cached,
8266 the resulting network hiccup is becoming a burden. Besides,
8267 authorities already avoid voting about Running for the first half
8268 hour of their uptime.
8271 Changes in version 0.2.2.12-alpha - 2010-04-20
8272 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
8273 handle and vote on descriptors. It was causing relays to drop out of
8277 - Many relays have been falling out of the consensus lately because
8278 not enough authorities know about their descriptor for them to get
8279 a majority of votes. When we deprecated the v2 directory protocol,
8280 we got rid of the only way that v3 authorities can hear from each
8281 other about other descriptors. Now authorities examine every v3
8282 vote for new descriptors, and fetch them from that authority. Bugfix
8284 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
8285 and a warning in or.h related to bandwidth_weight_rule_t that
8286 prevented clean compile on OS X. Fixes bug 1363; bugfix on
8288 - Fix a segfault on relays when DirReqStatistics is enabled
8289 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
8293 - Demote a confusing TLS warning that relay operators might get when
8294 someone tries to talk to their OrPort. It is neither the operator's
8295 fault nor can they do anything about it. Fixes bug 1364; bugfix
8299 Changes in version 0.2.2.11-alpha - 2010-04-15
8300 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
8301 libraries that was causing some relays to drop out of the consensus.
8304 - Directory mirrors were fetching relay descriptors only from v2
8305 directory authorities, rather than v3 authorities like they should.
8306 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8307 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8308 - Fix a parsing error that made every possible value of
8309 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
8310 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
8311 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
8312 about the option without breaking older ones.
8313 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8314 that claim to be earlier than 0.9.8m, but which have in reality
8315 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8316 behavior. Possible fix for some cases of bug 1346.
8319 - Experiment with a more aggressive approach to preventing clients
8320 from making one-hop exit streams. Exit relays who want to try it
8321 out can set "RefuseUnknownExits 1" in their torrc, and then look
8322 for "Attempt by %s to open a stream" log messages. Let us know
8324 - Add support for statically linking zlib by specifying
8325 --enable-static-zlib, to go with our support for statically linking
8326 openssl and libevent. Resolves bug 1358.
8329 - Fix a segfault that happens whenever a Tor client that is using
8330 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
8332 - When we cleaned up the contrib/tor-exit-notice.html file, we left
8333 out the first line. Fixes bug 1295.
8334 - When building the manpage from a tarball, we required asciidoc, but
8335 the asciidoc -> roff/html conversion was already done for the
8336 tarball. Make 'make' complain only when we need asciidoc (either
8337 because we're compiling directly from git, or because we altered
8338 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
8339 - When none of the directory authorities vote on any params, Tor
8340 segfaulted when trying to make the consensus from the votes. We
8341 didn't trigger the bug in practice, because authorities do include
8342 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
8345 - In the util/threads test, no longer free the test_mutex before all
8346 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8347 - The master thread could starve the worker threads quite badly on
8348 certain systems, causing them to run only partially in the allowed
8349 window. This resulted in test failures. Now the master thread sleeps
8350 occasionally for a few microseconds while the two worker-threads
8351 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8354 Changes in version 0.2.2.10-alpha - 2010-03-07
8355 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
8356 could prevent relays from guessing their IP address correctly. It also
8357 starts the groundwork for another client-side performance boost, since
8358 currently we're not making efficient use of relays that have both the
8359 Guard flag and the Exit flag.
8362 - Fix a regression from our patch for bug 1244 that caused relays
8363 to guess their IP address incorrectly if they didn't set Address
8364 in their torrc and/or their address fails to resolve. Bugfix on
8365 0.2.2.9-alpha; fixes bug 1269.
8367 o Major features (performance):
8368 - Directory authorities now compute consensus weightings that instruct
8369 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
8370 and no flag. Clients that use these weightings will distribute
8371 network load more evenly across these different relay types. The
8372 weightings are in the consensus so we can change them globally in
8373 the future. Extra thanks to "outofwords" for finding some nasty
8374 security bugs in the first implementation of this feature.
8376 o Minor features (performance):
8377 - Always perform router selections using weighted relay bandwidth,
8378 even if we don't need a high capacity circuit at the time. Non-fast
8379 circuits now only differ from fast ones in that they can use relays
8380 not marked with the Fast flag. This "feature" could turn out to
8381 be a horrible bug; we should investigate more before it goes into
8385 - Allow disabling building of the manpages. Skipping the manpage
8386 speeds up the build considerably.
8388 o Minor bugfixes (on 0.2.2.x):
8389 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
8390 Bugfix on 0.2.2.9-alpha.
8391 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
8392 config option. Bugfix on 0.2.2.7-alpha.
8393 - Ship the asciidoc-helper file in the tarball, so that people can
8394 build from source if they want to, and touching the .1.txt files
8395 doesn't break the build. Bugfix on 0.2.2.9-alpha.
8397 o Minor bugfixes (on 0.2.1.x or earlier):
8398 - Fix a dereference-then-NULL-check sequence when publishing
8399 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8401 - Fix another dereference-then-NULL-check sequence. Bugfix on
8402 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8403 - Make sure we treat potentially not NUL-terminated strings correctly.
8404 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8406 o Code simplifications and refactoring:
8407 - Fix some urls in the exit notice file and make it XHTML1.1 strict
8408 compliant. Based on a patch from Christian Kujau.
8409 - Don't use sed in asciidoc-helper anymore.
8410 - Make the build process fail if asciidoc cannot be found and
8411 building with asciidoc isn't disabled.
8414 Changes in version 0.2.2.9-alpha - 2010-02-22
8415 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
8416 location of a directory authority, and cleans up a bunch of small bugs.
8418 o Directory authority changes:
8419 - Change IP address for dannenberg (v3 directory authority), and
8420 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
8421 service directory authority) from the list.
8424 - Make Tor work again on the latest OS X: when deciding whether to
8425 use strange flags to turn TLS renegotiation on, detect the OpenSSL
8426 version at run-time, not compile time. We need to do this because
8427 Apple doesn't update its dev-tools headers when it updates its
8428 libraries in a security patch.
8429 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
8430 that could happen on 32-bit platforms with 64-bit time_t. Also fix
8431 a memory leak when requesting a hidden service descriptor we've
8432 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
8434 - Authorities could be tricked into giving out the Exit flag to relays
8435 that didn't allow exiting to any ports. This bug could screw
8436 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
8437 1238. Bug discovered by Martin Kowalczyk.
8438 - When freeing a session key, zero it out completely. We only zeroed
8439 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8440 patched by ekir. Fixes bug 1254.
8443 - Fix static compilation by listing the openssl libraries in the right
8444 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
8445 - Resume handling .exit hostnames in a special way: originally we
8446 stripped the .exit part and used the requested exit relay. In
8447 0.2.2.1-alpha we stopped treating them in any special way, meaning
8448 if you use a .exit address then Tor will pass it on to the exit
8449 relay. Now we reject the .exit stream outright, since that behavior
8450 might be more expected by the user. Found and diagnosed by Scott
8451 Bennett and Downie on or-talk.
8452 - Don't spam the controller with events when we have no file
8453 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
8454 for log messages was already solved from bug 748.)
8455 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
8457 - Make the DNSPort option work with libevent 2.x. Don't alter the
8458 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
8459 - Emit a GUARD DROPPED controller event for a case we missed.
8460 - Make more fields in the controller protocol case-insensitive, since
8461 control-spec.txt said they were.
8462 - Refactor resolve_my_address() to not use gethostbyname() anymore.
8463 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
8464 - Fix a spec conformance issue: the network-status-version token
8465 must be the first token in a v3 consensus or vote. Discovered by
8466 parakeep. Bugfix on 0.2.0.3-alpha.
8468 o Code simplifications and refactoring:
8469 - Generate our manpage and HTML documentation using Asciidoc. This
8470 change should make it easier to maintain the documentation, and
8472 - Remove the --enable-iphone option. According to reports from Marco
8473 Bonetti, Tor builds fine without any special tweaking on recent
8474 iPhone SDK versions.
8475 - Removed some unnecessary files from the source distribution. The
8476 AUTHORS file has now been merged into the people page on the
8477 website. The roadmaps and design doc can now be found in the
8478 projects directory in svn.
8479 - Enabled various circuit build timeout constants to be controlled
8480 by consensus parameters. Also set better defaults for these
8481 parameters based on experimentation on broadband and simulated
8485 - The 'EXTENDCIRCUIT' control port command can now be used with
8486 a circ id of 0 and no path. This feature will cause Tor to build
8487 a new 'fast' general purpose circuit using its own path selection
8489 - Added a BUILDTIMEOUT_SET controller event to describe changes
8490 to the circuit build timeout.
8491 - Future-proof the controller protocol a bit by ignoring keyword
8492 arguments we do not recognize.
8493 - Expand homedirs passed to tor-checkkey. This should silence a
8494 coverity complaint about passing a user-supplied string into
8495 open() without checking it.
8498 Changes in version 0.2.1.25 - 2010-03-16
8499 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
8500 prevent relays from guessing their IP address correctly. It also fixes
8501 several minor potential security bugs.
8504 - Fix a regression from our patch for bug 1244 that caused relays
8505 to guess their IP address incorrectly if they didn't set Address
8506 in their torrc and/or their address fails to resolve. Bugfix on
8507 0.2.1.23; fixes bug 1269.
8508 - When freeing a session key, zero it out completely. We only zeroed
8509 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8510 patched by ekir. Fixes bug 1254.
8513 - Fix a dereference-then-NULL-check sequence when publishing
8514 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8516 - Fix another dereference-then-NULL-check sequence. Bugfix on
8517 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8518 - Make sure we treat potentially not NUL-terminated strings correctly.
8519 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8523 Changes in version 0.2.1.24 - 2010-02-21
8524 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
8528 - Work correctly out-of-the-box with even more vendor-patched versions
8529 of OpenSSL. In particular, make it so Debian and OS X don't need
8530 customized patches to run/build.
8533 Changes in version 0.2.1.23 - 2010-02-13
8534 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
8535 again on the latest OS X, and updates the location of a directory
8538 o Major bugfixes (performance):
8539 - We were selecting our guards uniformly at random, and then weighting
8540 which of our guards we'd use uniformly at random. This imbalance
8541 meant that Tor clients were severely limited on throughput (and
8542 probably latency too) by the first hop in their circuit. Now we
8543 select guards weighted by currently advertised bandwidth. We also
8544 automatically discard guards picked using the old algorithm. Fixes
8545 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
8548 - Make Tor work again on the latest OS X: when deciding whether to
8549 use strange flags to turn TLS renegotiation on, detect the OpenSSL
8550 version at run-time, not compile time. We need to do this because
8551 Apple doesn't update its dev-tools headers when it updates its
8552 libraries in a security patch.
8553 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
8554 that could happen on 32-bit platforms with 64-bit time_t. Also fix
8555 a memory leak when requesting a hidden service descriptor we've
8556 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
8559 o Directory authority changes:
8560 - Change IP address for dannenberg (v3 directory authority), and
8561 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
8562 service directory authority) from the list.
8565 - Refactor resolve_my_address() to not use gethostbyname() anymore.
8566 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
8569 - Avoid a mad rush at the beginning of each month when each client
8570 rotates half of its guards. Instead we spread the rotation out
8571 throughout the month, but we still avoid leaving a precise timestamp
8572 in the state file about when we first picked the guard. Improves
8573 over the behavior introduced in 0.1.2.17.
8576 Changes in version 0.2.2.8-alpha - 2010-01-26
8577 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
8578 causing bridge relays to disappear. If you're running a bridge,
8582 - Fix a memory corruption bug on bridges that occured during the
8583 inclusion of stats data in extra-info descriptors. Also fix the
8584 interface for geoip_get_bridge_stats* to prevent similar bugs in
8585 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
8586 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
8589 - Ignore OutboundBindAddress when connecting to localhost.
8590 Connections to localhost need to come _from_ localhost, or else
8591 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
8595 Changes in version 0.2.2.7-alpha - 2010-01-19
8596 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
8597 as laying the groundwork for further relay-side performance fixes. It
8598 also starts cleaning up client behavior with respect to the EntryNodes,
8599 ExitNodes, and StrictNodes config options.
8601 This release also rotates two directory authority keys, due to a
8602 security breach of some of the Torproject servers.
8604 o Directory authority changes:
8605 - Rotate keys (both v3 identity and relay identity) for moria1
8608 o Major features (performance):
8609 - We were selecting our guards uniformly at random, and then weighting
8610 which of our guards we'd use uniformly at random. This imbalance
8611 meant that Tor clients were severely limited on throughput (and
8612 probably latency too) by the first hop in their circuit. Now we
8613 select guards weighted by currently advertised bandwidth. We also
8614 automatically discard guards picked using the old algorithm. Fixes
8615 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
8616 - When choosing which cells to relay first, relays can now favor
8617 circuits that have been quiet recently, to provide lower latency
8618 for low-volume circuits. By default, relays enable or disable this
8619 feature based on a setting in the consensus. You can override
8620 this default by using the new "CircuitPriorityHalflife" config
8621 option. Design and code by Ian Goldberg, Can Tang, and Chris
8623 - Add separate per-conn write limiting to go with the per-conn read
8624 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
8625 but never per-conn write limits.
8626 - New consensus params "bwconnrate" and "bwconnburst" to let us
8627 rate-limit client connections as they enter the network. It's
8628 controlled in the consensus so we can turn it on and off for
8629 experiments. It's starting out off. Based on proposal 163.
8631 o Major features (relay selection options):
8632 - Switch to a StrictNodes config option, rather than the previous
8633 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
8634 "StrictExcludeNodes" option.
8635 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
8636 change during a config reload, mark and discard all our origin
8637 circuits. This fix should address edge cases where we change the
8638 config options and but then choose a circuit that we created before
8640 - If EntryNodes or ExitNodes are set, be more willing to use an
8641 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
8643 - Make EntryNodes config option much more aggressive even when
8644 StrictNodes is not set. Before it would prepend your requested
8645 entrynodes to your list of guard nodes, but feel free to use others
8646 after that. Now it chooses only from your EntryNodes if any of
8647 those are available, and only falls back to others if a) they're
8648 all down and b) StrictNodes is not set.
8649 - Now we refresh your entry guards from EntryNodes at each consensus
8650 fetch -- rather than just at startup and then they slowly rot as
8651 the network changes.
8654 - Stop bridge directory authorities from answering dbg-stability.txt
8655 directory queries, which would let people fetch a list of all
8656 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8659 - Log a notice when we get a new control connection. Now it's easier
8660 for security-conscious users to recognize when a local application
8661 is knocking on their controller door. Suggested by bug 1196.
8662 - New config option "CircuitStreamTimeout" to override our internal
8663 timeout schedule for how many seconds until we detach a stream from
8664 a circuit and try a new circuit. If your network is particularly
8665 slow, you might want to set this to a number like 60.
8666 - New controller command "getinfo config-text". It returns the
8667 contents that Tor would write if you send it a SAVECONF command,
8668 so the controller can write the file to disk itself.
8669 - New options for SafeLogging to allow scrubbing only log messages
8670 generated while acting as a relay.
8671 - Ship the bridges spec file in the tarball too.
8672 - Avoid a mad rush at the beginning of each month when each client
8673 rotates half of its guards. Instead we spread the rotation out
8674 throughout the month, but we still avoid leaving a precise timestamp
8675 in the state file about when we first picked the guard. Improves
8676 over the behavior introduced in 0.1.2.17.
8678 o Minor bugfixes (compiling):
8679 - Fix compilation on OS X 10.3, which has a stub mlockall() but
8680 hides it. Bugfix on 0.2.2.6-alpha.
8681 - Fix compilation on Solaris by removing support for the
8682 DisableAllSwap config option. Solaris doesn't have an rlimit for
8683 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
8686 o Minor bugfixes (crashes):
8687 - Do not segfault when writing buffer stats when we haven't observed
8688 a single circuit to report about. Found by Fabian Lanze. Bugfix on
8690 - If we're in the pathological case where there's no exit bandwidth
8691 but there is non-exit bandwidth, or no guard bandwidth but there
8692 is non-guard bandwidth, don't crash during path selection. Bugfix
8694 - Fix an impossible-to-actually-trigger buffer overflow in relay
8695 descriptor generation. Bugfix on 0.1.0.15.
8697 o Minor bugfixes (privacy):
8698 - Fix an instance where a Tor directory mirror might accidentally
8699 log the IP address of a misbehaving Tor client. Bugfix on
8701 - Don't list Windows capabilities in relay descriptors. We never made
8702 use of them, and maybe it's a bad idea to publish them. Bugfix
8705 o Minor bugfixes (other):
8706 - Resolve an edge case in path weighting that could make us misweight
8707 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
8708 - Fix statistics on client numbers by country as seen by bridges that
8709 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
8710 intervals instead of variable 12-to-48-hour intervals.
8711 - After we free an internal connection structure, overwrite it
8712 with a different memory value than we use for overwriting a freed
8713 internal circuit structure. Should help with debugging. Suggested
8715 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
8719 - Remove the HSAuthorityRecordStats option that version 0 hidden
8720 service authorities could have used to track statistics of overall
8721 hidden service usage.
8724 Changes in version 0.2.1.22 - 2010-01-19
8725 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
8726 authorities -- it would tell you its whole history of bridge descriptors
8727 if you make the right directory request. This stable update also
8728 rotates two of the seven v3 directory authority keys and locations.
8730 o Directory authority changes:
8731 - Rotate keys (both v3 identity and relay identity) for moria1
8735 - Stop bridge directory authorities from answering dbg-stability.txt
8736 directory queries, which would let people fetch a list of all
8737 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8740 Changes in version 0.2.1.21 - 2009-12-21
8741 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
8742 library. If you use Tor on Linux / Unix and you're getting SSL
8743 renegotiation errors, upgrading should help. We also recommend an
8744 upgrade if you're an exit relay.
8747 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8748 handshake from working unless we explicitly tell OpenSSL that we
8749 are using SSL renegotiation safely. We are, of course, but OpenSSL
8750 0.9.8l won't work unless we say we are.
8751 - Avoid crashing if the client is trying to upload many bytes and the
8752 circuit gets torn down at the same time, or if the flip side
8753 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
8756 - Do not refuse to learn about authority certs and v2 networkstatus
8757 documents that are older than the latest consensus. This bug might
8758 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8759 Spotted and fixed by xmux.
8760 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
8761 trigger platform-specific option misparsing case found by Coverity
8763 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
8764 trigger assert. Fixes bug 1173.
8767 Changes in version 0.2.2.6-alpha - 2009-11-19
8768 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
8769 support for the new lower-footprint "microdescriptor" directory design,
8770 future-proofing our consensus format against new hash functions or
8771 other changes, and an Android port. It also makes Tor compatible with
8772 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
8775 - Directory authorities can now create, vote on, and serve multiple
8776 parallel formats of directory data as part of their voting process.
8777 Partially implements Proposal 162: "Publish the consensus in
8779 - Directory authorities can now agree on and publish small summaries
8780 of router information that clients can use in place of regular
8781 server descriptors. This transition will eventually allow clients
8782 to use far less bandwidth for downloading information about the
8783 network. Begins the implementation of Proposal 158: "Clients
8784 download consensus + microdescriptors".
8785 - The directory voting system is now extensible to use multiple hash
8786 algorithms for signatures and resource selection. Newer formats
8787 are signed with SHA256, with a possibility for moving to a better
8788 hash algorithm in the future.
8789 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
8790 current and future memory pages via mlockall(). On supported
8791 platforms (modern Linux and probably BSD but not Windows or OS X),
8792 this should effectively disable any and all attempts to page out
8793 memory. This option requires that you start your Tor as root --
8794 if you use DisableAllSwap, please consider using the User option
8795 to properly reduce the privileges of your Tor.
8796 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
8797 to help Tor build correctly for Android phones.
8800 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8801 handshake from working unless we explicitly tell OpenSSL that we
8802 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
8803 won't work unless we say we are.
8806 - Fix a crash bug when trying to initialize the evdns module in
8807 Libevent 2. Bugfix on 0.2.1.16-rc.
8808 - Stop logging at severity 'warn' when some other Tor client tries
8809 to establish a circuit with us using weak DH keys. It's a protocol
8810 violation, but that doesn't mean ordinary users need to hear about
8811 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
8812 - Do not refuse to learn about authority certs and v2 networkstatus
8813 documents that are older than the latest consensus. This bug might
8814 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8815 Spotted and fixed by xmux.
8816 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
8817 - If all authorities restart at once right before a consensus vote,
8818 nobody will vote about "Running", and clients will get a consensus
8819 with no usable relays. Instead, authorities refuse to build a
8820 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
8821 - If your relay can't keep up with the number of incoming create
8822 cells, it would log one warning per failure into your logs. Limit
8823 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
8824 - Bridges now use "reject *:*" as their default exit policy. Bugfix
8825 on 0.2.0.3-alpha; fixes bug 1113.
8826 - Fix a memory leak on directory authorities during voting that was
8827 introduced in 0.2.2.1-alpha. Found via valgrind.
8830 Changes in version 0.2.1.20 - 2009-10-15
8831 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
8832 services at once, prepares for more performance improvements, and
8833 fixes a bunch of smaller bugs.
8835 The Windows and OS X bundles also include a more recent Vidalia,
8836 and switch from Privoxy to Polipo.
8838 The OS X installers are now drag and drop. It's best to un-install
8839 Tor/Vidalia and then install this new bundle, rather than upgrade. If
8840 you want to upgrade, you'll need to update the paths for Tor and Polipo
8841 in the Vidalia Settings window.
8844 - Send circuit or stream sendme cells when our window has decreased
8845 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8846 by Karsten when testing the "reduce circuit window" performance
8847 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8848 before the release of Tor 0.0.0. This is the new winner of the
8850 - Fix a remotely triggerable memory leak when a consensus document
8851 contains more than one signature from the same voter. Bugfix on
8853 - Avoid segfault in rare cases when finishing an introduction circuit
8854 as a client and finding out that we don't have an introduction key
8855 for it. Fixes bug 1073. Reported by Aaron Swartz.
8858 - Tor now reads the "circwindow" parameter out of the consensus,
8859 and uses that value for its circuit package window rather than the
8860 default of 1000 cells. Begins the implementation of proposal 168.
8862 o New directory authorities:
8863 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8865 - Move moria1 and tonga to alternate IP addresses.
8868 - Fix a signed/unsigned compile warning in 0.2.1.19.
8869 - Fix possible segmentation fault on directory authorities. Bugfix on
8871 - Fix an extremely rare infinite recursion bug that could occur if
8872 we tried to log a message after shutting down the log subsystem.
8873 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8874 - Fix an obscure bug where hidden services on 64-bit big-endian
8875 systems might mis-read the timestamp in v3 introduce cells, and
8876 refuse to connect back to the client. Discovered by "rotor".
8877 Bugfix on 0.2.1.6-alpha.
8878 - We were triggering a CLOCK_SKEW controller status event whenever
8879 we connect via the v2 connection protocol to any relay that has
8880 a wrong clock. Instead, we should only inform the controller when
8881 it's a trusted authority that claims our clock is wrong. Bugfix
8882 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8883 - We were telling the controller about CHECKING_REACHABILITY and
8884 REACHABILITY_FAILED status events whenever we launch a testing
8885 circuit or notice that one has failed. Instead, only tell the
8886 controller when we want to inform the user of overall success or
8887 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8889 - Don't warn when we're using a circuit that ends with a node
8890 excluded in ExcludeExitNodes, but the circuit is not used to access
8891 the outside world. This should help fix bug 1090. Bugfix on
8893 - Work around a small memory leak in some versions of OpenSSL that
8894 stopped the memory used by the hostname TLS extension from being
8898 - Add a "getinfo status/accepted-server-descriptor" controller
8899 command, which is the recommended way for controllers to learn
8900 whether our server descriptor has been successfully received by at
8901 least on directory authority. Un-recommend good-server-descriptor
8902 getinfo and status events until we have a better design for them.
8905 Changes in version 0.2.2.5-alpha - 2009-10-11
8906 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
8909 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
8911 o Directory authorities:
8912 - Temporarily (just for this release) move dizum to an alternate
8916 Changes in version 0.2.2.4-alpha - 2009-10-10
8917 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
8918 introduces a new unit test framework, shifts directry authority
8919 addresses around to reduce the impact from recent blocking events,
8920 and fixes a few smaller bugs.
8923 - Fix several more asserts in the circuit_build_times code, for
8924 example one that causes Tor to fail to start once we have
8925 accumulated 5000 build times in the state file. Bugfixes on
8926 0.2.2.2-alpha; fixes bug 1108.
8928 o New directory authorities:
8929 - Move moria1 and Tonga to alternate IP addresses.
8932 - Log SSL state transitions at debug level during handshake, and
8933 include SSL states in error messages. This may help debug future
8934 SSL handshake issues.
8935 - Add a new "Handshake" log domain for activities that happen
8936 during the TLS handshake.
8937 - Revert to the "June 3 2009" ip-to-country file. The September one
8938 seems to have removed most US IP addresses.
8939 - Directory authorities now reject Tor relays with versions less than
8940 0.1.2.14. This step cuts out four relays from the current network,
8941 none of which are very big.
8944 - Fix a couple of smaller issues with gathering statistics. Bugfixes
8946 - Fix two memory leaks in the error case of
8947 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
8948 - Don't count one-hop circuits when we're estimating how long it
8949 takes circuits to build on average. Otherwise we'll set our circuit
8950 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
8951 - Directory authorities no longer change their opinion of, or vote on,
8952 whether a router is Running, unless they have themselves been
8953 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
8956 o Code simplifications and refactoring:
8957 - Revise our unit tests to use the "tinytest" framework, so we
8958 can run tests in their own processes, have smarter setup/teardown
8959 code, and so on. The unit test code has moved to its own
8960 subdirectory, and has been split into multiple modules.
8963 Changes in version 0.2.2.3-alpha - 2009-09-23
8964 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
8967 - Fix an overzealous assert in our new circuit build timeout code.
8968 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
8971 - If the networkstatus consensus tells us that we should use a
8972 negative circuit package window, ignore it. Otherwise we'll
8973 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
8976 Changes in version 0.2.2.2-alpha - 2009-09-21
8977 Tor 0.2.2.2-alpha introduces our latest performance improvement for
8978 clients: Tor tracks the average time it takes to build a circuit, and
8979 avoids using circuits that take too long to build. For fast connections,
8980 this feature can cut your expected latency in half. For slow or flaky
8981 connections, it could ruin your Tor experience. Let us know if it does!
8984 - Tor now tracks how long it takes to build client-side circuits
8985 over time, and adapts its timeout to local network performance.
8986 Since a circuit that takes a long time to build will also provide
8987 bad performance, we get significant latency improvements by
8988 discarding the slowest 20% of circuits. Specifically, Tor creates
8989 circuits more aggressively than usual until it has enough data
8990 points for a good timeout estimate. Implements proposal 151.
8991 We are especially looking for reports (good and bad) from users with
8992 both EDGE and broadband connections that can move from broadband
8993 to EDGE and find out if the build-time data in the .tor/state gets
8994 reset without loss of Tor usability. You should also see a notice
8995 log message telling you that Tor has reset its timeout.
8996 - Directory authorities can now vote on arbitary integer values as
8997 part of the consensus process. This is designed to help set
8998 network-wide parameters. Implements proposal 167.
8999 - Tor now reads the "circwindow" parameter out of the consensus,
9000 and uses that value for its circuit package window rather than the
9001 default of 1000 cells. Begins the implementation of proposal 168.
9004 - Fix a remotely triggerable memory leak when a consensus document
9005 contains more than one signature from the same voter. Bugfix on
9009 - Fix an extremely rare infinite recursion bug that could occur if
9010 we tried to log a message after shutting down the log subsystem.
9011 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9012 - Fix parsing for memory or time units given without a space between
9013 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
9014 - A networkstatus vote must contain exactly one signature. Spec
9015 conformance issue. Bugfix on 0.2.0.3-alpha.
9016 - Fix an obscure bug where hidden services on 64-bit big-endian
9017 systems might mis-read the timestamp in v3 introduce cells, and
9018 refuse to connect back to the client. Discovered by "rotor".
9019 Bugfix on 0.2.1.6-alpha.
9020 - We were triggering a CLOCK_SKEW controller status event whenever
9021 we connect via the v2 connection protocol to any relay that has
9022 a wrong clock. Instead, we should only inform the controller when
9023 it's a trusted authority that claims our clock is wrong. Bugfix
9024 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9025 - We were telling the controller about CHECKING_REACHABILITY and
9026 REACHABILITY_FAILED status events whenever we launch a testing
9027 circuit or notice that one has failed. Instead, only tell the
9028 controller when we want to inform the user of overall success or
9029 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9031 - Don't warn when we're using a circuit that ends with a node
9032 excluded in ExcludeExitNodes, but the circuit is not used to access
9033 the outside world. This should help fix bug 1090, but more problems
9034 remain. Bugfix on 0.2.1.6-alpha.
9035 - Work around a small memory leak in some versions of OpenSSL that
9036 stopped the memory used by the hostname TLS extension from being
9038 - Make our 'torify' script more portable; if we have only one of
9039 'torsocks' or 'tsocks' installed, don't complain to the user;
9040 and explain our warning about tsocks better.
9043 - Add a "getinfo status/accepted-server-descriptor" controller
9044 command, which is the recommended way for controllers to learn
9045 whether our server descriptor has been successfully received by at
9046 least on directory authority. Un-recommend good-server-descriptor
9047 getinfo and status events until we have a better design for them.
9048 - Update to the "September 4 2009" ip-to-country file.
9051 Changes in version 0.2.2.1-alpha - 2009-08-26
9052 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
9053 Tor clients to bootstrap on networks where only port 80 is reachable,
9054 makes it more straightforward to support hardware crypto accelerators,
9055 and starts the groundwork for gathering stats safely at relays.
9058 - Start the process of disabling ".exit" address notation, since it
9059 can be used for a variety of esoteric application-level attacks
9060 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
9063 o New directory authorities:
9064 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9068 - New AccelName and AccelDir options add support for dynamic OpenSSL
9069 hardware crypto acceleration engines.
9070 - Tor now supports tunneling all of its outgoing connections over
9071 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
9072 configuration options. Code by Christopher Davis.
9075 - Send circuit or stream sendme cells when our window has decreased
9076 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9077 by Karsten when testing the "reduce circuit window" performance
9078 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9079 before the release of Tor 0.0.0. This is the new winner of the
9082 o New options for gathering stats safely:
9083 - Directory mirrors that set "DirReqStatistics 1" write statistics
9084 about directory requests to disk every 24 hours. As compared to the
9085 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
9086 1) stats are written to disk exactly every 24 hours; 2) estimated
9087 shares of v2 and v3 requests are determined as mean values, not at
9088 the end of a measurement period; 3) unresolved requests are listed
9089 with country code '??'; 4) directories also measure download times.
9090 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
9091 number of exit streams and transferred bytes per port to disk every
9093 - Relays that set "CellStatistics 1" write statistics on how long
9094 cells spend in their circuit queues to disk every 24 hours.
9095 - Entry nodes that set "EntryStatistics 1" write statistics on the
9096 rough number and origins of connecting clients to disk every 24
9098 - Relays that write any of the above statistics to disk and set
9099 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
9100 their extra-info documents.
9103 - New --digests command-line switch to output the digests of the
9104 source files Tor was built with.
9105 - The "torify" script now uses torsocks where available.
9106 - The memarea code now uses a sentinel value at the end of each area
9107 to make sure nothing writes beyond the end of an area. This might
9108 help debug some conceivable causes of bug 930.
9109 - Time and memory units in the configuration file can now be set to
9110 fractional units. For example, "2.5 GB" is now a valid value for
9112 - Certain Tor clients (such as those behind check.torproject.org) may
9113 want to fetch the consensus in an extra early manner. To enable this
9114 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
9115 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
9116 as only certain clients who must have this information sooner should
9118 - Instead of adding the svn revision to the Tor version string, report
9119 the git commit (when we're building from a git checkout).
9122 - If any of the v3 certs we download are unparseable, we should
9123 actually notice the failure so we don't retry indefinitely. Bugfix
9124 on 0.2.0.x; reported by "rotator".
9125 - If the cached cert file is unparseable, warn but don't exit.
9126 - Fix possible segmentation fault on directory authorities. Bugfix on
9128 - When Tor fails to parse a descriptor of any kind, dump it to disk.
9129 Might help diagnosing bug 1051.
9131 o Deprecated and removed features:
9132 - The controller no longer accepts the old obsolete "addr-mappings/"
9133 or "unregistered-servers-" GETINFO values.
9134 - Hidden services no longer publish version 0 descriptors, and clients
9135 do not request or use version 0 descriptors. However, the old hidden
9136 service authorities still accept and serve version 0 descriptors
9137 when contacted by older hidden services/clients.
9138 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
9139 always on; using them is necessary for correct forward-compatible
9141 - Remove support for .noconnect style addresses. Nobody was using
9142 them, and they provided another avenue for detecting Tor users
9143 via application-level web tricks.
9145 o Packaging changes:
9146 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
9147 installer bundles. See
9148 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
9149 for details of what's new in Vidalia 0.2.3.
9150 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
9151 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
9152 configuration file, rather than the old Privoxy.
9153 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
9154 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
9155 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
9156 better compatibility with OS X 10.6, aka Snow Leopard.
9157 - OS X Vidalia Bundle: The multi-package installer is now replaced
9158 by a simple drag and drop to the /Applications folder. This change
9159 occurred with the upgrade to Vidalia 0.2.3.
9162 Changes in version 0.2.1.19 - 2009-07-28
9163 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
9164 services on Tor 0.2.1.3-alpha through 0.2.1.18.
9167 - Make accessing hidden services on 0.2.1.x work right again.
9168 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
9169 part of patch provided by "optimist".
9172 - When a relay/bridge is writing out its identity key fingerprint to
9173 the "fingerprint" file and to its logs, write it without spaces. Now
9174 it will look like the fingerprints in our bridges documentation,
9175 and confuse fewer users.
9178 - Relays no longer publish a new server descriptor if they change
9179 their MaxAdvertisedBandwidth config option but it doesn't end up
9180 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
9181 fixes bug 1026. Patch from Sebastian.
9182 - Avoid leaking memory every time we get a create cell but we have
9183 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
9184 fixes bug 1034. Reported by BarkerJr.
9187 Changes in version 0.2.1.18 - 2009-07-24
9188 Tor 0.2.1.18 lays the foundations for performance improvements,
9189 adds status events to help users diagnose bootstrap problems, adds
9190 optional authentication/authorization for hidden services, fixes a
9191 variety of potential anonymity problems, and includes a huge pile of
9192 other features and bug fixes.
9195 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
9198 Changes in version 0.2.1.17-rc - 2009-07-07
9199 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
9200 candidate for the 0.2.1.x series. It lays the groundwork for further
9201 client performance improvements, and also fixes a big bug with directory
9202 authorities that were causing them to assign Guard and Stable flags
9205 The Windows bundles also finally include the geoip database that we
9206 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
9207 should actually install Torbutton rather than giving you a cryptic
9208 failure message (oops).
9211 - Clients now use the bandwidth values in the consensus, rather than
9212 the bandwidth values in each relay descriptor. This approach opens
9213 the door to more accurate bandwidth estimates once the directory
9214 authorities start doing active measurements. Implements more of
9218 - When Tor clients restart after 1-5 days, they discard all their
9219 cached descriptors as too old, but they still use the cached
9220 consensus document. This approach is good for robustness, but
9221 bad for performance: since they don't know any bandwidths, they
9222 end up choosing at random rather than weighting their choice by
9223 speed. Fixed by the above feature of putting bandwidths in the
9224 consensus. Bugfix on 0.2.0.x.
9225 - Directory authorities were neglecting to mark relays down in their
9226 internal histories if the relays fall off the routerlist without
9227 ever being found unreachable. So there were relays in the histories
9228 that haven't been seen for eight months, and are listed as being
9229 up for eight months. This wreaked havoc on the "median wfu"
9230 and "median mtbf" calculations, in turn making Guard and Stable
9231 flags very wrong, hurting network performance. Fixes bugs 696 and
9232 969. Bugfix on 0.2.0.6-alpha.
9235 - Serve the DirPortFrontPage page even when we have been approaching
9236 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
9237 - The control port would close the connection before flushing long
9238 replies, such as the network consensus, if a QUIT command was issued
9239 before the reply had completed. Now, the control port flushes all
9240 pending replies before closing the connection. Also fixed a spurious
9241 warning when a QUIT command is issued after a malformed or rejected
9242 AUTHENTICATE command, but before the connection was closed. Patch
9243 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
9244 - When we can't find an intro key for a v2 hidden service descriptor,
9245 fall back to the v0 hidden service descriptor and log a bug message.
9246 Workaround for bug 1024.
9247 - Fix a log message that did not respect the SafeLogging option.
9251 - If we're a relay and we change our IP address, be more verbose
9252 about the reason that made us change. Should help track down
9253 further bugs for relays on dynamic IP addresses.
9256 Changes in version 0.2.0.35 - 2009-06-24
9258 - Avoid crashing in the presence of certain malformed descriptors.
9259 Found by lark, and by automated fuzzing.
9260 - Fix an edge case where a malicious exit relay could convince a
9261 controller that the client's DNS question resolves to an internal IP
9262 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9265 - Finally fix the bug where dynamic-IP relays disappear when their
9266 IP address changes: directory mirrors were mistakenly telling
9267 them their old address if they asked via begin_dir, so they
9268 never got an accurate answer about their new address, so they
9269 just vanished after a day. For belt-and-suspenders, relays that
9270 don't set Address in their config now avoid using begin_dir for
9271 all direct connections. Should fix bugs 827, 883, and 900.
9272 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9273 that would occur on some exit nodes when DNS failures and timeouts
9274 occurred in certain patterns. Fix for bug 957.
9277 - When starting with a cache over a few days old, do not leak
9278 memory for the obsolete router descriptors in it. Bugfix on
9279 0.2.0.33; fixes bug 672.
9280 - Hidden service clients didn't use a cached service descriptor that
9281 was older than 15 minutes, but wouldn't fetch a new one either,
9282 because there was already one in the cache. Now, fetch a v2
9283 descriptor unless the same descriptor was added to the cache within
9284 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9287 Changes in version 0.2.1.16-rc - 2009-06-20
9288 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
9289 a bunch of minor bugs.
9292 - Fix an edge case where a malicious exit relay could convince a
9293 controller that the client's DNS question resolves to an internal IP
9294 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9296 o Major performance improvements (on 0.2.0.x):
9297 - Disable and refactor some debugging checks that forced a linear scan
9298 over the whole server-side DNS cache. These accounted for over 50%
9299 of CPU time on a relatively busy exit node's gprof profile. Found
9301 - Disable some debugging checks that appeared in exit node profile
9305 - Update to the "June 3 2009" ip-to-country file.
9306 - Do not have tor-resolve automatically refuse all .onion addresses;
9307 if AutomapHostsOnResolve is set in your torrc, this will work fine.
9309 o Minor bugfixes (on 0.2.0.x):
9310 - Log correct error messages for DNS-related network errors on
9312 - Fix a race condition that could cause crashes or memory corruption
9313 when running as a server with a controller listening for log
9315 - Avoid crashing when we have a policy specified in a DirPolicy or
9316 SocksPolicy or ReachableAddresses option with ports set on it,
9317 and we re-load the policy. May fix bug 996.
9318 - Hidden service clients didn't use a cached service descriptor that
9319 was older than 15 minutes, but wouldn't fetch a new one either,
9320 because there was already one in the cache. Now, fetch a v2
9321 descriptor unless the same descriptor was added to the cache within
9322 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9324 o Minor bugfixes (on 0.2.1.x):
9325 - Don't warn users about low port and hibernation mix when they
9326 provide a *ListenAddress directive to fix that. Bugfix on
9328 - When switching back and forth between bridge mode, do not start
9329 gathering GeoIP data until two hours have passed.
9330 - Do not complain that the user has requested an excluded node as
9331 an exit when the node is not really an exit. This could happen
9332 because the circuit was for testing, or an introduction point.
9336 Changes in version 0.2.1.15-rc - 2009-05-25
9337 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
9338 series. It fixes a major bug on fast exit relays, as well as a variety
9341 o Major bugfixes (on 0.2.0.x):
9342 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9343 that would occur on some exit nodes when DNS failures and timeouts
9344 occurred in certain patterns. Fix for bug 957.
9346 o Minor bugfixes (on 0.2.0.x):
9347 - Actually return -1 in the error case for read_bandwidth_usage().
9348 Harmless bug, since we currently don't care about the return value
9349 anywhere. Bugfix on 0.2.0.9-alpha.
9350 - Provide a more useful log message if bug 977 (related to buffer
9351 freelists) ever reappears, and do not crash right away.
9352 - Fix an assertion failure on 64-bit platforms when we allocated
9353 memory right up to the end of a memarea, then realigned the memory
9354 one step beyond the end. Fixes a possible cause of bug 930.
9355 - Protect the count of open sockets with a mutex, so we can't
9356 corrupt it when two threads are closing or opening sockets at once.
9357 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
9358 - Don't allow a bridge to publish its router descriptor to a
9359 non-bridge directory authority. Fixes part of bug 932.
9360 - When we change to or from being a bridge, reset our counts of
9361 client usage by country. Fixes bug 932.
9362 - Fix a bug that made stream bandwidth get misreported to the
9364 - Stop using malloc_usable_size() to use more area than we had
9365 actually allocated: it was safe, but made valgrind really unhappy.
9366 - Fix a memory leak when v3 directory authorities load their keys
9367 and cert from disk. Bugfix on 0.2.0.1-alpha.
9369 o Minor bugfixes (on 0.2.1.x):
9370 - Fix use of freed memory when deciding to mark a non-addable
9371 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
9374 Changes in version 0.2.1.14-rc - 2009-04-12
9375 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
9376 series. It begins fixing some major performance problems, and also
9377 finally addresses the bug that was causing relays on dynamic IP
9378 addresses to fall out of the directory.
9381 - Clients replace entry guards that were chosen more than a few months
9382 ago. This change should significantly improve client performance,
9383 especially once more people upgrade, since relays that have been
9384 a guard for a long time are currently overloaded.
9386 o Major bugfixes (on 0.2.0):
9387 - Finally fix the bug where dynamic-IP relays disappear when their
9388 IP address changes: directory mirrors were mistakenly telling
9389 them their old address if they asked via begin_dir, so they
9390 never got an accurate answer about their new address, so they
9391 just vanished after a day. For belt-and-suspenders, relays that
9392 don't set Address in their config now avoid using begin_dir for
9393 all direct connections. Should fix bugs 827, 883, and 900.
9394 - Relays were falling out of the networkstatus consensus for
9395 part of a day if they changed their local config but the
9396 authorities discarded their new descriptor as "not sufficiently
9397 different". Now directory authorities accept a descriptor as changed
9398 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
9400 - Avoid crashing in the presence of certain malformed descriptors.
9401 Found by lark, and by automated fuzzing.
9404 - When generating circuit events with verbose nicknames for
9405 controllers, try harder to look up nicknames for routers on a
9406 circuit. (Previously, we would look in the router descriptors we had
9407 for nicknames, but not in the consensus.) Partial fix for bug 941.
9408 - If the bridge config line doesn't specify a port, assume 443.
9409 This makes bridge lines a bit smaller and easier for users to
9411 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
9412 bytes (aka 20KB/s), to match our documentation. Also update
9413 directory authorities so they always assign the Fast flag to relays
9414 with 20KB/s of capacity. Now people running relays won't suddenly
9415 find themselves not seeing any use, if the network gets faster
9417 - Update to the "April 3 2009" ip-to-country file.
9420 - Avoid trying to print raw memory to the logs when we decide to
9421 give up on downloading a given relay descriptor. Bugfix on
9423 - In tor-resolve, when the Tor client to use is specified by
9424 <hostname>:<port>, actually use the specified port rather than
9425 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
9426 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
9427 - When starting with a cache over a few days old, do not leak
9428 memory for the obsolete router descriptors in it. Bugfix on
9430 - Avoid double-free on list of successfully uploaded hidden
9431 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
9432 - Change memarea_strndup() implementation to work even when
9433 duplicating a string at the end of a page. This bug was
9434 harmless for now, but could have meant crashes later. Fix by
9435 lark. Bugfix on 0.2.1.1-alpha.
9436 - Limit uploaded directory documents to be 16M rather than 500K.
9437 The directory authorities were refusing v3 consensus votes from
9438 other authorities, since the votes are now 504K. Fixes bug 959;
9439 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
9440 - Directory authorities should never send a 503 "busy" response to
9441 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
9445 Changes in version 0.2.1.13-alpha - 2009-03-09
9446 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
9447 cleanups. We're finally getting close to a release candidate.
9450 - Correctly update the list of which countries we exclude as
9451 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
9452 lark. Bugfix on 0.2.1.6-alpha.
9454 o Minor bugfixes (on 0.2.0.x and earlier):
9455 - Automatically detect MacOSX versions earlier than 10.4.0, and
9456 disable kqueue from inside Tor when running with these versions.
9457 We previously did this from the startup script, but that was no
9458 help to people who didn't use the startup script. Resolves bug 863.
9459 - When we had picked an exit node for a connection, but marked it as
9460 "optional", and it turned out we had no onion key for the exit,
9461 stop wanting that exit and try again. This situation may not
9462 be possible now, but will probably become feasible with proposal
9463 158. Spotted by rovv. Fixes another case of bug 752.
9464 - Clients no longer cache certificates for authorities they do not
9465 recognize. Bugfix on 0.2.0.9-alpha.
9466 - When we can't transmit a DNS request due to a network error, retry
9467 it after a while, and eventually transmit a failing response to
9468 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
9469 - If the controller claimed responsibility for a stream, but that
9470 stream never finished making its connection, it would live
9471 forever in circuit_wait state. Now we close it after SocksTimeout
9472 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
9473 - Drop begin cells to a hidden service if they come from the middle
9474 of a circuit. Patch from lark.
9475 - When we erroneously receive two EXTEND cells for the same circuit
9476 ID on the same connection, drop the second. Patch from lark.
9477 - Fix a crash that occurs on exit nodes when a nameserver request
9478 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
9479 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
9481 - Do not assume that a stack-allocated character array will be
9482 64-bit aligned on platforms that demand that uint64_t access is
9483 aligned. Possible fix for bug 604.
9484 - Parse dates and IPv4 addresses in a locale- and libc-independent
9485 manner, to avoid platform-dependent behavior on malformed input.
9486 - Build correctly when configured to build outside the main source
9487 path. Patch from Michael Gold.
9488 - We were already rejecting relay begin cells with destination port
9489 of 0. Now also reject extend cells with destination port or address
9490 of 0. Suggested by lark.
9492 o Minor bugfixes (on 0.2.1.x):
9493 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
9494 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
9495 - If we're an exit node, scrub the IP address to which we are exiting
9496 in the logs. Bugfix on 0.2.1.8-alpha.
9499 - On Linux, use the prctl call to re-enable core dumps when the user
9501 - New controller event NEWCONSENSUS that lists the networkstatus
9502 lines for every recommended relay. Now controllers like Torflow
9503 can keep up-to-date on which relays they should be using.
9504 - Update to the "February 26 2009" ip-to-country file.
9507 Changes in version 0.2.0.34 - 2009-02-08
9508 Tor 0.2.0.34 features several more security-related fixes. You should
9509 upgrade, especially if you run an exit relay (remote crash) or a
9510 directory authority (remote infinite loop), or you're on an older
9511 (pre-XP) or not-recently-patched Windows (remote exploit).
9513 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
9514 have many known flaws, and nobody should be using them. You should
9515 upgrade. If you're using a Linux or BSD and its packages are obsolete,
9516 stop using those packages and upgrade anyway.
9519 - Fix an infinite-loop bug on handling corrupt votes under certain
9520 circumstances. Bugfix on 0.2.0.8-alpha.
9521 - Fix a temporary DoS vulnerability that could be performed by
9522 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9523 - Avoid a potential crash on exit nodes when processing malformed
9524 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
9525 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9526 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9529 - Fix compilation on systems where time_t is a 64-bit integer.
9530 Patch from Matthias Drochner.
9531 - Don't consider expiring already-closed client connections. Fixes
9532 bug 893. Bugfix on 0.0.2pre20.
9535 Changes in version 0.2.1.12-alpha - 2009-02-08
9536 Tor 0.2.1.12-alpha features several more security-related fixes. You
9537 should upgrade, especially if you run an exit relay (remote crash) or
9538 a directory authority (remote infinite loop), or you're on an older
9539 (pre-XP) or not-recently-patched Windows (remote exploit). It also
9540 includes a big pile of minor bugfixes and cleanups.
9543 - Fix an infinite-loop bug on handling corrupt votes under certain
9544 circumstances. Bugfix on 0.2.0.8-alpha.
9545 - Fix a temporary DoS vulnerability that could be performed by
9546 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9547 - Avoid a potential crash on exit nodes when processing malformed
9548 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
9551 - Let controllers actually ask for the "clients_seen" event for
9552 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
9553 reported by Matt Edman.
9554 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
9556 - Fix a bug in address parsing that was preventing bridges or hidden
9557 service targets from being at IPv6 addresses.
9558 - Solve a bug that kept hardware crypto acceleration from getting
9559 enabled when accounting was turned on. Fixes bug 907. Bugfix on
9561 - Remove a bash-ism from configure.in to build properly on non-Linux
9562 platforms. Bugfix on 0.2.1.1-alpha.
9563 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
9564 headers. Bugfix on 0.2.0.10-alpha.
9565 - Don't consider expiring already-closed client connections. Fixes
9566 bug 893. Bugfix on 0.0.2pre20.
9567 - Fix another interesting corner-case of bug 891 spotted by rovv:
9568 Previously, if two hosts had different amounts of clock drift, and
9569 one of them created a new connection with just the wrong timing,
9570 the other might decide to deprecate the new connection erroneously.
9571 Bugfix on 0.1.1.13-alpha.
9572 - Resolve a very rare crash bug that could occur when the user forced
9573 a nameserver reconfiguration during the middle of a nameserver
9574 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
9575 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
9576 Bugfix on 0.2.1.7-alpha.
9577 - If we're using bridges and our network goes away, be more willing
9578 to forgive our bridges and try again when we get an application
9579 request. Bugfix on 0.2.0.x.
9582 - Support platforms where time_t is 64 bits long. (Congratulations,
9583 NetBSD!) Patch from Matthias Drochner.
9584 - Add a 'getinfo status/clients-seen' controller command, in case
9585 controllers want to hear clients_seen events but connect late.
9588 - Disable GCC's strict alias optimization by default, to avoid the
9589 likelihood of its introducing subtle bugs whenever our code violates
9590 the letter of C99's alias rules.
9593 Changes in version 0.2.0.33 - 2009-01-21
9594 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
9595 useful to users. It also finally fixes a bug where a relay or client
9596 that's been off for many days would take a long time to bootstrap.
9598 This update also fixes an important security-related bug reported by
9599 Ilja van Sprundel. You should upgrade. (We'll send out more details
9600 about the bug once people have had some time to upgrade.)
9603 - Fix a heap-corruption bug that may be remotely triggerable on
9604 some platforms. Reported by Ilja van Sprundel.
9607 - When a stream at an exit relay is in state "resolving" or
9608 "connecting" and it receives an "end" relay cell, the exit relay
9609 would silently ignore the end cell and not close the stream. If
9610 the client never closes the circuit, then the exit relay never
9611 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
9613 - When sending CREATED cells back for a given circuit, use a 64-bit
9614 connection ID to find the right connection, rather than an addr:port
9615 combination. Now that we can have multiple OR connections between
9616 the same ORs, it is no longer possible to use addr:port to uniquely
9617 identify a connection.
9618 - Bridge relays that had DirPort set to 0 would stop fetching
9619 descriptors shortly after startup, and then briefly resume
9620 after a new bandwidth test and/or after publishing a new bridge
9621 descriptor. Bridge users that try to bootstrap from them would
9622 get a recent networkstatus but would get descriptors from up to
9623 18 hours earlier, meaning most of the descriptors were obsolete
9624 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9625 - Prevent bridge relays from serving their 'extrainfo' document
9626 to anybody who asks, now that extrainfo docs include potentially
9627 sensitive aggregated client geoip summaries. Bugfix on
9629 - If the cached networkstatus consensus is more than five days old,
9630 discard it rather than trying to use it. In theory it could be
9631 useful because it lists alternate directory mirrors, but in practice
9632 it just means we spend many minutes trying directory mirrors that
9633 are long gone from the network. Also discard router descriptors as
9634 we load them if they are more than five days old, since the onion
9635 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
9638 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9639 could make gcc generate non-functional binary search code. Bugfix
9641 - Build correctly on platforms without socklen_t.
9642 - Compile without warnings on solaris.
9643 - Avoid potential crash on internal error during signature collection.
9644 Fixes bug 864. Patch from rovv.
9645 - Correct handling of possible malformed authority signing key
9646 certificates with internal signature types. Fixes bug 880.
9647 Bugfix on 0.2.0.3-alpha.
9648 - Fix a hard-to-trigger resource leak when logging credential status.
9650 - When we can't initialize DNS because the network is down, do not
9651 automatically stop Tor from starting. Instead, we retry failed
9652 dns_init() every 10 minutes, and change the exit policy to reject
9653 *:* until one succeeds. Fixes bug 691.
9654 - Use 64 bits instead of 32 bits for connection identifiers used with
9655 the controller protocol, to greatly reduce risk of identifier reuse.
9656 - When we're choosing an exit node for a circuit, and we have
9657 no pending streams, choose a good general exit rather than one that
9658 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9659 - Fix another case of assuming, when a specific exit is requested,
9660 that we know more than the user about what hosts it allows.
9661 Fixes one case of bug 752. Patch from rovv.
9662 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9663 seconds. Warn the user if lower values are given in the
9664 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9665 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9666 user if lower values are given in the configuration. Bugfix on
9667 0.1.1.17-rc. Patch by Sebastian.
9668 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
9669 the cache because we already had a v0 descriptor with the same ID.
9670 Bugfix on 0.2.0.18-alpha.
9671 - Fix a race condition when freeing keys shared between main thread
9672 and CPU workers that could result in a memory leak. Bugfix on
9673 0.1.0.1-rc. Fixes bug 889.
9674 - Send a valid END cell back when a client tries to connect to a
9675 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9676 840. Patch from rovv.
9677 - Check which hops rendezvous stream cells are associated with to
9678 prevent possible guess-the-streamid injection attacks from
9679 intermediate hops. Fixes another case of bug 446. Based on patch
9681 - If a broken client asks a non-exit router to connect somewhere,
9682 do not even do the DNS lookup before rejecting the connection.
9683 Fixes another case of bug 619. Patch from rovv.
9684 - When a relay gets a create cell it can't decrypt (e.g. because it's
9685 using the wrong onion key), we were dropping it and letting the
9686 client time out. Now actually answer with a destroy cell. Fixes
9687 bug 904. Bugfix on 0.0.2pre8.
9689 o Minor bugfixes (hidden services):
9690 - Do not throw away existing introduction points on SIGHUP. Bugfix on
9691 0.0.6pre1. Patch by Karsten. Fixes bug 874.
9694 - Report the case where all signatures in a detached set are rejected
9695 differently than the case where there is an error handling the
9697 - When we realize that another process has modified our cached
9698 descriptors, print out a more useful error message rather than
9699 triggering an assertion. Fixes bug 885. Patch from Karsten.
9700 - Implement the 0x20 hack to better resist DNS poisoning: set the
9701 case on outgoing DNS requests randomly, and reject responses that do
9702 not match the case correctly. This logic can be disabled with the
9703 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
9704 of servers that do not reliably preserve case in replies. See
9705 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9707 - Check DNS replies for more matching fields to better resist DNS
9709 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9710 compress cells, which are basically all encrypted, compressed, or
9714 Changes in version 0.2.1.11-alpha - 2009-01-20
9715 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
9716 week it will take a long time to bootstrap again" bug. It also fixes
9717 an important security-related bug reported by Ilja van Sprundel. You
9718 should upgrade. (We'll send out more details about the bug once people
9719 have had some time to upgrade.)
9722 - Fix a heap-corruption bug that may be remotely triggerable on
9723 some platforms. Reported by Ilja van Sprundel.
9726 - Discard router descriptors as we load them if they are more than
9727 five days old. Otherwise if Tor is off for a long time and then
9728 starts with cached descriptors, it will try to use the onion
9729 keys in those obsolete descriptors when building circuits. Bugfix
9730 on 0.2.0.x. Fixes bug 887.
9733 - Try to make sure that the version of Libevent we're running with
9734 is binary-compatible with the one we built with. May address bug
9736 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
9737 for bug 905. Bugfix on 0.2.1.7-alpha.
9738 - Add a new --enable-local-appdata configuration switch to change
9739 the default location of the datadir on win32 from APPDATA to
9740 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
9741 entirely. Patch from coderman.
9744 - Make outbound DNS packets respect the OutboundBindAddress setting.
9745 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
9746 - When our circuit fails at the first hop (e.g. we get a destroy
9747 cell back), avoid using that OR connection anymore, and also
9748 tell all the one-hop directory requests waiting for it that they
9749 should fail. Bugfix on 0.2.1.3-alpha.
9750 - In the torify(1) manpage, mention that tsocks will leak your
9754 Changes in version 0.2.1.10-alpha - 2009-01-06
9755 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
9756 would make the bridge relay not so useful if it had DirPort set to 0,
9757 and one that could let an attacker learn a little bit of information
9758 about the bridge's users), and a bug that would cause your Tor relay
9759 to ignore a circuit create request it can't decrypt (rather than reply
9760 with an error). It also fixes a wide variety of other bugs.
9763 - If the cached networkstatus consensus is more than five days old,
9764 discard it rather than trying to use it. In theory it could
9765 be useful because it lists alternate directory mirrors, but in
9766 practice it just means we spend many minutes trying directory
9767 mirrors that are long gone from the network. Helps bug 887 a bit;
9769 - Bridge relays that had DirPort set to 0 would stop fetching
9770 descriptors shortly after startup, and then briefly resume
9771 after a new bandwidth test and/or after publishing a new bridge
9772 descriptor. Bridge users that try to bootstrap from them would
9773 get a recent networkstatus but would get descriptors from up to
9774 18 hours earlier, meaning most of the descriptors were obsolete
9775 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9776 - Prevent bridge relays from serving their 'extrainfo' document
9777 to anybody who asks, now that extrainfo docs include potentially
9778 sensitive aggregated client geoip summaries. Bugfix on
9782 - New controller event "clients_seen" to report a geoip-based summary
9783 of which countries we've seen clients from recently. Now controllers
9784 like Vidalia can show bridge operators that they're actually making
9786 - Build correctly against versions of OpenSSL 0.9.8 or later built
9787 without support for deprecated functions.
9788 - Update to the "December 19 2008" ip-to-country file.
9790 o Minor bugfixes (on 0.2.0.x):
9791 - Authorities now vote for the Stable flag for any router whose
9792 weighted MTBF is at least 5 days, regardless of the mean MTBF.
9793 - Do not remove routers as too old if we do not have any consensus
9794 document. Bugfix on 0.2.0.7-alpha.
9795 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9796 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9797 - When an exit relay resolves a stream address to a local IP address,
9798 do not just keep retrying that same exit relay over and
9799 over. Instead, just close the stream. Addresses bug 872. Bugfix
9800 on 0.2.0.32. Patch from rovv.
9801 - If a hidden service sends us an END cell, do not consider
9802 retrying the connection; just close it. Patch from rovv.
9803 - When we made bridge authorities stop serving bridge descriptors over
9804 unencrypted links, we also broke DirPort reachability testing for
9805 bridges. So bridges with a non-zero DirPort were printing spurious
9806 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
9807 - When a relay gets a create cell it can't decrypt (e.g. because it's
9808 using the wrong onion key), we were dropping it and letting the
9809 client time out. Now actually answer with a destroy cell. Fixes
9810 bug 904. Bugfix on 0.0.2pre8.
9811 - Squeeze 2-5% out of client performance (according to oprofile) by
9812 improving the implementation of some policy-manipulation functions.
9814 o Minor bugfixes (on 0.2.1.x):
9815 - Make get_interface_address() function work properly again; stop
9816 guessing the wrong parts of our address as our address.
9817 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
9818 send on that circuit. Otherwise we might violate the proposal-110
9819 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
9821 - When we're sending non-EXTEND cells to the first hop in a circuit,
9822 for example to use an encrypted directory connection, we don't need
9823 to use RELAY_EARLY cells: the first hop knows what kind of cell
9824 it is, and nobody else can even see the cell type. Conserving
9825 RELAY_EARLY cells makes it easier to cannibalize circuits like
9827 - Stop logging nameserver addresses in reverse order.
9828 - If we are retrying a directory download slowly over and over, do
9829 not automatically give up after the 254th failure. Bugfix on
9831 - Resume reporting accurate "stream end" reasons to the local control
9832 port. They were lost in the changes for Proposal 148. Bugfix on
9835 o Deprecated and removed features:
9836 - The old "tor --version --version" command, which would print out
9837 the subversion "Id" of most of the source files, is now removed. It
9838 turned out to be less useful than we'd expected, and harder to
9841 o Code simplifications and refactoring:
9842 - Change our header file guard macros to be less likely to conflict
9843 with system headers. Adam Langley noticed that we were conflicting
9844 with log.h on Android.
9845 - Tool-assisted documentation cleanup. Nearly every function or
9846 static variable in Tor should have its own documentation now.
9849 Changes in version 0.2.1.9-alpha - 2008-12-25
9850 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
9852 o New directory authorities:
9853 - gabelmoo (the authority run by Karsten Loesing) now has a new
9857 - Never use a connection with a mismatched address to extend a
9858 circuit, unless that connection is canonical. A canonical
9859 connection is one whose address is authenticated by the router's
9860 identity key, either in a NETINFO cell or in a router descriptor.
9861 - Avoid a possible memory corruption bug when receiving hidden service
9862 descriptors. Bugfix on 0.2.1.6-alpha.
9865 - Fix a logic error that would automatically reject all but the first
9866 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
9867 part of bug 813/868. Bug spotted by coderman.
9868 - When a stream at an exit relay is in state "resolving" or
9869 "connecting" and it receives an "end" relay cell, the exit relay
9870 would silently ignore the end cell and not close the stream. If
9871 the client never closes the circuit, then the exit relay never
9872 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
9874 - When we can't initialize DNS because the network is down, do not
9875 automatically stop Tor from starting. Instead, retry failed
9876 dns_init() every 10 minutes, and change the exit policy to reject
9877 *:* until one succeeds. Fixes bug 691.
9880 - Give a better error message when an overzealous init script says
9881 "sudo -u username tor --user username". Makes Bug 882 easier for
9883 - When a directory authority gives us a new guess for our IP address,
9884 log which authority we used. Hopefully this will help us debug
9885 the recent complaints about bad IP address guesses.
9886 - Detect svn revision properly when we're using git-svn.
9887 - Try not to open more than one descriptor-downloading connection
9888 to an authority at once. This should reduce load on directory
9889 authorities. Fixes bug 366.
9890 - Add cross-certification to newly generated certificates, so that
9891 a signing key is enough information to look up a certificate.
9892 Partial implementation of proposal 157.
9893 - Start serving certificates by <identity digest, signing key digest>
9894 pairs. Partial implementation of proposal 157.
9895 - Clients now never report any stream end reason except 'MISC'.
9896 Implements proposal 148.
9897 - On platforms with a maximum syslog string length, truncate syslog
9898 messages to that length ourselves, rather than relying on the
9899 system to do it for us.
9900 - Optimize out calls to time(NULL) that occur for every IO operation,
9901 or for every cell. On systems where time() is a slow syscall,
9902 this fix will be slightly helpful.
9903 - Exit servers can now answer resolve requests for ip6.arpa addresses.
9904 - When we download a descriptor that we then immediately (as
9905 a directory authority) reject, do not retry downloading it right
9906 away. Should save some bandwidth on authorities. Fix for bug
9907 888. Patch by Sebastian Hahn.
9908 - When a download gets us zero good descriptors, do not notify
9909 Tor that new directory information has arrived.
9910 - Avoid some nasty corner cases in the logic for marking connections
9911 as too old or obsolete or noncanonical for circuits. Partial
9914 o Minor features (controller):
9915 - New CONSENSUS_ARRIVED event to note when a new consensus has
9916 been fetched and validated.
9917 - When we realize that another process has modified our cached
9918 descriptors file, print out a more useful error message rather
9919 than triggering an assertion. Fixes bug 885. Patch from Karsten.
9920 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
9921 controllers to prevent SIGHUP from reloading the
9922 configuration. Fixes bug 856.
9925 - Resume using the correct "REASON=" stream when telling the
9926 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
9927 - When a canonical connection appears later in our internal list
9928 than a noncanonical one for a given OR ID, always use the
9929 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
9931 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9932 seconds. Warn the user if lower values are given in the
9933 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9934 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9935 user if lower values are given in the configuration. Bugfix on
9936 0.1.1.17-rc. Patch by Sebastian.
9937 - Fix a race condition when freeing keys shared between main thread
9938 and CPU workers that could result in a memory leak. Bugfix on
9939 0.1.0.1-rc. Fixes bug 889.
9941 o Minor bugfixes (hidden services):
9942 - Do not throw away existing introduction points on SIGHUP (bugfix on
9943 0.0.6pre1); also, do not stall hidden services because we're
9944 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
9945 by John Brooks. Patch by Karsten. Fixes bug 874.
9946 - Fix a memory leak when we decline to add a v2 rendezvous
9947 descriptor to the cache because we already had a v0 descriptor
9948 with the same ID. Bugfix on 0.2.0.18-alpha.
9950 o Deprecated and removed features:
9951 - RedirectExits has been removed. It was deprecated since
9953 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
9954 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
9955 - Cell pools are now always enabled; --disable-cell-pools is ignored.
9957 o Code simplifications and refactoring:
9958 - Rename the confusing or_is_obsolete field to the more appropriate
9959 is_bad_for_new_circs, and move it to or_connection_t where it
9961 - Move edge-only flags from connection_t to edge_connection_t: not
9962 only is this better coding, but on machines of plausible alignment,
9963 it should save 4-8 bytes per connection_t. "Every little bit helps."
9964 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
9965 for consistency; keep old option working for backward compatibility.
9966 - Simplify the code for finding connections to use for a circuit.
9969 Changes in version 0.2.1.8-alpha - 2008-12-08
9970 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
9971 builds better on unusual platforms like Solaris and old OS X, and
9972 fixes a variety of other issues.
9975 - New DirPortFrontPage option that takes an html file and publishes
9976 it as "/" on the DirPort. Now relay operators can provide a
9977 disclaimer without needing to set up a separate webserver. There's
9978 a sample disclaimer in contrib/tor-exit-notice.html.
9981 - When the client is choosing entry guards, now it selects at most
9982 one guard from a given relay family. Otherwise we could end up with
9983 all of our entry points into the network run by the same operator.
9984 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
9987 - Fix a DOS opportunity during the voting signature collection process
9988 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9989 - Fix a possible segfault when establishing an exit connection. Bugfix
9993 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
9995 - Made Tor a little less aggressive about deleting expired
9996 certificates. Partial fix for bug 854.
9997 - Stop doing unaligned memory access that generated bus errors on
9998 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
9999 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
10000 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
10001 - Make USR2 log-level switch take effect immediately. Bugfix on
10003 - If one win32 nameserver fails to get added, continue adding the
10004 rest, and don't automatically fail.
10005 - Use fcntl() for locking when flock() is not available. Should fix
10006 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
10007 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10008 could make gcc generate non-functional binary search code. Bugfix
10010 - Build correctly on platforms without socklen_t.
10011 - Avoid potential crash on internal error during signature collection.
10012 Fixes bug 864. Patch from rovv.
10013 - Do not use C's stdio library for writing to log files. This will
10014 improve logging performance by a minute amount, and will stop
10015 leaking fds when our disk is full. Fixes bug 861.
10016 - Stop erroneous use of O_APPEND in cases where we did not in fact
10017 want to re-seek to the end of a file before every last write().
10018 - Correct handling of possible malformed authority signing key
10019 certificates with internal signature types. Fixes bug 880. Bugfix
10021 - Fix a hard-to-trigger resource leak when logging credential status.
10025 - Directory mirrors no longer fetch the v1 directory or
10026 running-routers files. They are obsolete, and nobody asks for them
10027 anymore. This is the first step to making v1 authorities obsolete.
10029 o Minor features (controller):
10030 - Return circuit purposes in response to GETINFO circuit-status. Fixes
10034 Changes in version 0.2.0.32 - 2008-11-20
10035 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
10036 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10037 a smaller security flaw that might allow an attacker to access local
10038 services, further improves hidden service performance, and fixes a
10039 variety of other issues.
10042 - The "User" and "Group" config options did not clear the
10043 supplementary group entries for the Tor process. The "User" option
10044 is now more robust, and we now set the groups to the specified
10045 user's primary group. The "Group" option is now ignored. For more
10046 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10047 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10048 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
10049 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10050 consistently obeyed: if an exit relay refuses a stream because its
10051 exit policy doesn't allow it, we would remember what IP address
10052 the relay said the destination address resolves to, even if it's
10053 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10056 - Fix a DOS opportunity during the voting signature collection process
10057 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
10059 o Major bugfixes (hidden services):
10060 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10061 we were failing the whole hidden service request when the v0
10062 descriptor fetch fails, even if the v2 fetch is still pending and
10063 might succeed. Similarly, if the last v2 fetch fails, we were
10064 failing the whole hidden service request even if a v0 fetch is
10065 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10066 - When extending a circuit to a hidden service directory to upload a
10067 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10068 requests failed, because the router descriptor has not been
10069 downloaded yet. In these cases, do not attempt to upload the
10070 rendezvous descriptor, but wait until the router descriptor is
10071 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
10072 descriptor from a hidden service directory for which the router
10073 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
10077 - Fix several infrequent memory leaks spotted by Coverity.
10078 - When testing for libevent functions, set the LDFLAGS variable
10079 correctly. Found by Riastradh.
10080 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10081 bootstrapping with tunneled directory connections. Bugfix on
10082 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10083 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10084 and we know that server B rejects most-but-not all connections to
10085 port 80, we would previously reject the connection. Now, we assume
10086 the user knows what they were asking for. Fixes bug 752. Bugfix
10087 on 0.0.9rc5. Diagnosed by BarkerJr.
10088 - If we overrun our per-second write limits a little, count this as
10089 having used up our write allocation for the second, and choke
10090 outgoing directory writes. Previously, we had only counted this when
10091 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
10092 Bugfix on 0.2.0.x (??).
10093 - Remove the old v2 directory authority 'lefkada' from the default
10094 list. It has been gone for many months.
10095 - Stop doing unaligned memory access that generated bus errors on
10096 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
10097 - Make USR2 log-level switch take effect immediately. Bugfix on
10100 o Minor bugfixes (controller):
10101 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
10102 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
10105 Changes in version 0.2.1.7-alpha - 2008-11-08
10106 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
10107 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10108 a smaller security flaw that might allow an attacker to access local
10109 services, adds better defense against DNS poisoning attacks on exit
10110 relays, further improves hidden service performance, and fixes a
10111 variety of other issues.
10114 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10115 consistently obeyed: if an exit relay refuses a stream because its
10116 exit policy doesn't allow it, we would remember what IP address
10117 the relay said the destination address resolves to, even if it's
10118 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10119 - The "User" and "Group" config options did not clear the
10120 supplementary group entries for the Tor process. The "User" option
10121 is now more robust, and we now set the groups to the specified
10122 user's primary group. The "Group" option is now ignored. For more
10123 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10124 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10125 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
10126 - Do not use or believe expired v3 authority certificates. Patch
10127 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
10130 - Now NodeFamily and MyFamily config options allow spaces in
10131 identity fingerprints, so it's easier to paste them in.
10132 Suggested by Lucky Green.
10133 - Implement the 0x20 hack to better resist DNS poisoning: set the
10134 case on outgoing DNS requests randomly, and reject responses that do
10135 not match the case correctly. This logic can be disabled with the
10136 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
10137 of servers that do not reliably preserve case in replies. See
10138 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10140 - Preserve case in replies to DNSPort requests in order to support
10141 the 0x20 hack for resisting DNS poisoning attacks.
10143 o Hidden service performance improvements:
10144 - When the client launches an introduction circuit, retry with a
10145 new circuit after 30 seconds rather than 60 seconds.
10146 - Launch a second client-side introduction circuit in parallel
10147 after a delay of 15 seconds (based on work by Christian Wilms).
10148 - Hidden services start out building five intro circuits rather
10149 than three, and when the first three finish they publish a service
10150 descriptor using those. Now we publish our service descriptor much
10151 faster after restart.
10154 - Minor fix in the warning messages when you're having problems
10155 bootstrapping; also, be more forgiving of bootstrap problems when
10156 we're still making incremental progress on a given bootstrap phase.
10157 - When we're choosing an exit node for a circuit, and we have
10158 no pending streams, choose a good general exit rather than one that
10159 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10160 - Send a valid END cell back when a client tries to connect to a
10161 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10162 840. Patch from rovv.
10163 - If a broken client asks a non-exit router to connect somewhere,
10164 do not even do the DNS lookup before rejecting the connection.
10165 Fixes another case of bug 619. Patch from rovv.
10166 - Fix another case of assuming, when a specific exit is requested,
10167 that we know more than the user about what hosts it allows.
10168 Fixes another case of bug 752. Patch from rovv.
10169 - Check which hops rendezvous stream cells are associated with to
10170 prevent possible guess-the-streamid injection attacks from
10171 intermediate hops. Fixes another case of bug 446. Based on patch
10173 - Avoid using a negative right-shift when comparing 32-bit
10174 addresses. Possible fix for bug 845 and bug 811.
10175 - Make the assert_circuit_ok() function work correctly on circuits that
10176 have already been marked for close.
10177 - Fix read-off-the-end-of-string error in unit tests when decoding
10178 introduction points.
10179 - Fix uninitialized size field for memory area allocation: may improve
10180 memory performance during directory parsing.
10181 - Treat duplicate certificate fetches as failures, so that we do
10182 not try to re-fetch an expired certificate over and over and over.
10183 - Do not say we're fetching a certificate when we'll in fact skip it
10184 because of a pending download.
10187 Changes in version 0.2.1.6-alpha - 2008-09-30
10188 Tor 0.2.1.6-alpha further improves performance and robustness of
10189 hidden services, starts work on supporting per-country relay selection,
10190 and fixes a variety of smaller issues.
10193 - Implement proposal 121: make it possible to build hidden services
10194 that only certain clients are allowed to connect to. This is
10195 enforced at several points, so that unauthorized clients are unable
10196 to send INTRODUCE cells to the service, or even (depending on the
10197 type of authentication) to learn introduction points. This feature
10198 raises the bar for certain kinds of active attacks against hidden
10199 services. Code by Karsten Loesing.
10200 - Relays now store and serve v2 hidden service descriptors by default,
10201 i.e., the new default value for HidServDirectoryV2 is 1. This is
10202 the last step in proposal 114, which aims to make hidden service
10203 lookups more reliable.
10204 - Start work to allow node restrictions to include country codes. The
10205 syntax to exclude nodes in a country with country code XX is
10206 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
10207 refinement to decide what config options should take priority if
10208 you ask to both use a particular node and exclude it.
10209 - Allow ExitNodes list to include IP ranges and country codes, just
10210 like the Exclude*Nodes lists. Patch from Robert Hogan.
10213 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
10214 Tor to fail to start if you had it configured to use a bridge
10215 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
10216 - When extending a circuit to a hidden service directory to upload a
10217 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10218 requests failed, because the router descriptor had not been
10219 downloaded yet. In these cases, we now wait until the router
10220 descriptor is downloaded, and then retry. Likewise, clients
10221 now skip over a hidden service directory if they don't yet have
10222 its router descriptor, rather than futilely requesting it and
10223 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
10225 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10226 we were failing the whole hidden service request when the v0
10227 descriptor fetch fails, even if the v2 fetch is still pending and
10228 might succeed. Similarly, if the last v2 fetch fails, we were
10229 failing the whole hidden service request even if a v0 fetch is
10230 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10231 - DNS replies need to have names matching their requests, but
10232 these names should be in the questions section, not necessarily
10233 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
10236 - Update to the "September 1 2008" ip-to-country file.
10237 - Allow ports 465 and 587 in the default exit policy again. We had
10238 rejected them in 0.1.0.15, because back in 2005 they were commonly
10239 misconfigured and ended up as spam targets. We hear they are better
10240 locked down these days.
10241 - Use a lockfile to make sure that two Tor processes are not
10242 simultaneously running with the same datadir.
10243 - Serve the latest v3 networkstatus consensus via the control
10244 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
10245 - Better logging about stability/reliability calculations on directory
10247 - Drop the requirement to have an open dir port for storing and
10248 serving v2 hidden service descriptors.
10249 - Directory authorities now serve a /tor/dbg-stability.txt URL to
10250 help debug WFU and MTBF calculations.
10251 - Implement most of Proposal 152: allow specialized servers to permit
10252 single-hop circuits, and clients to use those servers to build
10253 single-hop circuits when using a specialized controller. Patch
10254 from Josh Albrecht. Resolves feature request 768.
10255 - Add a -p option to tor-resolve for specifying the SOCKS port: some
10256 people find host:port too confusing.
10257 - Make TrackHostExit mappings expire a while after their last use, not
10258 after their creation. Patch from Robert Hogan.
10259 - Provide circuit purposes along with circuit events to the controller.
10262 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
10264 - Fixed some memory leaks -- some quite frequent, some almost
10265 impossible to trigger -- based on results from Coverity.
10266 - When testing for libevent functions, set the LDFLAGS variable
10267 correctly. Found by Riastradh.
10268 - Fix an assertion bug in parsing policy-related options; possible fix
10270 - Catch and report a few more bootstrapping failure cases when Tor
10271 fails to establish a TCP connection. Cleanup on 0.2.1.x.
10272 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10273 bootstrapping with tunneled directory connections. Bugfix on
10274 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10275 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10276 and we know that server B rejects most-but-not all connections to
10277 port 80, we would previously reject the connection. Now, we assume
10278 the user knows what they were asking for. Fixes bug 752. Bugfix
10279 on 0.0.9rc5. Diagnosed by BarkerJr.
10280 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
10281 service directories if they have no advertised dir port. Bugfix
10283 - If we overrun our per-second write limits a little, count this as
10284 having used up our write allocation for the second, and choke
10285 outgoing directory writes. Previously, we had only counted this when
10286 we had met our limits precisely. Fixes bug 824. Patch by rovv.
10287 Bugfix on 0.2.0.x (??).
10288 - Avoid a "0 divided by 0" calculation when calculating router uptime
10289 at directory authorities. Bugfix on 0.2.0.8-alpha.
10290 - Make DNS resolved controller events into "CLOSED", not
10291 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
10293 - Fix a bug where an unreachable relay would establish enough
10294 reachability testing circuits to do a bandwidth test -- if
10295 we already have a connection to the middle hop of the testing
10296 circuit, then it could establish the last hop by using the existing
10297 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
10298 circuits no longer use entry guards in 0.2.1.3-alpha.
10299 - If we have correct permissions on $datadir, we complain to stdout
10300 and fail to start. But dangerous permissions on
10301 $datadir/cached-status/ would cause us to open a log and complain
10302 there. Now complain to stdout and fail to start in both cases. Fixes
10303 bug 820, reported by seeess.
10304 - Remove the old v2 directory authority 'lefkada' from the default
10305 list. It has been gone for many months.
10307 o Code simplifications and refactoring:
10308 - Revise the connection_new functions so that a more typesafe variant
10309 exists. This will work better with Coverity, and let us find any
10310 actual mistakes we're making here.
10311 - Refactor unit testing logic so that dmalloc can be used sensibly
10312 with unit tests to check for memory leaks.
10313 - Move all hidden-service related fields from connection and circuit
10314 structure to substructures: this way they won't eat so much memory.
10317 Changes in version 0.2.0.31 - 2008-09-03
10318 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10319 a big bug we're seeing where in rare cases traffic from one Tor stream
10320 gets mixed into another stream, and fixes a variety of smaller issues.
10323 - Make sure that two circuits can never exist on the same connection
10324 with the same circuit ID, even if one is marked for close. This
10325 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10326 - Relays now reject risky extend cells: if the extend cell includes
10327 a digest of all zeroes, or asks to extend back to the relay that
10328 sent the extend cell, tear down the circuit. Ideas suggested
10330 - If not enough of our entry guards are available so we add a new
10331 one, we might use the new one even if it overlapped with the
10332 current circuit's exit relay (or its family). Anonymity bugfix
10333 pointed out by rovv.
10336 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10337 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10338 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10339 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10340 - Pick size of default geoip filename string correctly on windows.
10341 Fixes bug 806. Bugfix on 0.2.0.30.
10342 - Make the autoconf script accept the obsolete --with-ssl-dir
10343 option as an alias for the actually-working --with-openssl-dir
10344 option. Fix the help documentation to recommend --with-openssl-dir.
10345 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10346 - When using the TransPort option on OpenBSD, and using the User
10347 option to change UID and drop privileges, make sure to open
10348 /dev/pf before dropping privileges. Fixes bug 782. Patch from
10349 Christopher Davis. Bugfix on 0.1.2.1-alpha.
10350 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10351 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10352 on the client side when connecting to a hidden service. Bugfix
10353 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10354 - When closing an application-side connection because its circuit is
10355 getting torn down, generate the stream event correctly. Bugfix on
10356 0.1.2.x. Anonymous patch.
10359 Changes in version 0.2.1.5-alpha - 2008-08-31
10360 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
10361 in a lot of the infrastructure for adding authorization to hidden
10362 services, lays the groundwork for having clients read their load
10363 balancing information out of the networkstatus consensus rather than
10364 the individual router descriptors, addresses two potential anonymity
10365 issues, and fixes a variety of smaller issues.
10368 - Convert many internal address representations to optionally hold
10370 - Generate and accept IPv6 addresses in many protocol elements.
10371 - Make resolver code handle nameservers located at ipv6 addresses.
10372 - Begin implementation of proposal 121 ("Client authorization for
10373 hidden services"): configure hidden services with client
10374 authorization, publish descriptors for them, and configure
10375 authorization data for hidden services at clients. The next
10376 step is to actually access hidden services that perform client
10378 - More progress toward proposal 141: Network status consensus
10379 documents and votes now contain bandwidth information for each
10380 router and a summary of that router's exit policy. Eventually this
10381 will be used by clients so that they do not have to download every
10382 known descriptor before building circuits.
10384 o Major bugfixes (on 0.2.0.x and before):
10385 - When sending CREATED cells back for a given circuit, use a 64-bit
10386 connection ID to find the right connection, rather than an addr:port
10387 combination. Now that we can have multiple OR connections between
10388 the same ORs, it is no longer possible to use addr:port to uniquely
10389 identify a connection.
10390 - Relays now reject risky extend cells: if the extend cell includes
10391 a digest of all zeroes, or asks to extend back to the relay that
10392 sent the extend cell, tear down the circuit. Ideas suggested
10394 - If not enough of our entry guards are available so we add a new
10395 one, we might use the new one even if it overlapped with the
10396 current circuit's exit relay (or its family). Anonymity bugfix
10397 pointed out by rovv.
10400 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10401 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10402 - When using the TransPort option on OpenBSD, and using the User
10403 option to change UID and drop privileges, make sure to open /dev/pf
10404 before dropping privileges. Fixes bug 782. Patch from Christopher
10405 Davis. Bugfix on 0.1.2.1-alpha.
10406 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10407 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10408 - Add a missing safe_str() call for a debug log message.
10409 - Use 64 bits instead of 32 bits for connection identifiers used with
10410 the controller protocol, to greatly reduce risk of identifier reuse.
10411 - Make the autoconf script accept the obsolete --with-ssl-dir
10412 option as an alias for the actually-working --with-openssl-dir
10413 option. Fix the help documentation to recommend --with-openssl-dir.
10414 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10417 - Rate-limit too-many-sockets messages: when they happen, they happen
10418 a lot. Resolves bug 748.
10419 - Resist DNS poisoning a little better by making sure that names in
10420 answer sections match.
10421 - Print the SOCKS5 error message string as well as the error code
10422 when a tor-resolve request fails. Patch from Jacob.
10425 Changes in version 0.2.1.4-alpha - 2008-08-04
10426 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
10429 - The address part of exit policies was not correctly written
10430 to router descriptors. This generated router descriptors that failed
10431 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
10433 - Tor triggered a false assert when extending a circuit to a relay
10434 but we already have a connection open to that relay. Noticed by
10435 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
10438 - Fix a hidden service logging bug: in some edge cases, the router
10439 descriptor of a previously picked introduction point becomes
10440 obsolete and we need to give up on it rather than continually
10441 complaining that it has become obsolete. Observed by xiando. Bugfix
10444 o Removed features:
10445 - Take out the TestVia config option, since it was a workaround for
10446 a bug that was fixed in Tor 0.1.1.21.
10449 Changes in version 0.2.1.3-alpha - 2008-08-03
10450 Tor 0.2.1.3-alpha implements most of the pieces to prevent
10451 infinite-length circuit attacks (see proposal 110); fixes a bug that
10452 might cause exit relays to corrupt streams they send back; allows
10453 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
10454 ExcludeExitNodes config options; and fixes a big pile of bugs.
10456 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
10457 - Send a bootstrap problem "warn" event on the first problem if the
10458 reason is NO_ROUTE (that is, our network is down).
10461 - Implement most of proposal 110: The first K cells to be sent
10462 along a circuit are marked as special "early" cells; only K "early"
10463 cells will be allowed. Once this code is universal, we can block
10464 certain kinds of DOS attack by requiring that EXTEND commands must
10465 be sent using an "early" cell.
10468 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10469 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10470 on the client side when connecting to a hidden service. Bugfix
10471 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10472 - Ensure that two circuits can never exist on the same connection
10473 with the same circuit ID, even if one is marked for close. This
10474 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
10477 - When relays do their initial bandwidth measurement, don't limit
10478 to just our entry guards for the test circuits. Otherwise we tend
10479 to have multiple test circuits going through a single entry guard,
10480 which makes our bandwidth test less accurate. Fixes part of bug 654;
10481 patch contributed by Josh Albrecht.
10482 - Add an ExcludeExitNodes option so users can list a set of nodes
10483 that should be be excluded from the exit node position, but
10484 allowed elsewhere. Implements proposal 151.
10485 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
10486 ExcludeNodes and ExcludeExitNodes lists.
10487 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
10488 be more efficient. Formerly it was quadratic in the number of
10489 servers; now it should be linear. Fixes bug 509.
10490 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
10491 and n_conn_id_digest fields into a separate structure that's
10492 only needed when the circuit has not yet attached to an n_conn.
10495 - Change the contrib/tor.logrotate script so it makes the new
10496 logs as "_tor:_tor" rather than the default, which is generally
10497 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
10498 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
10499 warnings (occasionally), but it can also cause the compiler to
10500 eliminate error-checking code. Suggested by Peter Gutmann.
10501 - When a hidden service is giving up on an introduction point candidate
10502 that was not included in the last published rendezvous descriptor,
10503 don't reschedule publication of the next descriptor. Fixes bug 763.
10505 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
10506 HiddenServiceExcludeNodes as obsolete: they never worked properly,
10507 and nobody claims to be using them. Fixes bug 754. Bugfix on
10508 0.1.0.1-rc. Patch from Christian Wilms.
10509 - Fix a small alignment and memory-wasting bug on buffer chunks.
10512 o Minor bugfixes (controller):
10513 - When closing an application-side connection because its circuit
10514 is getting torn down, generate the stream event correctly.
10515 Bugfix on 0.1.2.x. Anonymous patch.
10517 o Removed features:
10518 - Remove all backward-compatibility code to support relays running
10519 versions of Tor so old that they no longer work at all on the
10523 Changes in version 0.2.0.30 - 2008-07-15
10525 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
10526 warnings (occasionally), but it can also cause the compiler to
10527 eliminate error-checking code. Suggested by Peter Gutmann.
10530 Changes in version 0.2.0.29-rc - 2008-07-08
10531 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
10532 hidden-service performance bugs, and fixes a bunch of smaller bugs.
10535 - If you have more than one bridge but don't know their keys,
10536 you would only launch a request for the descriptor of the first one
10537 on your list. (Tor considered launching requests for the others, but
10538 found that it already had a connection on the way for $0000...0000
10539 so it didn't open another.) Bugfix on 0.2.0.x.
10540 - If you have more than one bridge but don't know their keys, and the
10541 connection to one of the bridges failed, you would cancel all
10542 pending bridge connections. (After all, they all have the same
10543 digest.) Bugfix on 0.2.0.x.
10544 - When a hidden service was trying to establish an introduction point,
10545 and Tor had built circuits preemptively for such purposes, we
10546 were ignoring all the preemptive circuits and launching a new one
10547 instead. Bugfix on 0.2.0.14-alpha.
10548 - When a hidden service was trying to establish an introduction point,
10549 and Tor *did* manage to reuse one of the preemptively built
10550 circuits, it didn't correctly remember which one it used,
10551 so it asked for another one soon after, until there were no
10552 more preemptive circuits, at which point it launched one from
10553 scratch. Bugfix on 0.0.9.x.
10554 - Make directory servers include the X-Your-Address-Is: http header in
10555 their responses even for begin_dir conns. Now clients who only
10556 ever use begin_dir connections still have a way to learn their IP
10557 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
10560 - Fix a macro/CPP interaction that was confusing some compilers:
10561 some GCCs don't like #if/#endif pairs inside macro arguments.
10563 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
10564 Fixes bug 704; fix from Steven Murdoch.
10565 - When opening /dev/null in finish_daemonize(), do not pass the
10566 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
10567 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
10568 - Correctly detect transparent proxy support on Linux hosts that
10569 require in.h to be included before netfilter_ipv4.h. Patch
10571 - Disallow session resumption attempts during the renegotiation
10572 stage of the v2 handshake protocol. Clients should never be trying
10573 session resumption at this point, but apparently some did, in
10574 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
10575 found by Geoff Goodell.
10578 Changes in version 0.2.1.2-alpha - 2008-06-20
10579 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
10580 make it easier to set up your own private Tor network; fixes several
10581 big bugs with using more than one bridge relay; fixes a big bug with
10582 offering hidden services quickly after Tor starts; and uses a better
10583 API for reporting potential bootstrapping problems to the controller.
10586 - New TestingTorNetwork config option to allow adjustment of
10587 previously constant values that, while reasonable, could slow
10588 bootstrapping. Implements proposal 135. Patch from Karsten.
10591 - If you have more than one bridge but don't know their digests,
10592 you would only learn a request for the descriptor of the first one
10593 on your list. (Tor considered launching requests for the others, but
10594 found that it already had a connection on the way for $0000...0000
10595 so it didn't open another.) Bugfix on 0.2.0.x.
10596 - If you have more than one bridge but don't know their digests,
10597 and the connection to one of the bridges failed, you would cancel
10598 all pending bridge connections. (After all, they all have the
10599 same digest.) Bugfix on 0.2.0.x.
10600 - When establishing a hidden service, introduction points that
10601 originate from cannibalized circuits are completely ignored and not
10602 included in rendezvous service descriptors. This might be another
10603 reason for delay in making a hidden service available. Bugfix
10604 from long ago (0.0.9.x?)
10607 - Allow OpenSSL to use dynamic locks if it wants.
10608 - When building a consensus, do not include routers that are down.
10609 This will cut down 30% to 40% on consensus size. Implements
10611 - In directory authorities' approved-routers files, allow
10612 fingerprints with or without space.
10613 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
10614 controller can query our current bootstrap state in case it attaches
10615 partway through and wants to catch up.
10616 - Send an initial "Starting" bootstrap status event, so we have a
10617 state to start out in.
10620 - Asking for a conditional consensus at .../consensus/<fingerprints>
10621 would crash a dirserver if it did not already have a
10622 consensus. Bugfix on 0.2.1.1-alpha.
10623 - Clean up some macro/CPP interactions: some GCC versions don't like
10624 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
10627 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
10628 - Directory authorities shouldn't complain about bootstrapping
10629 problems just because they do a lot of reachability testing and
10630 some of the connection attempts fail.
10631 - Start sending "count" and "recommendation" key/value pairs in
10632 bootstrap problem status events, so the controller can hear about
10633 problems even before Tor decides they're worth reporting for sure.
10634 - If you're using bridges, generate "bootstrap problem" warnings
10635 as soon as you run out of working bridges, rather than waiting
10636 for ten failures -- which will never happen if you have less than
10638 - If we close our OR connection because there's been a circuit
10639 pending on it for too long, we were telling our bootstrap status
10640 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
10643 Changes in version 0.2.1.1-alpha - 2008-06-13
10644 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
10645 were making the Tor process bloat especially on Linux; makes our TLS
10646 handshake blend in better; sends "bootstrap phase" status events to
10647 the controller, so it can keep the user informed of progress (and
10648 problems) fetching directory information and establishing circuits;
10649 and adds a variety of smaller features.
10652 - More work on making our TLS handshake blend in: modify the list
10653 of ciphers advertised by OpenSSL in client mode to even more
10654 closely resemble a common web browser. We cheat a little so that
10655 we can advertise ciphers that the locally installed OpenSSL doesn't
10657 - Start sending "bootstrap phase" status events to the controller,
10658 so it can keep the user informed of progress fetching directory
10659 information and establishing circuits. Also inform the controller
10660 if we think we're stuck at a particular bootstrap phase. Implements
10662 - Resume using OpenSSL's RAND_poll() for better (and more portable)
10663 cross-platform entropy collection again. We used to use it, then
10664 stopped using it because of a bug that could crash systems that
10665 called RAND_poll when they had a lot of fds open. It looks like the
10666 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
10667 at startup, and to call RAND_poll() when we reseed later only if
10668 we have a non-buggy OpenSSL version.
10671 - When we choose to abandon a new entry guard because we think our
10672 older ones might be better, close any circuits pending on that
10673 new entry guard connection. This fix should make us recover much
10674 faster when our network is down and then comes back. Bugfix on
10675 0.1.2.8-beta; found by lodger.
10677 o Memory fixes and improvements:
10678 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
10679 to avoid unused RAM in buffer chunks and memory pools.
10680 - Speed up parsing and cut down on memory fragmentation by using
10681 stack-style allocations for parsing directory objects. Previously,
10682 this accounted for over 40% of allocations from within Tor's code
10683 on a typical directory cache.
10684 - Use a Bloom filter rather than a digest-based set to track which
10685 descriptors we need to keep around when we're cleaning out old
10686 router descriptors. This speeds up the computation significantly,
10687 and may reduce fragmentation.
10688 - Reduce the default smartlist size from 32 to 16; it turns out that
10689 most smartlists hold around 8-12 elements tops.
10690 - Make dumpstats() log the fullness and size of openssl-internal
10692 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
10693 patch to their OpenSSL, turn it on to save memory on servers. This
10694 patch will (with any luck) get included in a mainline distribution
10696 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10697 compress cells, which are basically all encrypted, compressed,
10701 - Stop reloading the router list from disk for no reason when we
10702 run out of reachable directory mirrors. Once upon a time reloading
10703 it would set the 'is_running' flag back to 1 for them. It hasn't
10704 done that for a long time.
10705 - In very rare situations new hidden service descriptors were
10706 published earlier than 30 seconds after the last change to the
10707 service. (We currently think that a hidden service descriptor
10708 that's been stable for 30 seconds is worth publishing.)
10711 - Allow separate log levels to be configured for different logging
10712 domains. For example, this allows one to log all notices, warnings,
10713 or errors, plus all memory management messages of level debug or
10714 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
10715 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
10716 and stop using a warning that had become unfixably verbose under
10718 - New --hush command-line option similar to --quiet. While --quiet
10719 disables all logging to the console on startup, --hush limits the
10720 output to messages of warning and error severity.
10721 - Servers support a new URL scheme for consensus downloads that
10722 allows the client to specify which authorities are trusted.
10723 The server then only sends the consensus if the client will trust
10724 it. Otherwise a 404 error is sent back. Clients use this
10725 new scheme when the server supports it (meaning it's running
10726 0.2.1.1-alpha or later). Implements proposal 134.
10727 - New configure/torrc options (--enable-geoip-stats,
10728 DirRecordUsageByCountry) to record how many IPs we've served
10729 directory info to in each country code, how many status documents
10730 total we've sent to each country code, and what share of the total
10731 directory requests we should expect to see.
10732 - Use the TLS1 hostname extension to more closely resemble browser
10734 - Lots of new unit tests.
10735 - Add a macro to implement the common pattern of iterating through
10736 two parallel lists in lockstep.
10739 Changes in version 0.2.0.28-rc - 2008-06-13
10740 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
10741 performance bug, and fixes a bunch of smaller bugs.
10744 - Fix a bug where, when we were choosing the 'end stream reason' to
10745 put in our relay end cell that we send to the exit relay, Tor
10746 clients on Windows were sometimes sending the wrong 'reason'. The
10747 anonymity problem is that exit relays may be able to guess whether
10748 the client is running Windows, thus helping partition the anonymity
10749 set. Down the road we should stop sending reasons to exit relays,
10750 or otherwise prevent future versions of this bug.
10753 - While setting up a hidden service, some valid introduction circuits
10754 were overlooked and abandoned. This might be the reason for
10755 the long delay in making a hidden service available. Bugfix on
10759 - Update to the "June 9 2008" ip-to-country file.
10760 - Run 'make test' as part of 'make dist', so we stop releasing so
10761 many development snapshots that fail their unit tests.
10764 - When we're checking if we have enough dir info for each relay
10765 to begin establishing circuits, make sure that we actually have
10766 the descriptor listed in the consensus, not just any descriptor.
10768 - Bridge relays no longer print "xx=0" in their extrainfo document
10769 for every single country code in the geoip db. Bugfix on
10771 - Only warn when we fail to load the geoip file if we were planning to
10772 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
10773 - If we change our MaxAdvertisedBandwidth and then reload torrc,
10774 Tor won't realize it should publish a new relay descriptor. Fixes
10775 bug 688, reported by mfr. Bugfix on 0.1.2.x.
10776 - When we haven't had any application requests lately, don't bother
10777 logging that we have expired a bunch of descriptors. Bugfix
10779 - Make relay cells written on a connection count as non-padding when
10780 tracking how long a connection has been in use. Bugfix on
10781 0.2.0.1-alpha. Spotted by lodger.
10782 - Fix unit tests in 0.2.0.27-rc.
10783 - Fix compile on Windows.
10786 Changes in version 0.2.0.27-rc - 2008-06-03
10787 Tor 0.2.0.27-rc adds a few features we left out of the earlier
10788 release candidates. In particular, we now include an IP-to-country
10789 GeoIP database, so controllers can easily look up what country a
10790 given relay is in, and so bridge relays can give us some sanitized
10791 summaries about which countries are making use of bridges. (See proposal
10792 126-geoip-fetching.txt for details.)
10795 - Include an IP-to-country GeoIP file in the tarball, so bridge
10796 relays can report sanitized summaries of the usage they're seeing.
10799 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
10800 Robert Hogan. Fixes the first part of bug 681.
10801 - Make bridge authorities never serve extrainfo docs.
10802 - Add support to detect Libevent versions in the 1.4.x series
10804 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
10805 - Include a new contrib/tor-exit-notice.html file that exit relay
10806 operators can put on their website to help reduce abuse queries.
10809 - When tunneling an encrypted directory connection, and its first
10810 circuit fails, do not leave it unattached and ask the controller
10811 to deal. Fixes the second part of bug 681.
10812 - Make bridge authorities correctly expire old extrainfo documents
10816 Changes in version 0.2.0.26-rc - 2008-05-13
10817 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
10818 in Debian's OpenSSL packages. All users running any 0.2.0.x version
10819 should upgrade, whether they're running Debian or not.
10821 o Major security fixes:
10822 - Use new V3 directory authority keys on the tor26, gabelmoo, and
10823 moria1 V3 directory authorities. The old keys were generated with
10824 a vulnerable version of Debian's OpenSSL package, and must be
10825 considered compromised. Other authorities' keys were not generated
10826 with an affected version of OpenSSL.
10829 - List authority signatures as "unrecognized" based on DirServer
10830 lines, not on cert cache. Bugfix on 0.2.0.x.
10833 - Add a new V3AuthUseLegacyKey option to make it easier for
10834 authorities to change their identity keys if they have to.
10837 Changes in version 0.2.0.25-rc - 2008-04-23
10838 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
10841 - Remember to initialize threading before initializing logging.
10842 Otherwise, many BSD-family implementations will crash hard on
10843 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
10846 - Authorities correctly free policies on bad servers on
10847 exit. Fixes bug 672. Bugfix on 0.2.0.x.
10850 Changes in version 0.2.0.24-rc - 2008-04-22
10851 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
10852 v3 directory authority, makes relays with dynamic IP addresses and no
10853 DirPort notice more quickly when their IP address changes, fixes a few
10854 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
10856 o New directory authorities:
10857 - Take lefkada out of the list of v3 directory authorities, since
10858 it has been down for months.
10859 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
10863 - Detect address changes more quickly on non-directory mirror
10864 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
10866 o Minor features (security):
10867 - Reject requests for reverse-dns lookup of names that are in
10868 a private address space. Patch from lodger.
10869 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
10872 o Minor bugfixes (crashes):
10873 - Avoid a rare assert that can trigger when Tor doesn't have much
10874 directory information yet and it tries to fetch a v2 hidden
10875 service descriptor. Fixes bug 651, reported by nwf.
10876 - Initialize log mutex before initializing dmalloc. Otherwise,
10877 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
10878 - Use recursive pthread mutexes in order to avoid deadlock when
10879 logging debug-level messages to a controller. Bug spotted by nwf,
10880 bugfix on 0.2.0.16-alpha.
10882 o Minor bugfixes (resource management):
10883 - Keep address policies from leaking memory: start their refcount
10884 at 1, not 2. Bugfix on 0.2.0.16-alpha.
10885 - Free authority certificates on exit, so they don't look like memory
10886 leaks. Bugfix on 0.2.0.19-alpha.
10887 - Free static hashtables for policy maps and for TLS connections on
10888 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
10889 - Avoid allocating extra space when computing consensuses on 64-bit
10890 platforms. Bug spotted by aakova.
10892 o Minor bugfixes (misc):
10893 - Do not read the configuration file when we've only been told to
10894 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
10895 based on patch from Sebastian Hahn.
10896 - Exit relays that are used as a client can now reach themselves
10897 using the .exit notation, rather than just launching an infinite
10898 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
10899 - When attempting to open a logfile fails, tell us why.
10900 - Fix a dumb bug that was preventing us from knowing that we should
10901 preemptively build circuits to handle expected directory requests.
10902 Fixes bug 660. Bugfix on 0.1.2.x.
10903 - Warn less verbosely about clock skew from netinfo cells from
10904 untrusted sources. Fixes bug 663.
10905 - Make controller stream events for DNS requests more consistent,
10906 by adding "new stream" events for DNS requests, and removing
10907 spurious "stream closed" events" for cached reverse resolves.
10908 Patch from mwenge. Fixes bug 646.
10909 - Correctly notify one-hop connections when a circuit build has
10910 failed. Possible fix for bug 669. Found by lodger.
10913 Changes in version 0.2.0.23-rc - 2008-03-24
10914 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
10915 makes bootstrapping faster if the first directory mirror you contact
10916 is down. The bundles also include the new Vidalia 0.1.2 release.
10919 - When a tunneled directory request is made to a directory server
10920 that's down, notice after 30 seconds rather than 120 seconds. Also,
10921 fail any begindir streams that are pending on it, so they can
10922 retry elsewhere. This was causing multi-minute delays on bootstrap.
10925 Changes in version 0.2.0.22-rc - 2008-03-18
10926 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
10927 enables encrypted directory connections by default for non-relays, fixes
10928 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
10929 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
10932 - Enable encrypted directory connections by default for non-relays,
10933 so censor tools that block Tor directory connections based on their
10934 plaintext patterns will no longer work. This means Tor works in
10935 certain censored countries by default again.
10938 - Make sure servers always request certificates from clients during
10939 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
10940 - Do not enter a CPU-eating loop when a connection is closed in
10941 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
10942 diagnosed by lodger; bugfix on 0.2.0.20-rc.
10943 - Fix assertion failure that could occur when a blocked circuit
10944 became unblocked, and it had pending client DNS requests. Bugfix
10945 on 0.2.0.1-alpha. Fixes bug 632.
10947 o Minor bugfixes (on 0.1.2.x):
10948 - Generate "STATUS_SERVER" events rather than misspelled
10949 "STATUS_SEVER" events. Caught by mwenge.
10950 - When counting the number of bytes written on a TLS connection,
10951 look at the BIO actually used for writing to the network, not
10952 at the BIO used (sometimes) to buffer data for the network.
10953 Looking at different BIOs could result in write counts on the
10954 order of ULONG_MAX. Fixes bug 614.
10955 - On Windows, correctly detect errors when listing the contents of
10956 a directory. Fix from lodger.
10958 o Minor bugfixes (on 0.2.0.x):
10959 - Downgrade "sslv3 alert handshake failure" message to INFO.
10960 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
10961 left BandwidthRate and BandwidthBurst at the default, we would be
10962 silently limited by those defaults. Now raise them to match the
10963 RelayBandwidth* values.
10964 - Fix the SVK version detection logic to work correctly on a branch.
10965 - Make --enable-openbsd-malloc work correctly on Linux with alpha
10966 CPUs. Fixes bug 625.
10967 - Logging functions now check that the passed severity is sane.
10968 - Use proper log levels in the testsuite call of
10969 get_interface_address6().
10970 - When using a nonstandard malloc, do not use the platform values for
10971 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
10972 - Make the openbsd malloc code use 8k pages on alpha CPUs and
10974 - Detect mismatched page sizes when using --enable-openbsd-malloc.
10975 - Avoid double-marked-for-close warning when certain kinds of invalid
10976 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
10977 for bug 617. Bugfix on 0.2.0.1-alpha.
10978 - Make sure that the "NULL-means-reject *:*" convention is followed by
10979 all the policy manipulation functions, avoiding some possible crash
10980 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
10981 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
10982 actually works, and doesn't warn about every single reverse lookup.
10983 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
10986 - Only log guard node status when guard node status has changed.
10987 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
10988 make "INFO" 75% less verbose.
10991 Changes in version 0.2.0.21-rc - 2008-03-02
10992 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
10993 makes Tor work well with Vidalia again, fixes a rare assert bug,
10994 and fixes a pair of more minor bugs. The bundles also include Vidalia
10995 0.1.0 and Torbutton 1.1.16.
10998 - The control port should declare that it requires password auth
10999 when HashedControlSessionPassword is set too. Patch from Matt Edman;
11000 bugfix on 0.2.0.20-rc. Fixes bug 615.
11001 - Downgrade assert in connection_buckets_decrement() to a log message.
11002 This may help us solve bug 614, and in any case will make its
11003 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
11004 - We were sometimes miscounting the number of bytes read from the
11005 network, causing our rate limiting to not be followed exactly.
11006 Bugfix on 0.2.0.16-alpha. Reported by lodger.
11009 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
11010 OpenSSL versions should have been working fine. Diagnosis and patch
11011 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
11012 Bugfix on 0.2.0.20-rc.
11015 Changes in version 0.2.0.20-rc - 2008-02-24
11016 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
11017 makes more progress towards normalizing Tor's TLS handshake, makes
11018 hidden services work better again, helps relays bootstrap if they don't
11019 know their IP address, adds optional support for linking in openbsd's
11020 allocator or tcmalloc, allows really fast relays to scale past 15000
11021 sockets, and fixes a bunch of minor bugs reported by Veracode.
11024 - Enable the revised TLS handshake based on the one designed by
11025 Steven Murdoch in proposal 124, as revised in proposal 130. It
11026 includes version negotiation for OR connections as described in
11027 proposal 105. The new handshake is meant to be harder for censors
11028 to fingerprint, and it adds the ability to detect certain kinds of
11029 man-in-the-middle traffic analysis attacks. The version negotiation
11030 feature will allow us to improve Tor's link protocol more safely
11032 - Choose which bridge to use proportional to its advertised bandwidth,
11033 rather than uniformly at random. This should speed up Tor for
11034 bridge users. Also do this for people who set StrictEntryNodes.
11035 - When a TrackHostExits-chosen exit fails too many times in a row,
11036 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
11039 - Resolved problems with (re-)fetching hidden service descriptors.
11040 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
11041 and 0.2.0.19-alpha.
11042 - If we only ever used Tor for hidden service lookups or posts, we
11043 would stop building circuits and start refusing connections after
11044 24 hours, since we falsely believed that Tor was dormant. Reported
11045 by nwf; bugfix on 0.1.2.x.
11046 - Servers that don't know their own IP address should go to the
11047 authorities for their first directory fetch, even if their DirPort
11048 is off or if they don't know they're reachable yet. This will help
11049 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
11050 - When counting the number of open sockets, count not only the number
11051 of sockets we have received from the socket() call, but also
11052 the number we've gotten from accept() and socketpair(). This bug
11053 made us fail to count all sockets that we were using for incoming
11054 connections. Bugfix on 0.2.0.x.
11055 - Fix code used to find strings within buffers, when those strings
11056 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
11057 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
11058 - Add a new __HashedControlSessionPassword option for controllers
11059 to use for one-off session password hashes that shouldn't get
11060 saved to disk by SAVECONF --- Vidalia users were accumulating a
11061 pile of HashedControlPassword lines in their torrc files, one for
11062 each time they had restarted Tor and then clicked Save. Make Tor
11063 automatically convert "HashedControlPassword" to this new option but
11064 only when it's given on the command line. Partial fix for bug 586.
11066 o Minor features (performance):
11067 - Tune parameters for cell pool allocation to minimize amount of
11069 - Add OpenBSD malloc code from phk as an optional malloc
11070 replacement on Linux: some glibc libraries do very poorly
11071 with Tor's memory allocation patterns. Pass
11072 --enable-openbsd-malloc to get the replacement malloc code.
11073 - Add a --with-tcmalloc option to the configure script to link
11074 against tcmalloc (if present). Does not yet search for
11075 non-system include paths.
11076 - Stop imposing an arbitrary maximum on the number of file descriptors
11077 used for busy servers. Bug reported by Olaf Selke; patch from
11080 o Minor features (other):
11081 - When SafeLogging is disabled, log addresses along with all TLS
11083 - When building with --enable-gcc-warnings, check for whether Apple's
11084 warning "-Wshorten-64-to-32" is available.
11085 - Add a --passphrase-fd argument to the tor-gencert command for
11088 o Minor bugfixes (memory leaks and code problems):
11089 - We were leaking a file descriptor if Tor started with a zero-length
11090 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
11091 - Detect size overflow in zlib code. Reported by Justin Ferguson and
11093 - We were comparing the raw BridgePassword entry with a base64'ed
11094 version of it, when handling a "/tor/networkstatus-bridges"
11095 directory request. Now compare correctly. Noticed by Veracode.
11096 - Recover from bad tracked-since value in MTBF-history file.
11097 Should fix bug 537.
11098 - Alter the code that tries to recover from unhandled write
11099 errors, to not try to flush onto a socket that's given us
11100 unhandled errors. Bugfix on 0.1.2.x.
11101 - Make Unix controlsockets work correctly on OpenBSD. Patch from
11102 tup. Bugfix on 0.2.0.3-alpha.
11104 o Minor bugfixes (other):
11105 - If we have an extra-info document for our server, always make
11106 it available on the control port, even if we haven't gotten
11107 a copy of it from an authority yet. Patch from mwenge.
11108 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
11109 - Directory mirrors no longer include a guess at the client's IP
11110 address if the connection appears to be coming from the same /24
11111 network; it was producing too many wrong guesses.
11112 - Make the new hidden service code respect the SafeLogging setting.
11113 Bugfix on 0.2.0.x. Patch from Karsten.
11114 - When starting as an authority, do not overwrite all certificates
11115 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
11116 - If we're trying to flush the last bytes on a connection (for
11117 example, when answering a directory request), reset the
11118 time-to-give-up timeout every time we manage to write something
11119 on the socket. Bugfix on 0.1.2.x.
11120 - Change the behavior of "getinfo status/good-server-descriptor"
11121 so it doesn't return failure when any authority disappears.
11122 - Even though the man page said that "TrackHostExits ." should
11123 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
11124 - Report TLS "zero return" case as a "clean close" and "IO error"
11125 as a "close". Stop calling closes "unexpected closes": existing
11126 Tors don't use SSL_close(), so having a connection close without
11127 the TLS shutdown handshake is hardly unexpected.
11128 - Send NAMESERVER_STATUS messages for a single failed nameserver
11131 o Code simplifications and refactoring:
11132 - Remove the tor_strpartition function: its logic was confused,
11133 and it was only used for one thing that could be implemented far
11137 Changes in version 0.2.0.19-alpha - 2008-02-09
11138 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
11139 handshake, makes path selection for relays more secure and IP address
11140 guessing more robust, and generally fixes a lot of bugs in preparation
11141 for calling the 0.2.0 branch stable.
11144 - Do not include recognizeable strings in the commonname part of
11145 Tor's x509 certificates.
11148 - If we're a relay, avoid picking ourselves as an introduction point,
11149 a rendezvous point, or as the final hop for internal circuits. Bug
11150 reported by taranis and lodger. Bugfix on 0.1.2.x.
11151 - Patch from "Andrew S. Lists" to catch when we contact a directory
11152 mirror at IP address X and he says we look like we're coming from
11153 IP address X. Bugfix on 0.1.2.x.
11155 o Minor features (security):
11156 - Be more paranoid about overwriting sensitive memory on free(),
11157 as a defensive programming tactic to ensure forward secrecy.
11159 o Minor features (directory authority):
11160 - Actually validate the options passed to AuthDirReject,
11161 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
11162 - Reject router descriptors with out-of-range bandwidthcapacity or
11163 bandwidthburst values.
11165 o Minor features (controller):
11166 - Reject controller commands over 1MB in length. This keeps rogue
11167 processes from running us out of memory.
11169 o Minor features (misc):
11170 - Give more descriptive well-formedness errors for out-of-range
11171 hidden service descriptor/protocol versions.
11172 - Make memory debugging information describe more about history
11173 of cell allocation, so we can help reduce our memory use.
11175 o Deprecated features (controller):
11176 - The status/version/num-versioning and status/version/num-concurring
11177 GETINFO options are no longer useful in the v3 directory protocol:
11178 treat them as deprecated, and warn when they're used.
11181 - When our consensus networkstatus has been expired for a while, stop
11182 being willing to build circuits using it. Fixes bug 401. Bugfix
11184 - Directory caches now fetch certificates from all authorities
11185 listed in a networkstatus consensus, even when they do not
11186 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
11187 - When connecting to a bridge without specifying its key, insert
11188 the connection into the identity-to-connection map as soon as
11189 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
11190 - Detect versions of OS X where malloc_good_size() is present in the
11191 library but never actually declared. Resolves bug 587. Bugfix
11193 - Stop incorrectly truncating zlib responses to directory authority
11194 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
11195 - Stop recommending that every server operator send mail to tor-ops.
11196 Resolves bug 597. Bugfix on 0.1.2.x.
11197 - Don't trigger an assert if we start a directory authority with a
11198 private IP address (like 127.0.0.1).
11199 - Avoid possible failures when generating a directory with routers
11200 with over-long versions strings, or too many flags set. Bugfix
11202 - If an attempt to launch a DNS resolve request over the control
11203 port fails because we have overrun the limit on the number of
11204 connections, tell the controller that the request has failed.
11205 - Avoid using too little bandwidth when our clock skips a few
11206 seconds. Bugfix on 0.1.2.x.
11207 - Fix shell error when warning about missing packages in configure
11208 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
11209 - Do not become confused when receiving a spurious VERSIONS-like
11210 cell from a confused v1 client. Bugfix on 0.2.0.x.
11211 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
11212 introduction points for a hidden service have failed. Patch from
11213 Karsten Loesing. Bugfix on 0.2.0.x.
11215 o Code simplifications and refactoring:
11216 - Remove some needless generality from cpuworker code, for improved
11218 - Stop overloading the circuit_t.onionskin field for both "onionskin
11219 from a CREATE cell that we are waiting for a cpuworker to be
11220 assigned" and "onionskin from an EXTEND cell that we are going to
11221 send to an OR as soon as we are connected". Might help with bug 600.
11222 - Add an in-place version of aes_crypt() so that we can avoid doing a
11223 needless memcpy() call on each cell payload.
11226 Changes in version 0.2.0.18-alpha - 2008-01-25
11227 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
11228 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
11229 that can warn or reject connections to ports generally associated with
11230 vulnerable-plaintext protocols.
11232 o New directory authorities:
11233 - Set up dannenberg (run by CCC) as the sixth v3 directory
11237 - Fix a major memory leak when attempting to use the v2 TLS
11238 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
11239 - We accidentally enabled the under-development v2 TLS handshake
11240 code, which was causing log entries like "TLS error while
11241 renegotiating handshake". Disable it again. Resolves bug 590.
11242 - We were computing the wrong Content-Length: header for directory
11243 responses that need to be compressed on the fly, causing clients
11244 asking for those items to always fail. Bugfix on 0.2.0.x; partially
11248 - Avoid going directly to the directory authorities even if you're a
11249 relay, if you haven't found yourself reachable yet or if you've
11250 decided not to advertise your dirport yet. Addresses bug 556.
11251 - If we've gone 12 hours since our last bandwidth check, and we
11252 estimate we have less than 50KB bandwidth capacity but we could
11253 handle more, do another bandwidth test.
11254 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
11255 Tor can warn and/or refuse connections to ports commonly used with
11256 vulnerable-plaintext protocols. Currently we warn on ports 23,
11257 109, 110, and 143, but we don't reject any.
11260 - When we setconf ClientOnly to 1, close any current OR and Dir
11261 listeners. Reported by mwenge.
11262 - When we get a consensus that's been signed by more people than
11263 we expect, don't log about it; it's not a big deal. Reported
11267 - Don't answer "/tor/networkstatus-bridges" directory requests if
11268 the request isn't encrypted.
11269 - Make "ClientOnly 1" config option disable directory ports too.
11270 - Patches from Karsten Loesing to make v2 hidden services more
11271 robust: work even when there aren't enough HSDir relays available;
11272 retry when a v2 rend desc fetch fails; but don't retry if we
11273 already have a usable v0 rend desc.
11276 Changes in version 0.2.0.17-alpha - 2008-01-17
11277 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
11280 - Make the tor-gencert man page get included correctly in the tarball.
11283 Changes in version 0.2.0.16-alpha - 2008-01-17
11284 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
11285 Loesing, and generally cleans up a lot of features and minor bugs.
11287 o New directory authorities:
11288 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
11291 o Major performance improvements:
11292 - Switch our old ring buffer implementation for one more like that
11293 used by free Unix kernels. The wasted space in a buffer with 1mb
11294 of data will now be more like 8k than 1mb. The new implementation
11295 also avoids realloc();realloc(); patterns that can contribute to
11296 memory fragmentation.
11299 - Configuration files now accept C-style strings as values. This
11300 helps encode characters not allowed in the current configuration
11301 file format, such as newline or #. Addresses bug 557.
11302 - Although we fixed bug 539 (where servers would send HTTP status 503
11303 responses _and_ send a body too), there are still servers out
11304 there that haven't upgraded. Therefore, make clients parse such
11305 bodies when they receive them.
11306 - When we're not serving v2 directory information, there is no reason
11307 to actually keep any around. Remove the obsolete files and directory
11308 on startup if they are very old and we aren't going to serve them.
11310 o Minor performance improvements:
11311 - Reference-count and share copies of address policy entries; only 5%
11312 of them were actually distinct.
11313 - Never walk through the list of logs if we know that no log is
11314 interested in a given message.
11317 - When an authority has not signed a consensus, do not try to
11318 download a nonexistent "certificate with key 00000000". Bugfix
11319 on 0.2.0.x. Fixes bug 569.
11320 - Fix a rare assert error when we're closing one of our threads:
11321 use a mutex to protect the list of logs, so we never write to the
11322 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
11323 bug 575, which is kind of the revenge of bug 222.
11324 - Patch from Karsten Loesing to complain less at both the client
11325 and the relay when a relay used to have the HSDir flag but doesn't
11326 anymore, and we try to upload a hidden service descriptor.
11327 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
11329 - Do not try to download missing certificates until we have tried
11330 to check our fallback consensus. Fixes bug 583.
11331 - Make bridges round reported GeoIP stats info up to the nearest
11332 estimate, not down. Now we can distinguish between "0 people from
11333 this country" and "1 person from this country".
11334 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
11335 - Avoid possible segfault if key generation fails in
11336 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
11337 - Avoid segfault in the case where a badly behaved v2 versioning
11338 directory sends a signed networkstatus with missing client-versions.
11340 - Avoid segfaults on certain complex invocations of
11341 router_get_by_hexdigest(). Bugfix on 0.1.2.
11342 - Correct bad index on array access in parse_http_time(). Bugfix
11344 - Fix possible bug in vote generation when server versions are present
11345 but client versions are not.
11346 - Fix rare bug on REDIRECTSTREAM control command when called with no
11347 port set: it could erroneously report an error when none had
11349 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
11350 compressing large objects and find ourselves with more than 4k
11351 left over. Bugfix on 0.2.0.
11352 - Fix a small memory leak when setting up a hidden service.
11353 - Fix a few memory leaks that could in theory happen under bizarre
11355 - Fix an assert if we post a general-purpose descriptor via the
11356 control port but that descriptor isn't mentioned in our current
11357 network consensus. Bug reported by Jon McLachlan; bugfix on
11360 o Minor features (controller):
11361 - Get NS events working again. Patch from tup.
11362 - The GETCONF command now escapes and quotes configuration values
11363 that don't otherwise fit into the torrc file.
11364 - The SETCONF command now handles quoted values correctly.
11366 o Minor features (directory authorities):
11367 - New configuration options to override default maximum number of
11368 servers allowed on a single IP address. This is important for
11369 running a test network on a single host.
11370 - Actually implement the -s option to tor-gencert.
11371 - Add a manual page for tor-gencert.
11373 o Minor features (bridges):
11374 - Bridge authorities no longer serve bridge descriptors over
11375 unencrypted connections.
11377 o Minor features (other):
11378 - Add hidden services and DNSPorts to the list of things that make
11379 Tor accept that it has running ports. Change starting Tor with no
11380 ports from a fatal error to a warning; we might change it back if
11381 this turns out to confuse anybody. Fixes bug 579.
11384 Changes in version 0.1.2.19 - 2008-01-17
11385 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
11386 exit policy a little bit more conservative so it's safer to run an
11387 exit relay on a home system, and fixes a variety of smaller issues.
11390 - Exit policies now reject connections that are addressed to a
11391 relay's public (external) IP address too, unless
11392 ExitPolicyRejectPrivate is turned off. We do this because too
11393 many relays are running nearby to services that trust them based
11394 on network address.
11397 - When the clock jumps forward a lot, do not allow the bandwidth
11398 buckets to become negative. Fixes bug 544.
11399 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11400 on every successful resolve. Reported by Mike Perry.
11401 - Purge old entries from the "rephist" database and the hidden
11402 service descriptor database even when DirPort is zero.
11403 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11404 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11405 crashing or mis-answering these requests.
11406 - When we decide to send a 503 response to a request for servers, do
11407 not then also send the server descriptors: this defeats the whole
11408 purpose. Fixes bug 539.
11411 - Changing the ExitPolicyRejectPrivate setting should cause us to
11412 rebuild our server descriptor.
11413 - Fix handling of hex nicknames when answering controller requests for
11414 networkstatus by name, or when deciding whether to warn about
11415 unknown routers in a config option. (Patch from mwenge.)
11416 - Fix a couple of hard-to-trigger autoconf problems that could result
11417 in really weird results on platforms whose sys/types.h files define
11418 nonstandard integer types.
11419 - Don't try to create the datadir when running --verify-config or
11420 --hash-password. Resolves bug 540.
11421 - If we were having problems getting a particular descriptor from the
11422 directory caches, and then we learned about a new descriptor for
11423 that router, we weren't resetting our failure count. Reported
11425 - Although we fixed bug 539 (where servers would send HTTP status 503
11426 responses _and_ send a body too), there are still servers out there
11427 that haven't upgraded. Therefore, make clients parse such bodies
11428 when they receive them.
11429 - Run correctly on systems where rlim_t is larger than unsigned long.
11430 This includes some 64-bit systems.
11431 - Run correctly on platforms (like some versions of OS X 10.5) where
11432 the real limit for number of open files is OPEN_FILES, not rlim_max
11433 from getrlimit(RLIMIT_NOFILES).
11434 - Avoid a spurious free on base64 failure.
11435 - Avoid segfaults on certain complex invocations of
11436 router_get_by_hexdigest().
11437 - Fix rare bug on REDIRECTSTREAM control command when called with no
11438 port set: it could erroneously report an error when none had
11442 Changes in version 0.2.0.15-alpha - 2007-12-25
11443 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
11444 features added in 0.2.0.13-alpha.
11447 - Fix several remotely triggerable asserts based on DirPort requests
11448 for a v2 or v3 networkstatus object before we were prepared. This
11449 was particularly bad for 0.2.0.13 and later bridge relays, who
11450 would never have a v2 networkstatus and would thus always crash
11451 when used. Bugfixes on 0.2.0.x.
11452 - Estimate the v3 networkstatus size more accurately, rather than
11453 estimating it at zero bytes and giving it artificially high priority
11454 compared to other directory requests. Bugfix on 0.2.0.x.
11457 - Fix configure.in logic for cross-compilation.
11458 - When we load a bridge descriptor from the cache, and it was
11459 previously unreachable, mark it as retriable so we won't just
11460 ignore it. Also, try fetching a new copy immediately. Bugfixes
11462 - The bridge GeoIP stats were counting other relays, for example
11463 self-reachability and authority-reachability tests.
11466 - Support compilation to target iPhone; patch from cjacker huang.
11467 To build for iPhone, pass the --enable-iphone option to configure.
11470 Changes in version 0.2.0.14-alpha - 2007-12-23
11472 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
11473 without a datadirectory from a previous Tor install. Reported
11475 - Fix a crash when we fetch a descriptor that turns out to be
11476 unexpected (it used to be in our networkstatus when we started
11477 fetching it, but it isn't in our current networkstatus), and we
11478 aren't using bridges. Bugfix on 0.2.0.x.
11479 - Fix a crash when accessing hidden services: it would work the first
11480 time you use a given introduction point for your service, but
11481 on subsequent requests we'd be using garbage memory. Fixed by
11482 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
11483 - Fix a crash when we load a bridge descriptor from disk but we don't
11484 currently have a Bridge line for it in our torrc. Bugfix on
11488 - If bridge authorities set BridgePassword, they will serve a
11489 snapshot of known bridge routerstatuses from their DirPort to
11490 anybody who knows that password. Unset by default.
11493 - Make the unit tests build again.
11494 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
11495 - Make PublishServerDescriptor default to 1, so the default doesn't
11496 have to change as we invent new directory protocol versions.
11497 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
11498 be included unless sys/time.h is already included. Fixes
11499 bug 553. Bugfix on 0.2.0.x.
11500 - If we receive a general-purpose descriptor and then receive an
11501 identical bridge-purpose descriptor soon after, don't discard
11502 the next one as a duplicate.
11505 - If BridgeRelay is set to 1, then the default for
11506 PublishServerDescriptor is now "bridge" rather than "v2,v3".
11507 - If the user sets RelayBandwidthRate but doesn't set
11508 RelayBandwidthBurst, then make them equal rather than erroring out.
11511 Changes in version 0.2.0.13-alpha - 2007-12-21
11512 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
11513 Goodell, fixes many more bugs, and adds a lot of infrastructure for
11516 o New directory authorities:
11517 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
11521 - Only update guard status (usable / not usable) once we have
11522 enough directory information. This was causing us to always pick
11523 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
11524 causing us to discard all our guards on startup if we hadn't been
11525 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
11526 - Purge old entries from the "rephist" database and the hidden
11527 service descriptor databases even when DirPort is zero. Bugfix
11529 - We were ignoring our RelayBandwidthRate for the first 30 seconds
11530 after opening a circuit -- even a relayed circuit. Bugfix on
11532 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11533 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11534 crashing or mis-answering these types of requests.
11535 - Relays were publishing their server descriptor to v1 and v2
11536 directory authorities, but they didn't try publishing to v3-only
11537 authorities. Fix this; and also stop publishing to v1 authorities.
11539 - When we were reading router descriptors from cache, we were ignoring
11540 the annotations -- so for example we were reading in bridge-purpose
11541 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
11542 - When we decided to send a 503 response to a request for servers, we
11543 were then also sending the server descriptors: this defeats the
11544 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
11547 - Bridge relays now behave like clients with respect to time
11548 intervals for downloading new consensus documents -- otherwise they
11549 stand out. Bridge users now wait until the end of the interval,
11550 so their bridge relay will be sure to have a new consensus document.
11551 - Three new config options (AlternateDirAuthority,
11552 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
11553 user selectively replace the default directory authorities by type,
11554 rather than the all-or-nothing replacement that DirServer offers.
11555 - Tor can now be configured to read a GeoIP file from disk in one
11556 of two formats. This can be used by controllers to map IP addresses
11557 to countries. Eventually, it may support exit-by-country.
11558 - When possible, bridge relays remember which countries users
11559 are coming from, and report aggregate information in their
11560 extra-info documents, so that the bridge authorities can learn
11561 where Tor is blocked.
11562 - Bridge directory authorities now do reachability testing on the
11563 bridges they know. They provide router status summaries to the
11564 controller via "getinfo ns/purpose/bridge", and also dump summaries
11565 to a file periodically.
11566 - Stop fetching directory info so aggressively if your DirPort is
11567 on but your ORPort is off; stop fetching v2 dir info entirely.
11568 You can override these choices with the new FetchDirInfoEarly
11572 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
11573 consensus documents when there are too many relays at a single
11574 IP address. Now clear it in v2 network status documents too, and
11575 also clear it in routerinfo_t when the relay is no longer listed
11576 in the relevant networkstatus document.
11577 - Don't crash if we get an unexpected value for the
11578 PublishServerDescriptor config option. Reported by Matt Edman;
11579 bugfix on 0.2.0.9-alpha.
11580 - Our new v2 hidden service descriptor format allows descriptors
11581 that have no introduction points. But Tor crashed when we tried
11582 to build a descriptor with no intro points (and it would have
11583 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
11584 by Karsten Loesing.
11585 - Fix building with dmalloc 5.5.2 with glibc.
11586 - Reject uploaded descriptors and extrainfo documents if they're
11587 huge. Otherwise we'll cache them all over the network and it'll
11588 clog everything up. Reported by Aljosha Judmayer.
11589 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
11590 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
11591 - When the DANGEROUS_VERSION controller status event told us we're
11592 running an obsolete version, it used the string "OLD" to describe
11593 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
11594 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
11595 - If we can't expand our list of entry guards (e.g. because we're
11596 using bridges or we have StrictEntryNodes set), don't mark relays
11597 down when they fail a directory request. Otherwise we're too quick
11598 to mark all our entry points down. Bugfix on 0.1.2.x.
11599 - Fix handling of hex nicknames when answering controller requests for
11600 networkstatus by name, or when deciding whether to warn about unknown
11601 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
11602 - Fix a couple of hard-to-trigger autoconf problems that could result
11603 in really weird results on platforms whose sys/types.h files define
11604 nonstandard integer types. Bugfix on 0.1.2.x.
11605 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
11606 - Don't crash on name lookup when we have no current consensus. Fixes
11607 bug 538; bugfix on 0.2.0.x.
11608 - Only Tors that want to mirror the v2 directory info should
11609 create the "cached-status" directory in their datadir. (All Tors
11610 used to create it.) Bugfix on 0.2.0.9-alpha.
11611 - Directory authorities should only automatically download Extra Info
11612 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
11615 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
11616 consumers. (We already do this on HUP.)
11617 - Authorities and caches fetch the v2 networkstatus documents
11618 less often, now that v3 is encouraged.
11619 - Add a new config option BridgeRelay that specifies you want to
11620 be a bridge relay. Right now the only difference is that it makes
11621 you answer begin_dir requests, and it makes you cache dir info,
11622 even if your DirPort isn't on.
11623 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
11624 ask about source, timestamp of arrival, purpose, etc. We need
11625 something like this to help Vidalia not do GeoIP lookups on bridge
11627 - Allow multiple HashedControlPassword config lines, to support
11628 multiple controller passwords.
11629 - Authorities now decide whether they're authoritative for a given
11630 router based on the router's purpose.
11631 - New config options AuthDirBadDir and AuthDirListBadDirs for
11632 authorities to mark certain relays as "bad directories" in the
11633 networkstatus documents. Also supports the "!baddir" directive in
11634 the approved-routers file.
11637 Changes in version 0.2.0.12-alpha - 2007-11-16
11638 This twelfth development snapshot fixes some more build problems as
11639 well as a few minor bugs.
11642 - Make it build on OpenBSD again. Patch from tup.
11643 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
11644 package-building for Red Hat, OS X, etc.
11646 o Minor bugfixes (on 0.1.2.x):
11647 - Changing the ExitPolicyRejectPrivate setting should cause us to
11648 rebuild our server descriptor.
11650 o Minor bugfixes (on 0.2.0.x):
11651 - When we're lacking a consensus, don't try to perform rendezvous
11652 operations. Reported by Karsten Loesing.
11653 - Fix a small memory leak whenever we decide against using a
11654 newly picked entry guard. Reported by Mike Perry.
11655 - When authorities detected more than two relays running on the same
11656 IP address, they were clearing all the status flags but forgetting
11657 to clear the "hsdir" flag. So clients were being told that a
11658 given relay was the right choice for a v2 hsdir lookup, yet they
11659 never had its descriptor because it was marked as 'not running'
11661 - If we're trying to fetch a bridge descriptor and there's no way
11662 the bridge authority could help us (for example, we don't know
11663 a digest, or there is no bridge authority), don't be so eager to
11664 fall back to asking the bridge authority.
11665 - If we're using bridges or have strictentrynodes set, and our
11666 chosen exit is in the same family as all our bridges/entry guards,
11667 then be flexible about families.
11670 - When we negotiate a v2 link-layer connection (not yet implemented),
11671 accept RELAY_EARLY cells and turn them into RELAY cells if we've
11672 negotiated a v1 connection for their next step. Initial code for
11676 Changes in version 0.2.0.11-alpha - 2007-11-12
11677 This eleventh development snapshot fixes some build problems with
11678 the previous snapshot. It also includes a more secure-by-default exit
11679 policy for relays, fixes an enormous memory leak for exit relays, and
11680 fixes another bug where servers were falling out of the directory list.
11683 - Exit policies now reject connections that are addressed to a
11684 relay's public (external) IP address too, unless
11685 ExitPolicyRejectPrivate is turned off. We do this because too
11686 many relays are running nearby to services that trust them based
11687 on network address. Bugfix on 0.1.2.x.
11690 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11691 on every successful resolve. Reported by Mike Perry; bugfix
11693 - On authorities, never downgrade to old router descriptors simply
11694 because they're listed in the consensus. This created a catch-22
11695 where we wouldn't list a new descriptor because there was an
11696 old one in the consensus, and we couldn't get the new one in the
11697 consensus because we wouldn't list it. Possible fix for bug 548.
11698 Also, this might cause bug 543 to appear on authorities; if so,
11699 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
11701 o Packaging fixes on 0.2.0.10-alpha:
11702 - We were including instructions about what to do with the
11703 src/config/fallback-consensus file, but we weren't actually
11704 including it in the tarball. Disable all of that for now.
11707 - Allow people to say PreferTunnelledDirConns rather than
11708 PreferTunneledDirConns, for those alternate-spellers out there.
11711 - Don't reevaluate all the information from our consensus document
11712 just because we've downloaded a v2 networkstatus that we intend
11713 to cache. Fixes bug 545; bugfix on 0.2.0.x.
11716 Changes in version 0.2.0.10-alpha - 2007-11-10
11717 This tenth development snapshot adds a third v3 directory authority
11718 run by Mike Perry, adds most of Karsten Loesing's new hidden service
11719 descriptor format, fixes a bad crash bug and new bridge bugs introduced
11720 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
11721 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
11722 addresses many more minor issues.
11724 o New directory authorities:
11725 - Set up ides (run by Mike Perry) as the third v3 directory authority.
11728 - Allow tunnelled directory connections to ask for an encrypted
11729 "begin_dir" connection or an anonymized "uses a full Tor circuit"
11730 connection independently. Now we can make anonymized begin_dir
11731 connections for (e.g.) more secure hidden service posting and
11733 - More progress on proposal 114: code from Karsten Loesing to
11734 implement new hidden service descriptor format.
11735 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
11736 accommodate the growing number of servers that use the default
11737 and are reaching it.
11738 - Directory authorities use a new formula for selecting which nodes
11739 to advertise as Guards: they must be in the top 7/8 in terms of
11740 how long we have known about them, and above the median of those
11741 nodes in terms of weighted fractional uptime.
11742 - Make "not enough dir info yet" warnings describe *why* Tor feels
11743 it doesn't have enough directory info yet.
11746 - Stop servers from crashing if they set a Family option (or
11747 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
11749 - Make bridge users work again -- the move to v3 directories in
11750 0.2.0.9-alpha had introduced a number of bugs that made bridges
11751 no longer work for clients.
11752 - When the clock jumps forward a lot, do not allow the bandwidth
11753 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
11755 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
11756 - When the consensus lists a router descriptor that we previously were
11757 mirroring, but that we considered non-canonical, reload the
11758 descriptor as canonical. This fixes bug 543 where Tor servers
11759 would start complaining after a few days that they don't have
11760 enough directory information to build a circuit.
11761 - Consider replacing the current consensus when certificates arrive
11762 that make the pending consensus valid. Previously, we were only
11763 considering replacement when the new certs _didn't_ help.
11764 - Fix an assert error on startup if we didn't already have the
11765 consensus and certs cached in our datadirectory: we were caching
11766 the consensus in consensus_waiting_for_certs but then free'ing it
11768 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
11769 Request) if we need more v3 certs but we've already got pending
11770 requests for all of them.
11771 - Correctly back off from failing certificate downloads. Fixes
11773 - Authorities don't vote on the Running flag if they have been running
11774 for less than 30 minutes themselves. Fixes bug 547, where a newly
11775 started authority would vote that everyone was down.
11777 o New requirements:
11778 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
11779 it, it had no AES, and it hasn't seen any security patches since
11783 - Clients now hold circuitless TLS connections open for 1.5 times
11784 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
11785 rebuild a new circuit over them within that timeframe. Previously,
11786 they held them open only for KeepalivePeriod (5 minutes).
11787 - Use "If-Modified-Since" to avoid retrieving consensus
11788 networkstatuses that we already have.
11789 - When we have no consensus, check FallbackNetworkstatusFile (defaults
11790 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
11791 we start knowing some directory caches.
11792 - When we receive a consensus from the future, warn about skew.
11793 - Improve skew reporting: try to give the user a better log message
11794 about how skewed they are, and how much this matters.
11795 - When we have a certificate for an authority, believe that
11796 certificate's claims about the authority's IP address.
11797 - New --quiet command-line option to suppress the default console log.
11798 Good in combination with --hash-password.
11799 - Authorities send back an X-Descriptor-Not-New header in response to
11800 an accepted-but-discarded descriptor upload. Partially implements
11802 - Make the log message for "tls error. breaking." more useful.
11803 - Better log messages about certificate downloads, to attempt to
11804 track down the second incarnation of bug 546.
11806 o Minor features (bridges):
11807 - If bridge users set UpdateBridgesFromAuthority, but the digest
11808 they ask for is a 404 from the bridge authority, they now fall
11809 back to trying the bridge directly.
11810 - Bridges now use begin_dir to publish their server descriptor to
11811 the bridge authority, even when they haven't set TunnelDirConns.
11813 o Minor features (controller):
11814 - When reporting clock skew, and we know that the clock is _at least
11815 as skewed_ as some value, but we don't know the actual value,
11816 report the value as a "minimum skew."
11819 - Update linux-tor-prio.sh script to allow QoS based on the uid of
11820 the Tor process. Patch from Marco Bonetti with tweaks from Mike
11824 - Refuse to start if both ORPort and UseBridges are set. Bugfix
11825 on 0.2.0.x, suggested by Matt Edman.
11826 - Don't stop fetching descriptors when FetchUselessDescriptors is
11827 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
11828 reported by tup and ioerror.
11829 - Better log message on vote from unknown authority.
11830 - Don't log "Launching 0 request for 0 router" message.
11832 o Minor bugfixes (memory leaks):
11833 - Stop leaking memory every time we parse a v3 certificate. Bugfix
11835 - Stop leaking memory every time we load a v3 certificate. Bugfix
11836 on 0.2.0.1-alpha. Fixes bug 536.
11837 - Stop leaking a cached networkstatus on exit. Bugfix on
11839 - Stop leaking voter information every time we free a consensus.
11840 Bugfix on 0.2.0.3-alpha.
11841 - Stop leaking signed data every time we check a voter signature.
11842 Bugfix on 0.2.0.3-alpha.
11843 - Stop leaking a signature every time we fail to parse a consensus or
11844 a vote. Bugfix on 0.2.0.3-alpha.
11845 - Stop leaking v2_download_status_map on shutdown. Bugfix on
11847 - Stop leaking conn->nickname every time we make a connection to a
11848 Tor relay without knowing its expected identity digest (e.g. when
11849 using bridges). Bugfix on 0.2.0.3-alpha.
11851 - Minor bugfixes (portability):
11852 - Run correctly on platforms where rlim_t is larger than unsigned
11853 long, and/or where the real limit for number of open files is
11854 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
11855 particular, these may be needed for OS X 10.5.
11858 Changes in version 0.1.2.18 - 2007-10-28
11859 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
11860 hidden service introduction that were causing huge delays, and a big
11861 bug that was causing some servers to disappear from the network status
11862 lists for a few hours each day.
11864 o Major bugfixes (crashes):
11865 - If a connection is shut down abruptly because of something that
11866 happened inside connection_flushed_some(), do not call
11867 connection_finished_flushing(). Should fix bug 451:
11868 "connection_stop_writing: Assertion conn->write_event failed"
11869 Bugfix on 0.1.2.7-alpha.
11870 - Fix possible segfaults in functions called from
11871 rend_process_relay_cell().
11873 o Major bugfixes (hidden services):
11874 - Hidden services were choosing introduction points uniquely by
11875 hexdigest, but when constructing the hidden service descriptor
11876 they merely wrote the (potentially ambiguous) nickname.
11877 - Clients now use the v2 intro format for hidden service
11878 connections: they specify their chosen rendezvous point by identity
11879 digest rather than by (potentially ambiguous) nickname. These
11880 changes could speed up hidden service connections dramatically.
11882 o Major bugfixes (other):
11883 - Stop publishing a new server descriptor just because we get a
11884 HUP signal. This led (in a roundabout way) to some servers getting
11885 dropped from the networkstatus lists for a few hours each day.
11886 - When looking for a circuit to cannibalize, consider family as well
11887 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11888 circuit cannibalization).
11889 - When a router wasn't listed in a new networkstatus, we were leaving
11890 the flags for that router alone -- meaning it remained Named,
11891 Running, etc -- even though absence from the networkstatus means
11892 that it shouldn't be considered to exist at all anymore. Now we
11893 clear all the flags for routers that fall out of the networkstatus
11894 consensus. Fixes bug 529.
11897 - Don't try to access (or alter) the state file when running
11898 --list-fingerprint or --verify-config or --hash-password. Resolves
11900 - When generating information telling us how to extend to a given
11901 router, do not try to include the nickname if it is
11902 absent. Resolves bug 467.
11903 - Fix a user-triggerable segfault in expand_filename(). (There isn't
11904 a way to trigger this remotely.)
11905 - When sending a status event to the controller telling it that an
11906 OR address is reachable, set the port correctly. (Previously we
11907 were reporting the dir port.)
11908 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11909 command. Bugfix on 0.1.2.17.
11910 - When loading bandwidth history, do not believe any information in
11911 the future. Fixes bug 434.
11912 - When loading entry guard information, do not believe any information
11914 - When we have our clock set far in the future and generate an
11915 onion key, then re-set our clock to be correct, we should not stop
11916 the onion key from getting rotated.
11917 - On some platforms, accept() can return a broken address. Detect
11918 this more quietly, and deal accordingly. Fixes bug 483.
11919 - It's not actually an error to find a non-pending entry in the DNS
11920 cache when canceling a pending resolve. Don't log unless stuff
11921 is fishy. Resolves bug 463.
11922 - Don't reset trusted dir server list when we set a configuration
11923 option. Patch from Robert Hogan.
11924 - Don't try to create the datadir when running --verify-config or
11925 --hash-password. Resolves bug 540.
11928 Changes in version 0.2.0.9-alpha - 2007-10-24
11929 This ninth development snapshot switches clients to the new v3 directory
11930 system; allows servers to be listed in the network status even when they
11931 have the same nickname as a registered server; and fixes many other
11932 bugs including a big one that was causing some servers to disappear
11933 from the network status lists for a few hours each day.
11935 o Major features (directory system):
11936 - Clients now download v3 consensus networkstatus documents instead
11937 of v2 networkstatus documents. Clients and caches now base their
11938 opinions about routers on these consensus documents. Clients only
11939 download router descriptors listed in the consensus.
11940 - Authorities now list servers who have the same nickname as
11941 a different named server, but list them with a new flag,
11942 "Unnamed". Now we can list servers that happen to pick the same
11943 nickname as a server that registered two years ago and then
11944 disappeared. Partially implements proposal 122.
11945 - If the consensus lists a router as "Unnamed", the name is assigned
11946 to a different router: do not identify the router by that name.
11947 Partially implements proposal 122.
11948 - Authorities can now come to a consensus on which method to use to
11949 compute the consensus. This gives us forward compatibility.
11952 - Stop publishing a new server descriptor just because we HUP or
11953 when we find our DirPort to be reachable but won't actually publish
11954 it. New descriptors without any real changes are dropped by the
11955 authorities, and can screw up our "publish every 18 hours" schedule.
11957 - When a router wasn't listed in a new networkstatus, we were leaving
11958 the flags for that router alone -- meaning it remained Named,
11959 Running, etc -- even though absence from the networkstatus means
11960 that it shouldn't be considered to exist at all anymore. Now we
11961 clear all the flags for routers that fall out of the networkstatus
11962 consensus. Fixes bug 529; bugfix on 0.1.2.x.
11963 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
11964 extrainfo documents and then discard them immediately for not
11965 matching the latest router. Bugfix on 0.2.0.1-alpha.
11967 o Minor features (v3 directory protocol):
11968 - Allow tor-gencert to generate a new certificate without replacing
11970 - Allow certificates to include an address.
11971 - When we change our directory-cache settings, reschedule all voting
11972 and download operations.
11973 - Reattempt certificate downloads immediately on failure, as long as
11974 we haven't failed a threshold number of times yet.
11975 - Delay retrying consensus downloads while we're downloading
11976 certificates to verify the one we just got. Also, count getting a
11977 consensus that we already have (or one that isn't valid) as a failure,
11978 and count failing to get the certificates after 20 minutes as a
11980 - Build circuits and download descriptors even if our consensus is a
11981 little expired. (This feature will go away once authorities are
11984 o Minor features (router descriptor cache):
11985 - If we find a cached-routers file that's been sitting around for more
11986 than 28 days unmodified, then most likely it's a leftover from
11987 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
11989 - When we (as a cache) download a descriptor because it was listed
11990 in a consensus, remember when the consensus was supposed to expire,
11991 and don't expire the descriptor until then.
11993 o Minor features (performance):
11994 - Call routerlist_remove_old_routers() much less often. This should
11995 speed startup, especially on directory caches.
11996 - Don't try to launch new descriptor downloads quite so often when we
11997 already have enough directory information to build circuits.
11998 - Base64 decoding was actually showing up on our profile when parsing
11999 the initial descriptor file; switch to an in-process all-at-once
12000 implementation that's about 3.5x times faster than calling out to
12003 o Minor features (compilation):
12004 - Detect non-ASCII platforms (if any still exist) and refuse to
12005 build there: some of our code assumes that 'A' is 65 and so on.
12007 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
12008 - Make the "next period" votes into "current period" votes immediately
12009 after publishing the consensus; avoid a heisenbug that made them
12010 stick around indefinitely.
12011 - When we discard a vote as a duplicate, do not report this as
12013 - Treat missing v3 keys or certificates as an error when running as a
12014 v3 directory authority.
12015 - When we're configured to be a v3 authority, but we're only listed
12016 as a non-v3 authority in our DirServer line for ourself, correct
12018 - If an authority doesn't have a qualified hostname, just put
12019 its address in the vote. This fixes the problem where we referred to
12020 "moria on moria:9031."
12021 - Distinguish between detached signatures for the wrong period, and
12022 detached signatures for a divergent vote.
12023 - Fix a small memory leak when computing a consensus.
12024 - When there's no concensus, we were forming a vote every 30
12025 minutes, but writing the "valid-after" line in our vote based
12026 on our configured V3AuthVotingInterval: so unless the intervals
12027 matched up, we immediately rejected our own vote because it didn't
12028 start at the voting interval that caused us to construct a vote.
12030 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
12031 - Delete unverified-consensus when the real consensus is set.
12032 - Consider retrying a consensus networkstatus fetch immediately
12033 after one fails: don't wait 60 seconds to notice.
12034 - When fetching a consensus as a cache, wait until a newer consensus
12035 should exist before trying to replace the current one.
12036 - Use a more forgiving schedule for retrying failed consensus
12037 downloads than for other types.
12039 o Minor bugfixes (other directory issues):
12040 - Correct the implementation of "download votes by digest." Bugfix on
12042 - Authorities no longer send back "400 you're unreachable please fix
12043 it" errors to Tor servers that aren't online all the time. We're
12044 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
12046 o Minor bugfixes (controller):
12047 - Don't reset trusted dir server list when we set a configuration
12048 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
12049 - Respond to INT and TERM SIGNAL commands before we execute the
12050 signal, in case the signal shuts us down. We had a patch in
12051 0.1.2.1-alpha that tried to do this by queueing the response on
12052 the connection's buffer before shutting down, but that really
12053 isn't the same thing at all. Bug located by Matt Edman.
12055 o Minor bugfixes (misc):
12056 - Correctly check for bad options to the "PublishServerDescriptor"
12057 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
12058 - Stop leaking memory on failing case of base32_decode, and make
12059 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
12060 - Don't try to download extrainfo documents when we're trying to
12061 fetch enough directory info to build a circuit: having enough
12062 info should get priority. Bugfix on 0.2.0.x.
12063 - Don't complain that "your server has not managed to confirm that its
12064 ports are reachable" if we haven't been able to build any circuits
12065 yet. Bug found by spending four hours without a v3 consensus. Bugfix
12067 - Detect the reason for failing to mmap a descriptor file we just
12068 wrote, and give a more useful log message. Fixes bug 533. Bugfix
12071 o Code simplifications and refactoring:
12072 - Remove support for the old bw_accounting file: we've been storing
12073 bandwidth accounting information in the state file since
12074 0.1.2.5-alpha. This may result in bandwidth accounting errors
12075 if you try to upgrade from 0.1.1.x or earlier, or if you try to
12076 downgrade to 0.1.1.x or earlier.
12077 - New convenience code to locate a file within the DataDirectory.
12078 - Move non-authority functionality out of dirvote.c.
12079 - Refactor the arguments for router_pick_{directory_|trusteddir}server
12080 so that they all take the same named flags.
12083 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
12084 Unix users an easy way to script their Tor process (e.g. by
12085 adjusting bandwidth based on the time of the day).
12088 Changes in version 0.2.0.8-alpha - 2007-10-12
12089 This eighth development snapshot fixes a crash bug that's been bothering
12090 us since February 2007, lets bridge authorities store a list of bridge
12091 descriptors they've seen, gets v3 directory voting closer to working,
12092 starts caching v3 directory consensus documents on directory mirrors,
12093 and fixes a variety of smaller issues including some minor memory leaks.
12095 o Major features (router descriptor cache):
12096 - Store routers in a file called cached-descriptors instead of in
12097 cached-routers. Initialize cached-descriptors from cached-routers
12098 if the old format is around. The new format allows us to store
12099 annotations along with descriptors.
12100 - Use annotations to record the time we received each descriptor, its
12101 source, and its purpose.
12102 - Disable the SETROUTERPURPOSE controller command: it is now
12104 - Controllers should now specify cache=no or cache=yes when using
12105 the +POSTDESCRIPTOR command.
12106 - Bridge authorities now write bridge descriptors to disk, meaning
12107 we can export them to other programs and begin distributing them
12110 o Major features (directory authorities):
12111 - When a v3 authority is missing votes or signatures, it now tries
12113 - Directory authorities track weighted fractional uptime as well as
12114 weighted mean-time-between failures. WFU is suitable for deciding
12115 whether a node is "usually up", while MTBF is suitable for deciding
12116 whether a node is "likely to stay up." We need both, because
12117 "usually up" is a good requirement for guards, while "likely to
12118 stay up" is a good requirement for long-lived connections.
12120 o Major features (v3 directory system):
12121 - Caches now download v3 network status documents as needed,
12122 and download the descriptors listed in them.
12123 - All hosts now attempt to download and keep fresh v3 authority
12124 certificates, and re-attempt after failures.
12125 - More internal-consistency checks for vote parsing.
12127 o Major bugfixes (crashes):
12128 - If a connection is shut down abruptly because of something that
12129 happened inside connection_flushed_some(), do not call
12130 connection_finished_flushing(). Should fix bug 451. Bugfix on
12133 o Major bugfixes (performance):
12134 - Fix really bad O(n^2) performance when parsing a long list of
12135 routers: Instead of searching the entire list for an "extra-info "
12136 string which usually wasn't there, once for every routerinfo
12137 we read, just scan lines forward until we find one we like.
12139 - When we add data to a write buffer in response to the data on that
12140 write buffer getting low because of a flush, do not consider the
12141 newly added data as a candidate for immediate flushing, but rather
12142 make it wait until the next round of writing. Otherwise, we flush
12143 and refill recursively, and a single greedy TLS connection can
12144 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
12146 o Minor features (v3 authority system):
12147 - Add more ways for tools to download the votes that lead to the
12149 - Send a 503 when low on bandwidth and a vote, consensus, or
12150 certificate is requested.
12151 - If-modified-since is now implemented properly for all kinds of
12152 certificate requests.
12154 o Minor bugfixes (network statuses):
12155 - Tweak the implementation of proposal 109 slightly: allow at most
12156 two Tor servers on the same IP address, except if it's the location
12157 of a directory authority, in which case allow five. Bugfix on
12160 o Minor bugfixes (controller):
12161 - When sending a status event to the controller telling it that an
12162 OR address is reachable, set the port correctly. (Previously we
12163 were reporting the dir port.) Bugfix on 0.1.2.x.
12165 o Minor bugfixes (v3 directory system):
12166 - Fix logic to look up a cert by its signing key digest. Bugfix on
12168 - Only change the reply to a vote to "OK" if it's not already
12169 set. This gets rid of annoying "400 OK" log messages, which may
12170 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
12171 - When we get a valid consensus, recompute the voting schedule.
12172 - Base the valid-after time of a vote on the consensus voting
12173 schedule, not on our preferred schedule.
12174 - Make the return values and messages from signature uploads and
12175 downloads more sensible.
12176 - Fix a memory leak when serving votes and consensus documents, and
12177 another when serving certificates.
12179 o Minor bugfixes (performance):
12180 - Use a slightly simpler string hashing algorithm (copying Python's
12181 instead of Java's) and optimize our digest hashing algorithm to take
12182 advantage of 64-bit platforms and to remove some possibly-costly
12184 - Fix a minor memory leak whenever we parse guards from our state
12185 file. Bugfix on 0.2.0.7-alpha.
12186 - Fix a minor memory leak whenever we write out a file. Bugfix on
12188 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
12189 command. Bugfix on 0.2.0.5-alpha.
12191 o Minor bugfixes (portability):
12192 - On some platforms, accept() can return a broken address. Detect
12193 this more quietly, and deal accordingly. Fixes bug 483.
12194 - Stop calling tor_strlower() on uninitialized memory in some cases.
12195 Bugfix in 0.2.0.7-alpha.
12197 o Minor bugfixes (usability):
12198 - Treat some 403 responses from directory servers as INFO rather than
12199 WARN-severity events.
12200 - It's not actually an error to find a non-pending entry in the DNS
12201 cache when canceling a pending resolve. Don't log unless stuff is
12202 fishy. Resolves bug 463.
12204 o Minor bugfixes (anonymity):
12205 - Never report that we've used more bandwidth than we're willing to
12206 relay: it leaks how much non-relay traffic we're using. Resolves
12208 - When looking for a circuit to cannibalize, consider family as well
12209 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12210 circuit cannibalization).
12212 o Code simplifications and refactoring:
12213 - Make a bunch of functions static. Remove some dead code.
12214 - Pull out about a third of the really big routerlist.c; put it in a
12215 new module, networkstatus.c.
12216 - Merge the extra fields in local_routerstatus_t back into
12217 routerstatus_t: we used to need one routerstatus_t for each
12218 authority's opinion, plus a local_routerstatus_t for the locally
12219 computed consensus opinion. To save space, we put the locally
12220 modified fields into local_routerstatus_t, and only the common
12221 stuff into routerstatus_t. But once v3 directories are in use,
12222 clients and caches will no longer need to hold authority opinions;
12223 thus, the rationale for keeping the types separate is now gone.
12224 - Make the code used to reschedule and reattempt downloads more
12226 - Turn all 'Are we a directory server/mirror?' logic into a call to
12228 - Remove the code to generate the oldest (v1) directory format.
12229 The code has been disabled since 0.2.0.5-alpha.
12232 Changes in version 0.2.0.7-alpha - 2007-09-21
12233 This seventh development snapshot makes bridges work again, makes bridge
12234 authorities work for the first time, fixes two huge performance flaws
12235 in hidden services, and fixes a variety of minor issues.
12237 o New directory authorities:
12238 - Set up moria1 and tor26 as the first v3 directory authorities. See
12239 doc/spec/dir-spec.txt for details on the new directory design.
12241 o Major bugfixes (crashes):
12242 - Fix possible segfaults in functions called from
12243 rend_process_relay_cell(). Bugfix on 0.1.2.x.
12245 o Major bugfixes (bridges):
12246 - Fix a bug that made servers send a "404 Not found" in response to
12247 attempts to fetch their server descriptor. This caused Tor servers
12248 to take many minutes to establish reachability for their DirPort,
12249 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
12250 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
12251 users configure that and specify a bridge with an identity
12252 fingerprint, now they will lookup the bridge descriptor at the
12253 default bridge authority via a one-hop tunnel, but once circuits
12254 are established they will switch to a three-hop tunnel for later
12255 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
12257 o Major bugfixes (hidden services):
12258 - Hidden services were choosing introduction points uniquely by
12259 hexdigest, but when constructing the hidden service descriptor
12260 they merely wrote the (potentially ambiguous) nickname.
12261 - Clients now use the v2 intro format for hidden service
12262 connections: they specify their chosen rendezvous point by identity
12263 digest rather than by (potentially ambiguous) nickname. Both
12264 are bugfixes on 0.1.2.x, and they could speed up hidden service
12265 connections dramatically. Thanks to Karsten Loesing.
12267 o Minor features (security):
12268 - As a client, do not believe any server that tells us that an
12269 address maps to an internal address space.
12270 - Make it possible to enable HashedControlPassword and
12271 CookieAuthentication at the same time.
12273 o Minor features (guard nodes):
12274 - Tag every guard node in our state file with the version that
12275 we believe added it, or with our own version if we add it. This way,
12276 if a user temporarily runs an old version of Tor and then switches
12277 back to a new one, she doesn't automatically lose her guards.
12279 o Minor features (speed):
12280 - When implementing AES counter mode, update only the portions of the
12281 counter buffer that need to change, and don't keep separate
12282 network-order and host-order counters when they are the same (i.e.,
12283 on big-endian hosts.)
12285 o Minor features (controller):
12286 - Accept LF instead of CRLF on controller, since some software has a
12287 hard time generating real Internet newlines.
12288 - Add GETINFO values for the server status events
12289 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
12292 o Removed features:
12293 - Routers no longer include bandwidth-history lines in their
12294 descriptors; this information is already available in extra-info
12295 documents, and including it in router descriptors took up 60%
12296 (!) of compressed router descriptor downloads. Completes
12297 implementation of proposal 104.
12298 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
12299 and TorControl.py, as they use the old v0 controller protocol,
12300 and are obsoleted by TorFlow anyway.
12301 - Drop support for v1 rendezvous descriptors, since we never used
12302 them anyway, and the code has probably rotted by now. Based on
12303 patch from Karsten Loesing.
12304 - On OSX, stop warning the user that kqueue support in libevent is
12305 "experimental", since it seems to have worked fine for ages.
12308 - When generating information telling us how to extend to a given
12309 router, do not try to include the nickname if it is absent. Fixes
12310 bug 467. Bugfix on 0.2.0.3-alpha.
12311 - Fix a user-triggerable (but not remotely-triggerable) segfault
12312 in expand_filename(). Bugfix on 0.1.2.x.
12313 - Fix a memory leak when freeing incomplete requests from DNSPort.
12314 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
12315 - Don't try to access (or alter) the state file when running
12316 --list-fingerprint or --verify-config or --hash-password. (Resolves
12317 bug 499.) Bugfix on 0.1.2.x.
12318 - Servers used to decline to publish their DirPort if their
12319 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
12320 were below a threshold. Now they only look at BandwidthRate and
12321 RelayBandwidthRate. Bugfix on 0.1.2.x.
12322 - Remove an optimization in the AES counter-mode code that assumed
12323 that the counter never exceeded 2^68. When the counter can be set
12324 arbitrarily as an IV (as it is by Karsten's new hidden services
12325 code), this assumption no longer holds. Bugfix on 0.1.2.x.
12326 - Resume listing "AUTHORITY" flag for authorities in network status.
12327 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
12329 o Code simplifications and refactoring:
12330 - Revamp file-writing logic so we don't need to have the entire
12331 contents of a file in memory at once before we write to disk. Tor,
12333 - Turn "descriptor store" into a full-fledged type.
12334 - Move all NT services code into a separate source file.
12335 - Unify all code that computes medians, percentile elements, etc.
12336 - Get rid of a needless malloc when parsing address policies.
12339 Changes in version 0.1.2.17 - 2007-08-30
12340 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
12341 X bundles. Vidalia 0.0.14 makes authentication required for the
12342 ControlPort in the default configuration, which addresses important
12343 security risks. Everybody who uses Vidalia (or another controller)
12346 In addition, this Tor update fixes major load balancing problems with
12347 path selection, which should speed things up a lot once many people
12350 o Major bugfixes (security):
12351 - We removed support for the old (v0) control protocol. It has been
12352 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
12353 become more of a headache than it's worth.
12355 o Major bugfixes (load balancing):
12356 - When choosing nodes for non-guard positions, weight guards
12357 proportionally less, since they already have enough load. Patch
12359 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
12360 will allow fast Tor servers to get more attention.
12361 - When we're upgrading from an old Tor version, forget our current
12362 guards and pick new ones according to the new weightings. These
12363 three load balancing patches could raise effective network capacity
12364 by a factor of four. Thanks to Mike Perry for measurements.
12366 o Major bugfixes (stream expiration):
12367 - Expire not-yet-successful application streams in all cases if
12368 they've been around longer than SocksTimeout. Right now there are
12369 some cases where the stream will live forever, demanding a new
12370 circuit every 15 seconds. Fixes bug 454; reported by lodger.
12372 o Minor features (controller):
12373 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
12374 is valid before any authentication has been received. It tells
12375 a controller what kind of authentication is expected, and what
12376 protocol is spoken. Implements proposal 119.
12378 o Minor bugfixes (performance):
12379 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
12380 greatly speeding up loading cached-routers from disk on startup.
12381 - Disable sentinel-based debugging for buffer code: we squashed all
12382 the bugs that this was supposed to detect a long time ago, and now
12383 its only effect is to change our buffer sizes from nice powers of
12384 two (which platform mallocs tend to like) to values slightly over
12385 powers of two (which make some platform mallocs sad).
12387 o Minor bugfixes (misc):
12388 - If exit bandwidth ever exceeds one third of total bandwidth, then
12389 use the correct formula to weight exit nodes when choosing paths.
12390 Based on patch from Mike Perry.
12391 - Choose perfectly fairly among routers when choosing by bandwidth and
12392 weighting by fraction of bandwidth provided by exits. Previously, we
12393 would choose with only approximate fairness, and correct ourselves
12394 if we ran off the end of the list.
12395 - If we require CookieAuthentication but we fail to write the
12396 cookie file, we would warn but not exit, and end up in a state
12397 where no controller could authenticate. Now we exit.
12398 - If we require CookieAuthentication, stop generating a new cookie
12399 every time we change any piece of our config.
12400 - Refuse to start with certain directory authority keys, and
12401 encourage people using them to stop.
12402 - Terminate multi-line control events properly. Original patch
12404 - Fix a minor memory leak when we fail to find enough suitable
12405 servers to choose a circuit.
12406 - Stop leaking part of the descriptor when we run into a particularly
12407 unparseable piece of it.
12410 Changes in version 0.2.0.6-alpha - 2007-08-26
12411 This sixth development snapshot features a new Vidalia version in the
12412 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
12413 the ControlPort in the default configuration, which addresses important
12416 In addition, this snapshot fixes major load balancing problems
12417 with path selection, which should speed things up a lot once many
12418 people have upgraded. The directory authorities also use a new
12419 mean-time-between-failure approach to tracking which servers are stable,
12420 rather than just looking at the most recent uptime.
12422 o New directory authorities:
12423 - Set up Tonga as the default bridge directory authority.
12426 - Directory authorities now track servers by weighted
12427 mean-times-between-failures. When we have 4 or more days of data,
12428 use measured MTBF rather than declared uptime to decide whether
12429 to call a router Stable. Implements proposal 108.
12431 o Major bugfixes (load balancing):
12432 - When choosing nodes for non-guard positions, weight guards
12433 proportionally less, since they already have enough load. Patch
12435 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
12436 will allow fast Tor servers to get more attention.
12437 - When we're upgrading from an old Tor version, forget our current
12438 guards and pick new ones according to the new weightings. These
12439 three load balancing patches could raise effective network capacity
12440 by a factor of four. Thanks to Mike Perry for measurements.
12442 o Major bugfixes (descriptor parsing):
12443 - Handle unexpected whitespace better in malformed descriptors. Bug
12444 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
12447 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
12448 GETINFO for Torstat to use until it can switch to using extrainfos.
12449 - Optionally (if built with -DEXPORTMALLINFO) export the output
12450 of mallinfo via http, as tor/mallinfo.txt. Only accessible
12454 - Do not intermix bridge routers with controller-added
12455 routers. (Bugfix on 0.2.0.x)
12456 - Do not fail with an assert when accept() returns an unexpected
12457 address family. Addresses but does not wholly fix bug 483. (Bugfix
12459 - Let directory authorities startup even when they can't generate
12460 a descriptor immediately, e.g. because they don't know their
12462 - Stop putting the authentication cookie in a file called "0"
12463 in your working directory if you don't specify anything for the
12464 new CookieAuthFile option. Reported by Matt Edman.
12465 - Make it possible to read the PROTOCOLINFO response in a way that
12466 conforms to our control-spec. Reported by Matt Edman.
12467 - Fix a minor memory leak when we fail to find enough suitable
12468 servers to choose a circuit. Bugfix on 0.1.2.x.
12469 - Stop leaking part of the descriptor when we run into a particularly
12470 unparseable piece of it. Bugfix on 0.1.2.x.
12471 - Unmap the extrainfo cache file on exit.
12474 Changes in version 0.2.0.5-alpha - 2007-08-19
12475 This fifth development snapshot fixes compilation on Windows again;
12476 fixes an obnoxious client-side bug that slowed things down and put
12477 extra load on the network; gets us closer to using the v3 directory
12478 voting scheme; makes it easier for Tor controllers to use cookie-based
12479 authentication; and fixes a variety of other bugs.
12481 o Removed features:
12482 - Version 1 directories are no longer generated in full. Instead,
12483 authorities generate and serve "stub" v1 directories that list
12484 no servers. This will stop Tor versions 0.1.0.x and earlier from
12485 working, but (for security reasons) nobody should be running those
12488 o Major bugfixes (compilation, 0.2.0.x):
12489 - Try to fix Win32 compilation again: improve checking for IPv6 types.
12490 - Try to fix MSVC compilation: build correctly on platforms that do
12491 not define s6_addr16 or s6_addr32.
12492 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
12495 o Major bugfixes (stream expiration):
12496 - Expire not-yet-successful application streams in all cases if
12497 they've been around longer than SocksTimeout. Right now there are
12498 some cases where the stream will live forever, demanding a new
12499 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
12500 reported by lodger.
12502 o Minor features (directory servers):
12503 - When somebody requests a list of statuses or servers, and we have
12504 none of those, return a 404 rather than an empty 200.
12506 o Minor features (directory voting):
12507 - Store v3 consensus status consensuses on disk, and reload them
12510 o Minor features (security):
12511 - Warn about unsafe ControlPort configurations.
12512 - Refuse to start with certain directory authority keys, and
12513 encourage people using them to stop.
12515 o Minor features (controller):
12516 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
12517 is valid before any authentication has been received. It tells
12518 a controller what kind of authentication is expected, and what
12519 protocol is spoken. Implements proposal 119.
12520 - New config option CookieAuthFile to choose a new location for the
12521 cookie authentication file, and config option
12522 CookieAuthFileGroupReadable to make it group-readable.
12524 o Minor features (unit testing):
12525 - Add command-line arguments to unit-test executable so that we can
12526 invoke any chosen test from the command line rather than having
12527 to run the whole test suite at once; and so that we can turn on
12528 logging for the unit tests.
12530 o Minor bugfixes (on 0.1.2.x):
12531 - If we require CookieAuthentication but we fail to write the
12532 cookie file, we would warn but not exit, and end up in a state
12533 where no controller could authenticate. Now we exit.
12534 - If we require CookieAuthentication, stop generating a new cookie
12535 every time we change any piece of our config.
12536 - When loading bandwidth history, do not believe any information in
12537 the future. Fixes bug 434.
12538 - When loading entry guard information, do not believe any information
12540 - When we have our clock set far in the future and generate an
12541 onion key, then re-set our clock to be correct, we should not stop
12542 the onion key from getting rotated.
12543 - Clean up torrc sample config file.
12544 - Do not automatically run configure from autogen.sh. This
12545 non-standard behavior tended to annoy people who have built other
12548 o Minor bugfixes (on 0.2.0.x):
12549 - Fix a bug with AutomapHostsOnResolve that would always cause
12550 the second request to fail. Bug reported by Kate. Bugfix on
12552 - Fix a bug in ADDRMAP controller replies that would sometimes
12553 try to print a NULL. Patch from tup.
12554 - Read v3 directory authority keys from the right location.
12555 - Numerous bugfixes to directory voting code.
12558 Changes in version 0.1.2.16 - 2007-08-01
12559 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
12560 remote attacker in certain situations to rewrite the user's torrc
12561 configuration file. This can completely compromise anonymity of users
12562 in most configurations, including those running the Vidalia bundles,
12563 TorK, etc. Or worse.
12565 o Major security fixes:
12566 - Close immediately after missing authentication on control port;
12567 do not allow multiple authentication attempts.
12570 Changes in version 0.2.0.4-alpha - 2007-08-01
12571 This fourth development snapshot fixes a critical security vulnerability
12572 for most users, specifically those running Vidalia, TorK, etc. Everybody
12573 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
12575 o Major security fixes:
12576 - Close immediately after missing authentication on control port;
12577 do not allow multiple authentication attempts.
12579 o Major bugfixes (compilation):
12580 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
12583 o Minor features (performance):
12584 - Be even more aggressive about releasing RAM from small
12585 empty buffers. Thanks to our free-list code, this shouldn't be too
12586 performance-intensive.
12587 - Disable sentinel-based debugging for buffer code: we squashed all
12588 the bugs that this was supposed to detect a long time ago, and
12589 now its only effect is to change our buffer sizes from nice
12590 powers of two (which platform mallocs tend to like) to values
12591 slightly over powers of two (which make some platform mallocs sad).
12592 - Log malloc statistics from mallinfo() on platforms where it
12596 Changes in version 0.2.0.3-alpha - 2007-07-29
12597 This third development snapshot introduces new experimental
12598 blocking-resistance features and a preliminary version of the v3
12599 directory voting design, and includes many other smaller features
12603 - The first pieces of our "bridge" design for blocking-resistance
12604 are implemented. People can run bridge directory authorities;
12605 people can run bridges; and people can configure their Tor clients
12606 with a set of bridges to use as the first hop into the Tor network.
12607 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
12609 - Create listener connections before we setuid to the configured
12610 User and Group. Now non-Windows users can choose port values
12611 under 1024, start Tor as root, and have Tor bind those ports
12612 before it changes to another UID. (Windows users could already
12614 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
12615 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
12616 on "vserver" accounts. (Patch from coderman.)
12617 - Be even more aggressive about separating local traffic from relayed
12618 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
12620 o Major features (experimental):
12621 - First cut of code for "v3 dir voting": directory authorities will
12622 vote on a common network status document rather than each publishing
12623 their own opinion. This code needs more testing and more corner-case
12624 handling before it's ready for use.
12627 - Directory authorities now call routers Fast if their bandwidth is
12628 at least 100KB/s, and consider their bandwidth adequate to be a
12629 Guard if it is at least 250KB/s, no matter the medians. This fix
12630 complements proposal 107. [Bugfix on 0.1.2.x]
12631 - Directory authorities now never mark more than 3 servers per IP as
12632 Valid and Running. (Implements proposal 109, by Kevin Bauer and
12634 - Minor change to organizationName and commonName generation
12635 procedures in TLS certificates during Tor handshakes, to invalidate
12636 some earlier censorware approaches. This is not a long-term
12637 solution, but applying it will give us a bit of time to look into
12638 the epidemiology of countermeasures as they spread.
12640 o Major bugfixes (directory):
12641 - Rewrite directory tokenization code to never run off the end of
12642 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
12644 o Minor features (controller):
12645 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
12646 match requests to applications. (Patch from Robert Hogan.)
12647 - Report address and port correctly on connections to DNSPort. (Patch
12648 from Robert Hogan.)
12649 - Add a RESOLVE command to launch hostname lookups. (Original patch
12650 from Robert Hogan.)
12651 - Add GETINFO status/enough-dir-info to let controllers tell whether
12652 Tor has downloaded sufficient directory information. (Patch
12654 - You can now use the ControlSocket option to tell Tor to listen for
12655 controller connections on Unix domain sockets on systems that
12656 support them. (Patch from Peter Palfrader.)
12657 - STREAM NEW events are generated for DNSPort requests and for
12658 tunneled directory connections. (Patch from Robert Hogan.)
12659 - New "GETINFO address-mappings/*" command to get address mappings
12660 with expiry information. "addr-mappings/*" is now deprecated.
12663 o Minor features (misc):
12664 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
12666 - The tor-gencert tool for v3 directory authorities now creates all
12667 files as readable to the file creator only, and write-protects
12668 the authority identity key.
12669 - When dumping memory usage, list bytes used in buffer memory
12671 - When running with dmalloc, dump more stats on hup and on exit.
12672 - Directory authorities now fail quickly and (relatively) harmlessly
12673 if they generate a network status document that is somehow
12676 o Traffic load balancing improvements:
12677 - If exit bandwidth ever exceeds one third of total bandwidth, then
12678 use the correct formula to weight exit nodes when choosing paths.
12679 (Based on patch from Mike Perry.)
12680 - Choose perfectly fairly among routers when choosing by bandwidth and
12681 weighting by fraction of bandwidth provided by exits. Previously, we
12682 would choose with only approximate fairness, and correct ourselves
12683 if we ran off the end of the list. [Bugfix on 0.1.2.x]
12685 o Performance improvements:
12686 - Be more aggressive with freeing buffer RAM or putting it on the
12688 - Use Critical Sections rather than Mutexes for synchronizing threads
12689 on win32; Mutexes are heavier-weight, and designed for synchronizing
12692 o Deprecated and removed features:
12693 - RedirectExits is now deprecated.
12694 - Stop allowing address masks that do not correspond to bit prefixes.
12695 We have warned about these for a really long time; now it's time
12696 to reject them. (Patch from croup.)
12698 o Minor bugfixes (directory):
12699 - Fix another crash bug related to extra-info caching. (Bug found by
12700 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
12701 - Directories no longer return a "304 not modified" when they don't
12702 have the networkstatus the client asked for. Also fix a memory
12703 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
12704 - We had accidentally labelled 0.1.2.x directory servers as not
12705 suitable for begin_dir requests, and had labelled no directory
12706 servers as suitable for uploading extra-info documents. [Bugfix
12709 o Minor bugfixes (dns):
12710 - Fix a crash when DNSPort is set more than once. (Patch from Robert
12711 Hogan.) [Bugfix on 0.2.0.2-alpha]
12712 - Add DNSPort connections to the global connection list, so that we
12713 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
12715 - Fix a dangling reference that could lead to a crash when DNSPort is
12716 changed or closed (Patch from Robert Hogan.) [Bugfix on
12719 o Minor bugfixes (controller):
12720 - Provide DNS expiry times in GMT, not in local time. For backward
12721 compatibility, ADDRMAP events only provide GMT expiry in an extended
12722 field. "GETINFO address-mappings" always does the right thing.
12723 - Use CRLF line endings properly in NS events.
12724 - Terminate multi-line control events properly. (Original patch
12725 from tup.) [Bugfix on 0.1.2.x-alpha]
12726 - Do not include spaces in SOURCE_ADDR fields in STREAM
12727 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
12730 Changes in version 0.1.2.15 - 2007-07-17
12731 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
12732 problems, fixes compilation on BSD, and fixes a variety of other
12733 bugs. Everybody should upgrade.
12735 o Major bugfixes (compilation):
12736 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
12738 o Major bugfixes (crashes):
12739 - Try even harder not to dereference the first character after
12740 an mmap(). Reported by lodger.
12741 - Fix a crash bug in directory authorities when we re-number the
12742 routerlist while inserting a new router.
12743 - When the cached-routers file is an even multiple of the page size,
12744 don't run off the end and crash. (Fixes bug 455; based on idea
12746 - Fix eventdns.c behavior on Solaris: It is critical to include
12747 orconfig.h _before_ sys/types.h, so that we can get the expected
12748 definition of _FILE_OFFSET_BITS.
12750 o Major bugfixes (security):
12751 - Fix a possible buffer overrun when using BSD natd support. Bug
12753 - When sending destroy cells from a circuit's origin, don't include
12754 the reason for tearing down the circuit. The spec says we didn't,
12755 and now we actually don't. Reported by lodger.
12756 - Keep streamids from different exits on a circuit separate. This
12757 bug may have allowed other routers on a given circuit to inject
12758 cells into streams. Reported by lodger; fixes bug 446.
12759 - If there's a never-before-connected-to guard node in our list,
12760 never choose any guards past it. This way we don't expand our
12761 guard list unless we need to.
12763 o Minor bugfixes (guard nodes):
12764 - Weight guard selection by bandwidth, so that low-bandwidth nodes
12765 don't get overused as guards.
12767 o Minor bugfixes (directory):
12768 - Correctly count the number of authorities that recommend each
12769 version. Previously, we were under-counting by 1.
12770 - Fix a potential crash bug when we load many server descriptors at
12771 once and some of them make others of them obsolete. Fixes bug 458.
12773 o Minor bugfixes (hidden services):
12774 - Stop tearing down the whole circuit when the user asks for a
12775 connection to a port that the hidden service didn't configure.
12778 o Minor bugfixes (misc):
12779 - On Windows, we were preventing other processes from reading
12780 cached-routers while Tor was running. Reported by janbar.
12781 - Fix a possible (but very unlikely) bug in picking routers by
12782 bandwidth. Add a log message to confirm that it is in fact
12783 unlikely. Patch from lodger.
12784 - Backport a couple of memory leak fixes.
12785 - Backport miscellaneous cosmetic bugfixes.
12788 Changes in version 0.2.0.2-alpha - 2007-06-02
12789 o Major bugfixes on 0.2.0.1-alpha:
12790 - Fix an assertion failure related to servers without extra-info digests.
12791 Resolves bugs 441 and 442.
12793 o Minor features (directory):
12794 - Support "If-Modified-Since" when answering HTTP requests for
12795 directories, running-routers documents, and network-status documents.
12796 (There's no need to support it for router descriptors, since those
12797 are downloaded by descriptor digest.)
12799 o Minor build issues:
12800 - Clear up some MIPSPro compiler warnings.
12801 - When building from a tarball on a machine that happens to have SVK
12802 installed, report the micro-revision as whatever version existed
12803 in the tarball, not as "x".
12806 Changes in version 0.2.0.1-alpha - 2007-06-01
12807 This early development snapshot provides new features for people running
12808 Tor as both a client and a server (check out the new RelayBandwidth
12809 config options); lets Tor run as a DNS proxy; and generally moves us
12810 forward on a lot of fronts.
12812 o Major features, server usability:
12813 - New config options RelayBandwidthRate and RelayBandwidthBurst:
12814 a separate set of token buckets for relayed traffic. Right now
12815 relayed traffic is defined as answers to directory requests, and
12816 OR connections that don't have any local circuits on them.
12818 o Major features, client usability:
12819 - A client-side DNS proxy feature to replace the need for
12820 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
12821 for DNS requests on port 9999, use the Tor network to resolve them
12822 anonymously, and send the reply back like a regular DNS server.
12823 The code still only implements a subset of DNS.
12824 - Make PreferTunneledDirConns and TunnelDirConns work even when
12825 we have no cached directory info. This means Tor clients can now
12826 do all of their connections protected by TLS.
12828 o Major features, performance and efficiency:
12829 - Directory authorities accept and serve "extra info" documents for
12830 routers. These documents contain fields from router descriptors
12831 that aren't usually needed, and that use a lot of excess
12832 bandwidth. Once these fields are removed from router descriptors,
12833 the bandwidth savings should be about 60%. [Partially implements
12835 - Servers upload extra-info documents to any authority that accepts
12836 them. Authorities (and caches that have been configured to download
12837 extra-info documents) download them as needed. [Partially implements
12839 - Change the way that Tor buffers data that it is waiting to write.
12840 Instead of queueing data cells in an enormous ring buffer for each
12841 client->OR or OR->OR connection, we now queue cells on a separate
12842 queue for each circuit. This lets us use less slack memory, and
12843 will eventually let us be smarter about prioritizing different kinds
12845 - Use memory pools to allocate cells with better speed and memory
12846 efficiency, especially on platforms where malloc() is inefficient.
12847 - Stop reading on edge connections when their corresponding circuit
12848 buffers are full; start again as the circuits empty out.
12850 o Major features, other:
12851 - Add an HSAuthorityRecordStats option that hidden service authorities
12852 can use to track statistics of overall hidden service usage without
12853 logging information that would be very useful to an attacker.
12854 - Start work implementing multi-level keys for directory authorities:
12855 Add a standalone tool to generate key certificates. (Proposal 103.)
12858 - Directory authorities now call routers Stable if they have an
12859 uptime of at least 30 days, even if that's not the median uptime
12860 in the network. Implements proposal 107, suggested by Kevin Bauer
12863 o Minor fixes (resource management):
12864 - Count the number of open sockets separately from the number
12865 of active connection_t objects. This will let us avoid underusing
12866 our allocated connection limit.
12867 - We no longer use socket pairs to link an edge connection to an
12868 anonymous directory connection or a DirPort test connection.
12869 Instead, we track the link internally and transfer the data
12870 in-process. This saves two sockets per "linked" connection (at the
12871 client and at the server), and avoids the nasty Windows socketpair()
12873 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
12874 for every single inactive connection_t. Free items from the
12875 4k/16k-buffer free lists when they haven't been used for a while.
12877 o Minor features (build):
12878 - Make autoconf search for libevent, openssl, and zlib consistently.
12879 - Update deprecated macros in configure.in.
12880 - When warning about missing headers, tell the user to let us
12881 know if the compile succeeds anyway, so we can downgrade the
12883 - Include the current subversion revision as part of the version
12884 string: either fetch it directly if we're in an SVN checkout, do
12885 some magic to guess it if we're in an SVK checkout, or use
12886 the last-detected version if we're building from a .tar.gz.
12887 Use this version consistently in log messages.
12889 o Minor features (logging):
12890 - Always prepend "Bug: " to any log message about a bug.
12891 - Put a platform string (e.g. "Linux i686") in the startup log
12892 message, so when people paste just their logs, we know if it's
12893 OpenBSD or Windows or what.
12894 - When logging memory usage, break down memory used in buffers by
12897 o Minor features (directory system):
12898 - New config option V2AuthoritativeDirectory that all directory
12899 authorities should set. This will let future authorities choose
12900 not to serve V2 directory information.
12901 - Directory authorities allow multiple router descriptors and/or extra
12902 info documents to be uploaded in a single go. This will make
12903 implementing proposal 104 simpler.
12905 o Minor features (controller):
12906 - Add a new config option __DisablePredictedCircuits designed for
12907 use by the controller, when we don't want Tor to build any circuits
12909 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
12910 so we can exit from the middle of the circuit.
12911 - Implement "getinfo status/circuit-established".
12912 - Implement "getinfo status/version/..." so a controller can tell
12913 whether the current version is recommended, and whether any versions
12914 are good, and how many authorities agree. (Patch from shibz.)
12916 o Minor features (hidden services):
12917 - Allow multiple HiddenServicePort directives with the same virtual
12918 port; when they occur, the user is sent round-robin to one
12919 of the target ports chosen at random. Partially fixes bug 393 by
12920 adding limited ad-hoc round-robining.
12922 o Minor features (other):
12924 - Add a new AutomapHostsOnResolve option: when it is enabled, any
12925 resolve request for hosts matching a given pattern causes Tor to
12926 generate an internal virtual address mapping for that host. This
12927 allows DNSPort to work sensibly with hidden service users. By
12928 default, .exit and .onion addresses are remapped; the list of
12929 patterns can be reconfigured with AutomapHostsSuffixes.
12930 - Add an "-F" option to tor-resolve to force a resolve for a .onion
12931 address. Thanks to the AutomapHostsOnResolve option, this is no
12932 longer a completely silly thing to do.
12933 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
12934 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
12935 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
12936 minus 1 byte: the actual maximum declared bandwidth.
12938 o Removed features:
12939 - Removed support for the old binary "version 0" controller protocol.
12940 This has been deprecated since 0.1.1, and warnings have been issued
12941 since 0.1.2. When we encounter a v0 control message, we now send
12942 back an error and close the connection.
12943 - Remove the old "dns worker" server DNS code: it hasn't been default
12944 since 0.1.2.2-alpha, and all the servers seem to be using the new
12947 o Minor bugfixes (portability):
12948 - Even though Windows is equally happy with / and \ as path separators,
12949 try to use \ consistently on Windows and / consistently on Unix: it
12950 makes the log messages nicer.
12951 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
12952 - Read resolv.conf files correctly on platforms where read() returns
12953 partial results on small file reads.
12955 o Minor bugfixes (directory):
12956 - Correctly enforce that elements of directory objects do not appear
12957 more often than they are allowed to appear.
12958 - When we are reporting the DirServer line we just parsed, we were
12959 logging the second stanza of the key fingerprint, not the first.
12961 o Minor bugfixes (logging):
12962 - When we hit an EOF on a log (probably because we're shutting down),
12963 don't try to remove the log from the list: just mark it as
12964 unusable. (Bulletproofs against bug 222.)
12966 o Minor bugfixes (other):
12967 - In the exitlist script, only consider the most recently published
12968 server descriptor for each server. Also, when the user requests
12969 a list of servers that _reject_ connections to a given address,
12970 explicitly exclude the IPs that also have servers that accept
12971 connections to that address. (Resolves bug 405.)
12972 - Stop allowing hibernating servers to be "stable" or "fast".
12973 - On Windows, we were preventing other processes from reading
12974 cached-routers while Tor was running. (Reported by janbar)
12975 - Make the NodeFamilies config option work. (Reported by
12976 lodger -- it has never actually worked, even though we added it
12978 - Check return values from pthread_mutex functions.
12979 - Don't save non-general-purpose router descriptors to the disk cache,
12980 because we have no way of remembering what their purpose was when
12982 - Add even more asserts to hunt down bug 417.
12983 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
12984 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
12985 Add a log message to confirm that it is in fact unlikely.
12987 o Minor bugfixes (controller):
12988 - Make 'getinfo fingerprint' return a 551 error if we're not a
12989 server, so we match what the control spec claims we do. Reported
12991 - Fix a typo in an error message when extendcircuit fails that
12992 caused us to not follow the \r\n-based delimiter protocol. Reported
12995 o Code simplifications and refactoring:
12996 - Stop passing around circuit_t and crypt_path_t pointers that are
12997 implicit in other procedure arguments.
12998 - Drop the old code to choke directory connections when the
12999 corresponding OR connections got full: thanks to the cell queue
13000 feature, OR conns don't get full any more.
13001 - Make dns_resolve() handle attaching connections to circuits
13002 properly, so the caller doesn't have to.
13003 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
13004 - Keep the connection array as a dynamic smartlist_t, rather than as
13005 a fixed-sized array. This is important, as the number of connections
13006 is becoming increasingly decoupled from the number of sockets.
13009 Changes in version 0.1.2.14 - 2007-05-25
13010 Tor 0.1.2.14 changes the addresses of two directory authorities (this
13011 change especially affects those who serve or use hidden services),
13012 and fixes several other crash- and security-related bugs.
13014 o Directory authority changes:
13015 - Two directory authorities (moria1 and moria2) just moved to new
13016 IP addresses. This change will particularly affect those who serve
13017 or use hidden services.
13019 o Major bugfixes (crashes):
13020 - If a directory server runs out of space in the connection table
13021 as it's processing a begin_dir request, it will free the exit stream
13022 but leave it attached to the circuit, leading to unpredictable
13023 behavior. (Reported by seeess, fixes bug 425.)
13024 - Fix a bug in dirserv_remove_invalid() that would cause authorities
13025 to corrupt memory under some really unlikely scenarios.
13026 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
13027 - Avoid segfaults when reading from mmaped descriptor file. (Reported
13030 o Major bugfixes (security):
13031 - When choosing an entry guard for a circuit, avoid using guards
13032 that are in the same family as the chosen exit -- not just guards
13033 that are exactly the chosen exit. (Reported by lodger.)
13035 o Major bugfixes (resource management):
13036 - If a directory authority is down, skip it when deciding where to get
13037 networkstatus objects or descriptors. Otherwise we keep asking
13038 every 10 seconds forever. Fixes bug 384.
13039 - Count it as a failure if we fetch a valid network-status but we
13040 don't want to keep it. Otherwise we'll keep fetching it and keep
13041 not wanting to keep it. Fixes part of bug 422.
13042 - If all of our dirservers have given us bad or no networkstatuses
13043 lately, then stop hammering them once per minute even when we
13044 think they're failed. Fixes another part of bug 422.
13047 - Actually set the purpose correctly for descriptors inserted with
13048 purpose=controller.
13049 - When we have k non-v2 authorities in our DirServer config,
13050 we ignored the last k authorities in the list when updating our
13052 - Correctly back-off from requesting router descriptors that we are
13053 having a hard time downloading.
13054 - Read resolv.conf files correctly on platforms where read() returns
13055 partial results on small file reads.
13056 - Don't rebuild the entire router store every time we get 32K of
13057 routers: rebuild it when the journal gets very large, or when
13058 the gaps in the store get very large.
13061 - When routers publish SVN revisions in their router descriptors,
13062 authorities now include those versions correctly in networkstatus
13064 - Warn when using a version of libevent before 1.3b to run a server on
13065 OSX or BSD: these versions interact badly with userspace threads.
13068 Changes in version 0.1.2.13 - 2007-04-24
13069 This release features some major anonymity fixes, such as safer path
13070 selection; better client performance; faster bootstrapping, better
13071 address detection, and better DNS support for servers; write limiting as
13072 well as read limiting to make servers easier to run; and a huge pile of
13073 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
13075 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
13076 of the Freenode IRC network, remembering his patience and vision for
13077 free speech on the Internet.
13080 - Fix a memory leak when we ask for "all" networkstatuses and we
13081 get one we don't recognize.
13082 - Add more asserts to hunt down bug 417.
13083 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
13086 Changes in version 0.1.2.12-rc - 2007-03-16
13088 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
13089 directory information requested inside Tor connections (i.e. via
13090 begin_dir cells). It only triggered when the same connection was
13091 serving other data at the same time. Reported by seeess.
13094 - When creating a circuit via the controller, send a 'launched'
13095 event when we're done, so we follow the spec better.
13098 Changes in version 0.1.2.11-rc - 2007-03-15
13099 o Minor bugfixes (controller), reported by daejees:
13100 - Correct the control spec to match how the code actually responds
13101 to 'getinfo addr-mappings/*'.
13102 - The control spec described a GUARDS event, but the code
13103 implemented a GUARD event. Standardize on GUARD, but let people
13104 ask for GUARDS too.
13107 Changes in version 0.1.2.10-rc - 2007-03-07
13108 o Major bugfixes (Windows):
13109 - Do not load the NT services library functions (which may not exist)
13110 just to detect if we're a service trying to shut down. Now we run
13111 on Win98 and friends again.
13113 o Minor bugfixes (other):
13114 - Clarify a couple of log messages.
13115 - Fix a misleading socks5 error number.
13118 Changes in version 0.1.2.9-rc - 2007-03-02
13119 o Major bugfixes (Windows):
13120 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
13121 of the usual GCC "%llu". This prevents a bug when saving 64-bit
13122 int configuration values: the high-order 32 bits would get
13123 truncated. In particular, we were being bitten by the default
13124 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
13125 and maybe also bug 397.)
13127 o Minor bugfixes (performance):
13128 - Use OpenSSL's AES implementation on platforms where it's faster.
13129 This could save us as much as 10% CPU usage.
13131 o Minor bugfixes (server):
13132 - Do not rotate onion key immediately after setting it for the first
13135 o Minor bugfixes (directory authorities):
13136 - Stop calling servers that have been hibernating for a long time
13137 "stable". Also, stop letting hibernating or obsolete servers affect
13138 uptime and bandwidth cutoffs.
13139 - Stop listing hibernating servers in the v1 directory.
13141 o Minor bugfixes (hidden services):
13142 - Upload hidden service descriptors slightly less often, to reduce
13143 load on authorities.
13145 o Minor bugfixes (other):
13146 - Fix an assert that could trigger if a controller quickly set then
13147 cleared EntryNodes. Bug found by Udo van den Heuvel.
13148 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
13150 - Fix a potential race condition in the rpm installer. Found by
13152 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
13153 of 2 as indicating that the server is completely bad; it sometimes
13154 means that the server is just bad for the request in question. (may fix
13155 the last of bug 326.)
13156 - Disable encrypted directory connections when we don't have a server
13157 descriptor for the destination. We'll get this working again in
13161 Changes in version 0.1.2.8-beta - 2007-02-26
13162 o Major bugfixes (crashes):
13163 - Stop crashing when the controller asks us to resetconf more than
13164 one config option at once. (Vidalia 0.0.11 does this.)
13165 - Fix a crash that happened on Win98 when we're given command-line
13166 arguments: don't try to load NT service functions from advapi32.dll
13167 except when we need them. (Bug introduced in 0.1.2.7-alpha;
13169 - Fix a longstanding obscure crash bug that could occur when
13170 we run out of DNS worker processes. (Resolves bug 390.)
13172 o Major bugfixes (hidden services):
13173 - Correctly detect whether hidden service descriptor downloads are
13174 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
13176 o Major bugfixes (accounting):
13177 - When we start during an accounting interval before it's time to wake
13178 up, remember to wake up at the correct time. (May fix bug 342.)
13180 o Minor bugfixes (controller):
13181 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
13182 clear the corresponding on_circuit variable, and remember later
13183 that we don't need to send a redundant CLOSED event. Resolves part
13185 - Report events where a resolve succeeded or where we got a socks
13186 protocol error correctly, rather than calling both of them
13188 - Change reported stream target addresses to IP consistently when
13189 we finally get the IP from an exit node.
13190 - Send log messages to the controller even if they happen to be very
13193 o Minor bugfixes (other):
13194 - Display correct results when reporting which versions are
13195 recommended, and how recommended they are. (Resolves bug 383.)
13196 - Improve our estimates for directory bandwidth to be less random:
13197 guess that an unrecognized directory will have the average bandwidth
13198 from all known directories, not that it will have the average
13199 bandwidth from those directories earlier than it on the list.
13200 - If we start a server with ClientOnly 1, then set ClientOnly to 0
13201 and hup, stop triggering an assert based on an empty onion_key.
13202 - On platforms with no working mmap() equivalent, don't warn the
13203 user when cached-routers doesn't exist.
13204 - Warn the user when mmap() [or its equivalent] fails for some reason
13205 other than file-not-found.
13206 - Don't warn the user when cached-routers.new doesn't exist: that's
13207 perfectly fine when starting up for the first time.
13208 - When EntryNodes are configured, rebuild the guard list to contain,
13209 in order: the EntryNodes that were guards before; the rest of the
13210 EntryNodes; the nodes that were guards before.
13211 - Mask out all signals in sub-threads; only the libevent signal
13212 handler should be processing them. This should prevent some crashes
13213 on some machines using pthreads. (Patch from coderman.)
13214 - Fix switched arguments on memset in the implementation of
13215 tor_munmap() for systems with no mmap() call.
13216 - When Tor receives a router descriptor that it asked for, but
13217 no longer wants (because it has received fresh networkstatuses
13218 in the meantime), do not warn the user. Cache the descriptor if
13219 we're a cache; drop it if we aren't.
13220 - Make earlier entry guards _really_ get retried when the network
13222 - On a malformed DNS reply, always give an error to the corresponding
13224 - Build with recent libevents on platforms that do not define the
13225 nonstandard types "u_int8_t" and friends.
13227 o Minor features (controller):
13228 - Warn the user when an application uses the obsolete binary v0
13229 control protocol. We're planning to remove support for it during
13230 the next development series, so it's good to give people some
13232 - Add STREAM_BW events to report per-entry-stream bandwidth
13233 use. (Patch from Robert Hogan.)
13234 - Rate-limit SIGNEWNYM signals in response to controllers that
13235 impolitely generate them for every single stream. (Patch from
13236 mwenge; closes bug 394.)
13237 - Make REMAP stream events have a SOURCE (cache or exit), and
13238 make them generated in every case where we get a successful
13239 connected or resolved cell.
13241 o Minor bugfixes (performance):
13242 - Call router_have_min_dir_info half as often. (This is showing up in
13243 some profiles, but not others.)
13244 - When using GCC, make log_debug never get called at all, and its
13245 arguments never get evaluated, when no debug logs are configured.
13246 (This is showing up in some profiles, but not others.)
13249 - Remove some never-implemented options. Mark PathlenCoinWeight as
13251 - Implement proposal 106: Stop requiring clients to have well-formed
13252 certificates; stop checking nicknames in certificates. (Clients
13253 have certificates so that they can look like Tor servers, but in
13254 the future we might want to allow them to look like regular TLS
13255 clients instead. Nicknames in certificates serve no purpose other
13256 than making our protocol easier to recognize on the wire.)
13257 - Revise messages on handshake failure again to be even more clear about
13258 which are incoming connections and which are outgoing.
13259 - Discard any v1 directory info that's over 1 month old (for
13260 directories) or over 1 week old (for running-routers lists).
13261 - Do not warn when individual nodes in the configuration's EntryNodes,
13262 ExitNodes, etc are down: warn only when all possible nodes
13263 are down. (Fixes bug 348.)
13264 - Always remove expired routers and networkstatus docs before checking
13265 whether we have enough information to build circuits. (Fixes
13267 - Put a lower-bound on MaxAdvertisedBandwidth.
13270 Changes in version 0.1.2.7-alpha - 2007-02-06
13271 o Major bugfixes (rate limiting):
13272 - Servers decline directory requests much more aggressively when
13273 they're low on bandwidth. Otherwise they end up queueing more and
13274 more directory responses, which can't be good for latency.
13275 - But never refuse directory requests from local addresses.
13276 - Fix a memory leak when sending a 503 response for a networkstatus
13278 - Be willing to read or write on local connections (e.g. controller
13279 connections) even when the global rate limiting buckets are empty.
13280 - If our system clock jumps back in time, don't publish a negative
13281 uptime in the descriptor. Also, don't let the global rate limiting
13282 buckets go absurdly negative.
13283 - Flush local controller connection buffers periodically as we're
13284 writing to them, so we avoid queueing 4+ megabytes of data before
13287 o Major bugfixes (NT services):
13288 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
13289 command-line flag so that admins can override the default by saying
13290 "tor --service install --user "SomeUser"". This will not affect
13291 existing installed services. Also, warn the user that the service
13292 will look for its configuration file in the service user's
13293 %appdata% directory. (We can't do the 'hardwire the user's appdata
13294 directory' trick any more, since we may not have read access to that
13297 o Major bugfixes (other):
13298 - Previously, we would cache up to 16 old networkstatus documents
13299 indefinitely, if they came from nontrusted authorities. Now we
13300 discard them if they are more than 10 days old.
13301 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
13303 - Detect and reject malformed DNS responses containing circular
13305 - If exits are rare enough that we're not marking exits as guards,
13306 ignore exit bandwidth when we're deciding the required bandwidth
13308 - When we're handling a directory connection tunneled over Tor,
13309 don't fill up internal memory buffers with all the data we want
13310 to tunnel; instead, only add it if the OR connection that will
13311 eventually receive it has some room for it. (This can lead to
13312 slowdowns in tunneled dir connections; a better solution will have
13313 to wait for 0.2.0.)
13315 o Minor bugfixes (dns):
13316 - Add some defensive programming to eventdns.c in an attempt to catch
13317 possible memory-stomping bugs.
13318 - Detect and reject DNS replies containing IPv4 or IPv6 records with
13319 an incorrect number of bytes. (Previously, we would ignore the
13321 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
13322 in the correct order, and doesn't crash.
13323 - Free memory held in recently-completed DNS lookup attempts on exit.
13324 This was not a memory leak, but may have been hiding memory leaks.
13325 - Handle TTL values correctly on reverse DNS lookups.
13326 - Treat failure to parse resolv.conf as an error.
13328 o Minor bugfixes (other):
13329 - Fix crash with "tor --list-fingerprint" (reported by seeess).
13330 - When computing clock skew from directory HTTP headers, consider what
13331 time it was when we finished asking for the directory, not what
13333 - Expire socks connections if they spend too long waiting for the
13334 handshake to finish. Previously we would let them sit around for
13335 days, if the connecting application didn't close them either.
13336 - And if the socks handshake hasn't started, don't send a
13337 "DNS resolve socks failed" handshake reply; just close it.
13338 - Stop using C functions that OpenBSD's linker doesn't like.
13339 - Don't launch requests for descriptors unless we have networkstatuses
13340 from at least half of the authorities. This delays the first
13341 download slightly under pathological circumstances, but can prevent
13342 us from downloading a bunch of descriptors we don't need.
13343 - Do not log IPs with TLS failures for incoming TLS
13344 connections. (Fixes bug 382.)
13345 - If the user asks to use invalid exit nodes, be willing to use
13347 - Stop using the reserved ac_cv namespace in our configure script.
13348 - Call stat() slightly less often; use fstat() when possible.
13349 - Refactor the way we handle pending circuits when an OR connection
13350 completes or fails, in an attempt to fix a rare crash bug.
13351 - Only rewrite a conn's address based on X-Forwarded-For: headers
13352 if it's a parseable public IP address; and stop adding extra quotes
13353 to the resulting address.
13356 - Weight directory requests by advertised bandwidth. Now we can
13357 let servers enable write limiting but still allow most clients to
13358 succeed at their directory requests. (We still ignore weights when
13359 choosing a directory authority; I hope this is a feature.)
13362 - Create a new file ReleaseNotes which was the old ChangeLog. The
13363 new ChangeLog file now includes the summaries for all development
13365 - Check for addresses with invalid characters at the exit as well
13366 as at the client, and warn less verbosely when they fail. You can
13367 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
13368 - Adapt a patch from goodell to let the contrib/exitlist script
13369 take arguments rather than require direct editing.
13370 - Inform the server operator when we decide not to advertise a
13371 DirPort due to AccountingMax enabled or a low BandwidthRate. It
13372 was confusing Zax, so now we're hopefully more helpful.
13373 - Bring us one step closer to being able to establish an encrypted
13374 directory tunnel without knowing a descriptor first. Still not
13375 ready yet. As part of the change, now assume we can use a
13376 create_fast cell if we don't know anything about a router.
13377 - Allow exit nodes to use nameservers running on ports other than 53.
13378 - Servers now cache reverse DNS replies.
13379 - Add an --ignore-missing-torrc command-line option so that we can
13380 get the "use sensible defaults if the configuration file doesn't
13381 exist" behavior even when specifying a torrc location on the command
13384 o Minor features (controller):
13385 - Track reasons for OR connection failure; make these reasons
13386 available via the controller interface. (Patch from Mike Perry.)
13387 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
13388 can learn when clients are sending malformed hostnames to Tor.
13389 - Clean up documentation for controller status events.
13390 - Add a REMAP status to stream events to note that a stream's
13391 address has changed because of a cached address or a MapAddress
13395 Changes in version 0.1.2.6-alpha - 2007-01-09
13397 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
13398 connection handles more than 4 gigs in either direction, we crash.
13399 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
13400 advertised exit node, somebody might try to exit from us when
13401 we're bootstrapping and before we've built our descriptor yet.
13402 Refuse the connection rather than crashing.
13405 - Warn if we (as a server) find that we've resolved an address that we
13406 weren't planning to resolve.
13407 - Warn that using select() on any libevent version before 1.1 will be
13408 unnecessarily slow (even for select()).
13409 - Flush ERR-level controller status events just like we currently
13410 flush ERR-level log events, so that a Tor shutdown doesn't prevent
13411 the controller from learning about current events.
13413 o Minor features (more controller status events):
13414 - Implement EXTERNAL_ADDRESS server status event so controllers can
13415 learn when our address changes.
13416 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
13417 can learn when directories reject our descriptor.
13418 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
13419 can learn when a client application is speaking a non-socks protocol
13421 - Implement DANGEROUS_SOCKS client status event so controllers
13422 can learn when a client application is leaking DNS addresses.
13423 - Implement BUG general status event so controllers can learn when
13424 Tor is unhappy about its internal invariants.
13425 - Implement CLOCK_SKEW general status event so controllers can learn
13426 when Tor thinks the system clock is set incorrectly.
13427 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
13428 server status events so controllers can learn when their descriptors
13429 are accepted by a directory.
13430 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
13431 server status events so controllers can learn about Tor's progress in
13432 deciding whether it's reachable from the outside.
13433 - Implement BAD_LIBEVENT general status event so controllers can learn
13434 when we have a version/method combination in libevent that needs to
13436 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
13437 and DNS_USELESS server status events so controllers can learn
13438 about changes to DNS server status.
13440 o Minor features (directory):
13441 - Authorities no longer recommend exits as guards if this would shift
13442 too much load to the exit nodes.
13445 Changes in version 0.1.2.5-alpha - 2007-01-06
13447 - Enable write limiting as well as read limiting. Now we sacrifice
13448 capacity if we're pushing out lots of directory traffic, rather
13449 than overrunning the user's intended bandwidth limits.
13450 - Include TLS overhead when counting bandwidth usage; previously, we
13451 would count only the bytes sent over TLS, but not the bytes used
13453 - Support running the Tor service with a torrc not in the same
13454 directory as tor.exe and default to using the torrc located in
13455 the %appdata%\Tor\ of the user who installed the service. Patch
13457 - Servers now check for the case when common DNS requests are going to
13458 wildcarded addresses (i.e. all getting the same answer), and change
13459 their exit policy to reject *:* if it's happening.
13460 - Implement BEGIN_DIR cells, so we can connect to the directory
13461 server via TLS to do encrypted directory requests rather than
13462 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
13463 config options if you like.
13465 o Minor features (config and docs):
13466 - Start using the state file to store bandwidth accounting data:
13467 the bw_accounting file is now obsolete. We'll keep generating it
13468 for a while for people who are still using 0.1.2.4-alpha.
13469 - Try to batch changes to the state file so that we do as few
13470 disk writes as possible while still storing important things in
13472 - The state file and the bw_accounting file get saved less often when
13473 the AvoidDiskWrites config option is set.
13474 - Make PIDFile work on Windows (untested).
13475 - Add internal descriptions for a bunch of configuration options:
13476 accessible via controller interface and in comments in saved
13478 - Reject *:563 (NNTPS) in the default exit policy. We already reject
13479 NNTP by default, so this seems like a sensible addition.
13480 - Clients now reject hostnames with invalid characters. This should
13481 avoid some inadvertent info leaks. Add an option
13482 AllowNonRFC953Hostnames to disable this behavior, in case somebody
13483 is running a private network with hosts called @, !, and #.
13484 - Add a maintainer script to tell us which options are missing
13485 documentation: "make check-docs".
13486 - Add a new address-spec.txt document to describe our special-case
13487 addresses: .exit, .onion, and .noconnnect.
13489 o Minor features (DNS):
13490 - Ongoing work on eventdns infrastructure: now it has dns server
13491 and ipv6 support. One day Tor will make use of it.
13492 - Add client-side caching for reverse DNS lookups.
13493 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
13494 - When we change nameservers or IP addresses, reset and re-launch
13495 our tests for DNS hijacking.
13497 o Minor features (directory):
13498 - Authorities now specify server versions in networkstatus. This adds
13499 about 2% to the size of compressed networkstatus docs, and allows
13500 clients to tell which servers support BEGIN_DIR and which don't.
13501 The implementation is forward-compatible with a proposed future
13502 protocol version scheme not tied to Tor versions.
13503 - DirServer configuration lines now have an orport= option so
13504 clients can open encrypted tunnels to the authorities without
13505 having downloaded their descriptors yet. Enabled for moria1,
13506 moria2, tor26, and lefkada now in the default configuration.
13507 - Directory servers are more willing to send a 503 "busy" if they
13508 are near their write limit, especially for v1 directory requests.
13509 Now they can use their limited bandwidth for actual Tor traffic.
13510 - Clients track responses with status 503 from dirservers. After a
13511 dirserver has given us a 503, we try not to use it until an hour has
13512 gone by, or until we have no dirservers that haven't given us a 503.
13513 - When we get a 503 from a directory, and we're not a server, we don't
13514 count the failure against the total number of failures allowed
13515 for the thing we're trying to download.
13516 - Report X-Your-Address-Is correctly from tunneled directory
13517 connections; don't report X-Your-Address-Is when it's an internal
13518 address; and never believe reported remote addresses when they're
13520 - Protect against an unlikely DoS attack on directory servers.
13521 - Add a BadDirectory flag to network status docs so that authorities
13522 can (eventually) tell clients about caches they believe to be
13525 o Minor features (controller):
13526 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
13527 - Reimplement GETINFO so that info/names stays in sync with the
13529 - Implement "GETINFO fingerprint".
13530 - Implement "SETEVENTS GUARD" so controllers can get updates on
13531 entry guard status as it changes.
13533 o Minor features (clean up obsolete pieces):
13534 - Remove some options that have been deprecated since at least
13535 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
13536 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
13537 to set log options.
13538 - We no longer look for identity and onion keys in "identity.key" and
13539 "onion.key" -- these were replaced by secret_id_key and
13540 secret_onion_key in 0.0.8pre1.
13541 - We no longer require unrecognized directory entries to be
13544 o Major bugfixes (security):
13545 - Stop sending the HttpProxyAuthenticator string to directory
13546 servers when directory connections are tunnelled through Tor.
13547 - Clients no longer store bandwidth history in the state file.
13548 - Do not log introduction points for hidden services if SafeLogging
13550 - When generating bandwidth history, round down to the nearest
13551 1k. When storing accounting data, round up to the nearest 1k.
13552 - When we're running as a server, remember when we last rotated onion
13553 keys, so that we will rotate keys once they're a week old even if
13554 we never stay up for a week ourselves.
13556 o Major bugfixes (other):
13557 - Fix a longstanding bug in eventdns that prevented the count of
13558 timed-out resolves from ever being reset. This bug caused us to
13559 give up on a nameserver the third time it timed out, and try it
13560 10 seconds later... and to give up on it every time it timed out
13562 - Take out the '5 second' timeout from the connection retry
13563 schedule. Now the first connect attempt will wait a full 10
13564 seconds before switching to a new circuit. Perhaps this will help
13565 a lot. Based on observations from Mike Perry.
13566 - Fix a bug on the Windows implementation of tor_mmap_file() that
13567 would prevent the cached-routers file from ever loading. Reported
13571 - Fix an assert failure when a directory authority sets
13572 AuthDirRejectUnlisted and then receives a descriptor from an
13573 unlisted router. Reported by seeess.
13574 - Avoid a double-free when parsing malformed DirServer lines.
13575 - Fix a bug when a BSD-style PF socket is first used. Patch from
13577 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
13578 to resolve an address at a given exit node even when they ask for
13580 - Servers no longer ever list themselves in their "family" line,
13581 even if configured to do so. This makes it easier to configure
13582 family lists conveniently.
13583 - When running as a server, don't fall back to 127.0.0.1 when no
13584 nameservers are configured in /etc/resolv.conf; instead, make the
13585 user fix resolv.conf or specify nameservers explicitly. (Resolves
13587 - Stop accepting certain malformed ports in configured exit policies.
13588 - Don't re-write the fingerprint file every restart, unless it has
13590 - Stop warning when a single nameserver fails: only warn when _all_ of
13591 our nameservers have failed. Also, when we only have one nameserver,
13592 raise the threshold for deciding that the nameserver is dead.
13593 - Directory authorities now only decide that routers are reachable
13594 if their identity keys are as expected.
13595 - When the user uses bad syntax in the Log config line, stop
13596 suggesting other bad syntax as a replacement.
13597 - Correctly detect ipv6 DNS capability on OpenBSD.
13599 o Minor bugfixes (controller):
13600 - Report the circuit number correctly in STREAM CLOSED events. Bug
13601 reported by Mike Perry.
13602 - Do not report bizarre values for results of accounting GETINFOs
13603 when the last second's write or read exceeds the allotted bandwidth.
13604 - Report "unrecognized key" rather than an empty string when the
13605 controller tries to fetch a networkstatus that doesn't exist.
13608 Changes in version 0.1.1.26 - 2006-12-14
13609 o Security bugfixes:
13610 - Stop sending the HttpProxyAuthenticator string to directory
13611 servers when directory connections are tunnelled through Tor.
13612 - Clients no longer store bandwidth history in the state file.
13613 - Do not log introduction points for hidden services if SafeLogging
13617 - Fix an assert failure when a directory authority sets
13618 AuthDirRejectUnlisted and then receives a descriptor from an
13619 unlisted router (reported by seeess).
13622 Changes in version 0.1.2.4-alpha - 2006-12-03
13624 - Add support for using natd; this allows FreeBSDs earlier than
13625 5.1.2 to have ipfw send connections through Tor without using
13626 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
13629 - Make all connections to addresses of the form ".noconnect"
13630 immediately get closed. This lets application/controller combos
13631 successfully test whether they're talking to the same Tor by
13632 watching for STREAM events.
13633 - Make cross.sh cross-compilation script work even when autogen.sh
13634 hasn't been run. (Patch from Michael Mohr.)
13635 - Statistics dumped by -USR2 now include a breakdown of public key
13636 operations, for profiling.
13639 - Fix a major leak when directory authorities parse their
13640 approved-routers list, a minor memory leak when we fail to pick
13641 an exit node, and a few rare leaks on errors.
13642 - Handle TransPort connections even when the server sends data before
13643 the client sends data. Previously, the connection would just hang
13644 until the client sent data. (Patch from tup based on patch from
13646 - Avoid assert failure when our cached-routers file is empty on
13650 - Don't log spurious warnings when we see a circuit close reason we
13651 don't recognize; it's probably just from a newer version of Tor.
13652 - Have directory authorities allow larger amounts of drift in uptime
13653 without replacing the server descriptor: previously, a server that
13654 restarted every 30 minutes could have 48 "interesting" descriptors
13656 - Start linking to the Tor specification and Tor reference manual
13657 correctly in the Windows installer.
13658 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13659 Tor/Privoxy we also uninstall Vidalia.
13660 - Resume building on Irix64, and fix a lot of warnings from its
13661 MIPSpro C compiler.
13662 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
13663 when we're running as a client.
13666 Changes in version 0.1.1.25 - 2006-11-04
13668 - When a client asks us to resolve (rather than connect to)
13669 an address, and we have a cached answer, give them the cached
13670 answer. Previously, we would give them no answer at all.
13671 - We were building exactly the wrong circuits when we predict
13672 hidden service requirements, meaning Tor would have to build all
13673 its circuits on demand.
13674 - If none of our live entry guards have a high uptime, but we
13675 require a guard with a high uptime, try adding a new guard before
13676 we give up on the requirement. This patch should make long-lived
13677 connections more stable on average.
13678 - When testing reachability of our DirPort, don't launch new
13679 tests when there's already one in progress -- unreachable
13680 servers were stacking up dozens of testing streams.
13682 o Security bugfixes:
13683 - When the user sends a NEWNYM signal, clear the client-side DNS
13684 cache too. Otherwise we continue to act on previous information.
13687 - Avoid a memory corruption bug when creating a hash table for
13689 - Avoid possibility of controller-triggered crash when misusing
13690 certain commands from a v0 controller on platforms that do not
13691 handle printf("%s",NULL) gracefully.
13692 - Avoid infinite loop on unexpected controller input.
13693 - Don't log spurious warnings when we see a circuit close reason we
13694 don't recognize; it's probably just from a newer version of Tor.
13695 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13696 Tor/Privoxy we also uninstall Vidalia.
13699 Changes in version 0.1.2.3-alpha - 2006-10-29
13701 - Prepare for servers to publish descriptors less often: never
13702 discard a descriptor simply for being too old until either it is
13703 recommended by no authorities, or until we get a better one for
13704 the same router. Make caches consider retaining old recommended
13705 routers for even longer.
13706 - If most authorities set a BadExit flag for a server, clients
13707 don't think of it as a general-purpose exit. Clients only consider
13708 authorities that advertise themselves as listing bad exits.
13709 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
13710 headers for content, so that we can work better in the presence of
13711 caching HTTP proxies.
13712 - Allow authorities to list nodes as bad exits by fingerprint or by
13715 o Minor features, controller:
13716 - Add a REASON field to CIRC events; for backward compatibility, this
13717 field is sent only to controllers that have enabled the extended
13718 event format. Also, add additional reason codes to explain why
13719 a given circuit has been destroyed or truncated. (Patches from
13721 - Add a REMOTE_REASON field to extended CIRC events to tell the
13722 controller about why a remote OR told us to close a circuit.
13723 - Stream events also now have REASON and REMOTE_REASON fields,
13724 working much like those for circuit events.
13725 - There's now a GETINFO ns/... field so that controllers can ask Tor
13726 about the current status of a router.
13727 - A new event type "NS" to inform a controller when our opinion of
13728 a router's status has changed.
13729 - Add a GETINFO events/names and GETINFO features/names so controllers
13730 can tell which events and features are supported.
13731 - A new CLEARDNSCACHE signal to allow controllers to clear the
13732 client-side DNS cache without expiring circuits.
13734 o Security bugfixes:
13735 - When the user sends a NEWNYM signal, clear the client-side DNS
13736 cache too. Otherwise we continue to act on previous information.
13739 - Avoid sending junk to controllers or segfaulting when a controller
13740 uses EVENT_NEW_DESC with verbose nicknames.
13741 - Stop triggering asserts if the controller tries to extend hidden
13742 service circuits (reported by mwenge).
13743 - Avoid infinite loop on unexpected controller input.
13744 - When the controller does a "GETINFO network-status", tell it
13745 about even those routers whose descriptors are very old, and use
13746 long nicknames where appropriate.
13747 - Change NT service functions to be loaded on demand. This lets us
13748 build with MinGW without breaking Tor for Windows 98 users.
13749 - Do DirPort reachability tests less often, since a single test
13750 chews through many circuits before giving up.
13751 - In the hidden service example in torrc.sample, stop recommending
13752 esoteric and discouraged hidden service options.
13753 - When stopping an NT service, wait up to 10 sec for it to actually
13754 stop. Patch from Matt Edman; resolves bug 295.
13755 - Fix handling of verbose nicknames with ORCONN controller events:
13756 make them show up exactly when requested, rather than exactly when
13758 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
13759 printing a duplicate "$" in the keys we send (reported by mwenge).
13760 - Correctly set maximum connection limit on Cygwin. (This time
13762 - Try to detect Windows correctly when cross-compiling.
13763 - Detect the size of the routers file correctly even if it is
13764 corrupted (on systems without mmap) or not page-aligned (on systems
13765 with mmap). This bug was harmless.
13766 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
13767 to open a stream fails; now we do in more cases. This should
13768 make clients able to find a good exit faster in some cases, since
13769 unhandleable requests will now get an error rather than timing out.
13770 - Resolve two memory leaks when rebuilding the on-disk router cache
13771 (reported by fookoowa).
13772 - Clean up minor code warnings suggested by the MIPSpro C compiler,
13773 and reported by some Centos users.
13774 - Controller signals now work on non-Unix platforms that don't define
13775 SIGUSR1 and SIGUSR2 the way we expect.
13776 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
13777 values before failing, and always enables eventdns.
13778 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
13779 Try to fix this in configure.in by checking for most functions
13780 before we check for libevent.
13783 Changes in version 0.1.2.2-alpha - 2006-10-07
13785 - Make our async eventdns library on-by-default for Tor servers,
13786 and plan to deprecate the separate dnsworker threads.
13787 - Add server-side support for "reverse" DNS lookups (using PTR
13788 records so clients can determine the canonical hostname for a given
13789 IPv4 address). Only supported by servers using eventdns; servers
13790 now announce in their descriptors whether they support eventdns.
13791 - Specify and implement client-side SOCKS5 interface for reverse DNS
13792 lookups (see doc/socks-extensions.txt).
13793 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
13794 connect to directory servers through Tor. Previously, clients needed
13795 to find Tor exits to make private connections to directory servers.
13796 - Avoid choosing Exit nodes for entry or middle hops when the
13797 total bandwidth available from non-Exit nodes is much higher than
13798 the total bandwidth available from Exit nodes.
13799 - Workaround for name servers (like Earthlink's) that hijack failing
13800 DNS requests and replace the no-such-server answer with a "helpful"
13801 redirect to an advertising-driven search portal. Also work around
13802 DNS hijackers who "helpfully" decline to hijack known-invalid
13803 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
13804 lets you turn it off.
13805 - Send out a burst of long-range padding cells once we've established
13806 that we're reachable. Spread them over 4 circuits, so hopefully
13807 a few will be fast. This exercises our bandwidth and bootstraps
13808 us into the directory more quickly.
13810 o New/improved config options:
13811 - Add new config option "ResolvConf" to let the server operator
13812 choose an alternate resolve.conf file when using eventdns.
13813 - Add an "EnforceDistinctSubnets" option to control our "exclude
13814 servers on the same /16" behavior. It's still on by default; this
13815 is mostly for people who want to operate private test networks with
13816 all the machines on the same subnet.
13817 - If one of our entry guards is on the ExcludeNodes list, or the
13818 directory authorities don't think it's a good guard, treat it as
13819 if it were unlisted: stop using it as a guard, and throw it off
13820 the guards list if it stays that way for a long time.
13821 - Allow directory authorities to be marked separately as authorities
13822 for the v1 directory protocol, the v2 directory protocol, and
13823 as hidden service directories, to make it easier to retire old
13824 authorities. V1 authorities should set "HSAuthoritativeDir 1"
13825 to continue being hidden service authorities too.
13826 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
13828 o Minor features, controller:
13829 - Fix CIRC controller events so that controllers can learn the
13830 identity digests of non-Named servers used in circuit paths.
13831 - Let controllers ask for more useful identifiers for servers. Instead
13832 of learning identity digests for un-Named servers and nicknames
13833 for Named servers, the new identifiers include digest, nickname,
13834 and indication of Named status. Off by default; see control-spec.txt
13835 for more information.
13836 - Add a "getinfo address" controller command so it can display Tor's
13837 best guess to the user.
13838 - New controller event to alert the controller when our server
13839 descriptor has changed.
13840 - Give more meaningful errors on controller authentication failure.
13842 o Minor features, other:
13843 - When asked to resolve a hostname, don't use non-exit servers unless
13844 requested to do so. This allows servers with broken DNS to be
13845 useful to the network.
13846 - Divide eventdns log messages into warn and info messages.
13847 - Reserve the nickname "Unnamed" for routers that can't pick
13848 a hostname: any router can call itself Unnamed; directory
13849 authorities will never allocate Unnamed to any particular router;
13850 clients won't believe that any router is the canonical Unnamed.
13851 - Only include function names in log messages for info/debug messages.
13852 For notice/warn/err, the content of the message should be clear on
13853 its own, and printing the function name only confuses users.
13854 - Avoid some false positives during reachability testing: don't try
13855 to test via a server that's on the same /24 as us.
13856 - If we fail to build a circuit to an intended enclave, and it's
13857 not mandatory that we use that enclave, stop wanting it.
13858 - When eventdns is enabled, allow multithreaded builds on NetBSD and
13859 OpenBSD. (We had previously disabled threads on these platforms
13860 because they didn't have working thread-safe resolver functions.)
13862 o Major bugfixes, anonymity/security:
13863 - If a client asked for a server by name, and there's a named server
13864 in our network-status but we don't have its descriptor yet, we
13865 could return an unnamed server instead.
13866 - Fix NetBSD bug that could allow someone to force uninitialized RAM
13867 to be sent to a server's DNS resolver. This only affects NetBSD
13868 and other platforms that do not bounds-check tolower().
13869 - Reject (most) attempts to use Tor circuits with length one. (If
13870 many people start using Tor as a one-hop proxy, exit nodes become
13871 a more attractive target for compromise.)
13872 - Just because your DirPort is open doesn't mean people should be
13873 able to remotely teach you about hidden service descriptors. Now
13874 only accept rendezvous posts if you've got HSAuthoritativeDir set.
13876 o Major bugfixes, other:
13877 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
13878 - When a client asks the server to resolve (not connect to)
13879 an address, and it has a cached answer, give them the cached answer.
13880 Previously, the server would give them no answer at all.
13881 - Allow really slow clients to not hang up five minutes into their
13882 directory downloads (suggested by Adam J. Richter).
13883 - We were building exactly the wrong circuits when we anticipated
13884 hidden service requirements, meaning Tor would have to build all
13885 its circuits on demand.
13886 - Avoid crashing when we mmap a router cache file of size 0.
13887 - When testing reachability of our DirPort, don't launch new
13888 tests when there's already one in progress -- unreachable
13889 servers were stacking up dozens of testing streams.
13891 o Minor bugfixes, correctness:
13892 - If we're a directory mirror and we ask for "all" network status
13893 documents, we would discard status documents from authorities
13894 we don't recognize.
13895 - Avoid a memory corruption bug when creating a hash table for
13897 - Avoid controller-triggered crash when misusing certain commands
13898 from a v0 controller on platforms that do not handle
13899 printf("%s",NULL) gracefully.
13900 - Don't crash when a controller sends a third argument to an
13901 "extendcircuit" request.
13902 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13903 response; fix error code when "getinfo dir/status/" fails.
13904 - Avoid crash when telling controller stream-status and a stream
13906 - Patch from Adam Langley to fix assert() in eventdns.c.
13907 - Fix a debug log message in eventdns to say "X resolved to Y"
13908 instead of "X resolved to X".
13909 - Make eventdns give strings for DNS errors, not just error numbers.
13910 - Track unreachable entry guards correctly: don't conflate
13911 'unreachable by us right now' with 'listed as down by the directory
13912 authorities'. With the old code, if a guard was unreachable by
13913 us but listed as running, it would clog our guard list forever.
13914 - Behave correctly in case we ever have a network with more than
13915 2GB/s total advertised capacity.
13916 - Make TrackExitHosts case-insensitive, and fix the behavior of
13917 ".suffix" TrackExitHosts items to avoid matching in the middle of
13919 - Finally fix the openssl warnings from newer gccs that believe that
13920 ignoring a return value is okay, but casting a return value and
13921 then ignoring it is a sign of madness.
13922 - Prevent the contrib/exitlist script from printing the same
13923 result more than once.
13924 - Patch from Steve Hildrey: Generate network status correctly on
13925 non-versioning dirservers.
13926 - Don't listen to the X-Your-Address-Is hint if you did the lookup
13927 via Tor; otherwise you'll think you're the exit node's IP address.
13929 o Minor bugfixes, performance:
13930 - Two small performance improvements on parsing descriptors.
13931 - Major performance improvement on inserting descriptors: change
13932 algorithm from O(n^2) to O(n).
13933 - Make the common memory allocation path faster on machines where
13934 malloc(0) returns a pointer.
13935 - Start remembering X-Your-Address-Is directory hints even if you're
13936 a client, so you can become a server more smoothly.
13937 - Avoid duplicate entries on MyFamily line in server descriptor.
13939 o Packaging, features:
13940 - Remove architecture from OS X builds. The official builds are
13941 now universal binaries.
13942 - The Debian package now uses --verify-config when (re)starting,
13943 to distinguish configuration errors from other errors.
13944 - Update RPMs to require libevent 1.1b.
13946 o Packaging, bugfixes:
13947 - Patches so Tor builds with MinGW on Windows.
13948 - Patches so Tor might run on Cygwin again.
13949 - Resume building on non-gcc compilers and ancient gcc. Resume
13950 building with the -O0 compile flag. Resume building cleanly on
13952 - Run correctly on OS X platforms with case-sensitive filesystems.
13953 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
13954 - Add autoconf checks so Tor can build on Solaris x86 again.
13957 - Documented (and renamed) ServerDNSSearchDomains and
13958 ServerDNSResolvConfFile options.
13959 - Be clearer that the *ListenAddress directives can be repeated
13963 Changes in version 0.1.1.24 - 2006-09-29
13965 - Allow really slow clients to not hang up five minutes into their
13966 directory downloads (suggested by Adam J. Richter).
13967 - Fix major performance regression from 0.1.0.x: instead of checking
13968 whether we have enough directory information every time we want to
13969 do something, only check when the directory information has changed.
13970 This should improve client CPU usage by 25-50%.
13971 - Don't crash if, after a server has been running for a while,
13972 it can't resolve its hostname.
13975 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13976 - Don't crash when the controller receives a third argument to an
13977 "extendcircuit" request.
13978 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13979 response; fix error code when "getinfo dir/status/" fails.
13980 - Fix configure.in to not produce broken configure files with
13981 more recent versions of autoconf. Thanks to Clint for his auto*
13983 - Fix security bug on NetBSD that could allow someone to force
13984 uninitialized RAM to be sent to a server's DNS resolver. This
13985 only affects NetBSD and other platforms that do not bounds-check
13987 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
13988 methods: these are known to be buggy.
13989 - If we're a directory mirror and we ask for "all" network status
13990 documents, we would discard status documents from authorities
13991 we don't recognize.
13994 Changes in version 0.1.2.1-alpha - 2006-08-27
13996 - Add "eventdns" async dns library from Adam Langley, tweaked to
13997 build on OSX and Windows. Only enabled if you pass the
13998 --enable-eventdns argument to configure.
13999 - Allow servers with no hostname or IP address to learn their
14000 IP address by asking the directory authorities. This code only
14001 kicks in when you would normally have exited with a "no address"
14002 error. Nothing's authenticated, so use with care.
14003 - Rather than waiting a fixed amount of time between retrying
14004 application connections, we wait only 5 seconds for the first,
14005 10 seconds for the second, and 15 seconds for each retry after
14006 that. Hopefully this will improve the expected user experience.
14007 - Patch from Tup to add support for transparent AP connections:
14008 this basically bundles the functionality of trans-proxy-tor
14009 into the Tor mainline. Now hosts with compliant pf/netfilter
14010 implementations can redirect TCP connections straight to Tor
14011 without diverting through SOCKS. Needs docs.
14012 - Busy directory servers save lots of memory by spooling server
14013 descriptors, v1 directories, and v2 networkstatus docs to buffers
14014 as needed rather than en masse. Also mmap the cached-routers
14015 files, so we don't need to keep the whole thing in memory too.
14016 - Automatically avoid picking more than one node from the same
14017 /16 network when constructing a circuit.
14018 - Revise and clean up the torrc.sample that we ship with; add
14019 a section for BandwidthRate and BandwidthBurst.
14022 - Split circuit_t into origin_circuit_t and or_circuit_t, and
14023 split connection_t into edge, or, dir, control, and base structs.
14024 These will save quite a bit of memory on busy servers, and they'll
14025 also help us track down bugs in the code and bugs in the spec.
14026 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
14027 or later. Log when we are doing this, so we can diagnose it when
14028 it fails. (Also, recommend libevent 1.1b for kqueue and
14029 win32 methods; deprecate libevent 1.0b harder; make libevent
14030 recommendation system saner.)
14031 - Start being able to build universal binaries on OS X (thanks
14033 - Export the default exit policy via the control port, so controllers
14034 don't need to guess what it is / will be later.
14035 - Add a man page entry for ProtocolWarnings.
14036 - Add TestVia config option to the man page.
14037 - Remove even more protocol-related warnings from Tor server logs,
14038 such as bad TLS handshakes and malformed begin cells.
14039 - Stop fetching descriptors if you're not a dir mirror and you
14040 haven't tried to establish any circuits lately. [This currently
14041 causes some dangerous behavior, because when you start up again
14042 you'll use your ancient server descriptors.]
14043 - New DirPort behavior: if you have your dirport set, you download
14044 descriptors aggressively like a directory mirror, whether or not
14045 your ORPort is set.
14046 - Get rid of the router_retry_connections notion. Now routers
14047 no longer try to rebuild long-term connections to directory
14048 authorities, and directory authorities no longer try to rebuild
14049 long-term connections to all servers. We still don't hang up
14050 connections in these two cases though -- we need to look at it
14051 more carefully to avoid flapping, and we likely need to wait til
14052 0.1.1.x is obsolete.
14053 - Drop compatibility with obsolete Tors that permit create cells
14054 to have the wrong circ_id_type.
14055 - Re-enable per-connection rate limiting. Get rid of the "OP
14056 bandwidth" concept. Lay groundwork for "bandwidth classes" --
14057 separate global buckets that apply depending on what sort of conn
14059 - Start publishing one minute or so after we find our ORPort
14060 to be reachable. This will help reduce the number of descriptors
14061 we have for ourselves floating around, since it's quite likely
14062 other things (e.g. DirPort) will change during that minute too.
14063 - Fork the v1 directory protocol into its own spec document,
14064 and mark dir-spec.txt as the currently correct (v2) spec.
14067 - When we find our DirPort to be reachable, publish a new descriptor
14068 so we'll tell the world (reported by pnx).
14069 - Publish a new descriptor after we hup/reload. This is important
14070 if our config has changed such that we'll want to start advertising
14071 our DirPort now, etc.
14072 - Allow Tor to start when RunAsDaemon is set but no logs are set.
14073 - When we have a state file we cannot parse, tell the user and
14074 move it aside. Now we avoid situations where the user starts
14075 Tor in 1904, Tor writes a state file with that timestamp in it,
14076 the user fixes her clock, and Tor refuses to start.
14077 - Fix configure.in to not produce broken configure files with
14078 more recent versions of autoconf. Thanks to Clint for his auto*
14080 - "tor --verify-config" now exits with -1(255) or 0 depending on
14081 whether the config options are bad or good.
14082 - Resolve bug 321 when using dnsworkers: append a period to every
14083 address we resolve at the exit node, so that we do not accidentally
14084 pick up local addresses, and so that failing searches are retried
14085 in the resolver search domains. (This is already solved for
14086 eventdns.) (This breaks Blossom servers for now.)
14087 - If we are using an exit enclave and we can't connect, e.g. because
14088 its webserver is misconfigured to not listen on localhost, then
14089 back off and try connecting from somewhere else before we fail.
14092 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
14093 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
14094 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
14095 when the IP address is mapped through MapAddress to a hostname.
14096 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
14097 useless IPv6 DNS resolves.
14098 - Patch suggested by Karsten Loesing: respond to SIGNAL command
14099 before we execute the signal, in case the signal shuts us down.
14100 - Clean up AllowInvalidNodes man page entry.
14101 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
14102 - Add more asserts to track down an assert error on a windows Tor
14103 server with connection_add being called with socket == -1.
14104 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
14105 - Fix misleading log messages: an entry guard that is "unlisted",
14106 as well as not known to be "down" (because we've never heard
14107 of it), is not therefore "up".
14108 - Remove code to special-case "-cvs" ending, since it has not
14109 actually mattered since 0.0.9.
14110 - Make our socks5 handling more robust to broken socks clients:
14111 throw out everything waiting on the buffer in between socks
14112 handshake phases, since they can't possibly (so the theory
14113 goes) have predicted what we plan to respond to them.
14116 Changes in version 0.1.1.23 - 2006-07-30
14118 - Fast Tor servers, especially exit nodes, were triggering asserts
14119 due to a bug in handling the list of pending DNS resolves. Some
14120 bugs still remain here; we're hunting them.
14121 - Entry guards could crash clients by sending unexpected input.
14122 - More fixes on reachability testing: if you find yourself reachable,
14123 then don't ever make any client requests (so you stop predicting
14124 circuits), then hup or have your clock jump, then later your IP
14125 changes, you won't think circuits are working, so you won't try to
14126 test reachability, so you won't publish.
14129 - Avoid a crash if the controller does a resetconf firewallports
14130 and then a setconf fascistfirewall=1.
14131 - Avoid an integer underflow when the dir authority decides whether
14132 a router is stable: we might wrongly label it stable, and compute
14133 a slightly wrong median stability, when a descriptor is published
14135 - Fix a place where we might trigger an assert if we can't build our
14136 own server descriptor yet.
14139 Changes in version 0.1.1.22 - 2006-07-05
14141 - Fix a big bug that was causing servers to not find themselves
14142 reachable if they changed IP addresses. Since only 0.1.1.22+
14143 servers can do reachability testing correctly, now we automatically
14144 make sure to test via one of these.
14145 - Fix to allow clients and mirrors to learn directory info from
14146 descriptor downloads that get cut off partway through.
14147 - Directory authorities had a bug in deciding if a newly published
14148 descriptor was novel enough to make everybody want a copy -- a few
14149 servers seem to be publishing new descriptors many times a minute.
14151 - Fix a rare bug that was causing some servers to complain about
14152 "closing wedged cpuworkers" and skip some circuit create requests.
14153 - Make the Exit flag in directory status documents actually work.
14156 Changes in version 0.1.1.21 - 2006-06-10
14157 o Crash and assert fixes from 0.1.1.20:
14158 - Fix a rare crash on Tor servers that have enabled hibernation.
14159 - Fix a seg fault on startup for Tor networks that use only one
14160 directory authority.
14161 - Fix an assert from a race condition that occurs on Tor servers
14162 while exiting, where various threads are trying to log that they're
14163 exiting, and delete the logs, at the same time.
14164 - Make our unit tests pass again on certain obscure platforms.
14167 - Add support for building SUSE RPM packages.
14168 - Speed up initial bootstrapping for clients: if we are making our
14169 first ever connection to any entry guard, then don't mark it down
14171 - When only one Tor server in the network is labelled as a guard,
14172 and we've already picked him, we would cycle endlessly picking him
14173 again, being unhappy about it, etc. Now we specifically exclude
14174 current guards when picking a new guard.
14175 - Servers send create cells more reliably after the TLS connection
14176 is established: we were sometimes forgetting to send half of them
14177 when we had more than one pending.
14178 - If we get a create cell that asks us to extend somewhere, but the
14179 Tor server there doesn't match the expected digest, we now send
14180 a destroy cell back, rather than silently doing nothing.
14181 - Make options->RedirectExit work again.
14182 - Make cookie authentication for the controller work again.
14183 - Stop being picky about unusual characters in the arguments to
14184 mapaddress. It's none of our business.
14185 - Add a new config option "TestVia" that lets you specify preferred
14186 middle hops to use for test circuits. Perhaps this will let me
14187 debug the reachability problems better.
14189 o Log / documentation fixes:
14190 - If we're a server and some peer has a broken TLS certificate, don't
14191 log about it unless ProtocolWarnings is set, i.e., we want to hear
14192 about protocol violations by others.
14193 - Fix spelling of VirtualAddrNetwork in man page.
14194 - Add a better explanation at the top of the autogenerated torrc file
14195 about what happened to our old torrc.
14198 Changes in version 0.1.1.20 - 2006-05-23
14200 - Downgrade a log severity where servers complain that they're
14202 - Avoid a compile warning on FreeBSD.
14203 - Remove string size limit on NEWDESC messages; solve bug 291.
14204 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
14205 more thoroughly when we're running on windows.
14208 Changes in version 0.1.1.19-rc - 2006-05-03
14210 - Regenerate our local descriptor if it's dirty and we try to use
14211 it locally (e.g. if it changes during reachability detection).
14212 - If we setconf our ORPort to 0, we continued to listen on the
14213 old ORPort and receive connections.
14214 - Avoid a second warning about machine/limits.h on Debian
14216 - Be willing to add our own routerinfo into the routerlist.
14217 Now authorities will include themselves in their directories
14218 and network-statuses.
14219 - Stop trying to upload rendezvous descriptors to every
14220 directory authority: only try the v1 authorities.
14221 - Servers no longer complain when they think they're not
14222 registered with the directory authorities. There were too many
14224 - Backport dist-rpm changes so rpms can be built without errors.
14227 - Implement an option, VirtualAddrMask, to set which addresses
14228 get handed out in response to mapaddress requests. This works
14229 around a bug in tsocks where 127.0.0.0/8 is never socksified.
14232 Changes in version 0.1.1.18-rc - 2006-04-10
14234 - Work harder to download live network-statuses from all the
14235 directory authorities we know about. Improve the threshold
14236 decision logic so we're more robust to edge cases.
14237 - When fetching rendezvous descriptors, we were willing to ask
14238 v2 authorities too, which would always return 404.
14241 - Stop listing down or invalid nodes in the v1 directory. This will
14242 reduce its bulk by about 1/3, and reduce load on directory
14244 - When deciding whether a router is Fast or Guard-worthy, consider
14245 his advertised BandwidthRate and not just the BandwidthCapacity.
14246 - No longer ship INSTALL and README files -- they are useless now.
14247 - Force rpmbuild to behave and honor target_cpu.
14248 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
14249 - Start to include translated versions of the tor-doc-*.html
14250 files, along with the screenshots. Still needs more work.
14251 - Start sending back 512 and 451 errors if mapaddress fails,
14252 rather than not sending anything back at all.
14253 - When we fail to bind or listen on an incoming or outgoing
14254 socket, we should close it before failing. otherwise we just
14255 leak it. (thanks to weasel for finding.)
14256 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
14257 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
14258 - Make NoPublish (even though deprecated) work again.
14259 - Fix a minor security flaw where a versioning auth dirserver
14260 could list a recommended version many times in a row to make
14261 clients more convinced that it's recommended.
14262 - Fix crash bug if there are two unregistered servers running
14263 with the same nickname, one of them is down, and you ask for
14264 them by nickname in your EntryNodes or ExitNodes. Also, try
14265 to pick the one that's running rather than an arbitrary one.
14266 - Fix an infinite loop we could hit if we go offline for too long.
14267 - Complain when we hit WSAENOBUFS on recv() or write() too.
14268 Perhaps this will help us hunt the bug.
14269 - If you're not a versioning dirserver, don't put the string
14270 "client-versions \nserver-versions \n" in your network-status.
14271 - Lower the minimum required number of file descriptors to 1000,
14272 so we can have some overhead for Valgrind on Linux, where the
14273 default ulimit -n is 1024.
14276 - Add tor.dizum.com as the fifth authoritative directory server.
14277 - Add a new config option FetchUselessDescriptors, off by default,
14278 for when you plan to run "exitlist" on your client and you want
14279 to know about even the non-running descriptors.
14282 Changes in version 0.1.1.17-rc - 2006-03-28
14284 - Clients and servers since 0.1.1.10-alpha have been expiring
14285 connections whenever they are idle for 5 minutes and they *do*
14286 have circuits on them. Oops. With this new version, clients will
14287 discard their previous entry guard choices and avoid choosing
14288 entry guards running these flawed versions.
14289 - Fix memory leak when uncompressing concatenated zlib streams. This
14290 was causing substantial leaks over time on Tor servers.
14291 - The v1 directory was including servers as much as 48 hours old,
14292 because that's how the new routerlist->routers works. Now only
14293 include them if they're 20 hours old or less.
14296 - Resume building on irix64, netbsd 2.0, etc.
14297 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
14299 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
14300 and it is confusing some users.
14301 - Mirrors stop caching the v1 directory so often.
14302 - Make the max number of old descriptors that a cache will hold
14303 rise with the number of directory authorities, so we can scale.
14304 - Change our win32 uname() hack to be more forgiving about what
14305 win32 versions it thinks it's found.
14308 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
14310 - When the controller's *setconf commands fail, collect an error
14311 message in a string and hand it back to the controller.
14312 - Make the v2 dir's "Fast" flag based on relative capacity, just
14313 like "Stable" is based on median uptime. Name everything in the
14314 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
14315 - Log server fingerprint on startup, so new server operators don't
14316 have to go hunting around their filesystem for it.
14317 - Return a robots.txt on our dirport to discourage google indexing.
14318 - Let the controller ask for GETINFO dir/status/foo so it can ask
14319 directly rather than connecting to the dir port. Only works when
14320 dirport is set for now.
14322 o New config options rather than constants in the code:
14323 - SocksTimeout: How long do we let a socks connection wait
14324 unattached before we fail it?
14325 - CircuitBuildTimeout: Cull non-open circuits that were born
14326 at least this many seconds ago.
14327 - CircuitIdleTimeout: Cull open clean circuits that were born
14328 at least this many seconds ago.
14331 Changes in version 0.1.1.16-rc - 2006-03-18
14332 o Bugfixes on 0.1.1.15-rc:
14333 - Fix assert when the controller asks to attachstream a connect-wait
14334 or resolve-wait stream.
14335 - Now do address rewriting when the controller asks us to attach
14336 to a particular circuit too. This will let Blossom specify
14337 "moria2.exit" without having to learn what moria2's IP address is.
14338 - Make the "tor --verify-config" command-line work again, so people
14339 can automatically check if their torrc will parse.
14340 - Authoritative dirservers no longer require an open connection from
14341 a server to consider him "reachable". We need this change because
14342 when we add new auth dirservers, old servers won't know not to
14344 - Let Tor build on Sun CC again.
14345 - Fix an off-by-one buffer size in dirserv.c that magically never
14346 hit our three authorities but broke sjmurdoch's own tor network.
14347 - If we as a directory mirror don't know of any v1 directory
14348 authorities, then don't try to cache any v1 directories.
14349 - Stop warning about unknown servers in our family when they are
14350 given as hex digests.
14351 - Stop complaining as quickly to the server operator that he
14352 hasn't registered his nickname/key binding.
14353 - Various cleanups so we can add new V2 Auth Dirservers.
14354 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
14355 reflect the updated flags in our v2 dir protocol.
14356 - Resume allowing non-printable characters for exit streams (both
14357 for connecting and for resolving). Now we tolerate applications
14358 that don't follow the RFCs. But continue to block malformed names
14361 o Bugfixes on 0.1.0.x:
14362 - Fix assert bug in close_logs(): when we close and delete logs,
14363 remove them all from the global "logfiles" list.
14364 - Fix minor integer overflow in calculating when we expect to use up
14365 our bandwidth allocation before hibernating.
14366 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
14367 there are multiple SSLs installed with different versions.
14368 - When we try to be a server and Address is not explicitly set and
14369 our hostname resolves to a private IP address, try to use an
14370 interface address if it has a public address. Now Windows machines
14371 that think of themselves as localhost can work by default.
14374 - Let the controller ask for GETINFO dir/server/foo so it can ask
14375 directly rather than connecting to the dir port.
14376 - Let the controller tell us about certain router descriptors
14377 that it doesn't want Tor to use in circuits. Implement
14378 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
14379 - New config option SafeSocks to reject all application connections
14380 using unsafe socks protocols. Defaults to off.
14383 Changes in version 0.1.1.15-rc - 2006-03-11
14384 o Bugfixes and cleanups:
14385 - When we're printing strings from the network, don't try to print
14386 non-printable characters. This protects us against shell escape
14387 sequence exploits, and also against attacks to fool humans into
14388 misreading their logs.
14389 - Fix a bug where Tor would fail to establish any connections if you
14390 left it off for 24 hours and then started it: we were happy with
14391 the obsolete network statuses, but they all referred to router
14392 descriptors that were too old to fetch, so we ended up with no
14393 valid router descriptors.
14394 - Fix a seg fault in the controller's "getinfo orconn-status"
14395 command while listing status on incoming handshaking connections.
14396 Introduce a status name "NEW" for these connections.
14397 - If we get a linelist or linelist_s config option from the torrc
14398 (e.g. ExitPolicy) and it has no value, warn and skip rather than
14399 silently resetting it to its default.
14400 - Don't abandon entry guards until they've been down or gone for
14402 - Cleaner and quieter log messages.
14405 - New controller signal NEWNYM that makes new application requests
14406 use clean circuits.
14407 - Add a new circuit purpose 'controller' to let the controller ask
14408 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
14409 controller command to let you specify the purpose if you're
14410 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
14411 command to let you change a circuit's purpose after it's been
14413 - Accept "private:*" in routerdesc exit policies; not generated yet
14414 because older Tors do not understand it.
14415 - Add BSD-style contributed startup script "rc.subr" from Peter
14419 Changes in version 0.1.1.14-alpha - 2006-02-20
14420 o Bugfixes on 0.1.1.x:
14421 - Don't die if we ask for a stdout or stderr log (even implicitly)
14422 and we're set to RunAsDaemon -- just warn.
14423 - We still had a few bugs in the OR connection rotation code that
14424 caused directory servers to slowly aggregate connections to other
14425 fast Tor servers. This time for sure!
14426 - Make log entries on Win32 include the name of the function again.
14427 - We were treating a pair of exit policies if they were equal even
14428 if one said accept and the other said reject -- causing us to
14429 not always publish a new descriptor since we thought nothing
14431 - Retry pending server downloads as well as pending networkstatus
14432 downloads when we unexpectedly get a socks request.
14433 - We were ignoring the IS_FAST flag in the directory status,
14434 meaning we were willing to pick trivial-bandwidth nodes for "fast"
14436 - If the controller's SAVECONF command fails (e.g. due to file
14437 permissions), let the controller know that it failed.
14440 - If we're trying to be a Tor server and running Windows 95/98/ME
14441 as a server, explain that we'll likely crash.
14442 - When we're a server, a client asks for an old-style directory,
14443 and our write bucket is empty, don't give it to him. This way
14444 small servers can continue to serve the directory *sometimes*,
14445 without getting overloaded.
14446 - Compress exit policies even more -- look for duplicate lines
14448 - Clients now honor the "guard" flag in the router status when
14449 picking entry guards, rather than looking at is_fast or is_stable.
14450 - Retain unrecognized lines in $DATADIR/state file, so that we can
14451 be forward-compatible.
14452 - Generate 18.0.0.0/8 address policy format in descs when we can;
14453 warn when the mask is not reducible to a bit-prefix.
14454 - Let the user set ControlListenAddress in the torrc. This can be
14455 dangerous, but there are some cases (like a secured LAN) where it
14457 - Split ReachableAddresses into ReachableDirAddresses and
14458 ReachableORAddresses, so we can restrict Dir conns to port 80
14459 and OR conns to port 443.
14460 - Now we can target arch and OS in rpm builds (contributed by
14461 Phobos). Also make the resulting dist-rpm filename match the
14463 - New config options to help controllers: FetchServerDescriptors
14464 and FetchHidServDescriptors for whether to fetch server
14465 info and hidserv info or let the controller do it, and
14466 PublishServerDescriptor and PublishHidServDescriptors.
14467 - Also let the controller set the __AllDirActionsPrivate config
14468 option if you want all directory fetches/publishes to happen via
14469 Tor (it assumes your controller bootstraps your circuits).
14472 Changes in version 0.1.0.17 - 2006-02-17
14473 o Crash bugfixes on 0.1.0.x:
14474 - When servers with a non-zero DirPort came out of hibernation,
14475 sometimes they would trigger an assert.
14477 o Other important bugfixes:
14478 - On platforms that don't have getrlimit (like Windows), we were
14479 artificially constraining ourselves to a max of 1024
14480 connections. Now just assume that we can handle as many as 15000
14481 connections. Hopefully this won't cause other problems.
14483 o Backported features:
14484 - When we're a server, a client asks for an old-style directory,
14485 and our write bucket is empty, don't give it to him. This way
14486 small servers can continue to serve the directory *sometimes*,
14487 without getting overloaded.
14488 - Whenever you get a 503 in response to a directory fetch, try
14489 once more. This will become important once servers start sending
14490 503's whenever they feel busy.
14491 - Fetch a new directory every 120 minutes, not every 40 minutes.
14492 Now that we have hundreds of thousands of users running the old
14493 directory algorithm, it's starting to hurt a lot.
14494 - Bump up the period for forcing a hidden service descriptor upload
14495 from 20 minutes to 1 hour.
14498 Changes in version 0.1.1.13-alpha - 2006-02-09
14499 o Crashes in 0.1.1.x:
14500 - When you tried to setconf ORPort via the controller, Tor would
14501 crash. So people using TorCP to become a server were sad.
14502 - Solve (I hope) the stack-smashing bug that we were seeing on fast
14503 servers. The problem appears to be something do with OpenSSL's
14504 random number generation, or how we call it, or something. Let me
14505 know if the crashes continue.
14506 - Turn crypto hardware acceleration off by default, until we find
14507 somebody smart who can test it for us. (It appears to produce
14508 seg faults in at least some cases.)
14509 - Fix a rare assert error when we've tried all intro points for
14510 a hidden service and we try fetching the service descriptor again:
14511 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
14514 - Fix a major load balance bug: we were round-robining in 16 KB
14515 chunks, and servers with bandwidthrate of 20 KB, while downloading
14516 a 600 KB directory, would starve their other connections. Now we
14517 try to be a bit more fair.
14518 - Dir authorities and mirrors were never expiring the newest
14519 descriptor for each server, causing memory and directory bloat.
14520 - Fix memory-bloating and connection-bloating bug on servers: We
14521 were never closing any connection that had ever had a circuit on
14522 it, because we were checking conn->n_circuits == 0, yet we had a
14523 bug that let it go negative.
14524 - Make Tor work using squid as your http proxy again -- squid
14525 returns an error if you ask for a URL that's too long, and it uses
14526 a really generic error message. Plus, many people are behind a
14527 transparent squid so they don't even realize it.
14528 - On platforms that don't have getrlimit (like Windows), we were
14529 artificially constraining ourselves to a max of 1024
14530 connections. Now just assume that we can handle as many as 15000
14531 connections. Hopefully this won't cause other problems.
14532 - Add a new config option ExitPolicyRejectPrivate which defaults to
14533 1. This means all exit policies will begin with rejecting private
14534 addresses, unless the server operator explicitly turns it off.
14537 - Clients no longer download descriptors for non-running
14539 - Before we add new directory authorities, we should make it
14540 clear that only v1 authorities should receive/publish hidden
14541 service descriptors.
14544 - As soon as we've fetched some more directory info, immediately
14545 try to download more server descriptors. This way we don't have
14546 a 10 second pause during initial bootstrapping.
14547 - Remove even more loud log messages that the server operator can't
14549 - When we're running an obsolete or un-recommended version, make
14550 the log message more clear about what the problem is and what
14551 versions *are* still recommended.
14552 - Provide a more useful warn message when our onion queue gets full:
14553 the CPU is too slow or the exit policy is too liberal.
14554 - Don't warn when we receive a 503 from a dirserver/cache -- this
14555 will pave the way for them being able to refuse if they're busy.
14556 - When we fail to bind a listener, try to provide a more useful
14557 log message: e.g., "Is Tor already running?"
14558 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
14559 Goldberg can prove things about our handshake protocol more
14561 - MaxConn has been obsolete for a while now. Document the ConnLimit
14562 config option, which is a *minimum* number of file descriptors
14563 that must be available else Tor refuses to start.
14564 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
14565 if you log to syslog and want something other than LOG_DAEMON.
14566 - Make dirservers generate a separate "guard" flag to mean,
14567 "would make a good entry guard". Make clients parse it and vote
14568 on it. Not used by clients yet.
14569 - Implement --with-libevent-dir option to ./configure. Also, improve
14570 search techniques to find libevent, and use those for openssl too.
14571 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
14572 - Only start testing reachability once we've established a
14573 circuit. This will make startup on dirservers less noisy.
14574 - Don't try to upload hidden service descriptors until we have
14575 established a circuit.
14576 - Fix the controller's "attachstream 0" command to treat conn like
14577 it just connected, doing address remapping, handling .exit and
14578 .onion idioms, and so on. Now we're more uniform in making sure
14579 that the controller hears about new and closing connections.
14582 Changes in version 0.1.1.12-alpha - 2006-01-11
14583 o Bugfixes on 0.1.1.x:
14584 - The fix to close duplicate server connections was closing all
14585 Tor client connections if they didn't establish a circuit
14586 quickly enough. Oops.
14587 - Fix minor memory issue (double-free) that happened on exit.
14589 o Bugfixes on 0.1.0.x:
14590 - Tor didn't warn when it failed to open a log file.
14593 Changes in version 0.1.1.11-alpha - 2006-01-10
14594 o Crashes in 0.1.1.x:
14595 - Include all the assert/crash fixes from 0.1.0.16.
14596 - If you start Tor and then quit very quickly, there were some
14597 races that tried to free things that weren't allocated yet.
14598 - Fix a rare memory stomp if you're running hidden services.
14599 - Fix segfault when specifying DirServer in config without nickname.
14600 - Fix a seg fault when you finish connecting to a server but at
14601 that moment you dump his server descriptor.
14602 - Extendcircuit and Attachstream controller commands would
14603 assert/crash if you don't give them enough arguments.
14604 - Fix an assert error when we're out of space in the connection_list
14605 and we try to post a hidden service descriptor (reported by weasel).
14606 - If you specify a relative torrc path and you set RunAsDaemon in
14607 your torrc, then it chdir()'s to the new directory. If you HUP,
14608 it tries to load the new torrc location, fails, and exits.
14609 The fix: no longer allow a relative path to torrc using -f.
14612 - Implement "entry guards": automatically choose a handful of entry
14613 nodes and stick with them for all circuits. Only pick new guards
14614 when the ones you have are unsuitable, and if the old guards
14615 become suitable again, switch back. This will increase security
14616 dramatically against certain end-point attacks. The EntryNodes
14617 config option now provides some hints about which entry guards you
14618 want to use most; and StrictEntryNodes means to only use those.
14619 - New directory logic: download by descriptor digest, not by
14620 fingerprint. Caches try to download all listed digests from
14621 authorities; clients try to download "best" digests from caches.
14622 This avoids partitioning and isolating attacks better.
14623 - Make the "stable" router flag in network-status be the median of
14624 the uptimes of running valid servers, and make clients pay
14625 attention to the network-status flags. Thus the cutoff adapts
14626 to the stability of the network as a whole, making IRC, IM, etc
14627 connections more reliable.
14630 - Tor servers with dynamic IP addresses were needing to wait 18
14631 hours before they could start doing reachability testing using
14632 the new IP address and ports. This is because they were using
14633 the internal descriptor to learn what to test, yet they were only
14634 rebuilding the descriptor once they decided they were reachable.
14635 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
14636 to download certain server descriptors, throw them away, and then
14637 fetch them again after 30 minutes. Now mirrors throw away these
14638 server descriptors so clients can't get them.
14639 - We were leaving duplicate connections to other ORs open for a week,
14640 rather than closing them once we detect a duplicate. This only
14641 really affected authdirservers, but it affected them a lot.
14642 - Spread the authdirservers' reachability testing over the entire
14643 testing interval, so we don't try to do 500 TLS's at once every
14647 - If the network is down, and we try to connect to a conn because
14648 we have a circuit in mind, and we timeout (30 seconds) because the
14649 network never answers, we were expiring the circuit, but we weren't
14650 obsoleting the connection or telling the entry_guards functions.
14651 - Some Tor servers process billions of cells per day. These statistics
14652 need to be uint64_t's.
14653 - Check for integer overflows in more places, when adding elements
14654 to smartlists. This could possibly prevent a buffer overflow
14655 on malicious huge inputs. I don't see any, but I haven't looked
14657 - ReachableAddresses kept growing new "reject *:*" lines on every
14659 - When you "setconf log" via the controller, it should remove all
14660 logs. We were automatically adding back in a "log notice stdout".
14661 - Newly bootstrapped Tor networks couldn't establish hidden service
14662 circuits until they had nodes with high uptime. Be more tolerant.
14663 - We were marking servers down when they could not answer every piece
14664 of the directory request we sent them. This was far too harsh.
14665 - Fix the torify (tsocks) config file to not use Tor for localhost
14667 - Directory authorities now go to the proper authority when asking for
14668 a networkstatus, even when they want a compressed one.
14669 - Fix a harmless bug that was causing Tor servers to log
14670 "Got an end because of misc error, but we're not an AP. Closing."
14671 - Authorities were treating their own descriptor changes as cosmetic,
14672 meaning the descriptor available in the network-status and the
14673 descriptor that clients downloaded were different.
14674 - The OS X installer was adding a symlink for tor_resolve but
14675 the binary was called tor-resolve (reported by Thomas Hardly).
14676 - Workaround a problem with some http proxies where they refuse GET
14677 requests that specify "Content-Length: 0" (reported by Adrian).
14678 - Fix wrong log message when you add a "HiddenServiceNodes" config
14679 line without any HiddenServiceDir line (reported by Chris Thomas).
14682 - Write the TorVersion into the state file so we have a prayer of
14683 keeping forward and backward compatibility.
14684 - Revive the FascistFirewall config option rather than eliminating it:
14685 now it's a synonym for ReachableAddresses *:80,*:443.
14686 - Clients choose directory servers from the network status lists,
14687 not from their internal list of router descriptors. Now they can
14688 go to caches directly rather than needing to go to authorities
14690 - Directory authorities ignore router descriptors that have only
14691 cosmetic differences: do this for 0.1.0.x servers now too.
14692 - Add a new flag to network-status indicating whether the server
14693 can answer v2 directory requests too.
14694 - Authdirs now stop whining so loudly about bad descriptors that
14695 they fetch from other dirservers. So when there's a log complaint,
14696 it's for sure from a freshly uploaded descriptor.
14697 - Reduce memory requirements in our structs by changing the order
14699 - There used to be two ways to specify your listening ports in a
14700 server descriptor: on the "router" line and with a separate "ports"
14701 line. Remove support for the "ports" line.
14702 - New config option "AuthDirRejectUnlisted" for auth dirservers as
14703 a panic button: if we get flooded with unusable servers we can
14704 revert to only listing servers in the approved-routers file.
14705 - Auth dir servers can now mark a fingerprint as "!reject" or
14706 "!invalid" in the approved-routers file (as its nickname), to
14707 refuse descriptors outright or include them but marked as invalid.
14708 - Servers store bandwidth history across restarts/crashes.
14709 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
14710 get a better idea of why their circuits failed. Not used yet.
14711 - Directory mirrors now cache up to 16 unrecognized network-status
14712 docs. Now we can add new authdirservers and they'll be cached too.
14713 - When picking a random directory, prefer non-authorities if any
14715 - New controller option "getinfo desc/all-recent" to fetch the
14716 latest server descriptor for every router that Tor knows about.
14719 Changes in version 0.1.0.16 - 2006-01-02
14720 o Crash bugfixes on 0.1.0.x:
14721 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14722 corrupting the heap, losing FDs, or crashing when we need to resize
14723 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14724 - It turns out sparc64 platforms crash on unaligned memory access
14725 too -- so detect and avoid this.
14726 - Handle truncated compressed data correctly (by detecting it and
14728 - Fix possible-but-unlikely free(NULL) in control.c.
14729 - When we were closing connections, there was a rare case that
14730 stomped on memory, triggering seg faults and asserts.
14731 - Avoid potential infinite recursion when building a descriptor. (We
14732 don't know that it ever happened, but better to fix it anyway.)
14733 - We were neglecting to unlink marked circuits from soon-to-close OR
14734 connections, which caused some rare scribbling on freed memory.
14735 - Fix a memory stomping race bug when closing the joining point of two
14736 rendezvous circuits.
14737 - Fix an assert in time parsing found by Steven Murdoch.
14739 o Other bugfixes on 0.1.0.x:
14740 - When we're doing reachability testing, provide more useful log
14741 messages so the operator knows what to expect.
14742 - Do not check whether DirPort is reachable when we are suppressing
14743 advertising it because of hibernation.
14744 - When building with -static or on Solaris, we sometimes needed -ldl.
14745 - When we're deciding whether a stream has enough circuits around
14746 that can handle it, count the freshly dirty ones and not the ones
14747 that are so dirty they won't be able to handle it.
14748 - When we're expiring old circuits, we had a logic error that caused
14749 us to close new rendezvous circuits rather than old ones.
14750 - Give a more helpful log message when you try to change ORPort via
14751 the controller: you should upgrade Tor if you want that to work.
14752 - We were failing to parse Tor versions that start with "Tor ".
14753 - Tolerate faulty streams better: when a stream fails for reason
14754 exitpolicy, stop assuming that the router is lying about his exit
14755 policy. When a stream fails for reason misc, allow it to retry just
14756 as if it was resolvefailed. When a stream has failed three times,
14757 reset its failure count so we can try again and get all three tries.
14760 Changes in version 0.1.1.10-alpha - 2005-12-11
14761 o Correctness bugfixes on 0.1.0.x:
14762 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14763 corrupting the heap, losing FDs, or crashing when we need to resize
14764 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14765 - Stop doing the complex voodoo overkill checking for insecure
14766 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
14767 - When we were closing connections, there was a rare case that
14768 stomped on memory, triggering seg faults and asserts.
14769 - We were neglecting to unlink marked circuits from soon-to-close OR
14770 connections, which caused some rare scribbling on freed memory.
14771 - When we're deciding whether a stream has enough circuits around
14772 that can handle it, count the freshly dirty ones and not the ones
14773 that are so dirty they won't be able to handle it.
14774 - Recover better from TCP connections to Tor servers that are
14775 broken but don't tell you (it happens!); and rotate TLS
14776 connections once a week.
14777 - When we're expiring old circuits, we had a logic error that caused
14778 us to close new rendezvous circuits rather than old ones.
14779 - Fix a scary-looking but apparently harmless bug where circuits
14780 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
14781 servers, and never switch to state CIRCUIT_STATE_OPEN.
14782 - When building with -static or on Solaris, we sometimes needed to
14784 - Give a useful message when people run Tor as the wrong user,
14785 rather than telling them to start chowning random directories.
14786 - We were failing to inform the controller about new .onion streams.
14788 o Security bugfixes on 0.1.0.x:
14789 - Refuse server descriptors if the fingerprint line doesn't match
14790 the included identity key. Tor doesn't care, but other apps (and
14791 humans) might actually be trusting the fingerprint line.
14792 - We used to kill the circuit when we receive a relay command we
14793 don't recognize. Now we just drop it.
14794 - Start obeying our firewall options more rigorously:
14795 . If we can't get to a dirserver directly, try going via Tor.
14796 . Don't ever try to connect (as a client) to a place our
14797 firewall options forbid.
14798 . If we specify a proxy and also firewall options, obey the
14799 firewall options even when we're using the proxy: some proxies
14800 can only proxy to certain destinations.
14801 - Fix a bug found by Lasse Overlier: when we were making internal
14802 circuits (intended to be cannibalized later for rendezvous and
14803 introduction circuits), we were picking them so that they had
14804 useful exit nodes. There was no need for this, and it actually
14805 aids some statistical attacks.
14806 - Start treating internal circuits and exit circuits separately.
14807 It's important to keep them separate because internal circuits
14808 have their last hops picked like middle hops, rather than like
14809 exit hops. So exiting on them will break the user's expectations.
14811 o Bugfixes on 0.1.1.x:
14812 - Take out the mis-feature where we tried to detect IP address
14813 flapping for people with DynDNS, and chose not to upload a new
14814 server descriptor sometimes.
14815 - Try to be compatible with OpenSSL 0.9.6 again.
14816 - Log fix: when the controller is logging about .onion addresses,
14817 sometimes it didn't include the ".onion" part of the address.
14818 - Don't try to modify options->DirServers internally -- if the
14819 user didn't specify any, just add the default ones directly to
14820 the trusted dirserver list. This fixes a bug where people running
14821 controllers would use SETCONF on some totally unrelated config
14822 option, and Tor would start yelling at them about changing their
14824 - Let the controller's redirectstream command specify a port, in
14825 case the controller wants to change that too.
14826 - When we requested a pile of server descriptors, we sometimes
14827 accidentally launched a duplicate request for the first one.
14828 - Bugfix for trackhostexits: write down the fingerprint of the
14829 chosen exit, not its nickname, because the chosen exit might not
14831 - When parsing foo.exit, if foo is unknown, and we are leaving
14832 circuits unattached, set the chosen_exit field and leave the
14833 address empty. This matters because controllers got confused
14835 - Directory authorities no longer try to download server
14836 descriptors that they know they will reject.
14838 o Features and updates:
14839 - Replace balanced trees with hash tables: this should make stuff
14840 significantly faster.
14841 - Resume using the AES counter-mode implementation that we ship,
14842 rather than OpenSSL's. Ours is significantly faster.
14843 - Many other CPU and memory improvements.
14844 - Add a new config option FastFirstHopPK (on by default) so clients
14845 do a trivial crypto handshake for their first hop, since TLS has
14846 already taken care of confidentiality and authentication.
14847 - Add a new config option TestSocks so people can see if their
14848 applications are using socks4, socks4a, socks5-with-ip, or
14849 socks5-with-hostname. This way they don't have to keep mucking
14850 with tcpdump and wondering if something got cached somewhere.
14851 - Warn when listening on a public address for socks. I suspect a
14852 lot of people are setting themselves up as open socks proxies,
14853 and they have no idea that jerks on the Internet are using them,
14854 since they simply proxy the traffic into the Tor network.
14855 - Add "private:*" as an alias in configuration for policies. Now
14856 you can simplify your exit policy rather than needing to list
14857 every single internal or nonroutable network space.
14858 - Add a new controller event type that allows controllers to get
14859 all server descriptors that were uploaded to a router in its role
14860 as authoritative dirserver.
14861 - Start shipping socks-extensions.txt, tor-doc-unix.html,
14862 tor-doc-server.html, and stylesheet.css in the tarball.
14863 - Stop shipping tor-doc.html in the tarball.
14866 Changes in version 0.1.1.9-alpha - 2005-11-15
14867 o Usability improvements:
14868 - Start calling it FooListenAddress rather than FooBindAddress,
14869 since few of our users know what it means to bind an address
14871 - Reduce clutter in server logs. We're going to try to make
14872 them actually usable now. New config option ProtocolWarnings that
14873 lets you hear about how _other Tors_ are breaking the protocol. Off
14875 - Divide log messages into logging domains. Once we put some sort
14876 of interface on this, it will let people looking at more verbose
14877 log levels specify the topics they want to hear more about.
14878 - Make directory servers return better http 404 error messages
14879 instead of a generic "Servers unavailable".
14880 - Check for even more Windows version flags when writing the platform
14881 string in server descriptors, and note any we don't recognize.
14882 - Clean up more of the OpenSSL memory when exiting, so we can detect
14883 memory leaks better.
14884 - Make directory authorities be non-versioning, non-naming by
14885 default. Now we can add new directory servers without requiring
14886 their operators to pay close attention.
14887 - When logging via syslog, include the pid whenever we provide
14888 a log entry. Suggested by Todd Fries.
14890 o Performance improvements:
14891 - Directory servers now silently throw away new descriptors that
14892 haven't changed much if the timestamps are similar. We do this to
14893 tolerate older Tor servers that upload a new descriptor every 15
14894 minutes. (It seemed like a good idea at the time.)
14895 - Inline bottleneck smartlist functions; use fast versions by default.
14896 - Add a "Map from digest to void*" abstraction digestmap_t so we
14897 can do less hex encoding/decoding. Use it in router_get_by_digest()
14898 to resolve a performance bottleneck.
14899 - Allow tor_gzip_uncompress to extract as much as possible from
14900 truncated compressed data. Try to extract as many
14901 descriptors as possible from truncated http responses (when
14902 DIR_PURPOSE_FETCH_ROUTERDESC).
14903 - Make circ->onionskin a pointer, not a static array. moria2 was using
14904 125000 circuit_t's after it had been up for a few weeks, which
14905 translates to 20+ megs of wasted space.
14906 - The private half of our EDH handshake keys are now chosen out
14907 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
14909 o Security improvements:
14910 - Start making directory caches retain old routerinfos, so soon
14911 clients can start asking by digest of descriptor rather than by
14912 fingerprint of server.
14913 - Add half our entropy from RAND_poll in OpenSSL. This knows how
14914 to use egd (if present), openbsd weirdness (if present), vms/os2
14915 weirdness (if we ever port there), and more in the future.
14917 o Bugfixes on 0.1.0.x:
14918 - Do round-robin writes of at most 16 kB per write. This might be
14919 more fair on loaded Tor servers, and it might resolve our Windows
14920 crash bug. It might also slow things down.
14921 - Our TLS handshakes were generating a single public/private
14922 keypair for the TLS context, rather than making a new one for
14923 each new connections. Oops. (But we were still rotating them
14924 periodically, so it's not so bad.)
14925 - When we were cannibalizing a circuit with a particular exit
14926 node in mind, we weren't checking to see if that exit node was
14927 already present earlier in the circuit. Oops.
14928 - When a Tor server's IP changes (e.g. from a dyndns address),
14929 upload a new descriptor so clients will learn too.
14930 - Really busy servers were keeping enough circuits open on stable
14931 connections that they were wrapping around the circuit_id
14932 space. (It's only two bytes.) This exposed a bug where we would
14933 feel free to reuse a circuit_id even if it still exists but has
14934 been marked for close. Try to fix this bug. Some bug remains.
14935 - If we would close a stream early (e.g. it asks for a .exit that
14936 we know would refuse it) but the LeaveStreamsUnattached config
14937 option is set by the controller, then don't close it.
14939 o Bugfixes on 0.1.1.8-alpha:
14940 - Fix a big pile of memory leaks, some of them serious.
14941 - Do not try to download a routerdesc if we would immediately reject
14943 - Resume inserting a newline between all router descriptors when
14944 generating (old style) signed directories, since our spec says
14946 - When providing content-type application/octet-stream for
14947 server descriptors using .z, we were leaving out the
14948 content-encoding header. Oops. (Everything tolerated this just
14949 fine, but that doesn't mean we need to be part of the problem.)
14950 - Fix a potential seg fault in getconf and getinfo using version 1
14951 of the controller protocol.
14952 - Avoid crash: do not check whether DirPort is reachable when we
14953 are suppressing it because of hibernation.
14954 - Make --hash-password not crash on exit.
14957 Changes in version 0.1.1.8-alpha - 2005-10-07
14958 o New features (major):
14959 - Clients don't download or use the directory anymore. Now they
14960 download and use network-statuses from the trusted dirservers,
14961 and fetch individual server descriptors as needed from mirrors.
14962 See dir-spec.txt for all the gory details.
14963 - Be more conservative about whether to advertise our DirPort.
14964 The main change is to not advertise if we're running at capacity
14965 and either a) we could hibernate or b) our capacity is low and
14966 we're using a default DirPort.
14967 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
14969 o New features (minor):
14970 - Try to be smart about when to retry network-status and
14971 server-descriptor fetches. Still needs some tuning.
14972 - Stop parsing, storing, or using running-routers output (but
14973 mirrors still cache and serve it).
14974 - Consider a threshold of versioning dirservers (dirservers who have
14975 an opinion about which Tor versions are still recommended) before
14976 deciding whether to warn the user that he's obsolete.
14977 - Dirservers can now reject/invalidate by key and IP, with the
14978 config options "AuthDirInvalid" and "AuthDirReject". This is
14979 useful since currently we automatically list servers as running
14980 and usable even if we know they're jerks.
14981 - Provide dire warnings to any users who set DirServer; move it out
14982 of torrc.sample and into torrc.complete.
14983 - Add MyFamily to torrc.sample in the server section.
14984 - Add nicknames to the DirServer line, so we can refer to them
14985 without requiring all our users to memorize their IP addresses.
14986 - When we get an EOF or a timeout on a directory connection, note
14987 how many bytes of serverdesc we are dropping. This will help
14988 us determine whether it is smart to parse incomplete serverdesc
14990 - Add a new function to "change pseudonyms" -- that is, to stop
14991 using any currently-dirty circuits for new streams, so we don't
14992 link new actions to old actions. Currently it's only called on
14993 HUP (or SIGNAL RELOAD).
14994 - On sighup, if UseHelperNodes changed to 1, use new circuits.
14995 - Start using RAND_bytes rather than RAND_pseudo_bytes from
14996 OpenSSL. Also, reseed our entropy every hour, not just at
14997 startup. And entropy in 512-bit chunks, not 160-bit chunks.
14999 o Fixes on 0.1.1.7-alpha:
15000 - Nobody ever implemented EVENT_ADDRMAP for control protocol
15001 version 0, so don't let version 0 controllers ask for it.
15002 - If you requested something with too many newlines via the
15003 v1 controller protocol, you could crash tor.
15004 - Fix a number of memory leaks, including some pretty serious ones.
15005 - Re-enable DirPort testing again, so Tor servers will be willing
15006 to advertise their DirPort if it's reachable.
15007 - On TLS handshake, only check the other router's nickname against
15008 its expected nickname if is_named is set.
15010 o Fixes forward-ported from 0.1.0.15:
15011 - Don't crash when we don't have any spare file descriptors and we
15012 try to spawn a dns or cpu worker.
15013 - Make the numbers in read-history and write-history into uint64s,
15014 so they don't overflow and publish negatives in the descriptor.
15016 o Fixes on 0.1.0.x:
15017 - For the OS X package's modified privoxy config file, comment
15018 out the "logfile" line so we don't log everything passed
15020 - We were whining about using socks4 or socks5-with-local-lookup
15021 even when it's an IP in the "virtual" range we designed exactly
15023 - We were leaking some memory every time the client changes IPs.
15024 - Never call free() on tor_malloc()d memory. This will help us
15025 use dmalloc to detect memory leaks.
15026 - Check for named servers when looking them up by nickname;
15027 warn when we'recalling a non-named server by its nickname;
15028 don't warn twice about the same name.
15029 - Try to list MyFamily elements by key, not by nickname, and warn
15030 if we've not heard of the server.
15031 - Make windows platform detection (uname equivalent) smarter.
15032 - It turns out sparc64 doesn't like unaligned access either.
15035 Changes in version 0.1.0.15 - 2005-09-23
15036 o Bugfixes on 0.1.0.x:
15037 - Reject ports 465 and 587 (spam targets) in default exit policy.
15038 - Don't crash when we don't have any spare file descriptors and we
15039 try to spawn a dns or cpu worker.
15040 - Get rid of IgnoreVersion undocumented config option, and make us
15041 only warn, never exit, when we're running an obsolete version.
15042 - Don't try to print a null string when your server finds itself to
15043 be unreachable and the Address config option is empty.
15044 - Make the numbers in read-history and write-history into uint64s,
15045 so they don't overflow and publish negatives in the descriptor.
15046 - Fix a minor memory leak in smartlist_string_remove().
15047 - We were only allowing ourselves to upload a server descriptor at
15048 most every 20 minutes, even if it changed earlier than that.
15049 - Clean up log entries that pointed to old URLs.
15052 Changes in version 0.1.1.7-alpha - 2005-09-14
15053 o Fixes on 0.1.1.6-alpha:
15054 - Exit servers were crashing when people asked them to make a
15055 connection to an address not in their exit policy.
15056 - Looking up a non-existent stream for a v1 control connection would
15058 - Fix a seg fault if we ask a dirserver for a descriptor by
15059 fingerprint but he doesn't know about him.
15060 - SETCONF was appending items to linelists, not clearing them.
15061 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
15062 out and refuse the setconf if it would fail.
15063 - Downgrade the dirserver log messages when whining about
15067 - Add Peter Palfrader's check-tor script to tor/contrib/
15068 It lets you easily check whether a given server (referenced by
15069 nickname) is reachable by you.
15070 - Numerous changes to move towards client-side v2 directories. Not
15073 o Fixes on 0.1.0.x:
15074 - If the user gave tor an odd number of command-line arguments,
15075 we were silently ignoring the last one. Now we complain and fail.
15076 [This wins the oldest-bug prize -- this bug has been present since
15077 November 2002, as released in Tor 0.0.0.]
15078 - Do not use unaligned memory access on alpha, mips, or mipsel.
15079 It *works*, but is very slow, so we treat them as if it doesn't.
15080 - Retry directory requests if we fail to get an answer we like
15081 from a given dirserver (we were retrying before, but only if
15082 we fail to connect).
15083 - When writing the RecommendedVersions line, sort them first.
15084 - When the client asked for a rendezvous port that the hidden
15085 service didn't want to provide, we were sending an IP address
15086 back along with the end cell. Fortunately, it was zero. But stop
15088 - Correct "your server is reachable" log entries to indicate that
15089 it was self-testing that told us so.
15092 Changes in version 0.1.1.6-alpha - 2005-09-09
15093 o Fixes on 0.1.1.5-alpha:
15094 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
15095 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
15096 - Fix bug with tor_memmem finding a match at the end of the string.
15097 - Make unit tests run without segfaulting.
15098 - Resolve some solaris x86 compile warnings.
15099 - Handle duplicate lines in approved-routers files without warning.
15100 - Fix bug where as soon as a server refused any requests due to his
15101 exit policy (e.g. when we ask for localhost and he tells us that's
15102 127.0.0.1 and he won't do it), we decided he wasn't obeying his
15103 exit policy using him for any exits.
15104 - Only do openssl hardware accelerator stuff if openssl version is
15107 o New controller features/fixes:
15108 - Add a "RESETCONF" command so you can set config options like
15109 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
15110 a config option in the torrc with no value, then it clears it
15111 entirely (rather than setting it to its default).
15112 - Add a "GETINFO config-file" to tell us where torrc is.
15113 - Avoid sending blank lines when GETINFO replies should be empty.
15114 - Add a QUIT command for the controller (for using it manually).
15115 - Fix a bug in SAVECONF that was adding default dirservers and
15116 other redundant entries to the torrc file.
15118 o Start on the new directory design:
15119 - Generate, publish, cache, serve new network-status format.
15120 - Publish individual descriptors (by fingerprint, by "all", and by
15122 - Publish client and server recommended versions separately.
15123 - Allow tor_gzip_uncompress() to handle multiple concatenated
15124 compressed strings. Serve compressed groups of router
15125 descriptors. The compression logic here could be more
15127 - Distinguish v1 authorities (all currently trusted directories)
15128 from v2 authorities (all trusted directories).
15129 - Change DirServers config line to note which dirs are v1 authorities.
15130 - Add configuration option "V1AuthoritativeDirectory 1" which
15131 moria1, moria2, and tor26 should set.
15132 - Remove option when getting directory cache to see whether they
15133 support running-routers; they all do now. Replace it with one
15134 to see whether caches support v2 stuff.
15137 - Dirservers now do their own external reachability testing of each
15138 Tor server, and only list them as running if they've been found to
15139 be reachable. We also send back warnings to the server's logs if
15140 it uploads a descriptor that we already believe is unreachable.
15141 - Implement exit enclaves: if we know an IP address for the
15142 destination, and there's a running Tor server at that address
15143 which allows exit to the destination, then extend the circuit to
15144 that exit first. This provides end-to-end encryption and end-to-end
15145 authentication. Also, if the user wants a .exit address or enclave,
15146 use 4 hops rather than 3, and cannibalize a general circ for it
15148 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
15149 controller. Also, rotate dns and cpu workers if the controller
15150 changes options that will affect them; and initialize the dns
15151 worker cache tree whether or not we start out as a server.
15152 - Only upload a new server descriptor when options change, 18
15153 hours have passed, uptime is reset, or bandwidth changes a lot.
15154 - Check [X-]Forwarded-For headers in HTTP requests when generating
15155 log messages. This lets people run dirservers (and caches) behind
15156 Apache but still know which IP addresses are causing warnings.
15158 o Config option changes:
15159 - Replace (Fascist)Firewall* config options with a new
15160 ReachableAddresses option that understands address policies.
15161 For example, "ReachableAddresses *:80,*:443"
15162 - Get rid of IgnoreVersion undocumented config option, and make us
15163 only warn, never exit, when we're running an obsolete version.
15164 - Make MonthlyAccountingStart config option truly obsolete now.
15166 o Fixes on 0.1.0.x:
15167 - Reject ports 465 and 587 in the default exit policy, since
15168 people have started using them for spam too.
15169 - It turns out we couldn't bootstrap a network since we added
15170 reachability detection in 0.1.0.1-rc. Good thing the Tor network
15171 has never gone down. Add an AssumeReachable config option to let
15172 servers and dirservers bootstrap. When we're trying to build a
15173 high-uptime or high-bandwidth circuit but there aren't enough
15174 suitable servers, try being less picky rather than simply failing.
15175 - Our logic to decide if the OR we connected to was the right guy
15176 was brittle and maybe open to a mitm for unverified routers.
15177 - We weren't cannibalizing circuits correctly for
15178 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
15179 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
15180 build those from scratch. This should make hidden services faster.
15181 - Predict required circuits better, with an eye toward making hidden
15182 services faster on the service end.
15183 - Retry streams if the exit node sends back a 'misc' failure. This
15184 should result in fewer random failures. Also, after failing
15185 from resolve failed or misc, reset the num failures, so we give
15186 it a fair shake next time we try.
15187 - Clean up the rendezvous warn log msgs, and downgrade some to info.
15188 - Reduce severity on logs about dns worker spawning and culling.
15189 - When we're shutting down and we do something like try to post a
15190 server descriptor or rendezvous descriptor, don't complain that
15191 we seem to be unreachable. Of course we are, we're shutting down.
15192 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
15193 We don't use them yet, but maybe one day our DNS resolver will be
15194 able to discover them.
15195 - Make ContactInfo mandatory for authoritative directory servers.
15196 - Require server descriptors to list IPv4 addresses -- hostnames
15197 are no longer allowed. This also fixes some potential security
15198 problems with people providing hostnames as their address and then
15199 preferentially resolving them to partition users.
15200 - Change log line for unreachability to explicitly suggest /etc/hosts
15201 as the culprit. Also make it clearer what IP address and ports we're
15202 testing for reachability.
15203 - Put quotes around user-supplied strings when logging so users are
15204 more likely to realize if they add bad characters (like quotes)
15206 - Let auth dir servers start without specifying an Address config
15208 - Make unit tests (and other invocations that aren't the real Tor)
15209 run without launching listeners, creating subdirectories, and so on.
15212 Changes in version 0.1.1.5-alpha - 2005-08-08
15213 o Bugfixes included in 0.1.0.14.
15215 o Bugfixes on 0.1.0.x:
15216 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
15217 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
15218 it would silently using ignore the 6668.
15221 Changes in version 0.1.0.14 - 2005-08-08
15222 o Bugfixes on 0.1.0.x:
15223 - Fix the other half of the bug with crypto handshakes
15225 - Fix an assert trigger if you send a 'signal term' via the
15226 controller when it's listening for 'event info' messages.
15229 Changes in version 0.1.1.4-alpha - 2005-08-04
15230 o Bugfixes included in 0.1.0.13.
15233 - Improve tor_gettimeofday() granularity on windows.
15234 - Make clients regenerate their keys when their IP address changes.
15235 - Implement some more GETINFO goodness: expose helper nodes, config
15236 options, getinfo keys.
15239 Changes in version 0.1.0.13 - 2005-08-04
15240 o Bugfixes on 0.1.0.x:
15241 - Fix a critical bug in the security of our crypto handshakes.
15242 - Fix a size_t underflow in smartlist_join_strings2() that made
15243 it do bad things when you hand it an empty smartlist.
15244 - Fix Windows installer to ship Tor license (thanks to Aphex for
15245 pointing out this oversight) and put a link to the doc directory
15247 - Explicitly set no-unaligned-access for sparc: it turns out the
15248 new gcc's let you compile broken code, but that doesn't make it
15252 Changes in version 0.1.1.3-alpha - 2005-07-23
15253 o Bugfixes on 0.1.1.2-alpha:
15254 - Fix a bug in handling the controller's "post descriptor"
15256 - Fix several bugs in handling the controller's "extend circuit"
15258 - Fix a bug in handling the controller's "stream status" event.
15259 - Fix an assert failure if we have a controller listening for
15260 circuit events and we go offline.
15261 - Re-allow hidden service descriptors to publish 0 intro points.
15262 - Fix a crash when generating your hidden service descriptor if
15263 you don't have enough intro points already.
15265 o New features on 0.1.1.2-alpha:
15266 - New controller function "getinfo accounting", to ask how
15267 many bytes we've used in this time period.
15268 - Experimental support for helper nodes: a lot of the risk from
15269 a small static adversary comes because users pick new random
15270 nodes every time they rebuild a circuit. Now users will try to
15271 stick to the same small set of entry nodes if they can. Not
15272 enabled by default yet.
15274 o Bugfixes on 0.1.0.12:
15275 - If you're an auth dir server, always publish your dirport,
15276 even if you haven't yet found yourself to be reachable.
15277 - Fix a size_t underflow in smartlist_join_strings2() that made
15278 it do bad things when you hand it an empty smartlist.
15281 Changes in version 0.1.0.12 - 2005-07-18
15282 o New directory servers:
15283 - tor26 has changed IP address.
15285 o Bugfixes on 0.1.0.x:
15286 - Fix a possible double-free in tor_gzip_uncompress().
15287 - When --disable-threads is set, do not search for or link against
15288 pthreads libraries.
15289 - Don't trigger an assert if an authoritative directory server
15290 claims its dirport is 0.
15291 - Fix bug with removing Tor as an NT service: some people were
15292 getting "The service did not return an error." Thanks to Matt
15296 Changes in version 0.1.1.2-alpha - 2005-07-15
15297 o New directory servers:
15298 - tor26 has changed IP address.
15300 o Bugfixes on 0.1.0.x, crashes/leaks:
15301 - Port the servers-not-obeying-their-exit-policies fix from
15303 - Fix an fd leak in start_daemon().
15304 - On Windows, you can't always reopen a port right after you've
15305 closed it. So change retry_listeners() to only close and re-open
15306 ports that have changed.
15307 - Fix a possible double-free in tor_gzip_uncompress().
15309 o Bugfixes on 0.1.0.x, usability:
15310 - When tor_socketpair() fails in Windows, give a reasonable
15311 Windows-style errno back.
15312 - Let people type "tor --install" as well as "tor -install" when
15314 want to make it an NT service.
15315 - NT service patch from Matt Edman to improve error messages.
15316 - When the controller asks for a config option with an abbreviated
15317 name, give the full name in our response.
15318 - Correct the man page entry on TrackHostExitsExpire.
15319 - Looks like we were never delivering deflated (i.e. compressed)
15320 running-routers lists, even when asked. Oops.
15321 - When --disable-threads is set, do not search for or link against
15322 pthreads libraries.
15324 o Bugfixes on 0.1.1.x:
15325 - Fix a seg fault with autodetecting which controller version is
15329 - New hidden service descriptor format: put a version in it, and
15330 let people specify introduction/rendezvous points that aren't
15331 in "the directory" (which is subjective anyway).
15332 - Allow the DEBUG controller event to work again. Mark certain log
15333 entries as "don't tell this to controllers", so we avoid cycles.
15336 Changes in version 0.1.0.11 - 2005-06-30
15337 o Bugfixes on 0.1.0.x:
15338 - Fix major security bug: servers were disregarding their
15339 exit policies if clients behaved unexpectedly.
15340 - Make OS X init script check for missing argument, so we don't
15341 confuse users who invoke it incorrectly.
15342 - Fix a seg fault in "tor --hash-password foo".
15343 - The MAPADDRESS control command was broken.
15346 Changes in version 0.1.1.1-alpha - 2005-06-29
15348 - Make OS X init script check for missing argument, so we don't
15349 confuse users who invoke it incorrectly.
15350 - Fix a seg fault in "tor --hash-password foo".
15351 - Fix a possible way to DoS dirservers.
15352 - When we complain that your exit policy implicitly allows local or
15353 private address spaces, name them explicitly so operators can
15355 - Make the log message less scary when all the dirservers are
15356 temporarily unreachable.
15357 - We were printing the number of idle dns workers incorrectly when
15361 - Revised controller protocol (version 1) that uses ascii rather
15362 than binary. Add supporting libraries in python and java so you
15363 can use the controller from your applications without caring how
15364 our protocol works.
15365 - Spiffy new support for crypto hardware accelerators. Can somebody
15369 Changes in version 0.0.9.10 - 2005-06-16
15370 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
15371 - Refuse relay cells that claim to have a length larger than the
15372 maximum allowed. This prevents a potential attack that could read
15373 arbitrary memory (e.g. keys) from an exit server's process
15377 Changes in version 0.1.0.10 - 2005-06-14
15378 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
15379 libevent before 1.1a.
15382 Changes in version 0.1.0.9-rc - 2005-06-09
15384 - Reset buf->highwater every time buf_shrink() is called, not just on
15385 a successful shrink. This was causing significant memory bloat.
15386 - Fix buffer overflow when checking hashed passwords.
15387 - Security fix: if seeding the RNG on Win32 fails, quit.
15388 - Allow seeding the RNG on Win32 even when you're not running as
15390 - Disable threading on Solaris too. Something is wonky with it,
15391 cpuworkers, and reentrant libs.
15392 - Reenable the part of the code that tries to flush as soon as an
15393 OR outbuf has a full TLS record available. Perhaps this will make
15394 OR outbufs not grow as huge except in rare cases, thus saving lots
15395 of CPU time plus memory.
15396 - Reject malformed .onion addresses rather then passing them on as
15397 normal web requests.
15398 - Adapt patch from Adam Langley: fix possible memory leak in
15399 tor_lookup_hostname().
15400 - Initialize libevent later in the startup process, so the logs are
15401 already established by the time we start logging libevent warns.
15402 - Use correct errno on win32 if libevent fails.
15403 - Check and warn about known-bad/slow libevent versions.
15404 - Pay more attention to the ClientOnly config option.
15405 - Have torctl.in/tor.sh.in check for location of su binary (needed
15407 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
15408 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
15409 HttpProxyAuthenticator
15410 - Stop warning about sigpipes in the logs. We're going to
15411 pretend that getting these occassionally is normal and fine.
15412 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
15414 installer screens; and don't put stuff into StartupItems unless
15415 the user asks you to.
15416 - Require servers that use the default dirservers to have public IP
15417 addresses. We have too many servers that are configured with private
15418 IPs and their admins never notice the log entries complaining that
15419 their descriptors are being rejected.
15420 - Add OSX uninstall instructions. An actual uninstall script will
15424 Changes in version 0.1.0.8-rc - 2005-05-23
15426 - It turns out that kqueue on OS X 10.3.9 was causing kernel
15427 panics. Disable kqueue on all OS X Tors.
15428 - Fix RPM: remove duplicate line accidentally added to the rpm
15430 - Disable threads on openbsd too, since its gethostaddr is not
15432 - Tolerate libevent 0.8 since it still works, even though it's
15434 - Enable building on Red Hat 9.0 again.
15435 - Allow the middle hop of the testing circuit to be running any
15436 version, now that most of them have the bugfix to let them connect
15437 to unknown servers. This will allow reachability testing to work
15438 even when 0.0.9.7-0.0.9.9 become obsolete.
15439 - Handle relay cells with rh.length too large. This prevents
15440 a potential attack that could read arbitrary memory (maybe even
15441 keys) from the exit server's process.
15442 - We screwed up the dirport reachability testing when we don't yet
15443 have a cached version of the directory. Hopefully now fixed.
15444 - Clean up router_load_single_router() (used by the controller),
15445 so it doesn't seg fault on error.
15446 - Fix a minor memory leak when somebody establishes an introduction
15447 point at your Tor server.
15448 - If a socks connection ends because read fails, don't warn that
15449 you're not sending a socks reply back.
15452 - Add HttpProxyAuthenticator config option too, that works like
15453 the HttpsProxyAuthenticator config option.
15454 - Encode hashed controller passwords in hex instead of base64,
15455 to make it easier to write controllers.
15458 Changes in version 0.1.0.7-rc - 2005-05-17
15460 - Fix a bug in the OS X package installer that prevented it from
15461 installing on Tiger.
15462 - Fix a script bug in the OS X package installer that made it
15463 complain during installation.
15464 - Find libevent even if it's hiding in /usr/local/ and your
15465 CFLAGS and LDFLAGS don't tell you to look there.
15466 - Be able to link with libevent as a shared library (the default
15467 after 1.0d), even if it's hiding in /usr/local/lib and even
15468 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
15469 assuming you're running gcc. Otherwise fail and give a useful
15471 - Fix a bug in the RPM packager: set home directory for _tor to
15472 something more reasonable when first installing.
15473 - Free a minor amount of memory that is still reachable on exit.
15476 Changes in version 0.1.0.6-rc - 2005-05-14
15478 - Implement --disable-threads configure option. Disable threads on
15479 netbsd by default, because it appears to have no reentrant resolver
15481 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
15482 release (1.1) detects and disables kqueue if it's broken.
15483 - Append default exit policy before checking for implicit internal
15484 addresses. Now we don't log a bunch of complaints on startup
15485 when using the default exit policy.
15486 - Some people were putting "Address " in their torrc, and they had
15487 a buggy resolver that resolved " " to 0.0.0.0. Oops.
15488 - If DataDir is ~/.tor, and that expands to /.tor, then default to
15489 LOCALSTATEDIR/tor instead.
15490 - Fix fragmented-message bug in TorControl.py.
15491 - Resolve a minor bug which would prevent unreachable dirports
15492 from getting suppressed in the published descriptor.
15493 - When the controller gave us a new descriptor, we weren't resolving
15494 it immediately, so Tor would think its address was 0.0.0.0 until
15495 we fetched a new directory.
15496 - Fix an uppercase/lowercase case error in suppressing a bogus
15497 libevent warning on some Linuxes.
15500 - Begin scrubbing sensitive strings from logs by default. Turn off
15501 the config option SafeLogging if you need to do debugging.
15502 - Switch to a new buffer management algorithm, which tries to avoid
15503 reallocing and copying quite as much. In first tests it looks like
15504 it uses *more* memory on average, but less cpu.
15505 - First cut at support for "create-fast" cells. Clients can use
15506 these when extending to their first hop, since the TLS already
15507 provides forward secrecy and authentication. Not enabled on
15509 - When dirservers refuse a router descriptor, we now log its
15510 contactinfo, platform, and the poster's IP address.
15511 - Call tor_free_all instead of connections_free_all after forking, to
15512 save memory on systems that need to fork.
15513 - Whine at you if you're a server and you don't set your contactinfo.
15514 - Implement --verify-config command-line option to check if your torrc
15515 is valid without actually launching Tor.
15516 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
15517 rather than just rejecting it.
15520 Changes in version 0.1.0.5-rc - 2005-04-27
15522 - Stop trying to print a null pointer if an OR conn fails because
15523 we didn't like its cert.
15525 - Switch our internal buffers implementation to use a ring buffer,
15526 to hopefully improve performance for fast servers a lot.
15527 - Add HttpsProxyAuthenticator support (basic auth only), based
15528 on patch from Adam Langley.
15529 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
15530 the fast servers that have been joining lately.
15531 - Give hidden service accesses extra time on the first attempt,
15532 since 60 seconds is often only barely enough. This might improve
15534 - Improve performance for dirservers: stop re-parsing the whole
15535 directory every time you regenerate it.
15536 - Add more debugging info to help us find the weird dns freebsd
15537 pthreads bug; cleaner debug messages to help track future issues.
15540 Changes in version 0.0.9.9 - 2005-04-23
15541 o Bugfixes on 0.0.9.x:
15542 - If unofficial Tor clients connect and send weird TLS certs, our
15543 Tor server triggers an assert. This release contains a minimal
15544 backport from the broader fix that we put into 0.1.0.4-rc.
15547 Changes in version 0.1.0.4-rc - 2005-04-23
15549 - If unofficial Tor clients connect and send weird TLS certs, our
15550 Tor server triggers an assert. Stop asserting, and start handling
15551 TLS errors better in other situations too.
15552 - When the controller asks us to tell it about all the debug-level
15553 logs, it turns out we were generating debug-level logs while
15554 telling it about them, which turns into a bad loop. Now keep
15555 track of whether you're sending a debug log to the controller,
15556 and don't log when you are.
15557 - Fix the "postdescriptor" feature of the controller interface: on
15558 non-complete success, only say "done" once.
15560 - Clients are now willing to load balance over up to 2mB, not 1mB,
15561 of advertised bandwidth capacity.
15562 - Add a NoPublish config option, so you can be a server (e.g. for
15563 testing running Tor servers in other Tor networks) without
15564 publishing your descriptor to the primary dirservers.
15567 Changes in version 0.1.0.3-rc - 2005-04-08
15568 o Improvements on 0.1.0.2-rc:
15569 - Client now retries when streams end early for 'hibernating' or
15570 'resource limit' reasons, rather than failing them.
15571 - More automated handling for dirserver operators:
15572 - Automatically approve nodes running 0.1.0.2-rc or later,
15573 now that the the reachability detection stuff is working.
15574 - Now we allow two unverified servers with the same nickname
15575 but different keys. But if a nickname is verified, only that
15576 nickname+key are allowed.
15577 - If you're an authdirserver connecting to an address:port,
15578 and it's not the OR you were expecting, forget about that
15579 descriptor. If he *was* the one you were expecting, then forget
15580 about all other descriptors for that address:port.
15581 - Allow servers to publish descriptors from 12 hours in the future.
15582 Corollary: only whine about clock skew from the dirserver if
15583 he's a trusted dirserver (since now even verified servers could
15584 have quite wrong clocks).
15585 - Adjust maximum skew and age for rendezvous descriptors: let skew
15586 be 48 hours rather than 90 minutes.
15587 - Efficiency improvements:
15588 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
15589 it much faster to look up a circuit for each relay cell.
15590 - Remove most calls to assert_all_pending_dns_resolves_ok(),
15591 since they're eating our cpu on exit nodes.
15592 - Stop wasting time doing a case insensitive comparison for every
15593 dns name every time we do any lookup. Canonicalize the names to
15594 lowercase and be done with it.
15595 - Start sending 'truncated' cells back rather than destroy cells,
15596 if the circuit closes in front of you. This means we won't have
15597 to abandon partially built circuits.
15598 - Only warn once per nickname from add_nickname_list_to_smartlist
15599 per failure, so an entrynode or exitnode choice that's down won't
15601 - Put a note in the torrc about abuse potential with the default
15603 - Revise control spec and implementation to allow all log messages to
15604 be sent to controller with their severities intact (suggested by
15605 Matt Edman). Update TorControl to handle new log event types.
15606 - Provide better explanation messages when controller's POSTDESCRIPTOR
15608 - Stop putting nodename in the Platform string in server descriptors.
15609 It doesn't actually help, and it is confusing/upsetting some people.
15611 o Bugfixes on 0.1.0.2-rc:
15612 - We were printing the host mask wrong in exit policies in server
15613 descriptors. This isn't a critical bug though, since we were still
15614 obeying the exit policy internally.
15615 - Fix Tor when compiled with libevent but without pthreads: move
15616 connection_unregister() from _connection_free() to
15618 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
15619 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
15620 when we look through the connection array, we'll find any of the
15621 cpu/dnsworkers. This is no good.
15623 o Bugfixes on 0.0.9.8:
15624 - Fix possible bug on threading platforms (e.g. win32) which was
15625 leaking a file descriptor whenever a cpuworker or dnsworker died.
15626 - When using preferred entry or exit nodes, ignore whether the
15627 circuit wants uptime or capacity. They asked for the nodes, they
15629 - chdir() to your datadirectory at the *end* of the daemonize process,
15630 not the beginning. This was a problem because the first time you
15631 run tor, if your datadir isn't there, and you have runasdaemon set
15632 to 1, it will try to chdir to it before it tries to create it. Oops.
15633 - Handle changed router status correctly when dirserver reloads
15634 fingerprint file. We used to be dropping all unverified descriptors
15635 right then. The bug was hidden because we would immediately
15636 fetch a directory from another dirserver, which would include the
15637 descriptors we just dropped.
15638 - When we're connecting to an OR and he's got a different nickname/key
15639 than we were expecting, only complain loudly if we're an OP or a
15640 dirserver. Complaining loudly to the OR admins just confuses them.
15641 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
15642 artificially capped at 500kB.
15645 Changes in version 0.0.9.8 - 2005-04-07
15646 o Bugfixes on 0.0.9.x:
15647 - We have a bug that I haven't found yet. Sometimes, very rarely,
15648 cpuworkers get stuck in the 'busy' state, even though the cpuworker
15649 thinks of itself as idle. This meant that no new circuits ever got
15650 established. Here's a workaround to kill any cpuworker that's been
15651 busy for more than 100 seconds.
15654 Changes in version 0.1.0.2-rc - 2005-04-01
15655 o Bugfixes on 0.1.0.1-rc:
15656 - Fixes on reachability detection:
15657 - Don't check for reachability while hibernating.
15658 - If ORPort is reachable but DirPort isn't, still publish the
15659 descriptor, but zero out DirPort until it's found reachable.
15660 - When building testing circs for ORPort testing, use only
15661 high-bandwidth nodes, so fewer circuits fail.
15662 - Complain about unreachable ORPort separately from unreachable
15663 DirPort, so the user knows what's going on.
15664 - Make sure we only conclude ORPort reachability if we didn't
15665 initiate the conn. Otherwise we could falsely conclude that
15666 we're reachable just because we connected to the guy earlier
15667 and he used that same pipe to extend to us.
15668 - Authdirservers shouldn't do ORPort reachability detection,
15669 since they're in clique mode, so it will be rare to find a
15670 server not already connected to them.
15671 - When building testing circuits, always pick middle hops running
15672 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
15673 bug. (This is a kludge; it will go away when 0.0.9.x becomes
15675 - When we decide we're reachable, actually publish our descriptor
15677 - Fix bug in redirectstream in the controller.
15678 - Fix the state descriptor strings so logs don't claim edge streams
15679 are in a different state than they actually are.
15680 - Use recent libevent features when possible (this only really affects
15681 win32 and osx right now, because the new libevent with these
15682 features hasn't been released yet). Add code to suppress spurious
15684 - Prevent possible segfault in connection_close_unattached_ap().
15685 - Fix newlines on torrc in win32.
15686 - Improve error msgs when tor-resolve fails.
15688 o Improvements on 0.0.9.x:
15689 - New experimental script tor/contrib/ExerciseServer.py (needs more
15690 work) that uses the controller interface to build circuits and
15691 fetch pages over them. This will help us bootstrap servers that
15692 have lots of capacity but haven't noticed it yet.
15693 - New experimental script tor/contrib/PathDemo.py (needs more work)
15694 that uses the controller interface to let you choose whole paths
15696 "<hostname>.<path,separated by dots>.<length of path>.path"
15697 - When we've connected to an OR and handshaked but didn't like
15698 the result, we were closing the conn without sending destroy
15699 cells back for pending circuits. Now send those destroys.
15702 Changes in version 0.0.9.7 - 2005-04-01
15703 o Bugfixes on 0.0.9.x:
15704 - Fix another race crash bug (thanks to Glenn Fink for reporting).
15705 - Compare identity to identity, not to nickname, when extending to
15706 a router not already in the directory. This was preventing us from
15707 extending to unknown routers. Oops.
15708 - Make sure to create OS X Tor user in <500 range, so we aren't
15709 creating actual system users.
15710 - Note where connection-that-hasn't-sent-end was marked, and fix
15711 a few really loud instances of this harmless bug (it's fixed more
15715 Changes in version 0.1.0.1-rc - 2005-03-28
15717 - Add reachability testing. Your Tor server will automatically try
15718 to see if its ORPort and DirPort are reachable from the outside,
15719 and it won't upload its descriptor until it decides they are.
15720 - Handle unavailable hidden services better. Handle slow or busy
15721 hidden services better.
15722 - Add support for CONNECTing through https proxies, with "HttpsProxy"
15724 - New exit policy: accept most low-numbered ports, rather than
15725 rejecting most low-numbered ports.
15726 - More Tor controller support (still experimental). See
15727 http://tor.eff.org/doc/control-spec.txt for all the new features,
15728 including signals to emulate unix signals from any platform;
15729 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
15730 closestream; closecircuit; etc.
15731 - Make nt services work and start on startup on win32 (based on
15732 patch by Matt Edman).
15733 - Add a new AddressMap config directive to rewrite incoming socks
15734 addresses. This lets you, for example, declare an implicit
15735 required exit node for certain sites.
15736 - Add a new TrackHostExits config directive to trigger addressmaps
15737 for certain incoming socks addresses -- for sites that break when
15738 your exit keeps changing (based on patch by Mike Perry).
15739 - Redo the client-side dns cache so it's just an addressmap too.
15740 - Notice when our IP changes, and reset stats/uptime/reachability.
15741 - When an application is using socks5, give him the whole variety of
15742 potential socks5 responses (connect refused, host unreachable, etc),
15743 rather than just "success" or "failure".
15744 - A more sane version numbering system. See
15745 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
15746 - New contributed script "exitlist": a simple python script to
15747 parse directories and find Tor nodes that exit to listed
15749 - New contributed script "privoxy-tor-toggle" to toggle whether
15750 Privoxy uses Tor. Seems to be configured for Debian by default.
15751 - Report HTTP reasons to client when getting a response from directory
15752 servers -- so you can actually know what went wrong.
15753 - New config option MaxAdvertisedBandwidth which lets you advertise
15754 a low bandwidthrate (to not attract as many circuits) while still
15755 allowing a higher bandwidthrate in reality.
15757 o Robustness/stability fixes:
15758 - Make Tor use Niels Provos's libevent instead of its current
15759 poll-but-sometimes-select mess. This will let us use faster async
15760 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
15762 - pthread support now too. This was forced because when we forked,
15763 we ended up wasting a lot of duplicate ram over time. Also switch
15764 to foo_r versions of some library calls to allow reentry and
15766 - Better handling for heterogeneous / unreliable nodes:
15767 - Annotate circuits w/ whether they aim to contain high uptime nodes
15768 and/or high capacity nodes. When building circuits, choose
15770 - This means that every single node in an intro rend circuit,
15771 not just the last one, will have a minimum uptime.
15772 - New config option LongLivedPorts to indicate application streams
15773 that will want high uptime circuits.
15774 - Servers reset uptime when a dir fetch entirely fails. This
15775 hopefully reflects stability of the server's network connectivity.
15776 - If somebody starts his tor server in Jan 2004 and then fixes his
15777 clock, don't make his published uptime be a year.
15778 - Reset published uptime when you wake up from hibernation.
15779 - Introduce a notion of 'internal' circs, which are chosen without
15780 regard to the exit policy of the last hop. Intro and rendezvous
15781 circs must be internal circs, to avoid leaking information. Resolve
15782 and connect streams can use internal circs if they want.
15783 - New circuit pooling algorithm: make sure to have enough circs around
15784 to satisfy any predicted ports, and also make sure to have 2 internal
15785 circs around if we've required internal circs lately (and with high
15786 uptime if we've seen that lately too).
15787 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
15788 which describes how often we retry making new circuits if current
15789 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
15790 how long we're willing to make use of an already-dirty circuit.
15791 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
15792 circ as necessary, if there are any completed ones lying around
15793 when we try to launch one.
15794 - Make hidden services try to establish a rendezvous for 30 seconds,
15795 rather than for n (where n=3) attempts to build a circuit.
15796 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
15797 "ShutdownWaitLength".
15798 - Try to be more zealous about calling connection_edge_end when
15799 things go bad with edge conns in connection.c.
15800 - Revise tor-spec to add more/better stream end reasons.
15801 - Revise all calls to connection_edge_end to avoid sending "misc",
15802 and to take errno into account where possible.
15805 - Fix a race condition that can trigger an assert, when we have a
15806 pending create cell and an OR connection fails right then.
15807 - Fix several double-mark-for-close bugs, e.g. where we were finding
15808 a conn for a cell even if that conn is already marked for close.
15809 - Make sequence of log messages when starting on win32 with no config
15810 file more reasonable.
15811 - When choosing an exit node for a new non-internal circ, don't take
15812 into account whether it'll be useful for any pending x.onion
15813 addresses -- it won't.
15814 - Turn addr_policy_compare from a tristate to a quadstate; this should
15815 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
15816 for google.com" problem.
15817 - Make "platform" string in descriptor more accurate for Win32 servers,
15818 so it's not just "unknown platform".
15819 - Fix an edge case in parsing config options (thanks weasel).
15820 If they say "--" on the commandline, it's not an option.
15821 - Reject odd-looking addresses at the client (e.g. addresses that
15822 contain a colon), rather than having the server drop them because
15824 - tor-resolve requests were ignoring .exit if there was a working circuit
15825 they could use instead.
15826 - REUSEADDR on normal platforms means you can rebind to the port
15827 right after somebody else has let it go. But REUSEADDR on win32
15828 means to let you bind to the port _even when somebody else
15829 already has it bound_! So, don't do that on Win32.
15830 - Change version parsing logic: a version is "obsolete" if it is not
15831 recommended and (1) there is a newer recommended version in the
15832 same series, or (2) there are no recommended versions in the same
15833 series, but there are some recommended versions in a newer series.
15834 A version is "new" if it is newer than any recommended version in
15836 - Stop most cases of hanging up on a socks connection without sending
15840 - Require BandwidthRate to be at least 20kB/s for servers.
15841 - When a dirserver causes you to give a warn, mention which dirserver
15843 - New config option DirAllowPrivateAddresses for authdirservers.
15844 Now by default they refuse router descriptors that have non-IP or
15845 private-IP addresses.
15846 - Stop publishing socksport in the directory, since it's not
15847 actually meant to be public. For compatibility, publish a 0 there
15849 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
15850 smart" value, that is low for servers and high for clients.
15851 - If our clock jumps forward by 100 seconds or more, assume something
15852 has gone wrong with our network and abandon all not-yet-used circs.
15853 - Warn when exit policy implicitly allows local addresses.
15854 - If we get an incredibly skewed timestamp from a dirserver mirror
15855 that isn't a verified OR, don't warn -- it's probably him that's
15857 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
15858 cookies to disk and doesn't log each web request to disk. (Thanks
15859 to Brett Carrington for pointing this out.)
15860 - When a client asks us for a dir mirror and we don't have one,
15861 launch an attempt to get a fresh one.
15862 - If we're hibernating and we get a SIGINT, exit immediately.
15863 - Add --with-dmalloc ./configure option, to track memory leaks.
15864 - And try to free all memory on closing, so we can detect what
15866 - Cache local dns resolves correctly even when they're .exit
15868 - Give a better warning when some other server advertises an
15869 ORPort that is actually an apache running ssl.
15870 - Add "opt hibernating 1" to server descriptor to make it clearer
15871 whether the server is hibernating.
15874 Changes in version 0.0.9.6 - 2005-03-24
15875 o Bugfixes on 0.0.9.x (crashes and asserts):
15876 - Add new end stream reasons to maintainance branch. Fix bug where
15877 reason (8) could trigger an assert. Prevent bug from recurring.
15878 - Apparently win32 stat wants paths to not end with a slash.
15879 - Fix assert triggers in assert_cpath_layer_ok(), where we were
15880 blowing away the circuit that conn->cpath_layer points to, then
15881 checking to see if the circ is well-formed. Backport check to make
15882 sure we dont use the cpath on a closed connection.
15883 - Prevent circuit_resume_edge_reading_helper() from trying to package
15884 inbufs for marked-for-close streams.
15885 - Don't crash on hup if your options->address has become unresolvable.
15886 - Some systems (like OS X) sometimes accept() a connection and tell
15887 you the remote host is 0.0.0.0:0. If this happens, due to some
15888 other mis-features, we get confused; so refuse the conn for now.
15890 o Bugfixes on 0.0.9.x (other):
15891 - Fix harmless but scary "Unrecognized content encoding" warn message.
15892 - Add new stream error reason: TORPROTOCOL reason means "you are not
15893 speaking a version of Tor I understand; say bye-bye to your stream."
15894 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
15895 into the future, now that we are more tolerant of skew. This
15896 resolves a bug where a Tor server would refuse to cache a directory
15897 because all the directories it gets are too far in the future;
15898 yet the Tor server never logs any complaints about clock skew.
15899 - Mac packaging magic: make man pages useable, and do not overwrite
15900 existing torrc files.
15901 - Make OS X log happily to /var/log/tor/tor.log
15904 Changes in version 0.0.9.5 - 2005-02-22
15905 o Bugfixes on 0.0.9.x:
15906 - Fix an assert race at exit nodes when resolve requests fail.
15907 - Stop picking unverified dir mirrors--it only leads to misery.
15908 - Patch from Matt Edman to make NT services work better. Service
15909 support is still not compiled into the executable by default.
15910 - Patch from Dmitri Bely so the Tor service runs better under
15911 the win32 SYSTEM account.
15912 - Make tor-resolve actually work (?) on Win32.
15913 - Fix a sign bug when getrlimit claims to have 4+ billion
15914 file descriptors available.
15915 - Stop refusing to start when bandwidthburst == bandwidthrate.
15916 - When create cells have been on the onion queue more than five
15917 seconds, just send back a destroy and take them off the list.
15920 Changes in version 0.0.9.4 - 2005-02-03
15921 o Bugfixes on 0.0.9:
15922 - Fix an assert bug that took down most of our servers: when
15923 a server claims to have 1 GB of bandwidthburst, don't
15925 - Don't crash as badly if we have spawned the max allowed number
15926 of dnsworkers, or we're out of file descriptors.
15927 - Block more file-sharing ports in the default exit policy.
15928 - MaxConn is now automatically set to the hard limit of max
15929 file descriptors we're allowed (ulimit -n), minus a few for
15931 - Give a clearer message when servers need to raise their
15932 ulimit -n when they start running out of file descriptors.
15933 - SGI Compatibility patches from Jan Schaumann.
15934 - Tolerate a corrupt cached directory better.
15935 - When a dirserver hasn't approved your server, list which one.
15936 - Go into soft hibernation after 95% of the bandwidth is used,
15937 not 99%. This is especially important for daily hibernators who
15938 have a small accounting max. Hopefully it will result in fewer
15939 cut connections when the hard hibernation starts.
15940 - Load-balance better when using servers that claim more than
15941 800kB/s of capacity.
15942 - Make NT services work (experimental, only used if compiled in).
15945 Changes in version 0.0.9.3 - 2005-01-21
15946 o Bugfixes on 0.0.9:
15947 - Backport the cpu use fixes from main branch, so busy servers won't
15948 need as much processor time.
15949 - Work better when we go offline and then come back, or when we
15950 run Tor at boot before the network is up. We do this by
15951 optimistically trying to fetch a new directory whenever an
15952 application request comes in and we think we're offline -- the
15953 human is hopefully a good measure of when the network is back.
15954 - Backport some minimal hidserv bugfixes: keep rend circuits open as
15955 long as you keep using them; actually publish hidserv descriptors
15956 shortly after they change, rather than waiting 20-40 minutes.
15957 - Enable Mac startup script by default.
15958 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
15959 - When you update AllowUnverifiedNodes or FirewallPorts via the
15960 controller's setconf feature, we were always appending, never
15962 - When you update HiddenServiceDir via setconf, it was screwing up
15963 the order of reading the lines, making it fail.
15964 - Do not rewrite a cached directory back to the cache; otherwise we
15965 will think it is recent and not fetch a newer one on startup.
15966 - Workaround for webservers that lie about Content-Encoding: Tor
15967 now tries to autodetect compressed directories and compression
15968 itself. This lets us Proxypass dir fetches through apache.
15971 Changes in version 0.0.9.2 - 2005-01-04
15972 o Bugfixes on 0.0.9 (crashes and asserts):
15973 - Fix an assert on startup when the disk is full and you're logging
15975 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
15976 style address, then we'd crash.
15977 - Fix an assert trigger when the running-routers string we get from
15978 a dirserver is broken.
15979 - Make worker threads start and run on win32. Now win32 servers
15981 - Bandaid (not actually fix, but now it doesn't crash) an assert
15982 where the dns worker dies mysteriously and the main Tor process
15983 doesn't remember anything about the address it was resolving.
15985 o Bugfixes on 0.0.9 (Win32):
15986 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
15987 name out of the warning/assert messages.
15988 - Fix a superficial "unhandled error on read" bug on win32.
15989 - The win32 installer no longer requires a click-through for our
15990 license, since our Free Software license grants rights but does not
15992 - Win32: When connecting to a dirserver fails, try another one
15993 immediately. (This was already working for non-win32 Tors.)
15994 - Stop trying to parse $HOME on win32 when hunting for default
15996 - Make tor-resolve.c work on win32 by calling network_init().
15998 o Bugfixes on 0.0.9 (other):
15999 - Make 0.0.9.x build on Solaris again.
16000 - Due to a fencepost error, we were blowing away the \n when reporting
16001 confvalue items in the controller. So asking for multiple config
16002 values at once couldn't work.
16003 - When listing circuits that are pending on an opening OR connection,
16004 if we're an OR we were listing circuits that *end* at us as
16005 being pending on every listener, dns/cpu worker, etc. Stop that.
16006 - Dirservers were failing to create 'running-routers' or 'directory'
16007 strings if we had more than some threshold of routers. Fix them so
16008 they can handle any number of routers.
16009 - Fix a superficial "Duplicate mark for close" bug.
16010 - Stop checking for clock skew for OR connections, even for servers.
16011 - Fix a fencepost error that was chopping off the last letter of any
16012 nickname that is the maximum allowed nickname length.
16013 - Update URLs in log messages so they point to the new website.
16014 - Fix a potential problem in mangling server private keys while
16015 writing to disk (not triggered yet, as far as we know).
16016 - Include the licenses for other free software we include in Tor,
16017 now that we're shipping binary distributions more regularly.
16020 Changes in version 0.0.9.1 - 2004-12-15
16021 o Bugfixes on 0.0.9:
16022 - Make hibernation actually work.
16023 - Make HashedControlPassword config option work.
16024 - When we're reporting event circuit status to a controller,
16025 don't use the stream status code.
16028 Changes in version 0.0.9 - 2004-12-12
16030 - Clean up manpage and torrc.sample file.
16031 - Clean up severities and text of log warnings.
16033 - Make servers trigger an assert when they enter hibernation.
16036 Changes in version 0.0.9rc7 - 2004-12-08
16037 o Bugfixes on 0.0.9rc:
16038 - Fix a stack-trashing crash when an exit node begins hibernating.
16039 - Avoid looking at unallocated memory while considering which
16040 ports we need to build circuits to cover.
16041 - Stop a sigpipe: when an 'end' cell races with eof from the app,
16042 we shouldn't hold-open-until-flush if the eof arrived first.
16043 - Fix a bug with init_cookie_authentication() in the controller.
16044 - When recommending new-format log lines, if the upper bound is
16045 LOG_ERR, leave it implicit.
16047 o Bugfixes on 0.0.8.1:
16048 - Fix a whole slew of memory leaks.
16049 - Fix isspace() and friends so they still make Solaris happy
16050 but also so they don't trigger asserts on win32.
16051 - Fix parse_iso_time on platforms without strptime (eg win32).
16052 - win32: tolerate extra "readable" events better.
16053 - win32: when being multithreaded, leave parent fdarray open.
16054 - Make unit tests work on win32.
16057 Changes in version 0.0.9rc6 - 2004-12-06
16058 o Bugfixes on 0.0.9pre:
16059 - Clean up some more integer underflow opportunities (not exploitable
16061 - While hibernating, hup should not regrow our listeners.
16062 - Send an end to the streams we close when we hibernate, rather
16063 than just chopping them off.
16064 - React to eof immediately on non-open edge connections.
16066 o Bugfixes on 0.0.8.1:
16067 - Calculate timeout for waiting for a connected cell from the time
16068 we sent the begin cell, not from the time the stream started. If
16069 it took a long time to establish the circuit, we would time out
16070 right after sending the begin cell.
16071 - Fix router_compare_addr_to_addr_policy: it was not treating a port
16072 of * as always matching, so we were picking reject *:* nodes as
16073 exit nodes too. Oops.
16076 - New circuit building strategy: keep a list of ports that we've
16077 used in the past 6 hours, and always try to have 2 circuits open
16078 or on the way that will handle each such port. Seed us with port
16079 80 so web users won't complain that Tor is "slow to start up".
16080 - Make kill -USR1 dump more useful stats about circuits.
16081 - When warning about retrying or giving up, print the address, so
16082 the user knows which one it's talking about.
16083 - If you haven't used a clean circuit in an hour, throw it away,
16084 just to be on the safe side. (This means after 6 hours a totally
16085 unused Tor client will have no circuits open.)
16088 Changes in version 0.0.9rc5 - 2004-12-01
16089 o Bugfixes on 0.0.8.1:
16090 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
16091 - Let resolve conns retry/expire also, rather than sticking around
16093 - If we are using select, make sure we stay within FD_SETSIZE.
16095 o Bugfixes on 0.0.9pre:
16096 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
16097 but doesn't seem to be currently; thanks to Ilja van Sprundel for
16099 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
16100 instead. Impose minima and maxima for all *Period options; impose
16101 even tighter maxima for fetching if we are a caching dirserver.
16102 Clip rather than rejecting.
16103 - Fetch cached running-routers from servers that serve it (that is,
16104 authdirservers and servers running 0.0.9rc5-cvs or later.)
16107 - Accept *:706 (silc) in default exit policy.
16108 - Implement new versioning format for post 0.1.
16109 - Support "foo.nickname.exit" addresses, to let Alice request the
16110 address "foo" as viewed by exit node "nickname". Based on a patch
16112 - Make tor --version --version dump the cvs Id of every file.
16115 Changes in version 0.0.9rc4 - 2004-11-28
16116 o Bugfixes on 0.0.8.1:
16117 - Make windows sockets actually non-blocking (oops), and handle
16118 win32 socket errors better.
16120 o Bugfixes on 0.0.9rc1:
16121 - Actually catch the -USR2 signal.
16124 Changes in version 0.0.9rc3 - 2004-11-25
16125 o Bugfixes on 0.0.8.1:
16126 - Flush the log file descriptor after we print "Tor opening log file",
16127 so we don't see those messages days later.
16129 o Bugfixes on 0.0.9rc1:
16130 - Make tor-resolve work again.
16131 - Avoid infinite loop in tor-resolve if tor hangs up on it.
16132 - Fix an assert trigger for clients/servers handling resolves.
16135 Changes in version 0.0.9rc2 - 2004-11-24
16136 o Bugfixes on 0.0.9rc1:
16137 - I broke socks5 support while fixing the eof bug.
16138 - Allow unitless bandwidths and intervals; they default to bytes
16140 - New servers don't start out hibernating; they are active until
16141 they run out of bytes, so they have a better estimate of how
16142 long it takes, and so their operators can know they're working.
16145 Changes in version 0.0.9rc1 - 2004-11-23
16146 o Bugfixes on 0.0.8.1:
16147 - Finally fix a bug that's been plaguing us for a year:
16148 With high load, circuit package window was reaching 0. Whenever
16149 we got a circuit-level sendme, we were reading a lot on each
16150 socket, but only writing out a bit. So we would eventually reach
16151 eof. This would be noticed and acted on even when there were still
16152 bytes sitting in the inbuf.
16153 - When poll() is interrupted, we shouldn't believe the revents values.
16155 o Bugfixes on 0.0.9pre6:
16156 - Fix hibernate bug that caused pre6 to be broken.
16157 - Don't keep rephist info for routers that haven't had activity for
16158 24 hours. (This matters now that clients have keys, since we track
16160 - Never call close_temp_logs while validating log options.
16161 - Fix backslash-escaping on tor.sh.in and torctl.in.
16164 - Implement weekly/monthly/daily accounting: now you specify your
16165 hibernation properties by
16166 AccountingMax N bytes|KB|MB|GB|TB
16167 AccountingStart day|week|month [day] HH:MM
16168 Defaults to "month 1 0:00".
16169 - Let bandwidth and interval config options be specified as 5 bytes,
16170 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
16171 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
16172 get back to normal.)
16173 - If your requested entry or exit node has advertised bandwidth 0,
16175 - Be more greedy about filling up relay cells -- we try reading again
16176 once we've processed the stuff we read, in case enough has arrived
16177 to fill the last cell completely.
16178 - Apply NT service patch from Osamu Fujino. Still needs more work.
16181 Changes in version 0.0.9pre6 - 2004-11-15
16182 o Bugfixes on 0.0.8.1:
16183 - Fix assert failure on malformed socks4a requests.
16184 - Use identity comparison, not nickname comparison, to choose which
16185 half of circuit-ID-space each side gets to use. This is needed
16186 because sometimes we think of a router as a nickname, and sometimes
16187 as a hex ID, and we can't predict what the other side will do.
16188 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
16189 write() call will fail and we handle it there.
16190 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
16191 and smartlist_len, which are two major profiling offenders.
16193 o Bugfixes on 0.0.9pre5:
16194 - Fix a bug in read_all that was corrupting config files on windows.
16195 - When we're raising the max number of open file descriptors to
16196 'unlimited', don't log that we just raised it to '-1'.
16197 - Include event code with events, as required by control-spec.txt.
16198 - Don't give a fingerprint when clients do --list-fingerprint:
16199 it's misleading, because it will never be the same again.
16200 - Stop using strlcpy in tor_strndup, since it was slowing us
16202 - Remove warn on startup about missing cached-directory file.
16203 - Make kill -USR1 work again.
16204 - Hibernate if we start tor during the "wait for wakeup-time" phase
16205 of an accounting interval. Log our hibernation plans better.
16206 - Authoritative dirservers now also cache their directory, so they
16207 have it on start-up.
16210 - Fetch running-routers; cache running-routers; compress
16211 running-routers; serve compressed running-routers.z
16212 - Add NSI installer script contributed by J Doe.
16213 - Commit VC6 and VC7 workspace/project files.
16214 - Commit a tor.spec for making RPM files, with help from jbash.
16215 - Add contrib/torctl.in contributed by Glenn Fink.
16216 - Implement the control-spec's SAVECONF command, to write your
16217 configuration to torrc.
16218 - Get cookie authentication for the controller closer to working.
16219 - Include control-spec.txt in the tarball.
16220 - When set_conf changes our server descriptor, upload a new copy.
16221 But don't upload it too often if there are frequent changes.
16222 - Document authentication config in man page, and document signals
16224 - Clean up confusing parts of man page and torrc.sample.
16225 - Make expand_filename handle ~ and ~username.
16226 - Use autoconf to enable largefile support where necessary. Use
16227 ftello where available, since ftell can fail at 2GB.
16228 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
16229 log more informatively.
16230 - Give a slightly more useful output for "tor -h".
16231 - Refuse application socks connections to port 0.
16232 - Check clock skew for verified servers, but allow unverified
16233 servers and clients to have any clock skew.
16234 - Break DirFetchPostPeriod into:
16235 - DirFetchPeriod for fetching full directory,
16236 - StatusFetchPeriod for fetching running-routers,
16237 - DirPostPeriod for posting server descriptor,
16238 - RendPostPeriod for posting hidden service descriptors.
16239 - Make sure the hidden service descriptors are at a random offset
16240 from each other, to hinder linkability.
16243 Changes in version 0.0.9pre5 - 2004-11-09
16244 o Bugfixes on 0.0.9pre4:
16245 - Fix a seg fault in unit tests (doesn't affect main program).
16246 - Fix an assert bug where a hidden service provider would fail if
16247 the first hop of his rendezvous circuit was down.
16248 - Hidden service operators now correctly handle version 1 style
16249 INTRODUCE1 cells (nobody generates them still, so not a critical
16251 - If do_hup fails, actually notice.
16252 - Handle more errnos from accept() without closing the listener.
16253 Some OpenBSD machines were closing their listeners because
16254 they ran out of file descriptors.
16255 - Send resolve cells to exit routers that are running a new
16256 enough version of the resolve code to work right.
16257 - Better handling of winsock includes on non-MSV win32 compilers.
16258 - Some people had wrapped their tor client/server in a script
16259 that would restart it whenever it died. This did not play well
16260 with our "shut down if your version is obsolete" code. Now people
16261 don't fetch a new directory if their local cached version is
16263 - Make our autogen.sh work on ksh as well as bash.
16266 - Hibernation: New config option "AccountingMaxKB" lets you
16267 set how many KBytes per month you want to allow your server to
16268 consume. Rather than spreading those bytes out evenly over the
16269 month, we instead hibernate for some of the month and pop up
16270 at a deterministic time, work until the bytes are consumed, then
16271 hibernate again. Config option "MonthlyAccountingStart" lets you
16272 specify which day of the month your billing cycle starts on.
16273 - Control interface: a separate program can now talk to your
16274 client/server over a socket, and get/set config options, receive
16275 notifications of circuits and streams starting/finishing/dying,
16276 bandwidth used, etc. The next step is to get some GUIs working.
16277 Let us know if you want to help out. See doc/control-spec.txt .
16278 - Ship a contrib/tor-control.py as an example script to interact
16279 with the control port.
16280 - "tor --hash-password zzyxz" will output a salted password for
16281 use in authenticating to the control interface.
16282 - New log format in config:
16283 "Log minsev[-maxsev] stdout|stderr|syslog" or
16284 "Log minsev[-maxsev] file /var/foo"
16287 - DirPolicy config option, to let people reject incoming addresses
16288 from their dirserver.
16289 - "tor --list-fingerprint" will list your identity key fingerprint
16291 - Add "pass" target for RedirectExit, to make it easier to break
16292 out of a sequence of RedirectExit rules.
16293 - Clients now generate a TLS cert too, in preparation for having
16294 them act more like real nodes.
16295 - Ship src/win32/ in the tarball, so people can use it to build.
16296 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
16298 - New "router-status" line in directory, to better bind each verified
16299 nickname to its identity key.
16300 - Deprecate unofficial config option abbreviations, and abbreviations
16301 not on the command line.
16302 - Add a pure-C tor-resolve implementation.
16303 - Use getrlimit and friends to ensure we can reach MaxConn (currently
16304 1024) file descriptors.
16306 o Code security improvements, inspired by Ilja:
16307 - Replace sprintf with snprintf. (I think they were all safe, but
16309 - Replace strcpy/strncpy with strlcpy in more places.
16310 - Avoid strcat; use snprintf or strlcat instead.
16311 - snprintf wrapper with consistent (though not C99) overflow behavior.
16314 Changes in version 0.0.9pre4 - 2004-10-17
16315 o Bugfixes on 0.0.9pre3:
16316 - If the server doesn't specify an exit policy, use the real default
16317 exit policy, not reject *:*.
16318 - Ignore fascistfirewall when uploading/downloading hidden service
16319 descriptors, since we go through Tor for those; and when using
16320 an HttpProxy, since we assume it can reach them all.
16321 - When looking for an authoritative dirserver, use only the ones
16322 configured at boot. Don't bother looking in the directory.
16323 - The rest of the fix for get_default_conf_file() on older win32.
16324 - Make 'Routerfile' config option obsolete.
16327 - New 'MyFamily nick1,...' config option for a server to
16328 specify other servers that shouldn't be used in the same circuit
16329 with it. Only believed if nick1 also specifies us.
16330 - New 'NodeFamily nick1,nick2,...' config option for a client to
16331 specify nodes that it doesn't want to use in the same circuit.
16332 - New 'Redirectexit pattern address:port' config option for a
16333 server to redirect exit connections, e.g. to a local squid.
16336 Changes in version 0.0.9pre3 - 2004-10-13
16337 o Bugfixes on 0.0.8.1:
16338 - Better torrc example lines for dirbindaddress and orbindaddress.
16339 - Improved bounds checking on parsed ints (e.g. config options and
16340 the ones we find in directories.)
16341 - Better handling of size_t vs int, so we're more robust on 64
16343 - Fix the rest of the bug where a newly started OR would appear
16344 as unverified even after we've added his fingerprint and hupped
16346 - Fix a bug from 0.0.7: when read() failed on a stream, we would
16347 close it without sending back an end. So 'connection refused'
16348 would simply be ignored and the user would get no response.
16350 o Bugfixes on 0.0.9pre2:
16351 - Serving the cached-on-disk directory to people is bad. We now
16352 provide no directory until we've fetched a fresh one.
16353 - Workaround for bug on windows where cached-directories get crlf
16355 - Make get_default_conf_file() work on older windows too.
16356 - If we write a *:* exit policy line in the descriptor, don't write
16357 any more exit policy lines.
16360 - Use only 0.0.9pre1 and later servers for resolve cells.
16361 - Make the dirservers file obsolete.
16362 - Include a dir-signing-key token in directories to tell the
16363 parsing entity which key is being used to sign.
16364 - Remove the built-in bulky default dirservers string.
16365 - New config option "Dirserver %s:%d [fingerprint]", which can be
16366 repeated as many times as needed. If no dirservers specified,
16367 default to moria1,moria2,tor26.
16368 - Make moria2 advertise a dirport of 80, so people behind firewalls
16369 will be able to get a directory.
16370 - Http proxy support
16371 - Dirservers translate requests for http://%s:%d/x to /x
16372 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
16373 be routed through this host.
16374 - Clients ask for /tor/x rather than /x for new enough dirservers.
16375 This way we can one day coexist peacefully with apache.
16376 - Clients specify a "Host: %s%d" http header, to be compatible
16377 with more proxies, and so running squid on an exit node can work.
16380 Changes in version 0.0.8.1 - 2004-10-13
16382 - Fix a seg fault that can be triggered remotely for Tor
16383 clients/servers with an open dirport.
16384 - Fix a rare assert trigger, where routerinfos for entries in
16385 our cpath would expire while we're building the path.
16386 - Fix a bug in OutboundBindAddress so it (hopefully) works.
16387 - Fix a rare seg fault for people running hidden services on
16388 intermittent connections.
16389 - Fix a bug in parsing opt keywords with objects.
16390 - Fix a stale pointer assert bug when a stream detaches and
16392 - Fix a string format vulnerability (probably not exploitable)
16393 in reporting stats locally.
16394 - Fix an assert trigger: sometimes launching circuits can fail
16395 immediately, e.g. because too many circuits have failed recently.
16396 - Fix a compile warning on 64 bit platforms.
16399 Changes in version 0.0.9pre2 - 2004-10-03
16401 - Make fetching a cached directory work for 64-bit platforms too.
16402 - Make zlib.h a required header, not an optional header.
16405 Changes in version 0.0.9pre1 - 2004-10-01
16407 - Stop using separate defaults for no-config-file and
16408 empty-config-file. Now you have to explicitly turn off SocksPort,
16409 if you don't want it open.
16410 - Fix a bug in OutboundBindAddress so it (hopefully) works.
16411 - Improve man page to mention more of the 0.0.8 features.
16412 - Fix a rare seg fault for people running hidden services on
16413 intermittent connections.
16414 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
16416 - Fix more dns related bugs: send back resolve_failed and end cells
16417 more reliably when the resolve fails, rather than closing the
16418 circuit and then trying to send the cell. Also attach dummy resolve
16419 connections to a circuit *before* calling dns_resolve(), to fix
16420 a bug where cached answers would never be sent in RESOLVED cells.
16421 - When we run out of disk space, or other log writing error, don't
16422 crash. Just stop logging to that log and continue.
16423 - We were starting to daemonize before we opened our logs, so if
16424 there were any problems opening logs, we would complain to stderr,
16425 which wouldn't work, and then mysteriously exit.
16426 - Fix a rare bug where sometimes a verified OR would connect to us
16427 before he'd uploaded his descriptor, which would cause us to
16428 assign conn->nickname as though he's unverified. Now we look through
16429 the fingerprint list to see if he's there.
16430 - Fix a rare assert trigger, where routerinfos for entries in
16431 our cpath would expire while we're building the path.
16434 - Clients can ask dirservers for /dir.z to get a compressed version
16435 of the directory. Only works for servers running 0.0.9, of course.
16436 - Make clients cache directories and use them to seed their router
16437 lists at startup. This means clients have a datadir again.
16438 - Configuration infrastructure support for warning on obsolete
16440 - Respond to content-encoding headers by trying to uncompress as
16442 - Reply with a deflated directory when a client asks for "dir.z".
16443 We could use allow-encodings instead, but allow-encodings isn't
16444 specified in HTTP 1.0.
16445 - Raise the max dns workers from 50 to 100.
16446 - Discourage people from setting their dirfetchpostperiod more often
16447 than once per minute.
16448 - Protect dirservers from overzealous descriptor uploading -- wait
16449 10 seconds after directory gets dirty, before regenerating.
16452 Changes in version 0.0.8 - 2004-08-25
16453 o Port it to SunOS 5.9 / Athena
16456 Changes in version 0.0.8rc2 - 2004-08-20
16457 o Make it compile on cygwin again.
16458 o When picking unverified routers, skip those with low uptime and/or
16459 low bandwidth, depending on what properties you care about.
16462 Changes in version 0.0.8rc1 - 2004-08-18
16463 o Changes from 0.0.7.3:
16465 - Fix assert triggers: if the other side returns an address 0.0.0.0,
16466 don't put it into the client dns cache.
16467 - If a begin failed due to exit policy, but we believe the IP address
16468 should have been allowed, switch that router to exitpolicy reject *:*
16469 until we get our next directory.
16471 - Clients choose nodes proportional to advertised bandwidth.
16472 - Avoid using nodes with low uptime as introduction points.
16473 - Handle servers with dynamic IP addresses: don't replace
16474 options->Address with the resolved one at startup, and
16475 detect our address right before we make a routerinfo each time.
16476 - 'FascistFirewall' option to pick dirservers and ORs on specific
16477 ports; plus 'FirewallPorts' config option to tell FascistFirewall
16478 which ports are open. (Defaults to 80,443)
16479 - Be more aggressive about trying to make circuits when the network
16480 has changed (e.g. when you unsuspend your laptop).
16481 - Check for time skew on http headers; report date in response to
16483 - If the entrynode config line has only one node, don't pick it as
16485 - Add strict{entry|exit}nodes config options. If set to 1, then
16486 we refuse to build circuits that don't include the specified entry
16488 - OutboundBindAddress config option, to bind to a specific
16489 IP address for outgoing connect()s.
16490 - End truncated log entries (e.g. directories) with "[truncated]".
16492 o Patches to 0.0.8preX:
16494 - Patches to compile and run on win32 again (maybe)?
16495 - Fix crash when looking for ~/.torrc with no $HOME set.
16496 - Fix a race bug in the unit tests.
16497 - Handle verified/unverified name collisions better when new
16498 routerinfo's arrive in a directory.
16499 - Sometimes routers were getting entered into the stats before
16500 we'd assigned their identity_digest. Oops.
16501 - Only pick and establish intro points after we've gotten a
16504 - AllowUnverifiedNodes config option to let circuits choose no-name
16505 routers in entry,middle,exit,introduction,rendezvous positions.
16506 Allow middle and rendezvous positions by default.
16507 - Add a man page for tor-resolve.
16510 Changes in version 0.0.7.3 - 2004-08-12
16511 o Stop dnsworkers from triggering an assert failure when you
16512 ask them to resolve the host "".
16515 Changes in version 0.0.8pre3 - 2004-08-09
16516 o Changes from 0.0.7.2:
16517 - Allow multiple ORs with same nickname in routerlist -- now when
16518 people give us one identity key for a nickname, then later
16519 another, we don't constantly complain until the first expires.
16520 - Remember used bandwidth (both in and out), and publish 15-minute
16521 snapshots for the past day into our descriptor.
16522 - You can now fetch $DIRURL/running-routers to get just the
16523 running-routers line, not the whole descriptor list. (But
16524 clients don't use this yet.)
16525 - When people mistakenly use Tor as an http proxy, point them
16526 at the tor-doc.html rather than the INSTALL.
16527 - Remove our mostly unused -- and broken -- hex_encode()
16528 function. Use base16_encode() instead. (Thanks to Timo Lindfors
16529 for pointing out this bug.)
16530 - Rotate onion keys every 12 hours, not every 2 hours, so we have
16531 fewer problems with people using the wrong key.
16532 - Change the default exit policy to reject the default edonkey,
16533 kazaa, gnutella ports.
16534 - Add replace_file() to util.[ch] to handle win32's rename().
16536 o Changes from 0.0.8preX:
16537 - Fix two bugs in saving onion keys to disk when rotating, so
16538 hopefully we'll get fewer people using old onion keys.
16539 - Fix an assert error that was making SocksPolicy not work.
16540 - Be willing to expire routers that have an open dirport -- it's
16541 just the authoritative dirservers we want to not forget.
16542 - Reject tor-resolve requests for .onion addresses early, so we
16543 don't build a whole rendezvous circuit and then fail.
16544 - When you're warning a server that he's unverified, don't cry
16545 wolf unpredictably.
16546 - Fix a race condition: don't try to extend onto a connection
16547 that's still handshaking.
16548 - For servers in clique mode, require the conn to be open before
16549 you'll choose it for your path.
16550 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
16551 end relay cell, etc.
16552 - Measure bandwidth capacity over the last 24 hours, not just 12
16553 - Bugfix: authoritative dirservers were making and signing a new
16554 directory for each client, rather than reusing the cached one.
16557 Changes in version 0.0.8pre2 - 2004-08-04
16558 o Changes from 0.0.7.2:
16560 - Check directory signature _before_ you decide whether you're
16561 you're running an obsolete version and should exit.
16562 - Check directory signature _before_ you parse the running-routers
16563 list to decide who's running or verified.
16564 - Bugfixes and features:
16565 - Check return value of fclose while writing to disk, so we don't
16566 end up with broken files when servers run out of disk space.
16567 - Log a warning if the user uses an unsafe socks variant, so people
16568 are more likely to learn about privoxy or socat.
16569 - Dirservers now include RFC1123-style dates in the HTTP headers,
16570 which one day we will use to better detect clock skew.
16572 o Changes from 0.0.8pre1:
16573 - Make it compile without warnings again on win32.
16574 - Log a warning if you're running an unverified server, to let you
16575 know you might want to get it verified.
16576 - Only pick a default nickname if you plan to be a server.
16579 Changes in version 0.0.8pre1 - 2004-07-23
16581 - Made our unit tests compile again on OpenBSD 3.5, and tor
16582 itself compile again on OpenBSD on a sparc64.
16583 - We were neglecting milliseconds when logging on win32, so
16584 everything appeared to happen at the beginning of each second.
16586 o Protocol changes:
16587 - 'Extend' relay cell payloads now include the digest of the
16588 intended next hop's identity key. Now we can verify that we're
16589 extending to the right router, and also extend to routers we
16590 hadn't heard of before.
16593 - Tor nodes can now act as relays (with an advertised ORPort)
16594 without being manually verified by the dirserver operators.
16595 - Uploaded descriptors of unverified routers are now accepted
16596 by the dirservers, and included in the directory.
16597 - Verified routers are listed by nickname in the running-routers
16598 list; unverified routers are listed as "$<fingerprint>".
16599 - We now use hash-of-identity-key in most places rather than
16600 nickname or addr:port, for improved security/flexibility.
16601 - To avoid Sybil attacks, paths still use only verified servers.
16602 But now we have a chance to play around with hybrid approaches.
16603 - Nodes track bandwidth usage to estimate capacity (not used yet).
16604 - ClientOnly option for nodes that never want to become servers.
16605 - Directory caching.
16606 - "AuthoritativeDir 1" option for the official dirservers.
16607 - Now other nodes (clients and servers) will cache the latest
16608 directory they've pulled down.
16609 - They can enable their DirPort to serve it to others.
16610 - Clients will pull down a directory from any node with an open
16611 DirPort, and check the signature/timestamp correctly.
16612 - Authoritative dirservers now fetch directories from other
16613 authdirservers, to stay better synced.
16614 - Running-routers list tells who's down also, along with noting
16615 if they're verified (listed by nickname) or unverified (listed
16617 - Allow dirservers to serve running-router list separately.
16618 This isn't used yet.
16619 - ORs connect-on-demand to other ORs
16620 - If you get an extend cell to an OR you're not connected to,
16621 connect, handshake, and forward the create cell.
16622 - The authoritative dirservers stay connected to everybody,
16623 and everybody stays connected to 0.0.7 servers, but otherwise
16624 clients/servers expire unused connections after 5 minutes.
16625 - When servers get a sigint, they delay 30 seconds (refusing new
16626 connections) then exit. A second sigint causes immediate exit.
16627 - File and name management:
16628 - Look for .torrc if no CONFDIR "torrc" is found.
16629 - If no datadir is defined, then choose, make, and secure ~/.tor
16631 - If torrc not found, exitpolicy reject *:*.
16632 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
16633 - If no nickname is defined, derive default from hostname.
16634 - Rename secret key files, e.g. identity.key -> secret_id_key,
16635 to discourage people from mailing their identity key to tor-ops.
16636 - Refuse to build a circuit before the directory has arrived --
16637 it won't work anyway, since you won't know the right onion keys
16639 - Try other dirservers immediately if the one you try is down. This
16640 should tolerate down dirservers better now.
16641 - Parse tor version numbers so we can do an is-newer-than check
16642 rather than an is-in-the-list check.
16643 - New socks command 'resolve', to let us shim gethostbyname()
16645 - A 'tor_resolve' script to access the socks resolve functionality.
16646 - A new socks-extensions.txt doc file to describe our
16647 interpretation and extensions to the socks protocols.
16648 - Add a ContactInfo option, which gets published in descriptor.
16649 - Publish OR uptime in descriptor (and thus in directory) too.
16650 - Write tor version at the top of each log file
16651 - New docs in the tarball:
16653 - Document that you should proxy your SSL traffic too.
16656 Changes in version 0.0.7.2 - 2004-07-07
16657 o A better fix for the 0.0.0.0 problem, that will hopefully
16658 eliminate the remaining related assertion failures.
16661 Changes in version 0.0.7.1 - 2004-07-04
16662 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
16663 since internally we use 0.0.0.0 to signify "not yet resolved".
16666 Changes in version 0.0.7 - 2004-06-07
16667 o Updated the man page to reflect the new features.
16670 Changes in version 0.0.7rc2 - 2004-06-06
16671 o Changes from 0.0.7rc1:
16672 - Make it build on Win32 again.
16673 o Changes from 0.0.6.2:
16674 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
16678 Changes in version 0.0.7rc1 - 2004-06-02
16680 - On sighup, we were adding another log without removing the first
16681 one. So log messages would get duplicated n times for n sighups.
16682 - Several cases of using a connection after we'd freed it. The
16683 problem was that connections that are pending resolve are in both
16684 the pending_resolve tree, and also the circuit's resolving_streams
16685 list. When you want to remove one, you must remove it from both.
16686 - Fix a double-mark-for-close where an end cell arrived for a
16687 resolving stream, and then the resolve failed.
16688 - Check directory signatures based on name of signer, not on whom
16689 we got the directory from. This will let us cache directories more
16692 - Crank up some of our constants to handle more users.
16695 Changes in version 0.0.7pre1 - 2004-06-02
16696 o Fixes for crashes and other obnoxious bugs:
16697 - Fix an epipe bug: sometimes when directory connections failed
16698 to connect, we would give them a chance to flush before closing
16700 - When we detached from a circuit because of resolvefailed, we
16701 would immediately try the same circuit twice more, and then
16702 give up on the resolve thinking we'd tried three different
16704 - Limit the number of intro circuits we'll attempt to build for a
16705 hidden service per 15-minute period.
16706 - Check recommended-software string *early*, before actually parsing
16707 the directory. Thus we can detect an obsolete version and exit,
16708 even if the new directory format doesn't parse.
16709 o Fixes for security bugs:
16710 - Remember which nodes are dirservers when you startup, and if a
16711 random OR enables his dirport, don't automatically assume he's
16712 a trusted dirserver.
16714 - Directory connections were asking the wrong poll socket to
16715 start writing, and not asking themselves to start writing.
16716 - When we detached from a circuit because we sent a begin but
16717 didn't get a connected, we would use it again the first time;
16718 but after that we would correctly switch to a different one.
16719 - Stop warning when the first onion decrypt attempt fails; they
16720 will sometimes legitimately fail now that we rotate keys.
16721 - Override unaligned-access-ok check when $host_cpu is ia64 or
16722 arm. Apparently they allow it but the kernel whines.
16723 - Dirservers try to reconnect periodically too, in case connections
16725 - Fix some memory leaks in directory servers.
16726 - Allow backslash in Win32 filenames.
16727 - Made Tor build complain-free on FreeBSD, hopefully without
16728 breaking other BSD builds. We'll see.
16730 - Doxygen markup on all functions and global variables.
16731 - Make directory functions update routerlist, not replace it. So
16732 now directory disagreements are not so critical a problem.
16733 - Remove the upper limit on number of descriptors in a dirserver's
16734 directory (not that we were anywhere close).
16735 - Allow multiple logfiles at different severity ranges.
16736 - Allow *BindAddress to specify ":port" rather than setting *Port
16737 separately. Allow multiple instances of each BindAddress config
16738 option, so you can bind to multiple interfaces if you want.
16739 - Allow multiple exit policy lines, which are processed in order.
16740 Now we don't need that huge line with all the commas in it.
16741 - Enable accept/reject policies on SOCKS connections, so you can bind
16742 to 0.0.0.0 but still control who can use your OP.
16745 Changes in version 0.0.6.2 - 2004-05-16
16746 o Our integrity-checking digest was checking only the most recent cell,
16747 not the previous cells like we'd thought.
16748 Thanks to Stefan Mark for finding the flaw!
16751 Changes in version 0.0.6.1 - 2004-05-06
16752 o Fix two bugs in our AES counter-mode implementation (this affected
16753 onion-level stream encryption, but not TLS-level). It turns
16754 out we were doing something much more akin to a 16-character
16755 polyalphabetic cipher. Oops.
16756 Thanks to Stefan Mark for finding the flaw!
16757 o Retire moria3 as a directory server, and add tor26 as a directory
16761 Changes in version 0.0.6 - 2004-05-02
16762 [version bump only]
16765 Changes in version 0.0.6rc4 - 2004-05-01
16766 o Update the built-in dirservers list to use the new directory format
16767 o Fix a rare seg fault: if a node offering a hidden service attempts
16768 to build a circuit to Alice's rendezvous point and fails before it
16769 reaches the last hop, it retries with a different circuit, but
16771 o Handle windows socket errors correctly.
16774 Changes in version 0.0.6rc3 - 2004-04-28
16775 o Don't expire non-general excess circuits (if we had enough
16776 circuits open, we were expiring rendezvous circuits -- even
16777 when they had a stream attached. oops.)
16778 o Fetch randomness from /dev/urandom better (not via fopen/fread)
16779 o Better debugging for tls errors
16780 o Some versions of openssl have an SSL_pending function that erroneously
16781 returns bytes when there is a non-application record pending.
16782 o Set Content-Type on the directory and hidserv descriptor.
16783 o Remove IVs from cipher code, since AES-ctr has none.
16784 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
16785 o We were using an array of length zero in a few places.
16786 o win32's gethostbyname can't resolve an IP to an IP.
16787 o win32's close can't close a socket.
16790 Changes in version 0.0.6rc2 - 2004-04-26
16791 o Fix a bug where we were closing tls connections intermittently.
16792 It turns out openssl keeps its errors around -- so if an error
16793 happens, and you don't ask about it, and then another openssl
16794 operation happens and succeeds, and you ask if there was an error,
16795 it tells you about the first error. Fun fun.
16796 o Fix a bug that's been lurking since 27 may 03 (!)
16797 When passing back a destroy cell, we would use the wrong circ id.
16798 'Mostly harmless', but still worth fixing.
16799 o Since we don't support truncateds much, don't bother sending them;
16800 just close the circ.
16801 o check for <machine/limits.h> so we build on NetBSD again (I hope).
16802 o don't crash if a conn that sent a begin has suddenly lost its circuit
16803 (this was quite rare).
16806 Changes in version 0.0.6rc1 - 2004-04-25
16807 o We now rotate link (tls context) keys and onion keys.
16808 o CREATE cells now include oaep padding, so you can tell
16809 if you decrypted them correctly.
16810 o Add bandwidthburst to server descriptor.
16811 o Directories now say which dirserver signed them.
16812 o Use a tor_assert macro that logs failed assertions too.
16815 Changes in version 0.0.6pre5 - 2004-04-18
16816 o changes from 0.0.6pre4:
16817 - make tor build on broken freebsd 5.2 installs
16818 - fix a failed assert when you try an intro point, get a nack, and try
16819 a second one and it works.
16820 - when alice uses a port that the hidden service doesn't accept,
16821 it now sends back an end cell (denied by exit policy). otherwise
16822 alice would just have to wait to time out.
16823 - fix another rare bug: when we had tried all the intro
16824 points for a hidden service, we fetched the descriptor
16825 again, but we left our introcirc thinking it had already
16826 sent an intro, so it kept waiting for a response...
16827 - bugfix: when you sleep your hidden-service laptop, as soon
16828 as it wakes up it tries to upload a service descriptor, but
16829 socketpair fails for some reason (localhost not up yet?).
16830 now we simply give up on that upload, and we'll try again later.
16831 i'd still like to find the bug though.
16832 - if an intro circ waiting for an ack dies before getting one, then
16834 - we were reusing stale service descriptors and refetching usable
16838 Changes in version 0.0.6pre4 - 2004-04-14
16839 o changes from 0.0.6pre3:
16840 - when bob fails to connect to the rendezvous point, and his
16841 circ didn't fail because of the rendezvous point itself, then
16842 he retries a couple of times
16843 - we expire introduction and rendezvous circs more thoroughly
16844 (sometimes they were hanging around forever)
16845 - we expire unattached rendezvous streams that have been around
16846 too long (they were sticking around forever).
16847 - fix a measly fencepost error that was crashing everybody with
16851 Changes in version 0.0.6pre3 - 2004-04-14
16852 o changes from 0.0.6pre2:
16853 - make hup work again
16854 - fix some memory leaks for dirservers
16855 - allow more skew in rendezvous descriptor timestamps, to help
16856 handle people like blanu who don't know what time it is
16857 - normal circs are 3 hops, but some rend/intro circs are 4, if
16858 the initiator doesn't get to choose the last hop
16859 - send acks for introductions, so alice can know whether to try
16861 - bob publishes intro points more correctly
16862 o changes from 0.0.5:
16863 - fix an assert trigger that's been plaguing us since the days
16864 of 0.0.2prexx (thanks weasel!)
16865 - retry stream correctly when we fail to connect because of
16866 exit-policy-reject (should try another) or can't-resolve-address
16867 (also should try another, because dns on random internet servers
16869 - when we hup a dirserver and we've *removed* a server from the
16870 approved-routers list, now we remove that server from the
16871 in-memory directories too
16874 Changes in version 0.0.6pre2 - 2004-04-08
16875 o We fixed our base32 implementation. Now it works on all architectures.
16878 Changes in version 0.0.6pre1 - 2004-04-08
16880 - Hidden services and rendezvous points are implemented. Go to
16881 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
16882 hidden services. (This only works via a socks4a proxy such as
16883 Privoxy, and currently it's quite slow.)
16886 Changes in version 0.0.5 - 2004-03-30
16887 [version bump only]
16890 Changes in version 0.0.5rc3 - 2004-03-29
16891 o Install torrc as torrc.sample -- we no longer clobber your
16893 o Re-enable recommendedversion checking (we broke it in rc2, oops)
16894 o Add in a 'notice' log level for things the operator should hear
16895 but that aren't warnings
16898 Changes in version 0.0.5rc2 - 2004-03-29
16899 o Hold socks connection open until reply is flushed (if possible)
16900 o Make exit nodes resolve IPs to IPs immediately, rather than asking
16901 the dns farm to do it.
16902 o Fix c99 aliasing warnings in rephist.c
16903 o Don't include server descriptors that are older than 24 hours in the
16905 o Give socks 'reject' replies their whole 15s to attempt to flush,
16906 rather than seeing the 60s timeout and assuming the flush had failed.
16907 o Clean automake droppings from the cvs repository
16910 Changes in version 0.0.5rc1 - 2004-03-28
16911 o Fix mangled-state bug in directory fetching (was causing sigpipes).
16912 o Only build circuits after we've fetched the directory: clients were
16913 using only the directory servers before they'd fetched a directory.
16914 This also means longer startup time; so it goes.
16915 o Fix an assert trigger where an OP would fail to handshake, and we'd
16916 expect it to have a nickname.
16917 o Work around a tsocks bug: do a socks reject when AP connection dies
16918 early, else tsocks goes into an infinite loop.
16921 Changes in version 0.0.4 - 2004-03-26
16922 o When connecting to a dirserver or OR and the network is down,
16926 Changes in version 0.0.3 - 2004-03-26
16927 o Warn and fail if server chose a nickname with illegal characters
16928 o Port to Solaris and Sparc:
16929 - include missing header fcntl.h
16930 - have autoconf find -lsocket -lnsl automatically
16931 - deal with hardware word alignment
16932 - make uname() work (solaris has a different return convention)
16933 - switch from using signal() to sigaction()
16934 o Preliminary work on reputation system:
16935 - Keep statistics on success/fail of connect attempts; they're published
16936 by kill -USR1 currently.
16937 - Add a RunTesting option to try to learn link state by creating test
16938 circuits, even when SocksPort is off.
16939 - Remove unused open circuits when there are too many.
16942 Changes in version 0.0.2 - 2004-03-19
16943 - Include strlcpy and strlcat for safer string ops
16944 - define INADDR_NONE so we compile (but still not run) on solaris
16947 Changes in version 0.0.2pre27 - 2004-03-14
16949 - Allow internal tor networks (we were rejecting internal IPs,
16950 now we allow them if they're set explicitly).
16951 - And fix a few endian issues.
16954 Changes in version 0.0.2pre26 - 2004-03-14
16956 - If a stream times out after 15s without a connected cell, don't
16957 try that circuit again: try a new one.
16958 - Retry streams at most 4 times. Then give up.
16959 - When a dirserver gets a descriptor from an unknown router, it
16960 logs its fingerprint (so the dirserver operator can choose to
16961 accept it even without mail from the server operator).
16962 - Inform unapproved servers when we reject their descriptors.
16963 - Make tor build on Windows again. It works as a client, who knows
16965 - Clearer instructions in the torrc for how to set up a server.
16966 - Be more efficient about reading fd's when our global token bucket
16967 (used for rate limiting) becomes empty.
16969 - Stop asserting that computers always go forward in time. It's
16971 - When we sent a cell (e.g. destroy) and then marked an OR connection
16972 expired, we might close it before finishing a flush if the other
16973 side isn't reading right then.
16974 - Don't allow dirservers to start if they haven't defined
16975 RecommendedVersions
16976 - We were caching transient dns failures. Oops.
16977 - Prevent servers from publishing an internal IP as their address.
16978 - Address a strcat vulnerability in circuit.c
16981 Changes in version 0.0.2pre25 - 2004-03-04
16983 - Put the OR's IP in its router descriptor, not its fqdn. That way
16984 we'll stop being stalled by gethostbyname for nodes with flaky dns,
16987 - If the user typed in an address that didn't resolve, the server
16991 Changes in version 0.0.2pre24 - 2004-03-03
16993 - Fix an assertion failure in dns.c, where we were trying to dequeue
16994 a pending dns resolve even if it wasn't pending
16995 - Fix a spurious socks5 warning about still trying to write after the
16996 connection is finished.
16997 - Hold certain marked_for_close connections open until they're finished
16998 flushing, rather than losing bytes by closing them too early.
16999 - Correctly report the reason for ending a stream
17000 - Remove some duplicate calls to connection_mark_for_close
17001 - Put switch_id and start_daemon earlier in the boot sequence, so it
17002 will actually try to chdir() to options.DataDirectory
17003 - Make 'make test' exit(1) if a test fails; fix some unit tests
17004 - Make tor fail when you use a config option it doesn't know about,
17005 rather than warn and continue.
17006 - Make --version work
17007 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
17010 Changes in version 0.0.2pre23 - 2004-02-29
17012 - Print a statement when the first circ is finished, so the user
17013 knows it's working.
17014 - If a relay cell is unrecognized at the end of the circuit,
17015 send back a destroy. (So attacks to mutate cells are more
17017 - New config option 'excludenodes' to avoid certain nodes for circuits.
17018 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
17019 so you can collect coredumps there.
17021 - Fix a bug in tls flushing where sometimes data got wedged and
17022 didn't flush until more data got sent. Hopefully this bug was
17023 a big factor in the random delays we were seeing.
17024 - Make 'connected' cells include the resolved IP, so the client
17025 dns cache actually gets populated.
17026 - Disallow changing from ORPort=0 to ORPort>0 on hup.
17027 - When we time-out on a stream and detach from the circuit, send an
17028 end cell down it first.
17029 - Only warn about an unknown router (in exitnodes, entrynodes,
17030 excludenodes) after we've fetched a directory.
17033 Changes in version 0.0.2pre22 - 2004-02-26
17035 - Servers publish less revealing uname information in descriptors.
17036 - More memory tracking and assertions, to crash more usefully when
17038 - If the default torrc isn't there, just use some default defaults.
17039 Plus provide an internal dirservers file if they don't have one.
17040 - When the user tries to use Tor as an http proxy, give them an http
17041 501 failure explaining that we're a socks proxy.
17042 - Dump a new router.desc on hup, to help confused people who change
17043 their exit policies and then wonder why router.desc doesn't reflect
17045 - Clean up the generic tor.sh init script that we ship with.
17047 - If the exit stream is pending on the resolve, and a destroy arrives,
17048 then the stream wasn't getting removed from the pending list. I
17049 think this was the one causing recent server crashes.
17050 - Use a more robust poll on OSX 10.3, since their poll is flaky.
17051 - When it couldn't resolve any dirservers, it was useless from then on.
17052 Now it reloads the RouterFile (or default dirservers) if it has no
17054 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
17055 many users don't even *have* a /usr/local/sbin/.
17058 Changes in version 0.0.2pre21 - 2004-02-18
17060 - There's a ChangeLog file that actually reflects the changelog.
17061 - There's a 'torify' wrapper script, with an accompanying
17062 tor-tsocks.conf, that simplifies the process of using tsocks for
17063 tor. It even has a man page.
17064 - The tor binary gets installed to sbin rather than bin now.
17065 - Retry streams where the connected cell hasn't arrived in 15 seconds
17066 - Clean up exit policy handling -- get the default out of the torrc,
17067 so we can update it without forcing each server operator to fix
17069 - Allow imaps and pop3s in default exit policy
17071 - Prevent picking middleman nodes as the last node in the circuit
17074 Changes in version 0.0.2pre20 - 2004-01-30
17076 - We now have a deb package, and it's in debian unstable. Go to
17077 it, apt-getters. :)
17078 - I've split the TotalBandwidth option into BandwidthRate (how many
17079 bytes per second you want to allow, long-term) and
17080 BandwidthBurst (how many bytes you will allow at once before the cap
17081 kicks in). This better token bucket approach lets you, say, set
17082 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
17083 performance while not exceeding your monthly bandwidth quota.
17084 - Push out a tls record's worth of data once you've got it, rather
17085 than waiting until you've read everything waiting to be read. This
17086 may improve performance by pipelining better. We'll see.
17087 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
17088 from failed circuits (if they haven't been connected yet) and attach
17090 - Expire old streams that haven't managed to connect. Some day we'll
17091 have them reattach to new circuits instead.
17094 - Fix several memory leaks that were causing servers to become bloated
17096 - Fix a few very rare assert triggers. A few more remain.
17097 - Setuid to User _before_ complaining about running as root.
17100 Changes in version 0.0.2pre19 - 2004-01-07
17102 - Fix deadlock condition in dns farm. We were telling a child to die by
17103 closing the parent's file descriptor to him. But newer children were
17104 inheriting the open file descriptor from the parent, and since they
17105 weren't closing it, the socket never closed, so the child never read
17106 eof, so he never knew to exit. Similarly, dns workers were holding
17107 open other sockets, leading to all sorts of chaos.
17108 - New cleaner daemon() code for forking and backgrounding.
17109 - If you log to a file, it now prints an entry at the top of the
17110 logfile so you know it's working.
17111 - The onionskin challenge length was 30 bytes longer than necessary.
17112 - Started to patch up the spec so it's not quite so out of date.
17115 Changes in version 0.0.2pre18 - 2004-01-02
17117 - Fix endian issues with the 'integrity' field in the relay header.
17118 - Fix a potential bug where connections in state
17119 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
17122 Changes in version 0.0.2pre17 - 2003-12-30
17124 - Made --debuglogfile (or any second log file, actually) work.
17125 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
17126 adversary could force us into an infinite loop.
17129 - Each onionskin handshake now includes a hash of the computed key,
17130 to prove the server's identity and help perfect forward secrecy.
17131 - Changed cell size from 256 to 512 bytes (working toward compatibility
17133 - Changed cell length to 2 bytes, and moved it to the relay header.
17134 - Implemented end-to-end integrity checking for the payloads of
17136 - Separated streamid from 'recognized' (otherwise circuits will get
17137 messed up when we try to have streams exit from the middle). We
17138 use the integrity-checking to confirm that a cell is addressed to
17140 - Randomize the initial circid and streamid values, so an adversary who
17141 breaks into a node can't learn how many circuits or streams have
17145 Changes in version 0.0.2pre16 - 2003-12-14
17147 - Fixed a bug that made HUP trigger an assert
17148 - Fixed a bug where a circuit that immediately failed wasn't being
17149 counted as a failed circuit in counting retries.
17152 - Now we close the circuit when we get a truncated cell: otherwise we're
17153 open to an anonymity attack where a bad node in the path truncates
17154 the circuit and then we open streams at him.
17155 - Add port ranges to exit policies
17156 - Add a conservative default exit policy
17157 - Warn if you're running tor as root
17158 - on HUP, retry OR connections and close/rebind listeners
17159 - options.EntryNodes: try these nodes first when picking the first node
17160 - options.ExitNodes: if your best choices happen to include any of
17161 your preferred exit nodes, you choose among just those preferred
17163 - options.ExcludedNodes: nodes that are never picked in path building
17166 Changes in version 0.0.2pre15 - 2003-12-03
17167 o Robustness and bugfixes:
17168 - Sometimes clients would cache incorrect DNS resolves, which would
17169 really screw things up.
17170 - An OP that goes offline would slowly leak all its sockets and stop
17172 - A wide variety of bugfixes in exit node selection, exit policy
17173 handling, and processing pending streams when a new circuit is
17175 - Pick nodes for a path only from those the directory says are up
17176 - Choose randomly from all running dirservers, not always the first one
17177 - Increase allowed http header size for directory fetch.
17178 - Stop writing to stderr (if we're daemonized it will be closed).
17179 - Enable -g always, so cores will be more useful to me.
17180 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
17183 - Wrote a man page. It lists commonly used options.
17186 - Change default loglevel to warn.
17187 - Make PidFile default to null rather than littering in your CWD.
17188 - OnionRouter config option is now obsolete. Instead it just checks
17190 - Moved to a single unified torrc file for both clients and servers.
17193 Changes in version 0.0.2pre14 - 2003-11-29
17194 o Robustness and bugfixes:
17195 - Force the admin to make the DataDirectory himself
17196 - to get ownership/permissions right
17197 - so clients no longer make a DataDirectory and then never use it
17198 - fix bug where a client who was offline for 45 minutes would never
17199 pull down a directory again
17200 - fix (or at least hide really well) the dns assert bug that was
17201 causing server crashes
17202 - warnings and improved robustness wrt clockskew for certs
17203 - use the native daemon(3) to daemonize, when available
17204 - exit if bind() fails
17205 - exit if neither socksport nor orport is defined
17206 - include our own tor_timegm (Win32 doesn't have its own)
17207 - bugfix for win32 with lots of connections
17208 - fix minor bias in PRNG
17209 - make dirserver more robust to corrupt cached directory
17212 - Wrote the design document (woo)
17214 o Circuit building and exit policies:
17215 - Circuits no longer try to use nodes that the directory has told them
17217 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
17218 bitcounts (18.0.0.0/8).
17219 - Make AP connections standby for a circuit if no suitable circuit
17220 exists, rather than failing
17221 - Circuits choose exit node based on addr/port, exit policies, and
17222 which AP connections are standing by
17223 - Bump min pathlen from 2 to 3
17224 - Relay end cells have a payload to describe why the stream ended.
17225 - If the stream failed because of exit policy, try again with a new
17227 - Clients have a dns cache to remember resolved addresses.
17228 - Notice more quickly when we have no working circuits
17231 - APPort is now called SocksPort
17232 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
17234 - RecommendedVersions is now a config variable rather than
17235 hardcoded (for dirservers)
17236 - Reloads config on HUP
17237 - Usage info on -h or --help
17238 - If you set User and Group config vars, it'll setu/gid to them.
17241 Changes in version 0.0.2pre13 - 2003-10-19
17242 o General stability:
17243 - SSL_write no longer fails when it returns WANTWRITE and the number
17244 of bytes in the buf has changed by the next SSL_write call.
17245 - Fix segfault fetching directory when network is down
17246 - Fix a variety of minor memory leaks
17247 - Dirservers reload the fingerprints file on HUP, so I don't have
17248 to take down the network when I approve a new router
17249 - Default server config file has explicit Address line to specify fqdn
17252 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
17253 - Make listener connections not ever alloc bufs
17255 o Autoconf improvements:
17256 - don't clobber an external CFLAGS in ./configure
17257 - Make install now works
17258 - create var/lib/tor on make install
17259 - autocreate a tor.sh initscript to help distribs
17260 - autocreate the torrc and sample-server-torrc with correct paths
17262 o Log files and Daemonizing now work:
17263 - If --DebugLogFile is specified, log to it at -l debug
17264 - If --LogFile is specified, use it instead of commandline
17265 - If --RunAsDaemon is set, tor forks and backgrounds on startup