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 contains a response to the recent "POODLE" attack against
4 SSL3 (which doesn't affect Tor), and a response to a crash bug caused
5 by some operating systems' response to the "POODLE" attack (which does
6 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.5.8-rc - 2014-09-22
35 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
36 series. It fixes a bug that affects consistency and speed when
37 connecting to hidden services, and it updates the location of one of
38 the directory authorities.
41 - Clients now send the correct address for their chosen rendezvous
42 point when trying to access a hidden service. They used to send
43 the wrong address, which would still work some of the time because
44 they also sent the identity digest of the rendezvous point, and if
45 the hidden service happened to try connecting to the rendezvous
46 point from a relay that already had a connection open to it,
47 the relay would reuse that connection. Now connections to hidden
48 services should be more robust and faster. Also, this bug meant
49 that clients were leaking to the hidden service whether they were
50 on a little-endian (common) or big-endian (rare) system, which for
51 some users might have reduced their anonymity. Fixes bug 13151;
52 bugfix on 0.2.1.5-alpha.
54 o Directory authority changes:
55 - Change IP address for gabelmoo (v3 directory authority).
58 Changes in version 0.2.4.24 - 2014-09-22
59 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
60 connecting to hidden services, and it updates the location of one of
61 the directory authorities.
64 - Clients now send the correct address for their chosen rendezvous
65 point when trying to access a hidden service. They used to send
66 the wrong address, which would still work some of the time because
67 they also sent the identity digest of the rendezvous point, and if
68 the hidden service happened to try connecting to the rendezvous
69 point from a relay that already had a connection open to it,
70 the relay would reuse that connection. Now connections to hidden
71 services should be more robust and faster. Also, this bug meant
72 that clients were leaking to the hidden service whether they were
73 on a little-endian (common) or big-endian (rare) system, which for
74 some users might have reduced their anonymity. Fixes bug 13151;
75 bugfix on 0.2.1.5-alpha.
77 o Directory authority changes:
78 - Change IP address for gabelmoo (v3 directory authority).
80 o Minor features (geoip):
81 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
85 Changes in version 0.2.5.7-rc - 2014-09-11
86 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
87 release series, and some long-standing bugs related to ORPort reachability
88 testing and failure to send CREATE cells. It is the first release
89 candidate for the Tor 0.2.5.x series.
91 o Major bugfixes (client, startup):
92 - Start making circuits as soon as DisabledNetwork is turned off.
93 When Tor started with DisabledNetwork set, it would correctly
94 conclude that it shouldn't build circuits, but it would mistakenly
95 cache this conclusion, and continue believing it even when
96 DisableNetwork is set to 0. Fixes the bug introduced by the fix
97 for bug 11200; bugfix on 0.2.5.4-alpha.
98 - Resume expanding abbreviations for command-line options. The fix
99 for bug 4647 accidentally removed our hack from bug 586 that
100 rewrote HashedControlPassword to __HashedControlSessionPassword
101 when it appears on the commandline (which allowed the user to set
102 her own HashedControlPassword in the torrc file while the
103 controller generates a fresh session password for each run). Fixes
104 bug 12948; bugfix on 0.2.5.1-alpha.
105 - Warn about attempts to run hidden services and relays in the same
106 process: that's probably not a good idea. Closes ticket 12908.
108 o Major bugfixes (relay):
109 - Avoid queuing or sending destroy cells for circuit ID zero when we
110 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
111 Found and fixed by "cypherpunks".
112 - Fix ORPort reachability detection on relays running behind a
113 proxy, by correctly updating the "local" mark on the controlling
114 channel when changing the address of an or_connection_t after the
115 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
117 o Minor features (bridge):
118 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
119 cookie file for the ExtORPort g+r by default.
121 o Minor features (geoip):
122 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
125 o Minor bugfixes (logging):
126 - Reduce the log severity of the "Pluggable transport proxy does not
127 provide any needed transports and will not be launched." message,
128 since Tor Browser includes several ClientTransportPlugin lines in
129 its torrc-defaults file, leading every Tor Browser user who looks
130 at her logs to see these notices and wonder if they're dangerous.
131 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
132 - Downgrade "Unexpected onionskin length after decryption" warning
133 to a protocol-warn, since there's nothing relay operators can do
134 about a client that sends them a malformed create cell. Resolves
135 bug 12996; bugfix on 0.0.6rc1.
136 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
137 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
138 - When logging information about an EXTEND2 or EXTENDED2 cell, log
139 their names correctly. Fixes part of bug 12700; bugfix
141 - When logging information about a relay cell whose command we don't
142 recognize, log its command as an integer. Fixes part of bug 12700;
143 bugfix on 0.2.1.10-alpha.
144 - Escape all strings from the directory connection before logging
145 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
147 o Minor bugfixes (controller):
148 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
149 bug 12864; bugfix on 0.2.5.1-alpha.
150 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
151 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
154 o Minor bugfixes (compilation):
155 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
156 bugfix on 0.2.5.5-alpha.
157 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
158 0.2.5.1-alpha. Patch from "NewEraCracker".
159 - In routerlist_assert_ok(), don't take the address of a
160 routerinfo's cache_info member unless that routerinfo is non-NULL.
161 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
162 - Fix a large number of false positive warnings from the clang
163 analyzer static analysis tool. This should make real warnings
164 easier for clang analyzer to find. Patch from "teor". Closes
167 o Distribution (systemd):
168 - Verify configuration file via ExecStartPre in the systemd unit
169 file. Patch from intrigeri; resolves ticket 12730.
170 - Explicitly disable RunAsDaemon in the systemd unit file. Our
171 current systemd unit uses "Type = simple", so systemd does not
172 expect tor to fork. If the user has "RunAsDaemon 1" in their
173 torrc, then things won't work as expected. This is e.g. the case
174 on Debian (and derivatives), since there we pass "--defaults-torrc
175 /usr/share/tor/tor-service-defaults-torrc" (that contains
176 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
180 - Adjust the URLs in the README to refer to the new locations of
181 several documents on the website. Fixes bug 12830. Patch from
183 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
187 Changes in version 0.2.5.6-alpha - 2014-07-28
188 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
189 risk from guard rotation, and fixes a variety of other issues to get
190 us closer to a release candidate.
192 o Major features (also in 0.2.4.23):
193 - Make the number of entry guards configurable via a new
194 NumEntryGuards consensus parameter, and the number of directory
195 guards configurable via a new NumDirectoryGuards consensus
196 parameter. Implements ticket 12688.
198 o Major bugfixes (also in 0.2.4.23):
199 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
200 implementation that caused incorrect results on 32-bit
201 implementations when certain malformed inputs were used along with
202 a small class of private ntor keys. This bug does not currently
203 appear to allow an attacker to learn private keys or impersonate a
204 Tor server, but it could provide a means to distinguish 32-bit Tor
205 implementations from 64-bit Tor implementations. Fixes bug 12694;
206 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
210 - Perform circuit cleanup operations even when circuit
211 construction operations are disabled (because the network is
212 disabled, or because there isn't enough directory information).
213 Previously, when we were not building predictive circuits, we
214 were not closing expired circuits either. Fixes bug 8387; bugfix on
215 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
216 became more strict about when we have "enough directory information
220 - Authorities now assign the Guard flag to the fastest 25% of the
221 network (it used to be the fastest 50%). Also raise the consensus
222 weight that guarantees the Guard flag from 250 to 2000. For the
223 current network, this results in about 1100 guards, down from 2500.
224 This step paves the way for moving the number of entry guards
225 down to 1 (proposal 236) while still providing reasonable expected
226 performance for most users. Implements ticket 12690.
227 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
229 - Slightly enhance the diagnostic message for bug 12184.
231 o Minor bugfixes (also in 0.2.4.23):
232 - Warn and drop the circuit if we receive an inbound 'relay early'
233 cell. Those used to be normal to receive on hidden service circuits
234 due to bug 1038, but the buggy Tor versions are long gone from
235 the network so we can afford to resume watching for them. Resolves
236 the rest of bug 1038; bugfix on 0.2.1.19.
237 - Correct a confusing error message when trying to extend a circuit
238 via the control protocol but we don't know a descriptor or
239 microdescriptor for one of the specified relays. Fixes bug 12718;
240 bugfix on 0.2.3.1-alpha.
243 - Fix compilation when building with bufferevents enabled. (This
244 configuration is still not expected to work, however.)
245 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
246 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
248 - Compile correctly with builds and forks of OpenSSL (such as
249 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
250 0.2.1.1-alpha. Patch from "dhill".
253 Changes in version 0.2.4.23 - 2014-07-28
254 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
255 guard rotation, and also backports several important fixes from the
256 Tor 0.2.5 alpha release series.
259 - Clients now look at the "usecreatefast" consensus parameter to
260 decide whether to use CREATE_FAST or CREATE cells for the first hop
261 of their circuit. This approach can improve security on connections
262 where Tor's circuit handshake is stronger than the available TLS
263 connection security levels, but the tradeoff is more computational
264 load on guard relays. Implements proposal 221. Resolves ticket 9386.
265 - Make the number of entry guards configurable via a new
266 NumEntryGuards consensus parameter, and the number of directory
267 guards configurable via a new NumDirectoryGuards consensus
268 parameter. Implements ticket 12688.
271 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
272 implementation that caused incorrect results on 32-bit
273 implementations when certain malformed inputs were used along with
274 a small class of private ntor keys. This bug does not currently
275 appear to allow an attacker to learn private keys or impersonate a
276 Tor server, but it could provide a means to distinguish 32-bit Tor
277 implementations from 64-bit Tor implementations. Fixes bug 12694;
278 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
282 - Warn and drop the circuit if we receive an inbound 'relay early'
283 cell. Those used to be normal to receive on hidden service circuits
284 due to bug 1038, but the buggy Tor versions are long gone from
285 the network so we can afford to resume watching for them. Resolves
286 the rest of bug 1038; bugfix on 0.2.1.19.
287 - Correct a confusing error message when trying to extend a circuit
288 via the control protocol but we don't know a descriptor or
289 microdescriptor for one of the specified relays. Fixes bug 12718;
290 bugfix on 0.2.3.1-alpha.
291 - Avoid an illegal read from stack when initializing the TLS
292 module using a version of OpenSSL without all of the ciphers
293 used by the v2 link handshake. Fixes bug 12227; bugfix on
294 0.2.4.8-alpha. Found by "starlight".
297 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
301 Changes in version 0.2.5.5-alpha - 2014-06-18
302 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
303 0.2.5.x release series, including a couple of DoS issues, some
304 performance regressions, a large number of bugs affecting the Linux
305 seccomp2 sandbox code, and various other bugfixes. It also adds
306 diagnostic bugfixes for a few tricky issues that we're trying to
309 o Major features (security, traffic analysis resistance):
310 - Several major improvements to the algorithm used to decide when to
311 close TLS connections. Previous versions of Tor closed connections
312 at a fixed interval after the last time a non-padding cell was
313 sent over the connection, regardless of the target of the
314 connection. Now, we randomize the intervals by adding up to 50% of
315 their base value, we measure the length of time since connection
316 last had at least one circuit, and we allow connections to known
317 ORs to remain open a little longer (15 minutes instead of 3
318 minutes minimum). These changes should improve Tor's resistance
319 against some kinds of traffic analysis, and lower some overhead
320 from needlessly closed connections. Fixes ticket 6799.
321 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
323 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
324 - Fix a memory leak that could occur if a microdescriptor parse
325 fails during the tokenizing step. This bug could enable a memory
326 exhaustion attack by directory servers. Fixes bug 11649; bugfix
329 o Major bugfixes (security, directory authorities):
330 - Directory authorities now include a digest of each relay's
331 identity key as a part of its microdescriptor.
333 This is a workaround for bug 11743 (reported by "cypherpunks"),
334 where Tor clients do not support receiving multiple
335 microdescriptors with the same SHA256 digest in the same
336 consensus. When clients receive a consensus like this, they only
337 use one of the relays. Without this fix, a hostile relay could
338 selectively disable some client use of target relays by
339 constructing a router descriptor with a different identity and the
340 same microdescriptor parameters and getting the authorities to
341 list it in a microdescriptor consensus. This fix prevents an
342 attacker from causing a microdescriptor collision, because the
343 router's identity is not forgeable.
345 o Major bugfixes (relay):
346 - Use a direct dirport connection when uploading non-anonymous
347 descriptors to the directory authorities. Previously, relays would
348 incorrectly use tunnel connections under a fairly wide variety of
349 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
350 - When a circuit accidentally has the same circuit ID for its
351 forward and reverse direction, correctly detect the direction of
352 cells using that circuit. Previously, this bug made roughly one
353 circuit in a million non-functional. Fixes bug 12195; this is a
354 bugfix on every version of Tor.
356 o Major bugfixes (client, pluggable transports):
357 - When managing pluggable transports, use OS notification facilities
358 to learn if they have crashed, and don't attempt to kill any
359 process that has already exited. Fixes bug 8746; bugfix
362 o Minor features (diagnostic):
363 - When logging a warning because of bug 7164, additionally check the
364 hash table for consistency (as proposed on ticket 11737). This may
365 help diagnose bug 7164.
366 - When we log a heartbeat, log how many one-hop circuits we have
367 that are at least 30 minutes old, and log status information about
368 a few of them. This is an attempt to track down bug 8387.
369 - When encountering an unexpected CR while writing text to a file on
370 Windows, log the name of the file. Should help diagnosing
372 - Give more specific warnings when a client notices that an onion
373 handshake has failed. Fixes ticket 9635.
374 - Add significant new logging code to attempt to diagnose bug 12184,
375 where relays seem to run out of available circuit IDs.
376 - Improve the diagnostic log message for bug 8387 even further to
377 try to improve our odds of figuring out why one-hop directory
378 circuits sometimes do not get closed.
380 o Minor features (security, memory management):
381 - Memory allocation tricks (mempools and buffer freelists) are now
382 disabled by default. You can turn them back on with
383 --enable-mempools and --enable-buf-freelists respectively. We're
384 disabling these features because malloc performance is good enough
385 on most platforms, and a similar feature in OpenSSL exacerbated
386 exploitation of the Heartbleed attack. Resolves ticket 11476.
388 o Minor features (security):
389 - Apply the secure SipHash-2-4 function to the hash table mapping
390 circuit IDs and channels to circuits. We missed this one when we
391 were converting all the other hash functions to use SipHash back
392 in 0.2.5.3-alpha. Resolves ticket 11750.
394 o Minor features (build):
395 - The configure script has a --disable-seccomp option to turn off
396 support for libseccomp on systems that have it, in case it (or
397 Tor's use of it) is broken. Resolves ticket 11628.
399 o Minor features (other):
400 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
403 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
404 - When running a hidden service, do not allow TunneledDirConns 0;
405 this will keep the hidden service from running, and also
406 make it publish its descriptors directly over HTTP. Fixes bug 10849;
407 bugfix on 0.2.1.1-alpha.
409 o Minor bugfixes (performance):
410 - Avoid a bug where every successful connection made us recompute
411 the flag telling us whether we have sufficient information to
412 build circuits. Previously, we would forget our cached value
413 whenever we successfully opened a channel (or marked a router as
414 running or not running for any other reason), regardless of
415 whether we had previously believed the router to be running. This
416 forced us to run an expensive update operation far too often.
417 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
418 - Avoid using tor_memeq() for checking relay cell integrity. This
419 removes a possible performance bottleneck. Fixes part of bug
420 12169; bugfix on 0.2.1.31.
422 o Minor bugfixes (compilation):
423 - Fix compilation of test_status.c when building with MVSC. Bugfix
424 on 0.2.5.4-alpha. Patch from Gisle Vanem.
425 - Resolve GCC complaints on OpenBSD about discarding constness in
426 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
427 on 0.1.1.23. Patch from Dana Koch.
428 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
429 treatment of long and time_t as comparable types. Fixes part of
430 bug 11633. Patch from Dana Koch.
431 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
432 11623; bugfix on 0.2.5.3-alpha.
433 - When deciding whether to build the 64-bit curve25519
434 implementation, detect platforms where we can compile 128-bit
435 arithmetic but cannot link it. Fixes bug 11729; bugfix on
436 0.2.4.8-alpha. Patch from "conradev".
437 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
438 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
439 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
442 o Minor bugfixes (Directory server):
443 - When sending a compressed set of descriptors or microdescriptors,
444 make sure to finalize the zlib stream. Previously, we would write
445 all the compressed data, but if the last descriptor we wanted to
446 send was missing or too old, we would not mark the stream as
447 finished. This caused problems for decompression tools. Fixes bug
448 11648; bugfix on 0.1.1.23.
450 o Minor bugfixes (Linux seccomp sandbox):
451 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
452 11622; bugfix on 0.2.5.1-alpha.
453 - Avoid crashing when re-opening listener ports with the seccomp
454 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
455 - Avoid crashing with the seccomp sandbox enabled along with
456 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
457 - When we receive a SIGHUP with the sandbox enabled, correctly
458 support rotating our log files. Fixes bug 12032; bugfix
460 - Avoid crash when running with sandboxing enabled and
461 DirReqStatistics not disabled. Fixes bug 12035; bugfix
463 - Fix a "BUG" warning when trying to write bridge-stats files with
464 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
466 - Prevent the sandbox from crashing on startup when run with the
467 --enable-expensive-hardening configuration option. Fixes bug
468 11477; bugfix on 0.2.5.4-alpha.
469 - When running with DirPortFrontPage and sandboxing both enabled,
470 reload the DirPortFrontPage correctly when restarting. Fixes bug
471 12028; bugfix on 0.2.5.1-alpha.
472 - Don't try to enable the sandbox when using the Tor binary to check
473 its configuration, hash a passphrase, or so on. Doing so was
474 crashing on startup for some users. Fixes bug 11609; bugfix
476 - Avoid warnings when running with sandboxing and node statistics
477 enabled at the same time. Fixes part of 12064; bugfix on
478 0.2.5.1-alpha. Patch from Michael Wolf.
479 - Avoid warnings when running with sandboxing enabled at the same
480 time as cookie authentication, hidden services, or directory
481 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
482 - Do not allow options that require calls to exec to be enabled
483 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
484 bug 12043; bugfix on 0.2.5.1-alpha.
485 - Handle failures in getpwnam()/getpwuid() when running with the
486 User option set and the Linux syscall sandbox enabled. Fixes bug
487 11946; bugfix on 0.2.5.1-alpha.
488 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
489 to avoid calling getaddrinfo() after installing the sandbox
490 filters. Previously, it preloaded a cache with the IPv4 address
491 for our hostname, and nothing else. Now, it loads the cache with
492 every address that it used to initialize the Tor process. Fixes
493 bug 11970; bugfix on 0.2.5.1-alpha.
495 o Minor bugfixes (pluggable transports):
496 - Enable the ExtORPortCookieAuthFile option, to allow changing the
497 default location of the authentication token for the extended OR
498 Port as used by sever-side pluggable transports. We had
499 implemented this option before, but the code to make it settable
500 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
501 - Avoid another 60-second delay when starting Tor in a pluggable-
502 transport-using configuration when we already have cached
503 descriptors for our bridges. Fixes bug 11965; bugfix
506 o Minor bugfixes (client):
507 - Avoid "Tried to open a socket with DisableNetwork set" warnings
508 when starting a client with bridges configured and DisableNetwork
509 set. (Tor launcher starts Tor with DisableNetwork set the first
510 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
512 o Minor bugfixes (testing):
513 - The Python parts of the test scripts now work on Python 3 as well
514 as Python 2, so systems where '/usr/bin/python' is Python 3 will
515 no longer have the tests break. Fixes bug 11608; bugfix
517 - When looking for versions of python that we could run the tests
518 with, check for "python2.7" and "python3.3"; previously we were
519 only looking for "python", "python2", and "python3". Patch from
520 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
521 - Fix all valgrind warnings produced by the unit tests. There were
522 over a thousand memory leak warnings previously, mostly produced
523 by forgetting to free things in the unit test code. Fixes bug
524 11618, bugfixes on many versions of Tor.
526 o Minor bugfixes (tor-fw-helper):
527 - Give a correct log message when tor-fw-helper fails to launch.
528 (Previously, we would say something like "tor-fw-helper sent us a
529 string we could not parse".) Fixes bug 9781; bugfix
532 o Minor bugfixes (relay, threading):
533 - Check return code on spawn_func() in cpuworker code, so that we
534 don't think we've spawned a nonworking cpuworker and write junk to
535 it forever. Fix related to bug 4345; bugfix on all released Tor
536 versions. Found by "skruffy".
537 - Use a pthread_attr to make sure that spawn_func() cannot return an
538 error while at the same time launching a thread. Fix related to
539 bug 4345; bugfix on all released Tor versions. Reported
542 o Minor bugfixes (relay, oom prevention):
543 - Correctly detect the total available system memory. We tried to do
544 this in 0.2.5.4-alpha, but the code was set up to always return an
545 error value, even on success. Fixes bug 11805; bugfix
548 o Minor bugfixes (relay, other):
549 - We now drop CREATE cells for already-existent circuit IDs and for
550 zero-valued circuit IDs, regardless of other factors that might
551 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
553 - Avoid an illegal read from stack when initializing the TLS module
554 using a version of OpenSSL without all of the ciphers used by the
555 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
557 - When rejecting DATA cells for stream_id zero, still count them
558 against the circuit's deliver window so that we don't fail to send
559 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
561 o Minor bugfixes (logging):
562 - Fix a misformatted log message about delayed directory fetches.
563 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
564 - Squelch a spurious LD_BUG message "No origin circuit for
565 successful SOCKS stream" in certain hidden service failure cases;
569 - Include a tor.service file in contrib/dist for use with systemd.
570 Some distributions will be able to use this file unmodified;
571 others will need to tweak it, or write their own. Patch from Jamie
572 Nguyen; resolves ticket 8368.
575 - Clean up several option names in the manpage to match their real
576 names, add the missing documentation for a couple of testing and
577 directory authority options, remove the documentation for a
578 V2-directory fetching option that no longer exists. Resolves
580 - Correct the documenation so that it lists the correct directory
581 for the stats files. (They are in a subdirectory called "stats",
583 - In the manpage, move more authority-only options into the
584 directory authority section so that operators of regular directory
585 caches don't get confused.
588 - The contrib directory has been sorted and tidied. Before, it was
589 an unsorted dumping ground for useful and not-so-useful things.
590 Now, it is divided based on functionality, and the items which
591 seemed to be nonfunctional or useless have been removed. Resolves
592 ticket 8966; based on patches from "rl1987".
595 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
596 and MTBF calculations, but that nobody was using. Fixes #11742.
597 - The TunnelDirConns and PreferTunnelledDirConns options no longer
598 exist; tunneled directory connections have been available since
599 0.1.2.5-alpha, and turning them off is not a good idea. This is a
600 brute-force fix for 10849, where "TunnelDirConns 0" would break
604 Changes in version 0.2.4.22 - 2014-05-16
605 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
606 alpha release series. These include blocking all authority signing
607 keys that may have been affected by the OpenSSL "heartbleed" bug,
608 choosing a far more secure set of TLS ciphersuites by default, closing
609 a couple of memory leaks that could be used to run a target relay out
610 of RAM, and several others.
612 o Major features (security, backport from 0.2.5.4-alpha):
613 - Block authority signing keys that were used on authorities
614 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
615 don't have any evidence that these keys _were_ compromised; we're
616 doing this to be prudent.) Resolves ticket 11464.
618 o Major bugfixes (security, OOM):
619 - Fix a memory leak that could occur if a microdescriptor parse
620 fails during the tokenizing step. This bug could enable a memory
621 exhaustion attack by directory servers. Fixes bug 11649; bugfix
624 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
625 - The relay ciphersuite list is now generated automatically based on
626 uniform criteria, and includes all OpenSSL ciphersuites with
627 acceptable strength and forward secrecy. Previously, we had left
628 some perfectly fine ciphersuites unsupported due to omission or
629 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
630 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
631 - Relays now trust themselves to have a better view than clients of
632 which TLS ciphersuites are better than others. (Thanks to bug
633 11513, the relay list is now well-considered, whereas the client
634 list has been chosen mainly for anti-fingerprinting purposes.)
635 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
636 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
637 AES128. Resolves ticket 11528.
638 - Clients now try to advertise the same list of ciphersuites as
639 Firefox 28. This change enables selection of (fast) GCM
640 ciphersuites, disables some strange old ciphers, and stops
641 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
642 Resolves ticket 11438.
644 o Minor bugfixes (configuration, security):
645 - When running a hidden service, do not allow TunneledDirConns 0:
646 trying to set that option together with a hidden service would
647 otherwise prevent the hidden service from running, and also make
648 it publish its descriptors directly over HTTP. Fixes bug 10849;
649 bugfix on 0.2.1.1-alpha.
651 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
652 - Avoid sending a garbage value to the controller when a circuit is
653 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
655 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
656 - Stop leaking memory when we successfully resolve a PTR record.
657 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
659 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
660 - Avoid 60-second delays in the bootstrapping process when Tor is
661 launching for a second time while using bridges. Fixes bug 9229;
662 bugfix on 0.2.0.3-alpha.
664 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
665 - Give the correct URL in the warning message when trying to run a
666 relay on an ancient version of Windows. Fixes bug 9393.
668 o Minor bugfixes (compilation):
669 - Fix a compilation error when compiling with --disable-curve25519.
670 Fixes bug 9700; bugfix on 0.2.4.17-rc.
673 - Downgrade the warning severity for the the "md was still
674 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
675 for trying to diagnose this bug, and the current warning in
676 earlier versions of tor achieves nothing useful. Addresses warning
679 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
680 - When we run out of usable circuit IDs on a channel, log only one
681 warning for the whole channel, and describe how many circuits
682 there were on the channel. Fixes part of ticket 11553.
684 o Minor features (security, backport from 0.2.5.4-alpha):
685 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
686 leave the default at 8GBytes), to better support Raspberry Pi
687 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
689 o Documentation (backport from 0.2.5.4-alpha):
690 - Correctly document that we search for a system torrc file before
691 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
695 Changes in version 0.2.5.4-alpha - 2014-04-25
696 Tor 0.2.5.4-alpha includes several security and performance
697 improvements for clients and relays, including blacklisting authority
698 signing keys that were used while susceptible to the OpenSSL
699 "heartbleed" bug, fixing two expensive functions on busy relays,
700 improved TLS ciphersuite preference lists, support for run-time
701 hardening on compilers that support AddressSanitizer, and more work on
702 the Linux sandbox code.
704 There are also several usability fixes for clients (especially clients
705 that use bridges), two new TransPort protocols supported (one on
706 OpenBSD, one on FreeBSD), and various other bugfixes.
708 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
709 have accumulated many known flaws; everyone should upgrade.
711 o Major features (security):
712 - If you don't specify MaxMemInQueues yourself, Tor now tries to
713 pick a good value based on your total system memory. Previously,
714 the default was always 8 GB. You can still override the default by
715 setting MaxMemInQueues yourself. Resolves ticket 11396.
716 - Block authority signing keys that were used on authorities
717 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
718 don't have any evidence that these keys _were_ compromised; we're
719 doing this to be prudent.) Resolves ticket 11464.
721 o Major features (relay performance):
722 - Speed up server-side lookups of rendezvous and introduction point
723 circuits by using hashtables instead of linear searches. These
724 functions previously accounted between 3 and 7% of CPU usage on
725 some busy relays. Resolves ticket 9841.
726 - Avoid wasting CPU when extending a circuit over a channel that is
727 nearly out of circuit IDs. Previously, we would do a linear scan
728 over possible circuit IDs before finding one or deciding that we
729 had exhausted our possibilities. Now, we try at most 64 random
730 circuit IDs before deciding that we probably won't succeed. Fixes
731 a possible root cause of ticket 11553.
733 o Major features (seccomp2 sandbox, Linux only):
734 - The seccomp2 sandbox can now run a test network for multiple hours
735 without crashing. The sandbox is still experimental, and more bugs
736 will probably turn up. To try it, enable "Sandbox 1" on a Linux
737 host. Resolves ticket 11351.
738 - Strengthen sandbox code: the sandbox can now test the arguments
739 for rename(), and blocks _sysctl() entirely. Resolves another part
741 - When the sandbox blocks a system call, it now tries to log a stack
742 trace before exiting. Resolves ticket 11465.
744 o Major bugfixes (TLS cipher selection):
745 - The relay ciphersuite list is now generated automatically based on
746 uniform criteria, and includes all OpenSSL ciphersuites with
747 acceptable strength and forward secrecy. Previously, we had left
748 some perfectly fine ciphersuites unsupported due to omission or
749 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
750 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
751 - Relays now trust themselves to have a better view than clients of
752 which TLS ciphersuites are better than others. (Thanks to bug
753 11513, the relay list is now well-considered, whereas the client
754 list has been chosen mainly for anti-fingerprinting purposes.)
755 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
756 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
757 AES128. Resolves ticket 11528.
758 - Clients now try to advertise the same list of ciphersuites as
759 Firefox 28. This change enables selection of (fast) GCM
760 ciphersuites, disables some strange old ciphers, and stops
761 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
762 Resolves ticket 11438.
764 o Major bugfixes (bridge client):
765 - Avoid 60-second delays in the bootstrapping process when Tor is
766 launching for a second time while using bridges. Fixes bug 9229;
767 bugfix on 0.2.0.3-alpha.
769 o Minor features (transparent proxy, *BSD):
770 - Support FreeBSD's ipfw firewall interface for TransPort ports on
771 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
772 10267; patch from "yurivict".
773 - Support OpenBSD's divert-to rules with the pf firewall for
774 transparent proxy ports. To enable it, set "TransProxyType
775 pf-divert". This allows Tor to run a TransPort transparent proxy
776 port on OpenBSD 4.4 or later without root privileges. See the
777 pf.conf(5) manual page for information on configuring pf to use
778 divert-to rules. Closes ticket 10896; patch from Dana Koch.
780 o Minor features (security):
781 - New --enable-expensive-hardening option to enable security
782 hardening options that consume nontrivial amounts of CPU and
783 memory. Right now, this includes AddressSanitizer and UbSan, which
784 are supported in newer versions of GCC and Clang. Closes ticket
787 o Minor features (log verbosity):
788 - Demote the message that we give when a flushing connection times
789 out for too long from NOTICE to INFO. It was usually meaningless.
790 Resolves ticket 5286.
791 - Don't log so many notice-level bootstrapping messages at startup
792 about downloading descriptors. Previously, we'd log a notice
793 whenever we learned about more routers. Now, we only log a notice
794 at every 5% of progress. Fixes bug 9963.
795 - Warn less verbosely when receiving a malformed
796 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
797 - When we run out of usable circuit IDs on a channel, log only one
798 warning for the whole channel, and describe how many circuits
799 there were on the channel. Fixes part of ticket 11553.
801 o Minor features (relay):
802 - If a circuit timed out for at least 3 minutes, check if we have a
803 new external IP address, and publish a new descriptor with the new
804 IP address if it changed. Resolves ticket 2454.
806 o Minor features (controller):
807 - Make the entire exit policy available from the control port via
808 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
810 - Because of the fix for ticket 11396, the real limit for memory
811 usage may no longer match the configured MaxMemInQueues value. The
812 real limit is now exposed via GETINFO limits/max-mem-in-queues.
814 o Minor features (bridge client):
815 - Report a more useful failure message when we can't connect to a
816 bridge because we don't have the right pluggable transport
817 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
819 o Minor features (diagnostic):
820 - Add more log messages to diagnose bug 7164, which causes
821 intermittent "microdesc_free() called but md was still referenced"
822 warnings. We now include more information, to figure out why we
823 might be cleaning a microdescriptor for being too old if it's
824 still referenced by a live node_t object.
826 o Minor bugfixes (client, DNSPort):
827 - When using DNSPort, try to respond to AAAA requests with AAAA
828 answers. Previously, we hadn't looked at the request type when
829 deciding which answer type to prefer. Fixes bug 10468; bugfix on
831 - When receiving a DNS query for an unsupported record type, reply
832 with no answer rather than with a NOTIMPL error. This behavior
833 isn't correct either, but it will break fewer client programs, we
834 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
837 o Minor bugfixes (exit relay):
838 - Stop leaking memory when we successfully resolve a PTR record.
839 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
841 o Minor bugfixes (bridge client):
842 - Stop accepting bridge lines containing hostnames. Doing so would
843 cause clients to perform DNS requests on the hostnames, which was
844 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
845 - Avoid a 60-second delay in the bootstrapping process when a Tor
846 client with pluggable transports re-reads its configuration at
847 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
849 o Minor bugfixes (client, logging during bootstrap):
850 - Warn only once if we start logging in an unsafe way. Previously,
851 we complain as many times as we had problems. Fixes bug 9870;
852 bugfix on 0.2.5.1-alpha.
853 - Only report the first fatal bootstrap error on a given OR
854 connection. This stops us from telling the controller bogus error
855 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
856 - Be more helpful when trying to run sandboxed on Linux without
857 libseccomp. Instead of saying "Sandbox is not implemented on this
858 platform", we now explain that we need to be built with
859 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
860 - Avoid generating spurious warnings when starting with
861 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
864 o Minor bugfixes (closing OR connections):
865 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
866 check if it's an or_connection_t and correctly call
867 connection_or_close_for_error() rather than
868 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
870 - When closing all connections on setting DisableNetwork to 1, use
871 connection_or_close_normally() rather than closing OR connections
872 out from under the channel layer. Fixes bug 11306; bugfix on
875 o Minor bugfixes (controller):
876 - Avoid sending a garbage value to the controller when a circuit is
877 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
879 o Minor bugfixes (tor-fw-helper):
880 - Allow tor-fw-helper to build again by adding src/ext to its
881 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
883 o Minor bugfixes (bridges):
884 - Avoid potential crashes or bad behavior when launching a
885 server-side managed proxy with ORPort or ExtORPort temporarily
886 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
888 o Minor bugfixes (platform-specific):
889 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
890 bug 11426; bugfix on 0.2.5.3-alpha.
891 - When dumping a malformed directory object to disk, save it in
892 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
894 - Don't report failures from make_socket_reuseable() on incoming
895 sockets on OSX: this can happen when incoming connections close
896 early. Fixes bug 10081.
898 o Minor bugfixes (trivial memory leaks):
899 - Fix a small memory leak when signing a directory object. Fixes bug
900 11275; bugfix on 0.2.4.13-alpha.
901 - Free placeholder entries in our circuit table at exit; fixes a
902 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
903 - Don't re-initialize a second set of OpenSSL mutexes when starting
904 up. Previously, we'd make one set of mutexes, and then immediately
905 replace them with another. Fixes bug 11726; bugfix on
907 - Resolve some memory leaks found by coverity in the unit tests, on
908 exit in tor-gencert, and on a failure to compute digests for our
909 own keys when generating a v3 networkstatus vote. These leaks
910 should never have affected anyone in practice.
912 o Minor bugfixes (hidden service):
913 - Only retry attempts to connect to a chosen rendezvous point 8
914 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
916 o Minor bugfixes (misc code correctness):
917 - Fix various instances of undefined behavior in channeltls.c,
918 tor_memmem(), and eventdns.c that would cause us to construct
919 pointers to memory outside an allocated object. (These invalid
920 pointers were not accessed, but C does not even allow them to
921 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
922 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
923 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
924 fix some miscellaneous errors in our tests and codebase. Fixes bug
925 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
926 - Always check return values for unlink, munmap, UnmapViewOfFile;
927 check strftime return values more often. In some cases all we can
928 do is report a warning, but this may help prevent deeper bugs from
929 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
931 - Fix numerous warnings from the clang "scan-build" static analyzer.
932 Some of these are programming style issues; some of them are false
933 positives that indicated awkward code; some are undefined behavior
934 cases related to constructing (but not using) invalid pointers;
935 some are assumptions about API behavior; some are (harmlessly)
936 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
937 correct; and one or two are genuine bugs that weren't reachable
938 from the rest of the program. Fixes bug 8793; bugfixes on many,
942 - Build the torify.1 manpage again. Previously, we were only trying
943 to build it when also building tor-fw-helper. That's why we didn't
944 notice that we'd broken the ability to build it. Fixes bug 11321;
945 bugfix on 0.2.5.1-alpha.
946 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
947 11061; bugfix on 0.2.4.7-alpha.
948 - Correctly document that we search for a system torrc file before
949 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
951 - Resolve warnings from Doxygen.
953 o Code simplifications and refactoring:
954 - Remove is_internal_IP() function. Resolves ticket 4645.
955 - Remove unused function circuit_dump_by_chan from circuitlist.c.
956 Closes issue 9107; patch from "marek".
957 - Change our use of the ENUM_BF macro to avoid declarations that
960 o Deprecated versions:
961 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
962 attention for some while. Directory authorities no longer accept
963 descriptors from relays running any version of Tor prior to Tor
964 0.2.3.16-alpha. Resolves ticket 11149.
967 - New macros in test.h to simplify writing mock-functions for unit
968 tests. Part of ticket 11507. Patch from Dana Koch.
969 - Complete tests for the status.c module. Resolves ticket 11507.
970 Patch from Dana Koch.
973 - Remove all code for the long unused v1 directory protocol.
974 Resolves ticket 11070.
977 Changes in version 0.2.5.3-alpha - 2014-03-22
978 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
979 two new anti-DoS features for Tor relays, resolves a bug that kept
980 SOCKS5 support for IPv6 from working, fixes several annoying usability
981 issues for bridge users, and removes more old code for unused
984 The Tor 0.2.5.x release series is now in patch-freeze: no feature
985 patches not already written will be considered for inclusion in 0.2.5.x.
987 o Major features (relay security, DoS-resistance):
988 - When deciding whether we have run out of memory and we need to
989 close circuits, also consider memory allocated in buffers for
990 streams attached to each circuit.
992 This change, which extends an anti-DoS feature introduced in
993 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
994 better resist more memory-based DoS attacks than before. Since the
995 MaxMemInCellQueues option now applies to all queues, it is renamed
996 to MaxMemInQueues. This feature fixes bug 10169.
997 - Avoid hash-flooding denial-of-service attacks by using the secure
998 SipHash-2-4 hash function for our hashtables. Without this
999 feature, an attacker could degrade performance of a targeted
1000 client or server by flooding their data structures with a large
1001 number of entries to be stored at the same hash table position,
1002 thereby slowing down the Tor instance. With this feature, hash
1003 table positions are derived from a randomized cryptographic key,
1004 and an attacker cannot predict which entries will collide. Closes
1006 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
1007 the default at 8GBytes), to better support Raspberry Pi users. Fixes
1008 bug 9686; bugfix on 0.2.4.14-alpha.
1010 o Minor features (bridges, pluggable transports):
1011 - Bridges now write the SHA1 digest of their identity key
1012 fingerprint (that is, a hash of a hash of their public key) to
1013 notice-level logs, and to a new hashed-fingerprint file. This
1014 information will help bridge operators look up their bridge in
1015 Globe and similar tools. Resolves ticket 10884.
1016 - Improve the message that Tor displays when running as a bridge
1017 using pluggable transports without an Extended ORPort listener.
1018 Also, log the message in the log file too. Resolves ticket 11043.
1020 o Minor features (other):
1021 - Add a new option, PredictedPortsRelevanceTime, to control how long
1022 after having received a request to connect to a given port Tor
1023 will try to keep circuits ready in anticipation of future requests
1024 for that port. Patch from "unixninja92"; implements ticket 9176.
1025 - Generate a warning if any ports are listed in the SocksPolicy,
1026 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
1027 AuthDirBadExit options. (These options only support address
1028 ranges.) Fixes part of ticket 11108.
1029 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
1032 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
1033 - Build without warnings under clang 3.4. (We have some macros that
1034 define static functions only some of which will get used later in
1035 the module. Starting with clang 3.4, these give a warning unless the
1036 unused attribute is set on them.) Resolves ticket 10904.
1037 - Fix build warnings about missing "a2x" comment when building the
1038 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1039 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1041 o Minor bugfixes (client):
1042 - Improve the log message when we can't connect to a hidden service
1043 because all of the hidden service directory nodes hosting its
1044 descriptor are excluded. Improves on our fix for bug 10722, which
1045 was a bugfix on 0.2.0.10-alpha.
1046 - Raise a control port warning when we fail to connect to all of
1047 our bridges. Previously, we didn't inform the controller, and
1048 the bootstrap process would stall. Fixes bug 11069; bugfix on
1050 - Exit immediately when a process-owning controller exits.
1051 Previously, tor relays would wait for a little while after their
1052 controller exited, as if they had gotten an INT signal -- but this
1053 was problematic, since there was no feedback for the user. To do a
1054 clean shutdown, controllers should send an INT signal and give Tor
1055 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
1056 - Stop attempting to connect to bridges before our pluggable
1057 transports are configured (harmless but resulted in some erroneous
1058 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
1059 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
1060 generating incorrect SOCKS5 responses, and confusing client
1061 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
1063 o Minor bugfixes (relays and bridges):
1064 - Avoid crashing on a malformed resolv.conf file when running a
1065 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
1066 - Non-exit relays no longer launch mock DNS requests to check for
1067 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
1068 non-exit relays stopped servicing DNS requests. Fixes bug 965;
1069 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
1070 - Bridges now report complete directory request statistics. Related
1071 to bug 5824; bugfix on 0.2.2.1-alpha.
1072 - Bridges now never collect statistics that were designed for
1073 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
1074 - Stop giving annoying warning messages when we decide not to launch
1075 a pluggable transport proxy that we don't need (because there are
1076 no bridges configured to use it). Resolves ticket 5018; bugfix
1078 - Give the correct URL in the warning message when trying to run a
1079 relay on an ancient version of Windows. Fixes bug 9393.
1081 o Minor bugfixes (backtrace support):
1082 - Support automatic backtraces on more platforms by using the
1083 "-fasynchronous-unwind-tables" compiler option. This option is
1084 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
1085 is on by default and table generation is not. This doesn't yet
1086 add Windows support; only Linux, OSX, and some BSDs are affected.
1087 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
1088 - Avoid strange behavior if two threads hit failed assertions at the
1089 same time and both try to log backtraces at once. (Previously, if
1090 this had happened, both threads would have stored their intermediate
1091 results in the same buffer, and generated junk outputs.) Reported by
1092 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
1093 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
1094 0.2.5.2-alpha; patch from Nick Hopper.
1096 o Minor bugfixes (unit tests):
1097 - Fix a small bug in the unit tests that might have made the tests
1098 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
1099 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
1102 - Remove all remaining code related to version-0 hidden service
1103 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
1104 the rest of bug 10841.
1107 - Document in the manpage that "KBytes" may also be written as
1108 "kilobytes" or "KB", that "Kbits" may also be written as
1109 "kilobits", and so forth. Closes ticket 9222.
1110 - Document that the ClientOnly config option overrides ORPort.
1111 Our old explanation made ClientOnly sound as though it did
1112 nothing at all. Resolves bug 9059.
1113 - Explain that SocksPolicy, DirPolicy, and similar options don't
1114 take port arguments. Fixes the other part of ticket 11108.
1115 - Fix a comment about the rend_server_descriptor_t.protocols field
1116 to more accurately describe its range. Also, make that field
1117 unsigned, to more accurately reflect its usage. Fixes bug 9099;
1118 bugfix on 0.2.1.5-alpha.
1119 - Fix the manpage's description of HiddenServiceAuthorizeClient:
1120 the maximum client name length is 16, not 19. Fixes bug 11118;
1121 bugfix on 0.2.1.6-alpha.
1123 o Code simplifications and refactoring:
1124 - Get rid of router->address, since in all cases it was just the
1125 string representation of router->addr. Resolves ticket 5528.
1127 o Test infrastructure:
1128 - Update to the latest version of tinytest.
1129 - Improve the tinytest implementation of string operation tests so
1130 that comparisons with NULL strings no longer crash the tests; they
1131 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
1134 Changes in version 0.2.4.21 - 2014-02-28
1135 Tor 0.2.4.21 further improves security against potential adversaries who
1136 find breaking 1024-bit crypto doable, and backports several stability
1137 and robustness patches from the 0.2.5 branch.
1139 o Major features (client security):
1140 - When we choose a path for a 3-hop circuit, make sure it contains
1141 at least one relay that supports the NTor circuit extension
1142 handshake. Otherwise, there is a chance that we're building
1143 a circuit that's worth attacking by an adversary who finds
1144 breaking 1024-bit crypto doable, and that chance changes the game
1145 theory. Implements ticket 9777.
1148 - Do not treat streams that fail with reason
1149 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1150 since it could also indicate an ENETUNREACH connection error. Fixes
1151 part of bug 10777; bugfix on 0.2.4.8-alpha.
1153 o Code simplification and refactoring:
1154 - Remove data structures which were introduced to implement the
1155 CellStatistics option: they are now redundant with the new timestamp
1156 field in the regular packed_cell_t data structure, which we did
1157 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
1160 - Always clear OpenSSL bignums before freeing them -- even bignums
1161 that don't contain secrets. Resolves ticket 10793. Patch by
1163 - Build without warnings under clang 3.4. (We have some macros that
1164 define static functions only some of which will get used later in
1165 the module. Starting with clang 3.4, these give a warning unless the
1166 unused attribute is set on them.) Resolves ticket 10904.
1167 - Update geoip and geoip6 files to the February 7 2014 Maxmind
1168 GeoLite2 Country database.
1171 - Set the listen() backlog limit to the largest actually supported
1172 on the system, not to the value in a header file. Fixes bug 9716;
1173 bugfix on every released Tor.
1174 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1175 exit node as a NOROUTE error, not an INTERNAL error, since they
1176 can apparently happen when trying to connect to the wrong sort
1177 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1178 - Fix build warnings about missing "a2x" comment when building the
1179 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1180 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1181 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1182 not entirely remove it from the connection lists. Fixes bug 9602;
1183 bugfix on 0.2.4.4-alpha.
1184 - Fix a segmentation fault in our benchmark code when running with
1185 Fedora's OpenSSL package, or any other OpenSSL that provides
1186 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1187 - Turn "circuit handshake stats since last time" log messages into a
1188 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1190 o Documentation fixes:
1191 - Document that all but one DirPort entry must have the NoAdvertise
1192 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1195 Changes in version 0.2.5.2-alpha - 2014-02-13
1196 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
1197 like the "poor random number generation" fix and the "building too many
1198 circuits" fix. It also further improves security against potential
1199 adversaries who find breaking 1024-bit crypto doable, and launches
1200 pluggable transports on demand (which gets us closer to integrating
1201 pluggable transport support by default -- not to be confused with Tor
1202 bundles enabling pluggable transports and bridges by default).
1204 o Major features (client security):
1205 - When we choose a path for a 3-hop circuit, make sure it contains
1206 at least one relay that supports the NTor circuit extension
1207 handshake. Otherwise, there is a chance that we're building
1208 a circuit that's worth attacking by an adversary who finds
1209 breaking 1024-bit crypto doable, and that chance changes the game
1210 theory. Implements ticket 9777.
1211 - Clients now look at the "usecreatefast" consensus parameter to
1212 decide whether to use CREATE_FAST or CREATE cells for the first hop
1213 of their circuit. This approach can improve security on connections
1214 where Tor's circuit handshake is stronger than the available TLS
1215 connection security levels, but the tradeoff is more computational
1216 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1218 o Major features (bridges):
1219 - Don't launch pluggable transport proxies if we don't have any
1220 bridges configured that would use them. Now we can list many
1221 pluggable transports, and Tor will dynamically start one when it
1222 hears a bridge address that needs it. Resolves ticket 5018.
1223 - The bridge directory authority now assigns status flags (Stable,
1224 Guard, etc) to bridges based on thresholds calculated over all
1225 Running bridges. Now bridgedb can finally make use of its features
1226 to e.g. include at least one Stable bridge in its answers. Fixes
1229 o Major features (other):
1230 - Extend ORCONN controller event to include an "ID" parameter,
1231 and add four new controller event types CONN_BW, CIRC_BW,
1232 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
1233 The new events are emitted in private Tor networks only, with the
1234 goal of being able to better track performance and load during
1235 full-network simulations. Implements proposal 218 and ticket 7359.
1236 - On some platforms (currently: recent OSX versions, glibc-based
1237 platforms that support the ELF format, and a few other
1238 Unix-like operating systems), Tor can now dump stack traces
1239 when a crash occurs or an assertion fails. By default, traces
1240 are dumped to stderr (if possible) and to any logs that are
1241 reporting errors. Implements ticket 9299.
1244 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1245 not entirely remove it from the connection lists. Fixes bug 9602;
1246 bugfix on 0.2.4.4-alpha.
1247 - Do not treat streams that fail with reason
1248 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1249 since it could also indicate an ENETUNREACH connection error. Fixes
1250 part of bug 10777; bugfix on 0.2.4.8-alpha.
1252 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1253 - Do not allow OpenSSL engines to replace the PRNG, even when
1254 HardwareAccel is set. The only default builtin PRNG engine uses
1255 the Intel RDRAND instruction to replace the entire PRNG, and
1256 ignores all attempts to seed it with more entropy. That's
1257 cryptographically stupid: the right response to a new alleged
1258 entropy source is never to discard all previously used entropy
1259 sources. Fixes bug 10402; works around behavior introduced in
1260 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1262 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1263 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1264 - Avoid launching spurious extra circuits when a stream is pending.
1265 This fixes a bug where any circuit that _wasn't_ unusable for new
1266 streams would be treated as if it were, causing extra circuits to
1267 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1269 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1270 - No longer stop reading or writing on cpuworker connections when
1271 our rate limiting buckets go empty. Now we should handle circuit
1272 handshake requests more promptly. Resolves bug 9731.
1273 - Stop trying to bootstrap all our directory information from
1274 only our first guard. Discovered while fixing bug 9946; bugfix
1277 o Minor features (bridges, pluggable transports):
1278 - Add threshold cutoffs to the networkstatus document created by
1279 the Bridge Authority. Fixes bug 1117.
1280 - On Windows, spawn background processes using the CREATE_NO_WINDOW
1281 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
1282 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
1283 Vidalia set this option for us.) Implements ticket 10297.
1285 o Minor features (security):
1286 - Always clear OpenSSL bignums before freeing them -- even bignums
1287 that don't contain secrets. Resolves ticket 10793. Patch by
1290 o Minor features (config options and command line):
1291 - Add an --allow-missing-torrc commandline option that tells Tor to
1292 run even if the configuration file specified by -f is not available.
1293 Implements ticket 10060.
1294 - Add support for the TPROXY transparent proxying facility on Linux.
1295 See documentation for the new TransProxyType option for more
1296 details. Implementation by "thomo". Closes ticket 10582.
1298 o Minor features (controller):
1299 - Add a new "HS_DESC" controller event that reports activities
1300 related to hidden service descriptors. Resolves ticket 8510.
1301 - New "DROPGUARDS" controller command to forget all current entry
1302 guards. Not recommended for ordinary use, since replacing guards
1303 too frequently makes several attacks easier. Resolves ticket 9934;
1306 o Minor features (build):
1307 - Assume that a user using ./configure --host wants to cross-compile,
1308 and give an error if we cannot find a properly named
1309 tool-chain. Add a --disable-tool-name-check option to proceed
1310 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
1311 - If we run ./configure and the compiler recognizes -fstack-protector
1312 but the linker rejects it, warn the user about a potentially missing
1313 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
1315 o Minor features (testing):
1316 - If Python is installed, "make check" now runs extra tests beyond
1317 the unit test scripts.
1318 - When bootstrapping a test network, sometimes very few relays get
1319 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
1320 specify a set of relays which should be voted Guard regardless of
1321 their uptime or bandwidth. Addresses ticket 9206.
1323 o Minor features (log messages):
1324 - When ServerTransportPlugin is set on a bridge, Tor can write more
1325 useful statistics about bridge use in its extrainfo descriptors,
1326 but only if the Extended ORPort ("ExtORPort") is set too. Add a
1327 log message to inform the user in this case. Resolves ticket 9651.
1328 - When receiving a new controller connection, log the origin address.
1329 Resolves ticket 9698; patch from "sigpipe".
1330 - When logging OpenSSL engine status at startup, log the status of
1331 more engines. Fixes ticket 10043; patch from Joshua Datko.
1332 - Turn "circuit handshake stats since last time" log messages into a
1333 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1335 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1336 - Improve the circuit queue out-of-memory handler. Previously, when
1337 we ran low on memory, we'd close whichever circuits had the most
1338 queued cells. Now, we close those that have the *oldest* queued
1339 cells, on the theory that those are most responsible for us
1340 running low on memory. Based on analysis from a forthcoming paper
1341 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1342 - Generate bootstrapping status update events correctly when fetching
1343 microdescriptors. Fixes bug 9927.
1344 - Update to the October 2 2013 Maxmind GeoLite Country database.
1346 o Minor bugfixes (clients):
1347 - When closing a channel that has already been open, do not close
1348 pending circuits that were waiting to connect to the same relay.
1349 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
1352 o Minor bugfixes (relays):
1353 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1354 exit node as a NOROUTE error, not an INTERNAL error, since they
1355 can apparently happen when trying to connect to the wrong sort
1356 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1358 o Minor bugfixes (bridges):
1359 - Fix a bug where the first connection works to a bridge that uses a
1360 pluggable transport with client-side parameters, but we don't send
1361 the client-side parameters on subsequent connections. (We don't
1362 use any pluggable transports with client-side parameters yet,
1363 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
1364 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
1366 o Minor bugfixes (node selection):
1367 - If ExcludeNodes is set, consider non-excluded hidden service
1368 directory servers before excluded ones. Do not consider excluded
1369 hidden service directory servers at all if StrictNodes is
1370 set. (Previously, we would sometimes decide to connect to those
1371 servers, and then realize before we initiated a connection that
1372 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
1374 - If we set the ExitNodes option but it doesn't include any nodes
1375 that have the Exit flag, we would choose not to bootstrap. Now we
1376 bootstrap so long as ExitNodes includes nodes which can exit to
1377 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
1379 o Minor bugfixes (controller and command-line):
1380 - If changing a config option via "setconf" fails in a recoverable
1381 way, we used to nonetheless write our new control ports to the
1382 file described by the "ControlPortWriteToFile" option. Now we only
1383 write out that file if we successfully switch to the new config
1384 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
1385 - When a command-line option such as --version or --help that
1386 ordinarily implies --hush appears on the command line along with
1387 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
1388 only if it appeared later on the command line. Fixes bug 9578;
1389 bugfix on 0.2.5.1-alpha.
1391 o Minor bugfixes (code correctness):
1392 - Previously we used two temporary files when writing descriptors to
1393 disk; now we only use one. Fixes bug 1376.
1394 - Remove an erroneous (but impossible and thus harmless) pointer
1395 comparison that would have allowed compilers to skip a bounds
1396 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
1397 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
1398 - Fix an always-true assertion in pluggable transports code so it
1399 actually checks what it was trying to check. Fixes bug 10046;
1400 bugfix on 0.2.3.9-alpha. Found by "dcb".
1402 o Minor bugfixes (protocol correctness):
1403 - When receiving a VERSIONS cell with an odd number of bytes, close
1404 the connection immediately since the cell is malformed. Fixes bug
1405 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
1408 o Minor bugfixes (build):
1409 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
1410 turned off (that is, without support for v2 link handshakes). Fixes
1411 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
1412 - Fix compilation warnings and startup issues when running with
1413 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
1415 - Fix compilation on Solaris 9, which didn't like us having an
1416 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
1418 o Minor bugfixes (testing):
1419 - Fix a segmentation fault in our benchmark code when running with
1420 Fedora's OpenSSL package, or any other OpenSSL that provides
1421 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1423 o Minor bugfixes (log messages):
1424 - Fix a bug where clients using bridges would report themselves
1425 as 50% bootstrapped even without a live consensus document.
1426 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
1427 - Suppress a warning where, if there's only one directory authority
1428 in the network, we would complain that votes and signatures cannot
1429 be uploaded to other directory authorities. Fixes bug 10842;
1430 bugfix on 0.2.2.26-beta.
1431 - Report bootstrapping progress correctly when we're downloading
1432 microdescriptors. We had updated our "do we have enough microdescs
1433 to begin building circuits?" logic most recently in 0.2.4.10-alpha
1434 (see bug 5956), but we left the bootstrap status event logic at
1435 "how far through getting 1/4 of them are we?" Fixes bug 9958;
1436 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
1438 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1439 - Avoid a crash bug when starting with a corrupted microdescriptor
1440 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1441 - If we fail to dump a previously cached microdescriptor to disk, avoid
1442 freeing duplicate data later on. Fixes bug 10423; bugfix on
1443 0.2.4.13-alpha. Spotted by "bobnomnom".
1445 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1446 - Correctly log long IPv6 exit policies, instead of truncating them
1447 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1448 - Our default TLS ecdhe groups were backwards: we meant to be using
1449 P224 for relays (for performance win) and P256 for bridges (since
1450 it is more common in the wild). Instead we had it backwards. After
1451 reconsideration, we decided that the default should be P256 on all
1452 hosts, since its security is probably better, and since P224 is
1453 reportedly used quite little in the wild. Found by "skruffy" on
1454 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1455 - Free directory authority certificate download statuses on exit
1456 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1458 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1459 - If the guard we choose first doesn't answer, we would try the
1460 second guard, but once we connected to the second guard we would
1461 abandon it and retry the first one, slowing down bootstrapping.
1462 The fix is to treat all our initially chosen guards as acceptable
1463 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1464 - Fix an assertion failure that would occur when disabling the
1465 ORPort setting on a running Tor process while accounting was
1466 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1467 - When examining the list of network interfaces to find our address,
1468 do not consider non-running or disabled network interfaces. Fixes
1469 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1470 - Avoid an off-by-one error when checking buffer boundaries when
1471 formatting the exit status of a pluggable transport helper.
1472 This is probably not an exploitable bug, but better safe than
1473 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1476 o Removed code and features:
1477 - Clients now reject any directory authority certificates lacking
1478 a dir-key-crosscert element. These have been included since
1479 0.2.1.9-alpha, so there's no real reason for them to be optional
1480 any longer. Completes proposal 157. Resolves ticket 10162.
1481 - Remove all code that existed to support the v2 directory system,
1482 since there are no longer any v2 directory authorities. Resolves
1484 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
1485 options, which were used for designating authorities as "Hidden
1486 service authorities". There has been no use of hidden service
1487 authorities since 0.2.2.1-alpha, when we stopped uploading or
1488 downloading v0 hidden service descriptors. Fixes bug 10881; also
1489 part of a fix for bug 10841.
1491 o Code simplification and refactoring:
1492 - Remove some old fallback code designed to keep Tor clients working
1493 in a network with only two working relays. Elsewhere in the code we
1494 have long since stopped supporting such networks, so there wasn't
1495 much point in keeping it around. Addresses ticket 9926.
1496 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
1497 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
1498 - Remove data structures which were introduced to implement the
1499 CellStatistics option: they are now redundant with the addition
1500 of a timestamp to the regular packed_cell_t data structure, which
1501 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
1504 o Documentation (man page) fixes:
1505 - Update manpage to describe some of the files you can expect to
1506 find in Tor's DataDirectory. Addresses ticket 9839.
1507 - Document that all but one DirPort entry must have the NoAdvertise
1508 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1510 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1511 - Clarify the usage and risks of setting the ContactInfo torrc line
1512 for your relay or bridge. Resolves ticket 9854.
1513 - Add anchors to the manpage so we can link to the html version of
1514 the documentation for specific options. Resolves ticket 9866.
1515 - Replace remaining references to DirServer in man page and
1516 log entries. Resolves ticket 10124.
1519 - Make the "tor-gencert" tool used by directory authority operators
1520 create 2048-bit signing keys by default (rather than 1024-bit, since
1521 1024-bit is uncomfortably small these days). Addresses ticket 10324.
1524 Changes in version 0.2.4.20 - 2013-12-22
1525 Tor 0.2.4.20 fixes potentially poor random number generation for users
1526 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
1527 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
1528 and 4) have no state file in their DataDirectory (as would happen on
1529 first start). Users who generated relay or hidden service identity
1530 keys in such a situation should discard them and generate new ones.
1532 This release also fixes a logic error that caused Tor clients to build
1533 many more preemptive circuits than they actually need.
1536 - Do not allow OpenSSL engines to replace the PRNG, even when
1537 HardwareAccel is set. The only default builtin PRNG engine uses
1538 the Intel RDRAND instruction to replace the entire PRNG, and
1539 ignores all attempts to seed it with more entropy. That's
1540 cryptographically stupid: the right response to a new alleged
1541 entropy source is never to discard all previously used entropy
1542 sources. Fixes bug 10402; works around behavior introduced in
1543 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1545 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1546 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1547 - Avoid launching spurious extra circuits when a stream is pending.
1548 This fixes a bug where any circuit that _wasn't_ unusable for new
1549 streams would be treated as if it were, causing extra circuits to
1550 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1553 - Avoid a crash bug when starting with a corrupted microdescriptor
1554 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1555 - If we fail to dump a previously cached microdescriptor to disk, avoid
1556 freeing duplicate data later on. Fixes bug 10423; bugfix on
1557 0.2.4.13-alpha. Spotted by "bobnomnom".
1560 Changes in version 0.2.4.19 - 2013-12-11
1561 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
1562 (1986-2013). Aaron worked on diverse projects including helping to guide
1563 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
1564 transparency to the U.S government's PACER documents, and contributing
1565 design and development for Tor and Tor2Web. Aaron was one of the latest
1566 martyrs in our collective fight for civil liberties and human rights,
1567 and his death is all the more painful because he was one of us.
1569 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
1570 a new circuit handshake and link encryption that use ECC to provide
1571 better security and efficiency; makes relays better manage circuit
1572 creation requests; uses "directory guards" to reduce client enumeration
1573 risks; makes bridges collect and report statistics about the pluggable
1574 transports they support; cleans up and improves our geoip database;
1575 gets much closer to IPv6 support for clients, bridges, and relays; makes
1576 directory authorities use measured bandwidths rather than advertised
1577 ones when computing flags and thresholds; disables client-side DNS
1578 caching to reduce tracking risks; and fixes a big bug in bridge
1579 reachability testing. This release introduces two new design
1580 abstractions in the code: a new "channel" abstraction between circuits
1581 and or_connections to allow for implementing alternate relay-to-relay
1582 transports, and a new "circuitmux" abstraction storing the queue of
1583 circuits for a channel. The release also includes many stability,
1584 security, and privacy fixes.
1587 Changes in version 0.2.4.18-rc - 2013-11-16
1588 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
1589 series. It takes a variety of fixes from the 0.2.5.x branch to improve
1590 stability, performance, and better handling of edge cases.
1593 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1594 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1595 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1596 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1597 them to solve bug 6033.)
1600 - No longer stop reading or writing on cpuworker connections when
1601 our rate limiting buckets go empty. Now we should handle circuit
1602 handshake requests more promptly. Resolves bug 9731.
1603 - If we are unable to save a microdescriptor to the journal, do not
1604 drop it from memory and then reattempt downloading it. Fixes bug
1605 9645; bugfix on 0.2.2.6-alpha.
1606 - Stop trying to bootstrap all our directory information from
1607 only our first guard. Discovered while fixing bug 9946; bugfix
1609 - The new channel code sometimes lost track of in-progress circuits,
1610 causing long-running clients to stop building new circuits. The
1611 fix is to always call circuit_n_chan_done(chan, 0) from
1612 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1614 o Minor bugfixes (on 0.2.4.x):
1615 - Correctly log long IPv6 exit policies, instead of truncating them
1616 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1617 - Our default TLS ecdhe groups were backwards: we meant to be using
1618 P224 for relays (for performance win) and P256 for bridges (since
1619 it is more common in the wild). Instead we had it backwards. After
1620 reconsideration, we decided that the default should be P256 on all
1621 hosts, since its security is probably better, and since P224 is
1622 reportedly used quite little in the wild. Found by "skruffy" on
1623 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1624 - Free directory authority certificate download statuses on exit
1625 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1627 o Minor bugfixes (on 0.2.3.x and earlier):
1628 - If the guard we choose first doesn't answer, we would try the
1629 second guard, but once we connected to the second guard we would
1630 abandon it and retry the first one, slowing down bootstrapping.
1631 The fix is to treat all our initially chosen guards as acceptable
1632 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1633 - Fix an assertion failure that would occur when disabling the
1634 ORPort setting on a running Tor process while accounting was
1635 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1636 - When examining the list of network interfaces to find our address,
1637 do not consider non-running or disabled network interfaces. Fixes
1638 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1639 - Avoid an off-by-one error when checking buffer boundaries when
1640 formatting the exit status of a pluggable transport helper.
1641 This is probably not an exploitable bug, but better safe than
1642 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1645 o Minor features (protecting client timestamps):
1646 - Clients no longer send timestamps in their NETINFO cells. These were
1647 not used for anything, and they provided one small way for clients
1648 to be distinguished from each other as they moved from network to
1649 network or behind NAT. Implements part of proposal 222.
1650 - Clients now round timestamps in INTRODUCE cells down to the nearest
1651 10 minutes. If a new Support022HiddenServices option is set to 0, or
1652 if it's set to "auto" and the feature is disabled in the consensus,
1653 the timestamp is sent as 0 instead. Implements part of proposal 222.
1654 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1655 a big deal from a security point of view, but it achieves no actual
1656 good purpose, and isn't needed. Implements part of proposal 222.
1657 - Reduce down accuracy of timestamps in hidden service descriptors.
1658 Implements part of proposal 222.
1660 o Minor features (other):
1661 - Improve the circuit queue out-of-memory handler. Previously, when
1662 we ran low on memory, we'd close whichever circuits had the most
1663 queued cells. Now, we close those that have the *oldest* queued
1664 cells, on the theory that those are most responsible for us
1665 running low on memory. Based on analysis from a forthcoming paper
1666 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1667 - Generate bootstrapping status update events correctly when fetching
1668 microdescriptors. Fixes bug 9927.
1669 - Update to the October 2 2013 Maxmind GeoLite Country database.
1671 o Documentation fixes:
1672 - Clarify the usage and risks of setting the ContactInfo torrc line
1673 for your relay or bridge. Resolves ticket 9854.
1674 - Add anchors to the manpage so we can link to the html version of
1675 the documentation for specific options. Resolves ticket 9866.
1676 - Replace remaining references to DirServer in man page and
1677 log entries. Resolves ticket 10124.
1680 Changes in version 0.2.5.1-alpha - 2013-10-02
1681 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
1682 on Linux, allows bridges that offer pluggable transports to report usage
1683 statistics, fixes many issues to make testing easier, and provides
1684 a pile of minor features and bugfixes that have been waiting for a
1685 release of the new branch.
1687 This is the first alpha release in a new series, so expect there to
1688 be bugs. Users who would rather test out a more stable branch should
1689 stay with 0.2.4.x for now.
1691 o Major features (security):
1692 - Use the seccomp2 syscall filtering facility on Linux to limit
1693 which system calls Tor can invoke. This is an experimental,
1694 Linux-only feature to provide defense-in-depth against unknown
1695 attacks. To try turning it on, set "Sandbox 1" in your torrc
1696 file. Please be ready to report bugs. We hope to add support
1697 for better sandboxing in the future, including more fine-grained
1698 filters, better division of responsibility, and support for more
1699 platforms. This work has been done by Cristian-Matei Toader for
1700 Google Summer of Code.
1701 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1702 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1703 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1704 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1705 them to solve bug 6033.)
1707 o Major features (other):
1708 - Add support for passing arguments to managed pluggable transport
1709 proxies. Implements ticket 3594.
1710 - Bridges now track GeoIP information and the number of their users
1711 even when pluggable transports are in use, and report usage
1712 statistics in their extra-info descriptors. Resolves tickets 4773
1714 - Make testing Tor networks bootstrap better: lower directory fetch
1715 retry schedules and maximum interval without directory requests,
1716 and raise maximum download tries. Implements ticket 6752.
1717 - Add make target 'test-network' to run tests on a Chutney network.
1718 Implements ticket 8530.
1719 - The ntor handshake is now on-by-default, no matter what the
1720 directory authorities recommend. Implements ticket 8561.
1723 - Instead of writing destroy cells directly to outgoing connection
1724 buffers, queue them and intersperse them with other outgoing cells.
1725 This can prevent a set of resource starvation conditions where too
1726 many pending destroy cells prevent data cells from actually getting
1727 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
1728 bugfix on 0.2.0.1-alpha.
1729 - If we are unable to save a microdescriptor to the journal, do not
1730 drop it from memory and then reattempt downloading it. Fixes bug
1731 9645; bugfix on 0.2.2.6-alpha.
1732 - The new channel code sometimes lost track of in-progress circuits,
1733 causing long-running clients to stop building new circuits. The
1734 fix is to always call circuit_n_chan_done(chan, 0) from
1735 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1738 - Tor now builds each source file in two modes: a mode that avoids
1739 exposing identifiers needlessly, and another mode that exposes
1740 more identifiers for testing. This lets the compiler do better at
1741 optimizing the production code, while enabling us to take more
1742 radical measures to let the unit tests test things.
1743 - The production builds no longer include functions used only in
1744 the unit tests; all functions exposed from a module only for
1745 unit-testing are now static in production builds.
1746 - Add an --enable-coverage configuration option to make the unit
1747 tests (and a new src/or/tor-cov target) to build with gcov test
1751 - We now have rudimentary function mocking support that our unit
1752 tests can use to test functions in isolation. Function mocking
1753 lets the tests temporarily replace a function's dependencies with
1754 stub functions, so that the tests can check the function without
1755 invoking the other functions it calls.
1756 - Add more unit tests for the <circid,channel>->circuit map, and
1757 the destroy-cell-tracking code to fix bug 7912.
1758 - Unit tests for failing cases of the TAP onion handshake.
1759 - More unit tests for address-manipulation functions.
1761 o Minor features (protecting client timestamps):
1762 - Clients no longer send timestamps in their NETINFO cells. These were
1763 not used for anything, and they provided one small way for clients
1764 to be distinguished from each other as they moved from network to
1765 network or behind NAT. Implements part of proposal 222.
1766 - Clients now round timestamps in INTRODUCE cells down to the nearest
1767 10 minutes. If a new Support022HiddenServices option is set to 0, or
1768 if it's set to "auto" and the feature is disabled in the consensus,
1769 the timestamp is sent as 0 instead. Implements part of proposal 222.
1770 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1771 a big deal from a security point of view, but it achieves no actual
1772 good purpose, and isn't needed. Implements part of proposal 222.
1773 - Reduce down accuracy of timestamps in hidden service descriptors.
1774 Implements part of proposal 222.
1776 o Minor features (config options):
1777 - Config (torrc) lines now handle fingerprints which are missing
1778 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
1779 - Support a --dump-config option to print some or all of the
1780 configured options. Mainly useful for debugging the command-line
1781 option parsing code. Helps resolve ticket 4647.
1782 - Raise awareness of safer logging: notify user of potentially
1783 unsafe config options, like logging more verbosely than severity
1784 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
1785 - Add a new configuration option TestingV3AuthVotingStartOffset
1786 that bootstraps a network faster by changing the timing for
1787 consensus votes. Addresses ticket 8532.
1788 - Add a new torrc option "ServerTransportOptions" that allows
1789 bridge operators to pass configuration parameters to their
1790 pluggable transports. Resolves ticket 8929.
1791 - The config (torrc) file now accepts bandwidth and space limits in
1792 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
1793 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
1796 o Minor features (build):
1797 - Add support for `--library-versions` flag. Implements ticket 6384.
1798 - Return the "unexpected sendme" warnings to a warn severity, but make
1799 them rate limited, to help diagnose ticket 8093.
1800 - Detect a missing asciidoc, and warn the user about it, during
1801 configure rather than at build time. Fixes issue 6506. Patch from
1804 o Minor features (other):
1805 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
1806 sockets in a single system call. Implements ticket 5129.
1807 - Log current accounting state (bytes sent and received + remaining
1808 time for the current accounting period) in the relay's heartbeat
1809 message. Implements ticket 5526; patch from Peter Retzlaff.
1810 - Implement the TRANSPORT_LAUNCHED control port event that
1811 notifies controllers about new launched pluggable
1812 transports. Resolves ticket 5609.
1813 - If we're using the pure-C 32-bit curve25519_donna implementation
1814 of curve25519, build it with the -fomit-frame-pointer option to
1815 make it go faster on register-starved hosts. This improves our
1816 handshake performance by about 6% on i386 hosts without nacl.
1818 - Update to the September 4 2013 Maxmind GeoLite Country database.
1821 - Set the listen() backlog limit to the largest actually supported
1822 on the system, not to the value in a header file. Fixes bug 9716;
1823 bugfix on every released Tor.
1824 - No longer accept malformed http headers when parsing urls from
1825 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
1826 bugfix on 0.0.6pre1.
1827 - In munge_extrainfo_into_routerinfo(), check the return value of
1828 memchr(). This would have been a serious issue if we ever passed
1829 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
1831 - On the chance that somebody manages to build Tor on a
1832 platform where time_t is unsigned, correct the way that
1833 microdesc_add_to_cache() handles negative time arguments.
1834 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
1835 - Reject relative control socket paths and emit a warning. Previously,
1836 single-component control socket paths would be rejected, but Tor
1837 would not log why it could not validate the config. Fixes bug 9258;
1838 bugfix on 0.2.3.16-alpha.
1840 o Minor bugfixes (command line):
1841 - Use a single command-line parser for parsing torrc options on the
1842 command line and for finding special command-line options to avoid
1843 inconsistent behavior for torrc option arguments that have the same
1844 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
1846 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
1847 9573; bugfix on 0.0.9pre5.
1849 o Minor fixes (build, auxiliary programs):
1850 - Stop preprocessing the "torify" script with autoconf, since
1851 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
1853 - The tor-fw-helper program now follows the standard convention and
1854 exits with status code "0" on success. Fixes bug 9030; bugfix on
1855 0.2.3.1-alpha. Patch by Arlo Breault.
1856 - Corrected ./configure advice for what openssl dev package you should
1857 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
1859 o Minor code improvements:
1860 - Remove constants and tests for PKCS1 padding; it's insecure and
1861 shouldn't be used for anything new. Fixes bug 8792; patch
1863 - Remove instances of strcpy() from the unit tests. They weren't
1864 hurting anything, since they were only in the unit tests, but it's
1865 embarassing to have strcpy() in the code at all, and some analysis
1866 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
1867 0.2.3.8-alpha. Patch from Arlo Breault.
1870 - Remove migration code from when we renamed the "cached-routers"
1871 file to "cached-descriptors" back in 0.2.0.8-alpha. This
1872 incidentally resolves ticket 6502 by cleaning up the related code
1873 a bit. Patch from Akshay Hebbar.
1875 o Code simplification and refactoring:
1876 - Extract the common duplicated code for creating a subdirectory
1877 of the data directory and writing to a file in it. Fixes ticket
1878 4282; patch from Peter Retzlaff.
1879 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
1880 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
1881 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
1882 - Add a set of accessor functions for the circuit timeout data
1883 structure. Fixes ticket 6153; patch from "piet".
1884 - Clean up exit paths from connection_listener_new(). Closes ticket
1885 8789. Patch from Arlo Breault.
1886 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
1887 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
1888 - Use a doubly-linked list to implement the global circuit list.
1889 Resolves ticket 9108. Patch from Marek Majkowski.
1890 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
1893 Changes in version 0.2.4.17-rc - 2013-09-05
1894 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
1895 series. It adds an emergency step to help us tolerate the massive
1896 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
1897 circuit-level handshakes now effectively jump the queue compared to
1898 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
1899 big bug hindering bridge reachability tests.
1902 - Relays now process the new "NTor" circuit-level handshake requests
1903 with higher priority than the old "TAP" circuit-level handshake
1904 requests. We still process some TAP requests to not totally starve
1905 0.2.3 clients when NTor becomes popular. A new consensus parameter
1906 "NumNTorsPerTAP" lets us tune the balance later if we need to.
1907 Implements ticket 9574.
1910 - If the circuit build timeout logic is disabled (via the consensus,
1911 or because we are an authority), then don't build testing circuits.
1912 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
1913 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
1914 previously they did not, which prevented them from receiving
1915 successful connections from relays for self-test or bandwidth
1916 testing. Also, when a relay is extending a circuit to a bridge,
1917 it needs to send a NETINFO cell, even when the bridge hasn't sent
1918 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
1919 - If the time to download the next old-style networkstatus is in
1920 the future, do not decline to consider whether to download the
1921 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
1925 - Avoid double-closing the listener socket in our socketpair()
1926 replacement (used on Windows) in the case where the addresses on
1927 our opened sockets don't match what we expected. Fixes bug 9400;
1928 bugfix on 0.0.2pre7. Found by Coverity.
1930 o Minor fixes (config options):
1931 - Avoid overflows when the user sets MaxCircuitDirtiness to a
1932 ridiculously high value, by imposing a (ridiculously high) 30-day
1933 maximum on MaxCircuitDirtiness.
1934 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
1935 message is logged at notice, not at info.
1936 - Warn and fail if a server is configured not to advertise any
1937 ORPorts at all. (We need *something* to put in our descriptor,
1938 or we just won't work.)
1941 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1942 and how many we complete, and log it every hour to help relay
1943 operators follow trends in network load. Addresses ticket 9658.
1944 - Update to the August 7 2013 Maxmind GeoLite Country database.
1947 Changes in version 0.2.4.16-rc - 2013-08-10
1948 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
1949 series. It fixes several crash bugs in the 0.2.4 branch.
1952 - Fix a bug in the voting algorithm that could yield incorrect results
1953 when a non-naming authority declared too many flags. Fixes bug 9200;
1954 bugfix on 0.2.0.3-alpha.
1955 - Fix an uninitialized read that could in some cases lead to a remote
1956 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
1957 Anybody running a hidden service on the experimental 0.2.4.x
1958 branch should upgrade. (This is, so far as we know, unrelated to
1960 - Avoid an assertion failure when processing DNS replies without the
1961 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
1962 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
1963 0.2.4.15-rc. Found by stem integration tests.
1966 - Fix an invalid memory read that occured when a pluggable
1967 transport proxy failed its configuration protocol.
1968 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
1969 - When evaluating whether to use a connection that we haven't
1970 decided is canonical using a recent link protocol version,
1971 decide that it's canonical only if it used address _does_
1972 match the desired address. Fixes bug 9309; bugfix on
1973 0.2.4.4-alpha. Reported by skruffy.
1974 - Make the default behavior of NumDirectoryGuards be to track
1975 NumEntryGuards. Now a user who changes only NumEntryGuards will get
1976 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
1977 - Fix a spurious compilation warning with some older versions of
1978 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
1981 - Update to the July 3 2013 Maxmind GeoLite Country database.
1984 Changes in version 0.2.4.15-rc - 2013-07-01
1985 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
1986 series. It fixes a few smaller bugs, but generally appears stable.
1987 Please test it and let us know whether it is!
1990 - When receiving a new configuration file via the control port's
1991 LOADCONF command, do not treat the defaults file as absent.
1992 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1995 - Issue a warning when running with the bufferevents backend enabled.
1996 It's still not stable, and people should know that they're likely
1997 to hit unexpected problems. Closes ticket 9147.
2000 Changes in version 0.2.4.14-alpha - 2013-06-18
2001 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
2002 present in 0.2.4.13-alpha.
2005 - When we have too much memory queued in circuits (according to a new
2006 MaxMemInCellQueues option), close the circuits consuming the most
2007 memory. This prevents us from running out of memory as a relay if
2008 circuits fill up faster than they can be drained. Fixes bug 9063;
2009 bugfix on the 54th commit of Tor. This bug is a further fix beyond
2010 bug 6252, whose fix was merged into 0.2.3.21-rc.
2012 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
2013 where we tried to solve this issue simply by imposing an upper limit
2014 on the number of queued cells for a single circuit. That approach
2015 proved to be problematic, since there are ways to provoke clients to
2016 send a number of cells in excess of any such reasonable limit. Fixes
2017 bug 9072; bugfix on 0.2.4.13-alpha.
2019 - Limit hidden service descriptors to at most ten introduction
2020 points, to slow one kind of guard enumeration. Fixes bug 9002;
2021 bugfix on 0.1.1.11-alpha.
2024 Changes in version 0.2.4.13-alpha - 2013-06-14
2025 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
2026 vulnerabilities, makes socks5 username/password circuit isolation
2027 actually actually work (this time for sure!), and cleans up a bunch
2028 of other issues in preparation for a release candidate.
2030 o Major bugfixes (robustness):
2031 - Close any circuit that has too many cells queued on it. Fixes
2032 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
2033 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
2034 - Prevent the get_freelists() function from running off the end of
2035 the list of freelists if it somehow gets an unrecognized
2036 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
2038 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
2039 when an exit connection with optimistic data succeeds immediately
2040 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
2042 - Fix a directory authority crash bug when building a consensus
2043 using an older consensus as its basis. Fixes bug 8833. Bugfix
2047 - Avoid a memory leak where we would leak a consensus body when we
2048 find that a consensus which we couldn't previously verify due to
2049 missing certificates is now verifiable. Fixes bug 8719; bugfix
2051 - We used to always request authority certificates by identity digest,
2052 meaning we'd get the newest one even when we wanted one with a
2053 different signing key. Then we would complain about being given
2054 a certificate we already had, and never get the one we really
2055 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
2056 resource to request the one we want. Fixes bug 5595; bugfix on
2058 - Follow the socks5 protocol when offering username/password
2059 authentication. The fix for bug 8117 exposed this bug, and it
2060 turns out real-world applications like Pidgin do care. Bugfix on
2061 0.2.3.2-alpha; fixes bug 8879.
2062 - Prevent failures on Windows Vista and later when rebuilding the
2063 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
2064 bugfix on 0.2.4.12-alpha.
2067 - Fix an impossible buffer overrun in the AES unit tests. Fixes
2068 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
2069 - If for some reason we fail to write a microdescriptor while
2070 rebuilding the cache, do not let the annotations from that
2071 microdescriptor linger in the cache file, and do not let the
2072 microdescriptor stay recorded as present in its old location.
2073 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
2074 - Fix a memory leak that would occur whenever a configuration
2075 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
2076 - Paste the description for PathBias parameters from the man
2077 page into or.h, so the code documents them too. Fixes bug 7982;
2078 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
2079 - Relays now treat a changed IPv6 ORPort as sufficient reason to
2080 publish an updated descriptor. Fixes bug 6026; bugfix on
2082 - When launching a resolve request on behalf of an AF_UNIX control
2083 socket, omit the address field of the new entry connection, used in
2084 subsequent controller events, rather than letting tor_dup_addr()
2085 set it to "<unknown address type>". Fixes bug 8639; bugfix on
2088 o Minor bugfixes (log messages):
2089 - Fix a scaling issue in the path bias accounting code that
2090 resulted in "Bug:" log messages from either
2091 pathbias_scale_close_rates() or pathbias_count_build_success().
2092 This represents a bugfix on a previous bugfix: the original fix
2093 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
2095 - Give a less useless error message when the user asks for an IPv4
2096 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
2100 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
2101 to tolerate bug 8093 for now.
2102 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
2103 in directory authority votes to describe whether they have enough
2104 measured bandwidths to ignore advertised (relay descriptor)
2105 bandwidth claims. Resolves ticket 8711.
2106 - Update to the June 5 2013 Maxmind GeoLite Country database.
2108 o Removed documentation:
2109 - Remove some of the older contents of doc/ as obsolete; move others
2110 to torspec.git. Fixes bug 8965.
2112 o Code simplification and refactoring:
2113 - Avoid using character buffers when constructing most directory
2114 objects: this approach was unwieldy and error-prone. Instead,
2115 build smartlists of strings, and concatenate them when done.
2118 Changes in version 0.2.4.12-alpha - 2013-04-18
2119 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
2120 process for lengthening the guard rotation period, makes directory
2121 authority opinions in the consensus a bit less gameable, makes socks5
2122 username/password circuit isolation actually work, and fixes a wide
2123 variety of other issues.
2126 - Raise the default time that a client keeps an entry guard from
2127 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
2128 2012 paper. (We would make it even longer, but we need better client
2129 load balancing first.) Also, make the guard lifetime controllable
2130 via a new GuardLifetime torrc option and a GuardLifetime consensus
2131 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
2132 - Directory authorities now prefer using measured bandwidths to
2133 advertised ones when computing flags and thresholds. Resolves
2135 - Directory authorities that have more than a threshold number
2136 of relays with measured bandwidths now treat relays with unmeasured
2137 bandwidths as having bandwidth 0. Resolves ticket 8435.
2139 o Major bugfixes (assert / resource use):
2140 - Avoid a bug where our response to TLS renegotiation under certain
2141 network conditions could lead to a busy-loop, with 100% CPU
2142 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
2143 - Avoid an assertion when we discover that we'd like to write a cell
2144 onto a closing connection: just discard the cell. Fixes another
2145 case of bug 7350; bugfix on 0.2.4.4-alpha.
2147 o Major bugfixes (client-side privacy):
2148 - When we mark a circuit as unusable for new circuits, have it
2149 continue to be unusable for new circuits even if MaxCircuitDirtiness
2150 is increased too much at the wrong time, or the system clock jumps
2151 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
2152 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
2153 which have resolved to internal addresses") is set, apply that
2154 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
2155 - When an exit relay rejects a stream with reason "exit policy", but
2156 we only know an exit policy summary (e.g. from the microdesc
2157 consensus) for it, do not mark the relay as useless for all exiting.
2158 Instead, mark just the circuit as unsuitable for that particular
2159 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
2160 - Allow applications to get proper stream isolation with
2161 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
2162 username/password authentication also offer "no authentication". Tor
2163 had previously preferred "no authentication", so the applications
2164 never actually sent Tor their auth details. Now Tor selects
2165 username/password authentication if it's offered. You can disable
2166 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
2167 bug 8117; bugfix on 0.2.3.3-alpha.
2169 o Major bugfixes (other):
2170 - When unable to find any working directory nodes to use as a
2171 directory guard, give up rather than adding the same non-working
2172 nodes to the directory guard list over and over. Fixes bug 8231;
2173 bugfix on 0.2.4.8-alpha.
2176 - Reject as invalid most directory objects containing a NUL.
2177 Belt-and-suspender fix for bug 8037.
2178 - In our testsuite, create temporary directories with a bit more
2179 entropy in their name to make name collisions less likely. Fixes
2181 - Add CACHED keyword to ADDRMAP events in the control protocol
2182 to indicate whether a DNS result will be cached or not. Resolves
2184 - Update to the April 3 2013 Maxmind GeoLite Country database.
2186 o Minor features (build):
2187 - Detect and reject attempts to build Tor with threading support
2188 when OpenSSL has been compiled without threading support.
2190 - Clarify that when autoconf is checking for nacl, it is checking
2191 specifically for nacl with a fast curve25519 implementation.
2193 - Warn if building on a platform with an unsigned time_t: there
2194 are too many places where Tor currently assumes that time_t can
2195 hold negative values. We'd like to fix them all, but probably
2198 o Minor bugfixes (build):
2199 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
2200 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
2201 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
2202 - Add the old src/or/micro-revision.i filename to CLEANFILES.
2203 On the off chance that somebody has one, it will go away as soon
2204 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
2205 - Build Tor correctly on 32-bit platforms where the compiler can build
2206 but not run code using the "uint128_t" construction. Fixes bug 8587;
2207 bugfix on 0.2.4.8-alpha.
2208 - Fix compilation warning with some versions of clang that would
2209 prefer the -Wswitch-enum compiler flag to warn about switch
2210 statements with missing enum values, even if those switch
2211 statements have a "default:" statement. Fixes bug 8598; bugfix
2214 o Minor bugfixes (protocol):
2215 - Fix the handling of a TRUNCATE cell when it arrives while the
2216 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
2217 - Fix a misframing issue when reading the version numbers in a
2218 VERSIONS cell. Previously we would recognize [00 01 00 02] as
2219 'version 1, version 2, and version 0x100', when it should have
2220 only included versions 1 and 2. Fixes bug 8059; bugfix on
2221 0.2.0.10-alpha. Reported pseudonymously.
2222 - Make the format and order of STREAM events for DNS lookups
2223 consistent among the various ways to launch DNS lookups. Fixes
2224 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
2225 - Correct our check for which versions of Tor support the EXTEND2
2226 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
2227 later, when support was really added in version 0.2.4.8-alpha.
2228 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
2230 o Minor bugfixes (other):
2231 - Correctly store microdescriptors and extrainfo descriptors with
2232 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
2233 Bug reported by "cypherpunks".
2234 - Increase the width of the field used to remember a connection's
2235 link protocol version to two bytes. Harmless for now, since the
2236 only currently recognized versions are one byte long. Reported
2237 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
2238 - If the state file's path bias counts are invalid (presumably from a
2239 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
2240 additional checks and log messages to the scaling of Path Bias
2241 counts, in case there still are remaining issues with scaling.
2242 Should help resolve bug 8235.
2243 - Eliminate several instances where we use "Nickname=ID" to refer to
2244 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
2245 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
2246 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
2248 o Minor bugfixes (syscalls):
2249 - Always check the return values of functions fcntl() and
2250 setsockopt(). We don't believe these are ever actually failing in
2251 practice, but better safe than sorry. Also, checking these return
2252 values should please analysis tools like Coverity. Patch from
2253 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
2254 - Use direct writes rather than stdio when building microdescriptor
2255 caches, in an attempt to mitigate bug 8031, or at least make it
2258 o Minor bugfixes (config):
2259 - When rejecting a configuration because we were unable to parse a
2260 quoted string, log an actual error message. Fixes bug 7950; bugfix
2262 - Behave correctly when the user disables LearnCircuitBuildTimeout
2263 but doesn't tell us what they would like the timeout to be. Fixes
2264 bug 6304; bugfix on 0.2.2.14-alpha.
2265 - When autodetecting the number of CPUs, use the number of available
2266 CPUs in preference to the number of configured CPUs. Inform the
2267 user if this reduces the number of available CPUs. Fixes bug 8002;
2268 bugfix on 0.2.3.1-alpha.
2269 - Make it an error when you set EntryNodes but disable UseGuardNodes,
2270 since it will (surprisingly to some users) ignore EntryNodes. Fixes
2271 bug 8180; bugfix on 0.2.3.11-alpha.
2272 - Allow TestingTorNetworks to override the 4096-byte minimum for
2273 the Fast threshold. Otherwise they can't bootstrap until they've
2274 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
2275 - Fix some logic errors when the user manually overrides the
2276 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
2279 o Minor bugfixes (log messages to help diagnose bugs):
2280 - If we fail to free a microdescriptor because of bug 7164, log
2281 the filename and line number from which we tried to free it.
2282 - Add another diagnostic to the heartbeat message: track and log
2283 overhead that TLS is adding to the data we write. If this is
2284 high, we are sending too little data to SSL_write at a time.
2285 Diagnostic for bug 7707.
2286 - Add more detail to a log message about relaxed timeouts, to help
2288 - Warn more aggressively when flushing microdescriptors to a
2289 microdescriptor cache fails, in an attempt to mitigate bug 8031,
2290 or at least make it more diagnosable.
2291 - Improve debugging output to help track down bug 8185 ("Bug:
2292 outgoing relay cell has n_chan==NULL. Dropping.")
2293 - Log the purpose of a path-bias testing circuit correctly.
2294 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
2296 o Minor bugfixes (0.2.4.x log messages that were too noisy):
2297 - Don't attempt to relax the timeout of already opened 1-hop circuits.
2298 They might never timeout. This should eliminate some/all cases of
2299 the relaxed timeout log message.
2300 - Use circuit creation time for network liveness evaluation. This
2301 should eliminate warning log messages about liveness caused
2302 by changes in timeout evaluation. Fixes bug 6572; bugfix on
2304 - Reduce a path bias length check from notice to info. The message
2305 is triggered when creating controller circuits. Fixes bug 8196;
2306 bugfix on 0.2.4.8-alpha.
2307 - Fix a path state issue that triggered a notice during relay startup.
2308 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
2309 - Reduce occurrences of warns about circuit purpose in
2310 connection_ap_expire_building(). Fixes bug 8477; bugfix on
2313 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
2314 - If we encounter a write failure on a SOCKS connection before we
2315 finish our SOCKS handshake, don't warn that we closed the
2316 connection before we could send a SOCKS reply. Fixes bug 8427;
2317 bugfix on 0.1.0.1-rc.
2318 - Correctly recognize that [::1] is a loopback address. Fixes
2319 bug 8377; bugfix on 0.2.1.3-alpha.
2320 - Fix a directory authority warn caused when we have a large amount
2321 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
2322 - Don't log inappropriate heartbeat messages when hibernating: a
2323 hibernating node is _expected_ to drop out of the consensus,
2324 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
2325 bugfix on 0.2.3.1-alpha.
2326 - Don't complain about bootstrapping problems while hibernating.
2327 These complaints reflect a general code problem, but not one
2328 with any problematic effects (no connections are actually
2329 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
2331 o Documentation fixes:
2332 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
2333 names match. Fixes bug 7768.
2334 - Make the torify manpage no longer refer to tsocks; torify hasn't
2335 supported tsocks since 0.2.3.14-alpha.
2336 - Make the tor manpage no longer reference tsocks.
2337 - Fix the GeoIPExcludeUnknown documentation to refer to
2338 ExcludeExitNodes rather than the currently nonexistent
2339 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
2342 - The tor-tsocks.conf is no longer distributed or installed. We
2343 recommend that tsocks users use torsocks instead. Resolves
2347 Changes in version 0.2.4.11-alpha - 2013-03-11
2348 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
2349 more robust, makes hidden service authentication work again, and
2350 resolves a DPI fingerprint for Tor's SSL transport.
2352 o Major features (directory authorities):
2353 - Directory authorities now support a new consensus method (17)
2354 where they cap the published bandwidth of servers for which
2355 insufficient bandwidth measurements exist. Fixes part of bug 2286.
2356 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
2357 serve any v2 directory information. Now we can test disabling the
2358 old deprecated v2 directory format, and see whether doing so has
2359 any effect on network load. Begins to fix bug 6783.
2360 - Directory authorities now include inside each vote a statement of
2361 the performance thresholds they used when assigning flags.
2362 Implements ticket 8151.
2364 o Major bugfixes (directory authorities):
2365 - Stop marking every relay as having been down for one hour every
2366 time we restart a directory authority. These artificial downtimes
2367 were messing with our Stable and Guard flag calculations. Fixes
2368 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
2370 o Major bugfixes (hidden services):
2371 - Allow hidden service authentication to succeed again. When we
2372 refactored the hidden service introduction code back
2373 in 0.2.4.1-alpha, we didn't update the code that checks
2374 whether authentication information is present, causing all
2375 authentication checks to return "false". Fix for bug 8207; bugfix
2376 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
2378 o Minor features (relays, bridges):
2379 - Make bridge relays check once a minute for whether their IP
2380 address has changed, rather than only every 15 minutes. Resolves
2382 - Refactor resolve_my_address() so it returns the method by which we
2383 decided our public IP address (explicitly configured, resolved from
2384 explicit hostname, guessed from interfaces, learned by gethostname).
2385 Now we can provide more helpful log messages when a relay guesses
2386 its IP address incorrectly (e.g. due to unexpected lines in
2387 /etc/hosts). Resolves ticket 2267.
2388 - Teach bridge-using clients to avoid 0.2.2 bridges when making
2389 microdescriptor-related dir requests, and only fall back to normal
2390 descriptors if none of their bridges can handle microdescriptors
2391 (as opposed to the fix in ticket 4013, which caused them to fall
2392 back to normal descriptors if *any* of their bridges preferred
2393 them). Resolves ticket 4994.
2394 - Randomize the lifetime of our SSL link certificate, so censors can't
2395 use the static value for filtering Tor flows. Resolves ticket 8443;
2396 related to ticket 4014 which was included in 0.2.2.33.
2397 - Support a new version of the link protocol that allows 4-byte circuit
2398 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
2399 a possible resource exhaustion issue. Closes ticket 7351; implements
2402 o Minor features (portability):
2403 - Tweak the curve25519-donna*.c implementations to tolerate systems
2404 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
2405 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
2406 the signs of types during autoconf. This is better than our old
2407 approach, which didn't work when cross-compiling.
2408 - Detect the sign of enum values, rather than assuming that MSC is the
2409 only compiler where enum types are all signed. Fixes bug 7727;
2410 bugfix on 0.2.4.10-alpha.
2412 o Minor features (other):
2413 - Say "KBytes" rather than "KB" in the man page (for various values
2414 of K), to further reduce confusion about whether Tor counts in
2415 units of memory or fractions of units of memory. Resolves ticket 7054.
2416 - Clear the high bit on curve25519 public keys before passing them to
2417 our backend, in case we ever wind up using a backend that doesn't do
2418 so itself. If we used such a backend, and *didn't* clear the high bit,
2419 we could wind up in a situation where users with such backends would
2420 be distinguishable from users without. Fixes bug 8121; bugfix on
2422 - Update to the March 6 2013 Maxmind GeoLite Country database.
2424 o Minor bugfixes (clients):
2425 - When we receive a RELAY_END cell with the reason DONE, or with no
2426 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
2427 status as "connection refused". Previously we reported these cases
2428 as success but then immediately closed the connection. Fixes bug
2429 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
2430 - Downgrade an assertion in connection_ap_expire_beginning to an
2431 LD_BUG message. The fix for bug 8024 should prevent this message
2432 from displaying, but just in case, a warn that we can diagnose
2433 is better than more assert crashes. Fixes bug 8065; bugfix on
2435 - Lower path use bias thresholds to .80 for notice and .60 for warn.
2436 Also make the rate limiting flags for the path use bias log messages
2437 independent from the original path bias flags. Fixes bug 8161;
2438 bugfix on 0.2.4.10-alpha.
2440 o Minor bugfixes (relays):
2441 - Stop trying to resolve our hostname so often (e.g. every time we
2442 think about doing a directory fetch). Now we reuse the cached
2443 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
2444 and 2410 (bugfix on 0.1.2.2-alpha).
2445 - Stop sending a stray "(null)" in some cases for the server status
2446 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
2448 - When choosing which stream on a formerly stalled circuit to wake
2449 first, make better use of the platform's weak RNG. Previously,
2450 we had been using the % ("modulo") operator to try to generate a
2451 1/N chance of picking each stream, but this behaves badly with
2452 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
2454 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
2455 Irix's random() only return 15 bits; Solaris's random() returns more
2456 bits but its RAND_MAX says it only returns 15, and so on. Motivated
2457 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
2459 o Minor bugfixes (directory authorities):
2460 - Directory authorities now use less space when formatting identical
2461 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
2464 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
2465 - Avoid leaking memory if we fail to compute a consensus signature
2466 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
2467 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
2469 - Fix a memory leak during safe-cookie controller authentication.
2470 Bugfix on 0.2.3.13-alpha.
2471 - Avoid memory leak of IPv6 policy content if we fail to format it into
2472 a router descriptor. Bugfix on 0.2.4.7-alpha.
2474 o Minor bugfixes (other code correctness issues):
2475 - Avoid a crash if we fail to generate an extrainfo descriptor.
2476 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
2478 - When detecting the largest possible file descriptor (in order to
2479 close all file descriptors when launching a new program), actually
2480 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
2481 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
2483 - Fix a copy-and-paste error when adding a missing A1 to a routerset
2484 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
2485 Bugfix on 0.2.4.10-alpha.
2486 - Fix an impossible-to-trigger integer overflow when estimating how
2487 long our onionskin queue would take. (This overflow would require us
2488 to accept 4 million onionskins before processing 100 of them.) Fixes
2489 bug 8210; bugfix on 0.2.4.10-alpha.
2491 o Code simplification and refactoring:
2492 - Add a wrapper function for the common "log a message with a
2496 Changes in version 0.2.4.10-alpha - 2013-02-04
2497 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
2498 certain attacks that flood the network with relays; changes the queue
2499 for circuit create requests from a sized-based limit to a time-based
2500 limit; resumes building with MSVC on Windows; and fixes a wide variety
2503 o Major bugfixes (directory authority):
2504 - When computing directory thresholds, ignore any rejected-as-sybil
2505 nodes during the computation so that they can't influence Fast,
2506 Guard, etc. (We should have done this for proposal 109.) Fixes
2508 - When marking a node as a likely sybil, reset its uptime metrics
2509 to zero, so that it cannot time towards getting marked as Guard,
2510 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
2514 - When a TLS write is partially successful but incomplete, remember
2515 that the flushed part has been flushed, and notice that bytes were
2516 actually written. Reported and fixed pseudonymously. Fixes bug
2517 7708; bugfix on Tor 0.1.0.5-rc.
2518 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
2519 ID: these could be used to create unexpected streams and circuits
2520 which would count as "present" to some parts of Tor but "absent"
2521 to others, leading to zombie circuits and streams or to a bandwidth
2522 denial-of-service. Fixes bug 7889; bugfix on every released version
2523 of Tor. Reported by "oftc_must_be_destroyed".
2524 - Rename all macros in our local copy of queue.h to begin with "TOR_".
2525 This change seems the only good way to permanently prevent conflicts
2526 with queue.h on various operating systems. Fixes bug 8107; bugfix
2529 o Major features (relay):
2530 - Instead of limiting the number of queued onionskins (aka circuit
2531 create requests) to a fixed, hard-to-configure number, we limit
2532 the size of the queue based on how many we expect to be able to
2533 process in a given amount of time. We estimate the time it will
2534 take to process an onionskin based on average processing time
2535 of previous onionskins. Closes ticket 7291. You'll never have to
2536 configure MaxOnionsPending again.
2538 o Major features (portability):
2539 - Resume building correctly with MSVC and Makefile.nmake. This patch
2540 resolves numerous bugs and fixes reported by ultramage, including
2541 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
2542 - Make the ntor and curve25519 code build correctly with MSVC.
2543 Fix on 0.2.4.8-alpha.
2546 - When directory authorities are computing thresholds for flags,
2547 never let the threshold for the Fast flag fall below 4096
2548 bytes. Also, do not consider nodes with extremely low bandwidths
2549 when deciding thresholds for various directory flags. This change
2550 should raise our threshold for Fast relays, possibly in turn
2551 improving overall network performance; see ticket 1854. Resolves
2553 - The Tor client now ignores sub-domain components of a .onion
2554 address. This change makes HTTP "virtual" hosting
2555 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
2556 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
2557 hosted on the same hidden service. Implements proposal 204.
2558 - We compute the overhead from passing onionskins back and forth to
2559 cpuworkers, and report it when dumping statistics in response to
2560 SIGUSR1. Supports ticket 7291.
2562 o Minor features (path selection):
2563 - When deciding whether we have enough descriptors to build circuits,
2564 instead of looking at raw relay counts, look at which fraction
2565 of (bandwidth-weighted) paths we're able to build. This approach
2566 keeps clients from building circuits if their paths are likely to
2567 stand out statistically. The default fraction of paths needed is
2568 taken from the consensus directory; you can override it with the
2569 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
2570 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
2571 and we have GeoIP information, also exclude all nodes with unknown
2572 countries "??" and "A1". This behavior is controlled by the
2573 new GeoIPExcludeUnknown option: you can make such nodes always
2574 excluded with "GeoIPExcludeUnknown 1", and disable the feature
2575 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
2576 gets you the default behavior. Implements feature 7706.
2577 - Path Use Bias: Perform separate accounting for successful circuit
2578 use. Keep separate statistics on stream attempt rates versus stream
2579 success rates for each guard. Provide configurable thresholds to
2580 determine when to emit log messages or disable use of guards that
2581 fail too many stream attempts. Resolves ticket 7802.
2583 o Minor features (log messages):
2584 - When learning a fingerprint for a bridge, log its corresponding
2585 transport type. Implements ticket 7896.
2586 - Improve the log message when "Bug/attack: unexpected sendme cell
2587 from client" occurs, to help us track bug 8093.
2590 - Remove a couple of extraneous semicolons that were upsetting the
2591 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
2592 bugfix on 0.2.2.1-alpha.
2593 - Remove a source of rounding error during path bias count scaling;
2594 don't count cannibalized circuits as used for path bias until we
2595 actually try to use them; and fix a circuit_package_relay_cell()
2596 warning message about n_chan==NULL. Fixes bug 7802.
2597 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
2598 actually link against nacl when we're configured to use it. Fixes
2599 bug 7972; bugfix on 0.2.4.8-alpha.
2600 - Compile correctly with the --disable-curve25519 option. Fixes
2601 bug 8153; bugfix on 0.2.4.8-alpha.
2603 o Build improvements:
2604 - Do not report status verbosely from autogen.sh unless the -v flag
2605 is specified. Fixes issue 4664. Patch from Onizuka.
2606 - Replace all calls to snprintf() outside of src/ext with
2607 tor_snprintf(). Also remove the #define to replace snprintf with
2608 _snprintf on Windows; they have different semantics, and all of
2609 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
2610 - Try to detect if we are ever building on a platform where
2611 memset(...,0,...) does not set the value of a double to 0.0. Such
2612 platforms are permitted by the C standard, though in practice
2613 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
2614 currently support them, but it's better to detect them and fail
2615 than to perform erroneously.
2618 - Stop exporting estimates of v2 and v3 directory traffic shares
2619 in extrainfo documents. They were unneeded and sometimes inaccurate.
2620 Also stop exporting any v2 directory request statistics. Resolves
2622 - Drop support for detecting and warning about versions of Libevent
2623 before 1.3e. Nothing reasonable ships with them any longer;
2624 warning the user about them shouldn't be needed. Resolves ticket
2627 o Code simplifications and refactoring:
2628 - Rename "isin" functions to "contains", for grammar. Resolves
2630 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
2631 with the natural logarithm function from the system libm. Resolves
2635 Changes in version 0.2.4.9-alpha - 2013-01-15
2636 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
2640 - Fix backward compatibility logic when receiving an embedded ntor
2641 handshake tunneled in a CREATE cell. This clears up the "Bug:
2642 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
2646 Changes in version 0.2.4.8-alpha - 2013-01-14
2647 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
2648 risks, adds a new stronger and faster circuit handshake, and offers
2649 stronger and faster link encryption when both sides support it.
2652 - Preliminary support for directory guards (proposal 207): when
2653 possible, clients now use their entry guards for non-anonymous
2654 directory requests. This can help prevent client enumeration. Note
2655 that this behavior only works when we have a usable consensus
2656 directory, and when options about what to download are more or less
2657 standard. In the future we should re-bootstrap from our guards,
2658 rather than re-bootstrapping from the preconfigured list of
2659 directory sources that ships with Tor. Resolves ticket 6526.
2660 - Tor relays and clients now support a better CREATE/EXTEND cell
2661 format, allowing the sender to specify multiple address, identity,
2662 and handshake types. Implements Robert Ransom's proposal 200;
2665 o Major features (new circuit handshake):
2666 - Tor now supports a new circuit extension handshake designed by Ian
2667 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
2668 circuit extension handshake, later called "TAP", was a bit slow
2669 (especially on the relay side), had a fragile security proof, and
2670 used weaker keys than we'd now prefer. The new circuit handshake
2671 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
2672 function, making it significantly more secure than the older
2673 handshake, and significantly faster. Tor can use one of two built-in
2674 pure-C curve25519-donna implementations by Adam Langley, or it
2675 can link against the "nacl" library for a tuned version if present.
2677 The built-in version is very fast for 64-bit systems when building
2678 with GCC. The built-in 32-bit version is still faster than the
2679 old TAP protocol, but using libnacl is better on most such hosts.
2681 Clients don't currently use this protocol by default, since
2682 comparatively few clients support it so far. To try it, set
2683 UseNTorHandshake to 1.
2685 Implements proposal 216; closes ticket 7202.
2687 o Major features (better link encryption):
2688 - Relays can now enable the ECDHE TLS ciphersuites when available
2689 and appropriate. These ciphersuites let us negotiate forward-secure
2690 TLS secret keys more safely and more efficiently than with our
2691 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
2692 public relays prefer the (faster) P224 group, and bridges prefer
2693 the (more common) P256 group; you can override this with the
2696 Enabling these ciphers was a little tricky, since for a long time,
2697 clients had been claiming to support them without actually doing
2698 so, in order to foil fingerprinting. But with the client-side
2699 implementation of proposal 198 in 0.2.3.17-beta, clients can now
2700 match the ciphers from recent Firefox versions *and* list the
2701 ciphers they actually mean, so relays can believe such clients
2702 when they advertise ECDHE support in their TLS ClientHello messages.
2704 This feature requires clients running 0.2.3.17-beta or later,
2705 and requires both sides to be running OpenSSL 1.0.0 or later
2706 with ECC support. OpenSSL 1.0.1, with the compile-time option
2707 "enable-ec_nistp_64_gcc_128", is highly recommended.
2709 Implements the relay side of proposal 198; closes ticket 7200.
2712 - Avoid crashing when, as a relay without IPv6-exit support, a
2713 client insists on getting an IPv6 address or nothing. Fixes bug
2714 7814; bugfix on 0.2.4.7-alpha.
2717 - Improve circuit build timeout handling for hidden services.
2718 In particular: adjust build timeouts more accurately depending
2719 upon the number of hop-RTTs that a particular circuit type
2720 undergoes. Additionally, launch intro circuits in parallel
2721 if they timeout, and take the first one to reply as valid.
2722 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
2723 separate error codes; or at least, don't break for that reason.
2724 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
2725 - Update to the January 2 2013 Maxmind GeoLite Country database.
2727 o Minor features (testing):
2728 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
2729 (P-256) Diffie-Hellman handshakes to src/or/bench.
2730 - Add benchmark functions to test onion handshake performance.
2732 o Minor features (path bias detection):
2733 - Alter the Path Bias log messages to be more descriptive in terms
2734 of reporting timeouts and other statistics.
2735 - Create three levels of Path Bias log messages, as opposed to just
2736 two. These are configurable via consensus as well as via the torrc
2737 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
2738 The default values are 0.70, 0.50, and 0.30 respectively.
2739 - Separate the log message levels from the decision to drop guards,
2740 which also is available via torrc option PathBiasDropGuards.
2741 PathBiasDropGuards still defaults to 0 (off).
2742 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
2743 in combination with PathBiasExtremeRate.
2744 - Increase the default values for PathBiasScaleThreshold and
2745 PathBiasCircThreshold from (200, 20) to (300, 150).
2746 - Add in circuit usage accounting to path bias. If we try to use a
2747 built circuit but fail for any reason, it counts as path bias.
2748 Certain classes of circuits where the adversary gets to pick your
2749 destination node are exempt from this accounting. Usage accounting
2750 can be specifically disabled via consensus parameter or torrc.
2751 - Convert all internal path bias state to double-precision floating
2752 point, to avoid roundoff error and other issues.
2753 - Only record path bias information for circuits that have completed
2754 *two* hops. Assuming end-to-end tagging is the attack vector, this
2755 makes us more resilient to ambient circuit failure without any
2756 detection capability loss.
2758 o Minor bugfixes (log messages):
2759 - Rate-limit the "No circuits are opened. Relaxed timeout for a
2760 circuit with channel state open..." message to once per hour to
2761 keep it from filling the notice logs. Mitigates bug 7799 but does
2762 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
2763 - Avoid spurious warnings when configuring multiple client ports of
2764 which only some are nonlocal. Previously, we had claimed that some
2765 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
2768 o Code simplifications and refactoring:
2769 - Get rid of a couple of harmless clang warnings, where we compared
2770 enums to ints. These warnings are newly introduced in clang 3.2.
2771 - Split the onion.c file into separate modules for the onion queue
2772 and the different handshakes it supports.
2773 - Remove the marshalling/unmarshalling code for sending requests to
2774 cpuworkers over a socket, and instead just send structs. The
2775 recipient will always be the same Tor binary as the sender, so
2776 any encoding is overkill.
2779 Changes in version 0.2.4.7-alpha - 2012-12-24
2780 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
2781 directory mirrors for more robust bootstrapping; fixes more issues where
2782 clients with changing network conditions refuse to make any circuits;
2783 adds initial support for exiting to IPv6 addresses; resumes being able
2784 to update our GeoIP database, and includes the geoip6 file this time;
2785 turns off the client-side DNS cache by default due to privacy risks;
2786 and fixes a variety of other issues.
2788 o Major features (client resilience):
2789 - Add a new "FallbackDir" torrc option to use when we can't use
2790 a directory mirror from the consensus (either because we lack a
2791 consensus, or because they're all down). Currently, all authorities
2792 are fallbacks by default, and there are no other default fallbacks,
2793 but that will change. This option will allow us to give clients a
2794 longer list of servers to try to get a consensus from when first
2795 connecting to the Tor network, and thereby reduce load on the
2796 directory authorities. Implements proposal 206, "Preconfigured
2797 directory sources for bootstrapping". We also removed the old
2798 "FallbackNetworkstatus" option, since we never got it working well
2799 enough to use it. Closes bug 572.
2800 - If we have no circuits open, use a relaxed timeout (the
2801 95-percentile cutoff) until a circuit succeeds. This heuristic
2802 should allow Tor to succeed at building circuits even when the
2803 network connection drastically changes. Should help with bug 3443.
2805 o Major features (IPv6):
2806 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
2807 connectivity, then set the IPv6Exit flag to 1. Also make sure your
2808 exit policy reads as you would like: the address * applies to all
2809 address families, whereas *4 is IPv4 address only, and *6 is IPv6
2810 addresses only. On the client side, you'll need to wait until the
2811 authorities have upgraded, wait for enough exits to support IPv6,
2812 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
2813 ticket 5547, implements proposal 117 as revised in proposal 208.
2815 We DO NOT recommend that clients with actual anonymity needs start
2816 using IPv6 over Tor yet, since not enough exits support it yet.
2818 o Major features (geoip database):
2819 - Maxmind began labelling Tor relays as being in country "A1",
2820 which breaks by-country node selection inside Tor. Now we use a
2821 script to replace "A1" ("Anonymous Proxy") entries in our geoip
2822 file with real country codes. This script fixes about 90% of "A1"
2823 entries automatically and uses manual country code assignments to
2824 fix the remaining 10%. See src/config/README.geoip for details.
2825 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
2826 Country database, as modified above.
2828 o Major bugfixes (client-side DNS):
2829 - Turn off the client-side DNS cache by default. Updating and using
2830 the DNS cache is now configurable on a per-client-port
2831 level. SOCKSPort, DNSPort, etc lines may now contain
2832 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
2833 cache these types of DNS answers when we receive them from an
2834 exit node in response to an application request on this port, and
2835 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
2836 cached DNS answers of these types, we shouldn't use them. It's
2837 potentially risky to use cached DNS answers at the client, since
2838 doing so can indicate to one exit what answers we've gotten
2839 for DNS lookups in the past. With IPv6, this becomes especially
2840 problematic. Using cached DNS answers for requests on the same
2841 circuit would present less linkability risk, since all traffic
2842 on a circuit is already linkable, but it would also provide
2843 little performance benefit: the exit node caches DNS replies
2844 too. Implements a simplified version of Proposal 205. Implements
2847 o Major bugfixes (other):
2848 - Alter circuit build timeout measurement to start at the point
2849 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
2850 initialization). This should make our timeout measurements more
2851 uniform. Previously, we were sometimes including ORconn setup time
2852 in our circuit build time measurements. Should resolve bug 3443.
2853 - Fix an assertion that could trigger in hibernate_go_dormant() when
2854 closing an or_connection_t: call channel_mark_for_close() rather
2855 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
2857 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
2858 7655; bugfix on 0.2.4.6-alpha.
2861 - Add a new torrc option "ServerTransportListenAddr" to let bridge
2862 operators select the address where their pluggable transports will
2863 listen for connections. Resolves ticket 7013.
2864 - Allow an optional $ before the node identity digest in the
2865 controller command GETINFO ns/id/<identity>, for consistency with
2866 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
2867 - Log packaged cell fullness as part of the heartbeat message.
2868 Diagnosis to try to determine the extent of bug 7743.
2870 o Minor features (IPv6):
2871 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
2872 prefer to hand out virtual IPv6 addresses, since there are more of
2873 them and we can't run out. To override this behavior and make IPv4
2874 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
2875 or DNSPort you're using for resolving. Implements ticket 7571.
2876 - AutomapHostsOnResolve responses are now randomized, to avoid
2877 annoying situations where Tor is restarted and applications
2878 connect to the wrong addresses.
2879 - Never try more than 1000 times to pick a new virtual address when
2880 AutomapHostsOnResolve is set. That's good enough so long as we
2881 aren't close to handing out our entire virtual address space;
2882 if you're getting there, it's best to switch to IPv6 virtual
2886 - The ADDRMAP command can no longer generate an ill-formed error
2887 code on a failed MAPADDRESS. It now says "internal" rather than
2888 an English sentence fragment with spaces in the middle. Bugfix on
2890 - Fix log messages and comments to avoid saying "GMT" when we mean
2891 "UTC". Fixes bug 6113.
2892 - Compile on win64 using mingw64. Fixes bug 7260; patches from
2894 - Fix a crash when debugging unit tests on Windows: deallocate a
2895 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
2896 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
2899 - The DirServer option is now DirAuthority, for consistency with
2900 current naming patterns. You can still use the old DirServer form.
2902 o Code simplification and refactoring:
2903 - Move the client-side address-map/virtual-address/DNS-cache code
2904 out of connection_edge.c into a new addressmap.c module.
2905 - Remove unused code for parsing v1 directories and "running routers"
2906 documents. Fixes bug 6887.
2909 Changes in version 0.2.3.25 - 2012-11-19
2910 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
2911 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
2912 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
2913 programmer, and friend. Unstinting in his dedication to the cause of
2914 freedom, he inspired and helped many of us as we began our work on
2915 anonymity, and inspires us still. Please honor his memory by writing
2916 software to protect people's freedoms, and by helping others to do so.
2918 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
2919 significantly reduced directory overhead (via microdescriptors),
2920 enormous crypto performance improvements for fast relays on new
2921 enough hardware, a new v3 TLS handshake protocol that can better
2922 resist fingerprinting, support for protocol obfuscation plugins (aka
2923 pluggable transports), better scalability for hidden services, IPv6
2924 support for bridges, performance improvements like allowing clients
2925 to skip the first round-trip on the circuit ("optimistic data") and
2926 refilling token buckets more often, a new "stream isolation" design
2927 to isolate different applications on different circuits, and many
2928 stability, security, and privacy fixes.
2931 - Tor tries to wipe potentially sensitive data after using it, so
2932 that if some subsequent security failure exposes Tor's memory,
2933 the damage will be limited. But we had a bug where the compiler
2934 was eliminating these wipe operations when it decided that the
2935 memory was no longer visible to a (correctly running) program,
2936 hence defeating our attempt at defense in depth. We fix that
2937 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2938 is unlikely to optimize away. Future versions of Tor may use
2939 a less ridiculously heavy approach for this. Fixes bug 7352.
2940 Reported in an article by Andrey Karpov.
2943 - Fix a harmless bug when opting against publishing a relay descriptor
2944 because DisableNetwork is set. Fixes bug 7464; bugfix on
2948 Changes in version 0.2.4.6-alpha - 2012-11-13
2949 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
2950 makes our defense-in-depth memory wiping more reliable, and begins to
2951 count IPv6 addresses in bridge statistics,
2954 - Fix an assertion failure that could occur when closing a connection
2955 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
2957 - Tor tries to wipe potentially sensitive data after using it, so
2958 that if some subsequent security failure exposes Tor's memory,
2959 the damage will be limited. But we had a bug where the compiler
2960 was eliminating these wipe operations when it decided that the
2961 memory was no longer visible to a (correctly running) program,
2962 hence defeating our attempt at defense in depth. We fix that
2963 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2964 is unlikely to optimize away. Future versions of Tor may use
2965 a less ridiculously heavy approach for this. Fixes bug 7352.
2966 Reported in an article by Andrey Karpov.
2969 - Add GeoIP database for IPv6 addresses. The new config option
2971 - Bridge statistics now count bridge clients connecting over IPv6:
2972 bridge statistics files now list "bridge-ip-versions" and
2973 extra-info documents list "geoip6-db-digest". The control protocol
2974 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
2975 implementation by "shkoo", addressing ticket 5055.
2978 - Warn when we are binding low ports when hibernation is enabled;
2979 previously we had warned when we were _advertising_ low ports with
2980 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
2981 - Fix a harmless bug when opting against publishing a relay descriptor
2982 because DisableNetwork is set. Fixes bug 7464; bugfix on
2984 - Add warning message when a managed proxy dies during configuration.
2985 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
2986 - Fix a linking error when building tor-fw-helper without miniupnp.
2987 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
2988 - Check for closing an or_connection_t without going through correct
2989 channel functions; emit a warning and then call
2990 connection_or_close_for_error() so we don't assert as in bugs 7212
2992 - Compile correctly on compilers without C99 designated initializer
2993 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
2994 - Avoid a possible assert that can occur when channel_send_destroy() is
2995 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
2996 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
2997 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
2998 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
2999 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
3001 o Code simplification and refactoring:
3002 - Start using OpenBSD's implementation of queue.h, so that we don't
3003 need to hand-roll our own pointer and list structures whenever we
3004 need them. (We can't rely on a sys/queue.h, since some operating
3005 systems don't have them, and the ones that do have them don't all
3006 present the same extensions.)
3009 Changes in version 0.2.4.5-alpha - 2012-10-25
3010 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
3011 two important security vulnerabilities that could lead to remotely
3012 triggerable relay crashes, fix a major bug that was preventing clients
3013 from choosing suitable exit nodes, and refactor some of our code.
3015 o Major bugfixes (security, also in 0.2.3.24-rc):
3016 - Fix a group of remotely triggerable assertion failures related to
3017 incorrect link protocol negotiation. Found, diagnosed, and fixed
3018 by "some guy from France". Fix for CVE-2012-2250; bugfix on
3020 - Fix a denial of service attack by which any directory authority
3021 could crash all the others, or by which a single v2 directory
3022 authority could crash everybody downloading v2 directory
3023 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3025 o Major bugfixes (also in 0.2.3.24-rc):
3026 - When parsing exit policy summaries from microdescriptors, we had
3027 previously been ignoring the last character in each one, so that
3028 "accept 80,443,8080" would be treated by clients as indicating
3029 a node that allows access to ports 80, 443, and 808. That would
3030 lead to clients attempting connections that could never work,
3031 and ignoring exit nodes that would support their connections. Now
3032 clients parse these exit policy summaries correctly. Fixes bug 7192;
3033 bugfix on 0.2.3.1-alpha.
3035 o Minor bugfixes (also in 0.2.3.24-rc):
3036 - Clients now consider the ClientRejectInternalAddresses config option
3037 when using a microdescriptor consensus stanza to decide whether
3038 an exit relay would allow exiting to an internal address. Fixes
3039 bug 7190; bugfix on 0.2.3.1-alpha.
3042 - Only disable TLS session ticket support when running as a TLS
3043 server. Now clients will blend better with regular Firefox
3044 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
3046 o Code simplification and refactoring:
3047 - Start using OpenBSD's implementation of queue.h (originally by
3049 - Move the entry node code from circuitbuild.c to its own file.
3050 - Move the circuit build timeout tracking code from circuitbuild.c
3054 Changes in version 0.2.3.24-rc - 2012-10-25
3055 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
3056 could lead to remotely triggerable relay crashes, and fixes
3057 a major bug that was preventing clients from choosing suitable exit
3060 o Major bugfixes (security):
3061 - Fix a group of remotely triggerable assertion failures related to
3062 incorrect link protocol negotiation. Found, diagnosed, and fixed
3063 by "some guy from France". Fix for CVE-2012-2250; bugfix on
3065 - Fix a denial of service attack by which any directory authority
3066 could crash all the others, or by which a single v2 directory
3067 authority could crash everybody downloading v2 directory
3068 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3071 - When parsing exit policy summaries from microdescriptors, we had
3072 previously been ignoring the last character in each one, so that
3073 "accept 80,443,8080" would be treated by clients as indicating
3074 a node that allows access to ports 80, 443, and 808. That would
3075 lead to clients attempting connections that could never work,
3076 and ignoring exit nodes that would support their connections. Now
3077 clients parse these exit policy summaries correctly. Fixes bug 7192;
3078 bugfix on 0.2.3.1-alpha.
3081 - Clients now consider the ClientRejectInternalAddresses config option
3082 when using a microdescriptor consensus stanza to decide whether
3083 an exit relay would allow exiting to an internal address. Fixes
3084 bug 7190; bugfix on 0.2.3.1-alpha.
3087 Changes in version 0.2.4.4-alpha - 2012-10-20
3088 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
3089 vulnerability introduced by a change in OpenSSL, fixes a remotely
3090 triggerable assert, and adds new channel_t and circuitmux_t abstractions
3091 that will make it easier to test new connection transport and cell
3092 scheduling algorithms.
3094 o New directory authorities (also in 0.2.3.23-rc):
3095 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3096 authority. Closes ticket 5749.
3098 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
3099 - Disable TLS session tickets. OpenSSL's implementation was giving
3100 our TLS session keys the lifetime of our TLS context objects, when
3101 perfect forward secrecy would want us to discard anything that
3102 could decrypt a link connection as soon as the link connection
3103 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3104 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3105 - Discard extraneous renegotiation attempts once the V3 link
3106 protocol has been initiated. Failure to do so left us open to
3107 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3108 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3110 o Internal abstraction features:
3111 - Introduce new channel_t abstraction between circuits and
3112 or_connection_t to allow for implementing alternate OR-to-OR
3113 transports. A channel_t is an abstract object which can either be a
3114 cell-bearing channel, which is responsible for authenticating and
3115 handshaking with the remote OR and transmitting cells to and from
3116 it, or a listening channel, which spawns new cell-bearing channels
3117 at the request of remote ORs. Implements part of ticket 6465.
3118 - Also new is the channel_tls_t subclass of channel_t, adapting it
3119 to the existing or_connection_t code. The V2/V3 protocol handshaking
3120 code which formerly resided in command.c has been moved below the
3121 channel_t abstraction layer and may be found in channeltls.c now.
3122 Implements the rest of ticket 6465.
3123 - Introduce new circuitmux_t storing the queue of circuits for
3124 a channel; this encapsulates and abstracts the queue logic and
3125 circuit selection policy, and allows the latter to be overridden
3126 easily by switching out a policy object. The existing EWMA behavior
3127 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
3129 o Required libraries:
3130 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
3131 strongly recommended.
3134 - Warn users who run hidden services on a Tor client with
3135 UseEntryGuards disabled that their hidden services will be
3136 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
3137 attack which motivated Tor to support entry guards in the first
3138 place). Resolves ticket 6889.
3139 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
3140 dhill. Resolves ticket 6982.
3141 - Option OutboundBindAddress can be specified multiple times and
3142 accepts IPv6 addresses. Resolves ticket 6876.
3144 o Minor bugfixes (also in 0.2.3.23-rc):
3145 - Don't serve or accept v2 hidden service descriptors over a
3146 relay's DirPort. It's never correct to do so, and disabling it
3147 might make it more annoying to exploit any bugs that turn up in the
3148 descriptor-parsing code. Fixes bug 7149.
3149 - Fix two cases in src/or/transports.c where we were calling
3150 fmt_addr() twice in a parameter list. Bug found by David
3151 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3152 - Fix memory leaks whenever we logged any message about the "path
3153 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3154 - When relays refuse a "create" cell because their queue of pending
3155 create cells is too big (typically because their cpu can't keep up
3156 with the arrival rate), send back reason "resource limit" rather
3157 than reason "internal", so network measurement scripts can get a
3158 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
3161 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
3162 - Free some more still-in-use memory at exit, to make hunting for
3163 memory leaks easier. Resolves bug 7029.
3164 - When a Tor client gets a "truncated" relay cell, the first byte of
3165 its payload specifies why the circuit was truncated. We were
3166 ignoring this 'reason' byte when tearing down the circuit, resulting
3167 in the controller not being told why the circuit closed. Now we
3168 pass the reason from the truncated cell to the controller. Bugfix
3169 on 0.1.2.3-alpha; fixes bug 7039.
3170 - Downgrade "Failed to hand off onionskin" messages to "debug"
3171 severity, since they're typically redundant with the "Your computer
3172 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
3173 - Make clients running with IPv6 bridges connect over IPv6 again,
3174 even without setting new config options ClientUseIPv6 and
3175 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
3176 - Use square brackets around IPv6 addresses in numerous places
3177 that needed them, including log messages, HTTPS CONNECT proxy
3178 requests, TransportProxy statefile entries, and pluggable transport
3179 extra-info lines. Fixes bug 7011; patch by David Fifield.
3181 o Code refactoring and cleanup:
3182 - Source files taken from other packages now reside in src/ext;
3183 previously they were scattered around the rest of Tor.
3184 - Avoid use of reserved identifiers in our C code. The C standard
3185 doesn't like us declaring anything that starts with an
3186 underscore, so let's knock it off before we get in trouble. Fix
3187 for bug 1031; bugfix on the first Tor commit.
3190 Changes in version 0.2.3.23-rc - 2012-10-20
3191 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
3192 vulnerability introduced by a change in OpenSSL, and fixes a variety
3193 of smaller bugs in preparation for the release.
3195 o New directory authorities:
3196 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3197 authority. Closes ticket 5749.
3199 o Major bugfixes (security/privacy):
3200 - Disable TLS session tickets. OpenSSL's implementation was giving
3201 our TLS session keys the lifetime of our TLS context objects, when
3202 perfect forward secrecy would want us to discard anything that
3203 could decrypt a link connection as soon as the link connection
3204 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3205 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3206 - Discard extraneous renegotiation attempts once the V3 link
3207 protocol has been initiated. Failure to do so left us open to
3208 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3209 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3212 - Fix a possible crash bug when checking for deactivated circuits
3213 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3214 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3216 o Minor bugfixes (on 0.2.3.x):
3217 - Fix two cases in src/or/transports.c where we were calling
3218 fmt_addr() twice in a parameter list. Bug found by David
3219 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3220 - Convert an assert in the pathbias code to a log message. The assert
3221 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3222 bugfix on 0.2.3.17-beta.
3223 - Fix memory leaks whenever we logged any message about the "path
3224 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3226 o Minor bugfixes (on 0.2.2.x and earlier):
3227 - Don't serve or accept v2 hidden service descriptors over a relay's
3228 DirPort. It's never correct to do so, and disabling it might
3229 make it more annoying to exploit any bugs that turn up in the
3230 descriptor-parsing code. Fixes bug 7149.
3231 - When relays refuse a "create" cell because their queue of pending
3232 create cells is too big (typically because their cpu can't keep up
3233 with the arrival rate), send back reason "resource limit" rather
3234 than reason "internal", so network measurement scripts can get a
3235 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
3236 - Correct file sizes when reading binary files on Cygwin, to avoid
3237 a bug where Tor would fail to read its state file. Fixes bug 6844;
3238 bugfix on 0.1.2.7-alpha.
3239 - Avoid undefined behaviour when parsing the list of supported
3240 rendezvous/introduction protocols in a hidden service descriptor.
3241 Previously, Tor would have confused (as-yet-unused) protocol version
3242 numbers greater than 32 with lower ones on many platforms. Fixes
3243 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3245 o Documentation fixes:
3246 - Clarify that hidden services are TCP only. Fixes bug 6024.
3249 Changes in version 0.2.4.3-alpha - 2012-09-22
3250 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
3251 assertion, resumes letting relays test reachability of their DirPort,
3252 and cleans up a bunch of smaller bugs.
3255 - Fix an assertion failure in tor_timegm() that could be triggered
3256 by a badly formatted directory object. Bug found by fuzzing with
3257 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3260 - Fix a possible crash bug when checking for deactivated circuits
3261 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3262 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3263 - Allow routers to detect that their own DirPorts are running. When
3264 we removed support for versions_supports_begindir, we also
3265 accidentally removed the mechanism we used to self-test our
3266 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
3267 bugfix on 0.2.4.2-alpha.
3269 o Security features:
3270 - Switch to a completely time-invariant approach for picking nodes
3271 weighted by bandwidth. Our old approach would run through the
3272 part of the loop after it had made its choice slightly slower
3273 than it ran through the part of the loop before it had made its
3274 choice. Addresses ticket 6538.
3275 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
3276 by tor2web clients allows hidden services to identify tor2web
3277 clients through their repeated selection of the same rendezvous
3278 and introduction point circuit endpoints (their guards). Resolves
3282 - Enable Tor to read configuration, state, and key information from
3283 a FIFO. Previously Tor would only read from files with a positive
3284 stat.st_size. Code from meejah; fixes bug 6044.
3287 - Correct file sizes when reading binary files on Cygwin, to avoid
3288 a bug where Tor would fail to read its state file. Fixes bug 6844;
3289 bugfix on 0.1.2.7-alpha.
3290 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
3291 bugfix on 0.2.0.3-alpha.
3292 - When complaining about a client port on a public address, log
3293 which address we're complaining about. Fixes bug 4020; bugfix on
3294 0.2.3.3-alpha. Patch by Tom Fitzhenry.
3295 - Convert an assert in the pathbias code to a log message. The assert
3296 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3297 bugfix on 0.2.3.17-beta.
3298 - Our new buildsystem was overzealous about rebuilding manpages: it
3299 would rebuild them all whenever any one of them changed. Now our
3300 dependency checking should be correct. Fixes bug 6843; bugfix on
3302 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
3303 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
3304 - Correct log printout about which address family is preferred
3305 when connecting to a bridge with both an IPv4 and IPv6 OR port.
3306 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
3308 o Minor bugfixes (code cleanliness):
3309 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
3310 with large values. This situation was untriggered, but nevertheless
3311 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
3312 - Reject consensus votes with more than 64 known-flags. We aren't even
3313 close to that limit yet, and our code doesn't handle it correctly.
3314 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
3315 - Avoid undefined behaviour when parsing the list of supported
3316 rendezvous/introduction protocols in a hidden service descriptor.
3317 Previously, Tor would have confused (as-yet-unused) protocol version
3318 numbers greater than 32 with lower ones on many platforms. Fixes
3319 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3320 - Fix handling of rendezvous client authorization types over 8.
3321 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
3322 - Fix building with older versions of GCC (2.95, for one) that don't
3323 like preprocessor directives inside macro arguments. Found by
3324 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
3325 - Switch weighted node selection rule from using a list of doubles
3326 to using a list of int64_t. This change should make the process
3327 slightly easier to debug and maintain. Needed to finish ticket 6538.
3329 o Code simplification and refactoring:
3330 - Move the generic "config" code into a new file, and have "config.c"
3331 hold only torrc- and state-related code. Resolves ticket 6823.
3332 - Move the core of our "choose a weighted element at random" logic
3333 into its own function, and give it unit tests. Now the logic is
3334 testable, and a little less fragile too.
3335 - Removed the testing_since field of node_t, which hasn't been used
3336 for anything since 0.2.0.9-alpha.
3338 o Documentation fixes:
3339 - Clarify that hidden services are TCP only. Fixes bug 6024.
3340 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
3344 Changes in version 0.2.3.22-rc - 2012-09-11
3345 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
3349 - Fix an assertion failure in tor_timegm() that could be triggered
3350 by a badly formatted directory object. Bug found by fuzzing with
3351 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3354 - Avoid segfault when starting up having run with an extremely old
3355 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3359 Changes in version 0.2.2.39 - 2012-09-11
3360 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
3364 - Fix an assertion failure in tor_timegm() that could be triggered
3365 by a badly formatted directory object. Bug found by fuzzing with
3366 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3367 - Do not crash when comparing an address with port value 0 to an
3368 address policy. This bug could have been used to cause a remote
3369 assertion failure by or against directory authorities, or to
3370 allow some applications to crash clients. Fixes bug 6690; bugfix
3374 Changes in version 0.2.4.2-alpha - 2012-09-10
3375 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
3376 raises the default rate limiting even more, and makes the bootstrapping
3377 log messages less noisy.
3380 - Automatically forward the TCP ports of pluggable transport
3381 proxies using tor-fw-helper if PortForwarding is enabled. Implements
3385 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
3386 to 1GB/1GB. The previous defaults were intended to be "basically
3387 infinite", but it turns out they're now limiting our 100mbit+
3388 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
3389 last time we raised it).
3392 - Detect when we're running with a version of OpenSSL other than the
3393 one we compiled with. This has occasionally given people hard-to-
3395 - Log fewer lines at level "notice" about our OpenSSL and Libevent
3396 versions and capabilities when everything is going right. Resolves
3397 part of ticket 6736.
3398 - Directory authorities no long accept descriptors for any version of
3399 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
3400 These versions are insecure, unsupported, or both. Implements
3404 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
3405 to start with a triple-underscore so the controller won't touch it.
3406 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
3407 - Avoid segfault when starting up having run with an extremely old
3408 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3410 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
3411 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
3412 - Don't follow the NULL pointer if microdescriptor generation fails.
3413 (This does not appear to be triggerable, but it's best to be safe.)
3414 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
3415 - Fix mis-declared dependencies on src/common/crypto.c and
3416 src/or/tor_main.c that could break out-of-tree builds under some
3417 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
3418 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
3419 6778; bugfix on 0.2.4.1-alpha.
3420 - Fix a harmless (in this case) build warning for implicitly
3421 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
3424 - Now that all versions before 0.2.2.x are disallowed, we no longer
3425 need to work around their missing features. Thus we can remove a
3426 bunch of compatibility code.
3429 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
3430 TCP ports to forward. In the past it only accepted two ports:
3431 the ORPort and the DirPort.
3434 Changes in version 0.2.4.1-alpha - 2012-09-05
3435 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
3436 bridgedb; lets relays use IPv6 addresses and directory authorities
3437 advertise them; and switches to a cleaner build interface.
3439 This is the first alpha release in a new series, so expect there to
3440 be bugs. Users who would rather test out a more stable branch should
3441 stay with 0.2.3.x for now.
3443 o Major features (bridges):
3444 - Bridges now report the pluggable transports they support to the
3445 bridge authority, so it can pass the supported transports on to
3446 bridgedb and/or eventually do reachability testing. Implements
3449 o Major features (IPv6):
3450 - Bridge authorities now accept IPv6 bridge addresses and include
3451 them in network status documents. Implements ticket 5534.
3452 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
3453 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
3454 to happen. Implements ticket 5535.
3455 - All kind of relays, not just bridges, can now advertise an IPv6
3456 OR port. Implements ticket 6362.
3457 - Directory authorities vote on IPv6 OR ports using the new consensus
3458 method 14. Implements ticket 6363.
3460 o Major features (build):
3461 - Switch to a nonrecursive Makefile structure. Now instead of each
3462 Makefile.am invoking other Makefile.am's, there is a master
3463 Makefile.am that includes the others. This change makes our build
3464 process slightly more maintainable, and improves parallelism for
3465 building with make -j. Original patch by Stewart Smith; various
3466 fixes by Jim Meyering.
3467 - Where available, we now use automake's "silent" make rules by
3468 default, so that warnings are easier to spot. You can get the old
3469 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
3471 o Minor features (code security and spec conformance):
3472 - Clear keys and key-derived material left on the stack in
3473 rendservice.c and rendclient.c. Check return value of
3474 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
3475 These fixes should make us more forward-secure against cold-boot
3476 attacks and the like. Fixes bug 2385.
3477 - Reject EXTEND cells sent to nonexistent streams. According to the
3478 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
3479 we were only checking for stream IDs that were currently in use.
3480 Found while hunting for more instances of bug 6271. Bugfix on
3481 0.0.2pre8, which introduced incremental circuit construction.
3483 o Minor features (streamlining);
3484 - No longer include the "opt" prefix when generating routerinfos
3485 or v2 directories: it has been needless since Tor 0.1.2. Closes
3487 - Remove some now-needless code that tried to aggressively flush
3488 OR connections as data was added to them. Since 0.2.0.1-alpha, our
3489 cell queue logic has saved us from the failure mode that this code
3490 was supposed to prevent. Removing this code will limit the number
3491 of baroque control flow paths through Tor's network logic. Reported
3492 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
3494 o Minor features (controller):
3495 - Add a "GETINFO signal/names" control port command. Implements
3497 - Provide default values for all options via "GETINFO config/defaults".
3498 Implements ticket 4971.
3500 o Minor features (IPv6):
3501 - New config option "AuthDirHasIPv6Connectivity 1" that directory
3502 authorities should set if they have IPv6 connectivity and want to
3503 do reachability tests for IPv6 relays. Implements feature 5974.
3504 - A relay with an IPv6 OR port now sends that address in NETINFO
3505 cells (in addition to its other address). Implements ticket 6364.
3507 o Minor features (log messages):
3508 - Omit the first heartbeat log message, because it never has anything
3509 useful to say, and it clutters up the bootstrapping messages.
3510 Resolves ticket 6758.
3511 - Don't log about reloading the microdescriptor cache at startup. Our
3512 bootstrap warnings are supposed to tell the user when there's a
3513 problem, and our bootstrap notices say when there isn't. Resolves
3514 ticket 6759; bugfix on 0.2.2.6-alpha.
3515 - Don't log "I learned some more directory information" when we're
3516 reading cached directory information. Reserve it for when new
3517 directory information arrives in response to a fetch. Resolves
3519 - Prevent rounding error in path bias counts when scaling
3520 them down, and use the correct scale factor default. Also demote
3521 some path bias related log messages down a level and make others
3522 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
3523 - We no longer warn so much when generating manpages from their
3526 o Code simplifications and refactoring:
3527 - Enhance our internal sscanf replacement so that we can eliminate
3528 the last remaining uses of the system sscanf. (Though those uses
3529 of sscanf were safe, sscanf itself is generally error prone, so
3530 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
3532 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
3533 - Move last_reachable and testing_since from routerinfo_t to node_t.
3534 Implements ticket 5529.
3535 - Add replaycache_t structure, functions and unit tests, then refactor
3536 rend_service_introduce() to be more clear to read, improve, debug,
3537 and test. Resolves bug 6177.
3538 - Finally remove support for malloc_good_size and malloc_usable_size.
3539 We had hoped that these functions would let us eke a little more
3540 memory out of our malloc implementation. Unfortunately, the only
3541 implementations that provided these functions are also ones that
3542 are already efficient about not overallocation: they never got us
3543 more than 7 or so bytes per allocation. Removing them saves us a
3544 little code complexity and a nontrivial amount of build complexity.
3547 - Tor maintainers now require Automake version 1.9 or later to build
3548 Tor from the Git repository. (Automake is not required when building
3549 from a source distribution.)
3552 Changes in version 0.2.3.21-rc - 2012-09-05
3553 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
3554 series. It fixes a trio of potential security bugs, fixes a bug where
3555 we were leaving some of the fast relays out of the microdescriptor
3556 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
3557 and cleans up other smaller issues.
3559 o Major bugfixes (security):
3560 - Tear down the circuit if we get an unexpected SENDME cell. Clients
3561 could use this trick to make their circuits receive cells faster
3562 than our flow control would have allowed, or to gum up the network,
3563 or possibly to do targeted memory denial-of-service attacks on
3564 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
3565 from July 2002, before the release of Tor 0.0.0. We had committed
3566 this patch previously, but we had to revert it because of bug 6271.
3567 Now that 6271 is fixed, this patch appears to work.
3568 - Reject any attempt to extend to an internal address. Without
3569 this fix, a router could be used to probe addresses on an internal
3570 network to see whether they were accepting connections. Fixes bug
3571 6710; bugfix on 0.0.8pre1.
3572 - Do not crash when comparing an address with port value 0 to an
3573 address policy. This bug could have been used to cause a remote
3574 assertion failure by or against directory authorities, or to
3575 allow some applications to crash clients. Fixes bug 6690; bugfix
3579 - Remove the upper bound on microdescriptor length. We were hitting
3580 the limit for routers with complex exit policies or family
3581 declarations, causing clients to not use them. Fixes the first
3582 piece of bug 6404; fix on 0.2.2.6-alpha.
3583 - Detect "ORPort 0" as meaning, uniformly, that we're not running
3584 as a relay. Previously, some of our code would treat the presence
3585 of any ORPort line as meaning that we should act like a relay,
3586 even though our new listener code would correctly not open any
3587 ORPorts for ORPort 0. Similar bugs in other Port options are also
3588 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
3591 - Avoid a pair of double-free and use-after-mark bugs that can
3592 occur with certain timings in canceled and re-received DNS
3593 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
3594 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
3595 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
3596 - Allow one-hop directory fetching circuits the full "circuit build
3597 timeout" period, rather than just half of it, before failing them
3598 and marking the relay down. This fix should help reduce cases where
3599 clients declare relays (or worse, bridges) unreachable because
3600 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
3601 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
3603 - Authorities no longer include any router in their microdescriptor
3604 consensuses for which they couldn't generate or agree on a
3605 microdescriptor. Fixes the second piece of bug 6404; fix on
3607 - Detect and reject attempts to specify both "FooPort" and
3608 "FooPort 0" in the same configuration domain. (It's still okay
3609 to have a FooPort in your configuration file, and use "FooPort 0"
3610 on the command line to disable it.) Fixes the second half of bug
3611 6507; bugfix on 0.2.3.3-alpha.
3612 - Make wildcarded addresses (that is, ones beginning with "*.") work
3613 when provided via the controller's MapAddress command. Previously,
3614 they were accepted, but we never actually noticed that they were
3615 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
3616 - Avoid crashing on a malformed state file where EntryGuardPathBias
3617 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
3618 - Add a (probably redundant) memory clear between iterations of
3619 the router status voting loop, to prevent future coding errors
3620 where data might leak between iterations of the loop. Resolves
3623 o Minor bugfixes (log messages):
3624 - Downgrade "set buildtimeout to low value" messages to "info"
3625 severity; they were never an actual problem, there was never
3626 anything reasonable to do about them, and they tended to spam logs
3627 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
3628 - Downgrade path-bias warning messages to "info". We'll try to get
3629 them working better in 0.2.4. Add internal circuit construction
3630 state to protect against the noisy warn message "Unexpectedly high
3631 circuit_successes". Also add some additional rate-limited notice
3632 messages to help determine the root cause of the warn. Fixes bug
3633 6475. Bugfix against 0.2.3.17-beta.
3634 - Move log message when unable to find a microdesc in a routerstatus
3635 entry to parse time. Previously we'd spam this warning every time
3636 we tried to figure out which microdescriptors to download. Fixes
3637 the third piece of bug 6404; fix on 0.2.3.18-rc.
3640 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
3641 change when the authority is deciding whether to accept a newly
3642 uploaded descriptor. Implements ticket 6423.
3643 - Add missing documentation for consensus and microdesc files.
3644 Resolves ticket 6732.
3647 Changes in version 0.2.2.38 - 2012-08-12
3648 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
3649 attack that could in theory leak path information.
3652 - Avoid an uninitialized memory read when reading a vote or consensus
3653 document that has an unrecognized flavor name. This read could
3654 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3655 - Try to leak less information about what relays a client is
3656 choosing to a side-channel attacker. Previously, a Tor client would
3657 stop iterating through the list of available relays as soon as it
3658 had chosen one, thus finishing a little earlier when it picked
3659 a router earlier in the list. If an attacker can recover this
3660 timing information (nontrivial but not proven to be impossible),
3661 they could learn some coarse-grained information about which relays
3662 a client was picking (middle nodes in particular are likelier to
3663 be affected than exits). The timing attack might be mitigated by
3664 other factors (see bug 6537 for some discussion), but it's best
3665 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3668 Changes in version 0.2.3.20-rc - 2012-08-05
3669 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
3670 series. It fixes a pair of code security bugs and a potential anonymity
3671 issue, updates our RPM spec files, and cleans up other smaller issues.
3674 - Avoid read-from-freed-memory and double-free bugs that could occur
3675 when a DNS request fails while launching it. Fixes bug 6480;
3676 bugfix on 0.2.0.1-alpha.
3677 - Avoid an uninitialized memory read when reading a vote or consensus
3678 document that has an unrecognized flavor name. This read could
3679 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3680 - Try to leak less information about what relays a client is
3681 choosing to a side-channel attacker. Previously, a Tor client would
3682 stop iterating through the list of available relays as soon as it
3683 had chosen one, thus finishing a little earlier when it picked
3684 a router earlier in the list. If an attacker can recover this
3685 timing information (nontrivial but not proven to be impossible),
3686 they could learn some coarse-grained information about which relays
3687 a client was picking (middle nodes in particular are likelier to
3688 be affected than exits). The timing attack might be mitigated by
3689 other factors (see bug 6537 for some discussion), but it's best
3690 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3693 - Try to make the warning when giving an obsolete SOCKSListenAddress
3694 a little more useful.
3695 - Terminate active server managed proxies if Tor stops being a
3696 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
3697 - Provide a better error message about possible OSX Asciidoc failure
3698 reasons. Fixes bug 6436.
3699 - Warn when Tor is configured to use accounting in a way that can
3700 link a hidden service to some other hidden service or public
3701 address. Resolves ticket 6490.
3704 - Check return value of fputs() when writing authority certificate
3705 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
3706 - Ignore ServerTransportPlugin lines when Tor is not configured as
3707 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
3708 - When disabling guards for having too high a proportion of failed
3709 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
3713 - Update our default RPM spec files to work with mock and rpmbuild
3714 on RHEL/Fedora. They have an updated set of dependencies and
3715 conflicts, a fix for an ancient typo when creating the "_tor"
3716 user, and better instructions. Thanks to Ondrej Mikle for the
3717 patch series. Fixes bug 6043.
3720 - Make it possible to set the TestingTorNetwork configuration
3721 option using AlternateDirAuthority and AlternateBridgeAuthority
3722 as an alternative to setting DirServer. Addresses ticket 6377.
3725 - Clarify the documentation for the Alternate*Authority options.
3727 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
3729 o Code simplification and refactoring:
3730 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
3731 10 lines. Also, don't nest them. Doing so in the past has
3732 led to hard-to-debug code. The new style is to use the
3733 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
3736 Changes in version 0.2.3.19-rc - 2012-07-06
3737 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
3738 series. It fixes the compile on Windows, reverts to a GeoIP database
3739 that isn't as broken, and fixes a flow control bug that has been around
3740 since the beginning of Tor.
3743 - Fix a bug handling SENDME cells on nonexistent streams that could
3744 result in bizarre window values. Report and patch contributed
3745 pseudonymously. Fixes part of bug 6271. This bug was introduced
3746 before the first Tor release, in svn commit r152.
3747 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
3748 June 2012 database, Maxmind marked many Tor relays as country "A1",
3749 which will cause risky behavior for clients that set EntryNodes
3750 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
3751 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
3752 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
3755 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
3756 bugfix on 0.2.1.10-alpha.
3759 Changes in version 0.2.3.18-rc - 2012-06-28
3760 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
3761 series. It fixes a few smaller bugs, but generally appears stable.
3762 Please test it and let us know whether it is!
3765 - Allow wildcarded mapaddress targets to be specified on the
3766 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
3767 - Make our linker option detection code more robust against linkers
3768 such as on FreeBSD 8, where a bad combination of options completes
3769 successfully but makes an unrunnable binary. Fixes bug 6173;
3770 bugfix on 0.2.3.17-beta.
3772 o Minor bugfixes (on 0.2.2.x and earlier):
3773 - Avoid a false positive in the util/threads unit test by increasing
3774 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
3775 - Replace "Sending publish request" log messages with "Launching
3776 upload", so that they no longer confusingly imply that we're
3777 sending something to a directory we might not even be connected
3778 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
3779 - Make sure to set *socket_error in all error cases in
3780 connection_connect(), so it can't produce a warning about
3781 errno being zero from errno_to_orconn_end_reason(). Bugfix on
3782 0.2.1.1-alpha; resolves ticket 6028.
3783 - Downgrade "Got a certificate, but we already have it" log messages
3784 from warning to info, except when we're a dirauth. Fixes bug 5238;
3785 bugfix on 0.2.1.7-alpha.
3786 - When checking for requested signatures on the latest consensus
3787 before serving it to a client, make sure to check the right
3788 consensus flavor. Bugfix on 0.2.2.6-alpha.
3789 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
3790 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
3792 o Minor bugfixes (on 0.2.3.x):
3793 - Make format_helper_exit_status() avoid unnecessary space padding
3794 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
3796 - Downgrade a message about cleaning the microdescriptor cache to
3797 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
3798 - Log a BUG message at severity INFO if we have a networkstatus with
3799 a missing entry for some microdescriptor. Continues on a patch
3801 - Improve the log message when a managed proxy fails to launch. Fixes
3802 bug 5099; bugfix on 0.2.3.6-alpha.
3803 - Don't do DNS lookups when parsing corrupted managed proxy protocol
3804 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
3805 - When formatting wildcarded address mappings for the controller,
3806 be sure to include "*." as appropriate. Partially fixes bug 6244;
3807 bugfix on 0.2.3.9-alpha.
3808 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
3809 Bugfix on 0.2.3.13-alpha.
3810 - Stop logging messages about running with circuit timeout learning
3811 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
3812 - Disable a spurious warning about reading on a marked and flushing
3813 connection. We shouldn't be doing that, but apparently we
3814 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
3815 - Fix a bug that stopped AllowDotExit from working on addresses
3816 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
3819 o Code simplification, refactoring, unit tests:
3820 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
3821 Libevent's notion of cached time when possible.
3822 - Remove duplicate code for invoking getrlimit() from control.c.
3823 - Add a unit test for the environment_variable_names_equal function.
3826 - Document the --defaults-torrc option, and the new (in 0.2.3)
3827 semantics for overriding, extending, and clearing lists of
3828 options. Closes bug 4748.
3831 Changes in version 0.2.3.17-beta - 2012-06-15
3832 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
3833 gets our TLS handshake back on track for being able to blend in with
3834 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
3835 with Vidalia, and otherwise continues to get us closer to a release
3839 - Enable gcc and ld hardening by default. Resolves ticket 5210.
3840 - Update TLS cipher list to match Firefox 8 and later. Resolves
3842 - Implement the client side of proposal 198: remove support for
3843 clients falsely claiming to support standard ciphersuites that
3844 they can actually provide. As of modern OpenSSL versions, it's not
3845 necessary to fake any standard ciphersuite, and doing so prevents
3846 us from using better ciphersuites in the future, since servers
3847 can't know whether an advertised ciphersuite is really supported or
3848 not. Some hosts -- notably, ones with very old versions of OpenSSL
3849 or where OpenSSL has been built with ECC disabled -- will stand
3850 out because of this change; TBB users should not be affected.
3853 - Change the default value for DynamicDHGroups (introduced in
3854 0.2.3.9-alpha) to 0. This feature can make Tor relays less
3855 identifiable by their use of the mod_ssl DH group, but at
3856 the cost of some usability (#4721) and bridge tracing (#6087)
3857 regressions. Resolves ticket 5598.
3858 - Send a CRLF at the end of each STATUS_* control protocol event. This
3859 bug tickled a bug in Vidalia which would make it freeze. Fixes
3860 bug 6094; bugfix on 0.2.3.16-alpha.
3863 - Disable writing on marked-for-close connections when they are
3864 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
3865 bug 5263; bugfix on 0.0.2pre13, where we first added a special
3866 case for flushing marked connections.
3867 - Detect SSL handshake even when the initial attempt to write the
3868 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
3869 - Change the AllowDotExit rules so they should actually work.
3870 We now enforce AllowDotExit only immediately after receiving an
3871 address via SOCKS or DNSPort: other sources are free to provide
3872 .exit addresses after the resolution occurs. Fixes bug 3940;
3873 bugfix on 0.2.2.1-alpha.
3874 - Fix a (harmless) integer overflow in cell statistics reported by
3875 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
3876 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
3877 right places and never depends on the consensus parameters or
3878 computes adaptive timeouts when it is disabled. Fixes bug 5049;
3879 bugfix on 0.2.2.14-alpha.
3880 - When building Tor on Windows with -DUNICODE (not default), ensure
3881 that error messages, filenames, and DNS server names are always
3882 NUL-terminated when we convert them to a single-byte encoding.
3883 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
3884 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
3885 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
3886 - Fix an edge case where TestingTorNetwork is set but the authorities
3887 and relays all have an uptime of zero, where the private Tor network
3888 could briefly lack support for hidden services. Fixes bug 3886;
3889 bugfix on 0.2.2.18-alpha.
3890 - Correct the manpage's descriptions for the default values of
3891 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
3893 - Fix the documentation for the --hush and --quiet command line
3894 options, which changed their behavior back in 0.2.3.3-alpha.
3895 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
3899 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
3900 more information to it, so that we can track it down in case it
3901 returns again. Mitigates bug 5235.
3902 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
3903 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
3904 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
3905 - Warn the user when HTTPProxy, but no other proxy type, is
3906 configured. This can cause surprising behavior: it doesn't send
3907 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
3908 directory traffic only. Resolves ticket 4663.
3909 - Issue a notice if a guard completes less than 40% of your circuits.
3910 Threshold is configurable by torrc option PathBiasNoticeRate and
3911 consensus parameter pb_noticepct. There is additional, off-by-
3912 default code to disable guards which fail too many circuits.
3913 Addresses ticket 5458.
3914 - Update to the June 6 2012 Maxmind GeoLite Country database.
3916 o Code simplifications and refactoring:
3917 - Remove validate_pluggable_transports_config(): its warning
3918 message is now handled by connection_or_connect().
3921 Changes in version 0.2.2.37 - 2012-06-06
3922 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
3923 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3927 - Work around a bug in OpenSSL that broke renegotiation with TLS
3928 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3929 the v2 Tor connection protocol when both sides were using OpenSSL
3930 1.0.1 would fail. Resolves ticket 6033.
3931 - When waiting for a client to renegotiate, don't allow it to add
3932 any bytes to the input buffer. This fixes a potential DoS issue.
3933 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3934 - Fix an edge case where if we fetch or publish a hidden service
3935 descriptor, we might build a 4-hop circuit and then use that circuit
3936 for exiting afterwards -- even if the new last hop doesn't obey our
3937 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3940 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3941 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3944 - Tell GCC and Clang to check for any errors in format strings passed
3945 to the tor_v*(print|scan)f functions.
3948 Changes in version 0.2.3.16-alpha - 2012-06-05
3949 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
3950 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3951 currently). It also fixes a variety of smaller bugs and other cleanups
3952 that get us closer to a release candidate.
3954 o Major bugfixes (general):
3955 - Work around a bug in OpenSSL that broke renegotiation with TLS
3956 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3957 the v2 Tor connection protocol when both sides were using OpenSSL
3958 1.0.1 would fail. Resolves ticket 6033.
3959 - When waiting for a client to renegotiate, don't allow it to add
3960 any bytes to the input buffer. This fixes a potential DoS issue.
3961 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3962 - Pass correct OR address to managed proxies (like obfsproxy),
3963 even when ORListenAddress is used. Fixes bug 4865; bugfix on
3965 - The advertised platform of a router now includes only its operating
3966 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
3967 service pack level (for Windows) or its CPU architecture (for Unix).
3968 We also no longer include the "git-XYZ" tag in the version. Resolves
3971 o Major bugfixes (clients):
3972 - If we are unable to find any exit that supports our predicted ports,
3973 stop calling them predicted, so that we don't loop and build
3974 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
3975 which introduced predicted ports.
3976 - Fix an edge case where if we fetch or publish a hidden service
3977 descriptor, we might build a 4-hop circuit and then use that circuit
3978 for exiting afterwards -- even if the new last hop doesn't obey our
3979 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3980 - Check at each new consensus whether our entry guards were picked
3981 long enough ago that we should rotate them. Previously, we only
3982 did this check at startup, which could lead to us holding a guard
3983 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
3984 - When fetching a bridge descriptor from a bridge authority,
3985 always do so anonymously, whether we have been able to open
3986 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
3987 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
3988 but we'll need to wait for bug 6010 before it's actually usable.
3990 o Major bugfixes (directory authorities):
3991 - When computing weight parameters, behave more robustly in the
3992 presence of a bad bwweightscale value. Previously, the authorities
3993 would crash if they agreed on a sufficiently broken weight_scale
3994 value: now, they use a reasonable default and carry on. Partial
3995 fix for 5786; bugfix on 0.2.2.17-alpha.
3996 - Check more thoroughly to prevent a rogue authority from
3997 double-voting on any consensus directory parameter. Previously,
3998 authorities would crash in this case if the total number of
3999 votes for any parameter exceeded the number of active voters,
4000 but would let it pass otherwise. Partial fix for bug 5786; bugfix
4004 - Rate-limit log messages when asked to connect anonymously to
4005 a private address. When these hit, they tended to hit fast and
4006 often. Also, don't bother trying to connect to addresses that we
4007 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
4008 reply makes us think we have been lied to, even when the address the
4009 client tried to connect to was "localhost." Resolves ticket 2822.
4010 - Allow packagers to insert an extra string in server descriptor
4011 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
4012 Resolves the rest of ticket 2988.
4013 - Raise the threshold of server descriptors needed (75%) and exit
4014 server descriptors needed (50%) before we will declare ourselves
4015 bootstrapped. This will make clients start building circuits a
4016 little later, but makes the initially constructed circuits less
4017 skewed and less in conflict with further directory fetches. Fixes
4019 - Close any connection that sends unrecognized junk before the
4020 handshake. Solves an issue noted in bug 4369.
4021 - Improve log messages about managed transports. Resolves ticket 5070.
4022 - Tag a bridge's descriptor as "never to be sent unencrypted".
4023 This shouldn't matter, since bridges don't open non-anonymous
4024 connections to the bridge authority and don't allow unencrypted
4025 directory connections from clients, but we might as well make
4026 sure. Closes bug 5139.
4027 - Expose our view of whether we have gone dormant to the controller,
4028 via a new "GETINFO dormant" value. Torbutton and other controllers
4029 can use this to avoid doing periodic requests through Tor while
4030 it's dormant (bug 4718). Fixes bug 5954.
4031 - Tell GCC and Clang to check for any errors in format strings passed
4032 to the tor_v*(print|scan)f functions.
4033 - Update to the May 1 2012 Maxmind GeoLite Country database.
4035 o Minor bugfixes (already included in 0.2.2.36):
4036 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4037 Fixes bug 5346; bugfix on 0.0.8pre3.
4038 - Correct parsing of certain date types in parse_http_time().
4039 Without this patch, If-Modified-Since would behave
4040 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4041 Esteban Manchado Velázques.
4042 - Make our number-parsing functions always treat too-large values
4043 as an error, even when those values exceed the width of the
4044 underlying type. Previously, if the caller provided these
4045 functions with minima or maxima set to the extreme values of the
4046 underlying integer type, these functions would return those
4047 values on overflow rather than treating overflow as an error.
4048 Fixes part of bug 5786; bugfix on 0.0.9.
4049 - If we hit the error case where routerlist_insert() replaces an
4050 existing (old) server descriptor, make sure to remove that
4051 server descriptor from the old_routers list. Fix related to bug
4052 1776. Bugfix on 0.2.2.18-alpha.
4053 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4054 circuits. Fixes issue 5259.
4056 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
4057 - Prevent a null-pointer dereference when receiving a data cell
4058 for a nonexistent stream when the circuit in question has an
4059 empty deliver window. We don't believe this is triggerable,
4060 since we don't currently allow deliver windows to become empty,
4061 but the logic is tricky enough that it's better to make the code
4062 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
4063 - Fix a memory leak when trying to launch a DNS request when the
4064 network is disabled or the nameservers are unconfigurable. Fixes
4065 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
4066 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
4067 - Don't hold a Windows file handle open for every file mapping;
4068 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
4070 - Avoid O(n^2) performance characteristics when parsing a large
4071 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
4072 - Format more doubles with %f, not %lf. Patch from grarpamp to make
4073 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
4075 - Make our replacement implementation of strtok_r() compatible with
4076 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
4077 bugfix on 0.2.2.1-alpha.
4078 - Fix a NULL-pointer dereference on a badly formed
4079 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
4080 bugfix on 0.2.2.9-alpha.
4081 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
4082 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
4083 - Defensively refactor rend_mid_rendezvous() so that protocol
4084 violations and length checks happen in the beginning. Fixes
4086 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
4087 that IPv6 stuff will compile on MSVC, and compilation issues
4088 will be easier to track down. Fixes bug 5861.
4090 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
4091 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
4092 resource exhaustion, so that clients can adjust their load to
4093 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
4094 started using END_STREAM_REASON_RESOURCELIMIT.
4095 - Don't check for whether the address we're using for outbound
4096 connections has changed until after the outbound connection has
4097 completed. On Windows, getsockname() doesn't succeed until the
4098 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
4099 - If the configuration tries to set MyFamily on a bridge, refuse to
4100 do so, and warn about the security implications. Fixes bug 4657;
4101 bugfix on 0.2.0.3-alpha.
4102 - If the client fails to set a reasonable set of ciphersuites
4103 during its v2 handshake renegotiation, allow the renegotiation to
4104 continue nevertheless (i.e. send all the required certificates).
4105 Fixes bug 4591; bugfix on 0.2.0.20-rc.
4106 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
4107 option is set to 0 (which Vidalia version 0.2.16 now does when
4108 a SAVECONF attempt fails), perform other actions that SIGHUP
4109 usually causes (like reopening the logs). Fixes bug 5095; bugfix
4111 - If we fail to write a microdescriptor to the disk cache, do not
4112 continue replacing the old microdescriptor file. Fixes bug 2954;
4113 bugfix on 0.2.2.6-alpha.
4114 - Exit nodes don't need to fetch certificates for authorities that
4115 they don't recognize; only directory authorities, bridges,
4116 and caches need to do that. Fixes part of bug 2297; bugfix on
4118 - Correctly handle checking the permissions on the parent
4119 directory of a control socket in the root directory. Bug found
4120 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
4122 - When told to add a bridge with the same digest as a preexisting
4123 bridge but a different addr:port, change the addr:port as
4124 requested. Previously we would not notice the change. Fixes half
4125 of bug 5603; fix on 0.2.2.26-beta.
4126 - End AUTHCHALLENGE error messages (in the control protocol) with
4127 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
4129 o Minor bugfixes (on 0.2.3.x):
4130 - Turn an assertion (that the number of handshakes received as a
4131 server is not < 1) into a warning. Fixes bug 4873; bugfix on
4133 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
4134 we had reversed them when the answer was cached.) Fixes bug
4135 5723; bugfix on 0.2.3.1-alpha.
4136 - Work correctly on Linux systems with accept4 support advertised in
4137 their headers, but without accept4 support in the kernel. Fix
4138 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
4139 - When told to add a bridge with the same addr:port as a preexisting
4140 bridge but a different transport, change the transport as
4141 requested. Previously we would not notice the change. Fixes half
4142 of bug 5603; fix on 0.2.3.2-alpha.
4143 - Avoid a "double-reply" warning when replying to a SOCKS request
4144 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
4145 bugfix on 0.2.3.4-alpha.
4146 - Fix a bug where a bridge authority crashes if it has seen no
4147 directory requests when it's time to write statistics to disk.
4148 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
4150 - Don't try to open non-control listeners when DisableNetwork is set.
4151 Previously, we'd open all listeners, then immediately close them.
4152 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
4153 - Don't abort the managed proxy protocol if the managed proxy
4154 sends us an unrecognized line; ignore it instead. Fixes bug
4155 5910; bugfix on 0.2.3.9-alpha.
4156 - Fix a compile warning in crypto.c when compiling with clang 3.1.
4157 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
4158 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
4159 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
4160 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
4161 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
4162 - Resolve numerous small warnings and build issues with MSVC. Resolves
4165 o Documentation fixes:
4166 - Improve the manual's documentation for the NT Service command-line
4167 options. Addresses ticket 3964.
4168 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
4169 - Document the changes to the ORPort and DirPort options, and the
4170 fact that {OR/Dir}ListenAddress is now unnecessary (and
4171 therefore deprecated). Resolves ticket 5597.
4174 - Remove the torrc.bridge file: we don't use it for anything, and
4175 it had become badly desynchronized from torrc.sample. Resolves
4179 Changes in version 0.2.2.36 - 2012-05-24
4180 Tor 0.2.2.36 updates the addresses for two of the eight directory
4181 authorities, fixes some potential anonymity and security issues,
4182 and fixes several crash bugs.
4184 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
4185 known flaws, and nobody should be using them. You should upgrade. If
4186 you're using a Linux or BSD and its packages are obsolete, stop using
4187 those packages and upgrade anyway.
4189 o Directory authority changes:
4190 - Change IP address for maatuska (v3 directory authority).
4191 - Change IP address for ides (v3 directory authority), and rename
4195 - When building or running with any version of OpenSSL earlier
4196 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4197 versions have a bug (CVE-2011-4576) in which their block cipher
4198 padding includes uninitialized data, potentially leaking sensitive
4199 information to any peer with whom they make a SSLv3 connection. Tor
4200 does not use SSL v3 by default, but a hostile client or server
4201 could force an SSLv3 connection in order to gain information that
4202 they shouldn't have been able to get. The best solution here is to
4203 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4204 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4205 to make sure that the bug can't happen.
4206 - Never use a bridge or a controller-supplied node as an exit, even
4207 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4208 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4209 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4210 - Only build circuits if we have a sufficient threshold of the total
4211 descriptors that are marked in the consensus with the "Exit"
4212 flag. This mitigates an attack proposed by wanoskarnet, in which
4213 all of a client's bridges collude to restrict the exit nodes that
4214 the client knows about. Fixes bug 5343.
4215 - Provide controllers with a safer way to implement the cookie
4216 authentication mechanism. With the old method, if another locally
4217 running program could convince a controller that it was the Tor
4218 process, then that program could trick the controller into telling
4219 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4220 authentication method uses a challenge-response approach to prevent
4221 this attack. Fixes bug 5185; implements proposal 193.
4224 - Avoid logging uninitialized data when unable to decode a hidden
4225 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4226 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4227 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4229 - Fix builds when the path to sed, openssl, or sha1sum contains
4230 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4232 - Correct our replacements for the timeradd() and timersub() functions
4233 on platforms that lack them (for example, Windows). The timersub()
4234 function is used when expiring circuits, while timeradd() is
4235 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4236 bugfix on 0.2.2.24-alpha.
4237 - Fix the SOCKET_OK test that we use to tell when socket
4238 creation fails so that it works on Win64. Fixes part of bug 4533;
4239 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4242 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4243 Fixes bug 5346; bugfix on 0.0.8pre3.
4244 - Make our number-parsing functions always treat too-large values
4245 as an error, even when those values exceed the width of the
4246 underlying type. Previously, if the caller provided these
4247 functions with minima or maxima set to the extreme values of the
4248 underlying integer type, these functions would return those
4249 values on overflow rather than treating overflow as an error.
4250 Fixes part of bug 5786; bugfix on 0.0.9.
4251 - Older Linux kernels erroneously respond to strange nmap behavior
4252 by having accept() return successfully with a zero-length
4253 socket. When this happens, just close the connection. Previously,
4254 we would try harder to learn the remote address: but there was
4255 no such remote address to learn, and our method for trying to
4256 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4257 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4258 - Correct parsing of certain date types in parse_http_time().
4259 Without this patch, If-Modified-Since would behave
4260 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4261 Esteban Manchado Velázques.
4262 - Change the BridgePassword feature (part of the "bridge community"
4263 design, which is not yet implemented) to use a time-independent
4264 comparison. The old behavior might have allowed an adversary
4265 to use timing to guess the BridgePassword value. Fixes bug 5543;
4266 bugfix on 0.2.0.14-alpha.
4267 - Detect and reject certain misformed escape sequences in
4268 configuration values. Previously, these values would cause us
4269 to crash if received in a torrc file or over an authenticated
4270 control port. Bug found by Esteban Manchado Velázquez, and
4271 independently by Robert Connolly from Matta Consulting who further
4272 noted that it allows a post-authentication heap overflow. Patch
4273 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4274 bugfix on 0.2.0.16-alpha.
4275 - Fix a compile warning when using the --enable-openbsd-malloc
4276 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4277 - During configure, detect when we're building with clang version
4278 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4279 CFLAGS. clang doesn't support them yet.
4280 - When sending an HTTP/1.1 proxy request, include a Host header.
4281 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4282 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
4283 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
4284 - If we hit the error case where routerlist_insert() replaces an
4285 existing (old) server descriptor, make sure to remove that
4286 server descriptor from the old_routers list. Fix related to bug
4287 1776. Bugfix on 0.2.2.18-alpha.
4289 o Minor bugfixes (documentation and log messages):
4290 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4291 Fixes bug 4856; bugfix on Tor 0.0.6.
4292 - Update "ClientOnly" man page entry to explain that there isn't
4293 really any point to messing with it. Resolves ticket 5005.
4294 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4295 directory authority option (introduced in Tor 0.2.2.34).
4296 - Downgrade the "We're missing a certificate" message from notice
4297 to info: people kept mistaking it for a real problem, whereas it
4298 is seldom the problem even when we are failing to bootstrap. Fixes
4299 bug 5067; bugfix on 0.2.0.10-alpha.
4300 - Correctly spell "connect" in a log message on failure to create a
4301 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
4302 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4303 circuits. Fixes issue 5259.
4306 - Directory authorities now reject versions of Tor older than
4307 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4308 inclusive. These versions accounted for only a small fraction of
4309 the Tor network, and have numerous known security issues. Resolves
4311 - Update to the May 1 2012 Maxmind GeoLite Country database.
4314 - When sending or relaying a RELAY_EARLY cell, we used to convert
4315 it to a RELAY cell if the connection was using the v1 link
4316 protocol. This was a workaround for older versions of Tor, which
4317 didn't handle RELAY_EARLY cells properly. Now that all supported
4318 versions can handle RELAY_EARLY cells, and now that we're enforcing
4319 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4320 remove this workaround. Addresses bug 4786.
4323 Changes in version 0.2.3.15-alpha - 2012-04-30
4324 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
4325 the development branch build on Windows again.
4327 o Minor bugfixes (on 0.2.2.x and earlier):
4328 - Make sure that there are no unhandled pending TLS errors before
4329 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
4330 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
4331 Bugfix on 0.1.0.5-rc; fixes bug 4528.
4332 - Fix an assert that directory authorities could trigger on sighup
4333 during some configuration state transitions. We now don't treat
4334 it as a fatal error when the new descriptor we just generated in
4335 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
4336 - After we pick a directory mirror, we would refuse to use it if
4337 it's in our ExcludeExitNodes list, resulting in mysterious failures
4338 to bootstrap for people who just wanted to avoid exiting from
4339 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
4340 - When building with --enable-static-tor on OpenBSD, do not
4341 erroneously attempt to link -lrt. Fixes bug 5103.
4343 o Minor bugfixes (on 0.2.3.x):
4344 - When Tor is built with kernel headers from a recent (last few
4345 years) Linux kernel, do not fail to run on older (pre-2.6.28
4346 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
4347 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
4349 - Fix compilation with miniupnpc version 1.6; patch from
4350 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
4351 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
4352 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
4353 - Fix compilation on platforms without unistd.h, or where environ
4354 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
4357 - Directory authorities are now a little more lenient at accepting
4358 older router descriptors, or newer router descriptors that don't
4359 make big changes. This should help ameliorate past and future
4360 issues where routers think they have uploaded valid descriptors,
4361 but the authorities don't think so. Fix for ticket 2479.
4362 - Make the code that clients use to detect an address change be
4363 IPv6-aware, so that it won't fill clients' logs with error
4364 messages when trying to get the IPv4 address of an IPv6
4365 connection. Implements ticket 5537.
4368 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
4369 authorities needed to use it for a while to keep the network working
4370 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
4371 that was six months ago. As of now, it should no longer be needed
4375 Changes in version 0.2.3.14-alpha - 2012-04-23
4376 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
4377 candidate. It also dramatically speeds up AES: fast relays should
4378 consider switching to the newer OpenSSL library.
4380 o Directory authority changes:
4381 - Change IP address for ides (v3 directory authority), and rename
4385 - Avoid logging uninitialized data when unable to decode a hidden
4386 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4387 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4388 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4390 - If authorities are unable to get a v2 consensus document from other
4391 directory authorities, they no longer fall back to fetching
4392 them from regular directory caches. Fixes bug 5635; bugfix on
4393 0.2.2.26-beta, where routers stopped downloading v2 consensus
4395 - When we start a Tor client with a normal consensus already cached,
4396 be willing to download a microdescriptor consensus. Fixes bug 4011;
4397 fix on 0.2.3.1-alpha.
4399 o Major features (performance):
4400 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
4401 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
4402 vectorized AES implementations as appropriate. These can be much,
4403 much faster than other AES implementations.
4405 o Minor bugfixes (0.2.2.x and earlier):
4406 - Don't launch more than 10 service-side introduction-point circuits
4407 for a hidden service in five minutes. Previously, we would consider
4408 launching more introduction-point circuits if at least one second
4409 had passed without any introduction-point circuits failing. Fixes
4410 bug 4607; bugfix on 0.0.7pre1.
4411 - Change the BridgePassword feature (part of the "bridge community"
4412 design, which is not yet implemented) to use a time-independent
4413 comparison. The old behavior might have allowed an adversary
4414 to use timing to guess the BridgePassword value. Fixes bug 5543;
4415 bugfix on 0.2.0.14-alpha.
4416 - Enforce correct return behavior of tor_vsscanf() when the '%%'
4417 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
4418 - When sending an HTTP/1.1 proxy request, include a Host header.
4419 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4420 - Don't log that we have "decided to publish new relay descriptor"
4421 unless we are actually publishing a descriptor. Fixes bug 3942;
4422 bugfix on 0.2.2.28-beta.
4424 o Minor bugfixes (0.2.3.x):
4425 - Fix a bug where a bridge authority crashes (on a failed assert)
4426 if it has seen no directory requests when it's time to write
4427 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
4428 - Fix bug stomping on ORPort option NoListen and ignoring option
4429 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
4430 - In the testsuite, provide a large enough buffer in the tor_sscanf
4431 unit test. Otherwise we'd overrun that buffer and crash during
4432 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
4434 - Make sure we create the keys directory if it doesn't exist and we're
4435 about to store the dynamic Diffie-Hellman parameters. Fixes bug
4436 5572; bugfix on 0.2.3.13-alpha.
4437 - Fix a small memory leak when trying to decode incorrect base16
4438 authenticator during SAFECOOKIE authentication. Found by
4439 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
4442 - Add more information to a log statement that might help track down
4443 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
4444 non-IP address" messages (or any Bug messages, for that matter!),
4445 please let us know about it.
4446 - Relays now understand an IPv6 address when they get one from a
4447 directory server. Resolves ticket 4875.
4448 - Resolve IPv6 addresses in bridge and entry statistics to country
4449 code "??" which means we at least count them. Resolves ticket 5053;
4450 improves on 0.2.3.9-alpha.
4451 - Update to the April 3 2012 Maxmind GeoLite Country database.
4452 - Begin a doc/state-contents.txt file to explain the contents of
4453 the Tor state file. Fixes bug 2987.
4455 o Default torrc changes:
4456 - Stop listing "socksport 9050" in torrc.sample. We open a socks
4457 port on 9050 by default anyway, so this should not change anything
4459 - Stop mentioning the deprecated *ListenAddress options in
4460 torrc.sample. Fixes bug 5438.
4461 - Document unit of bandwidth related options in sample torrc.
4465 - The "torify" script no longer supports the "tsocks" socksifier
4466 tool, since tsocks doesn't support DNS and UDP right for Tor.
4467 Everyone should be using torsocks instead. Fixes bugs 3530 and
4468 5180. Based on a patch by "ugh".
4471 - Change the symmetric cipher interface so that creating and
4472 initializing a stream cipher are no longer separate functions.
4473 - Remove all internal support for unpadded RSA. We never used it, and
4474 it would be a bad idea to start.
4477 Changes in version 0.2.3.13-alpha - 2012-03-26
4478 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
4479 in managed pluggable transports, as well as providing other cleanups
4480 that get us closer to a release candidate.
4482 o Directory authority changes:
4483 - Change IP address for maatuska (v3 directory authority).
4486 - Provide controllers with a safer way to implement the cookie
4487 authentication mechanism. With the old method, if another locally
4488 running program could convince a controller that it was the Tor
4489 process, then that program could trick the controller into telling
4490 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4491 authentication method uses a challenge-response approach to prevent
4492 this attack. Fixes bug 5185, implements proposal 193.
4493 - Never use a bridge or a controller-supplied node as an exit, even
4494 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4495 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4496 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4497 - Only build circuits if we have a sufficient threshold of the total
4498 descriptors that are marked in the consensus with the "Exit"
4499 flag. This mitigates an attack proposed by wanoskarnet, in which
4500 all of a client's bridges collude to restrict the exit nodes that
4501 the client knows about. Fixes bug 5343.
4503 o Major bugfixes (on Tor 0.2.3.x):
4504 - Avoid an assert when managed proxies like obfsproxy are configured,
4505 and we receive HUP signals or setconf attempts too rapidly. This
4506 situation happens most commonly when Vidalia tries to attach to
4507 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
4508 bugfix on 0.2.3.6-alpha.
4509 - Fix a relay-side pluggable transports bug where managed proxies were
4510 unreachable from the Internet, because Tor asked them to bind on
4511 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
4512 - Stop discarding command-line arguments when TestingTorNetwork
4513 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
4514 0.2.3.9-alpha, where task 4552 added support for two layers of
4516 - Resume allowing the unit tests to run in gdb. This was accidentally
4517 made impossible when the DisableDebuggerAttachment option was
4518 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
4519 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
4520 0.2.3.11-alpha. Reported by Anthony G. Basile.
4522 o Minor bugfixes (on 0.2.2.x and earlier):
4523 - Ensure we don't cannibalize circuits that are longer than three hops
4524 already, so we don't end up making circuits with 5 or more
4525 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
4526 0.1.0.1-rc which introduced cannibalization.
4527 - Detect and reject certain misformed escape sequences in
4528 configuration values. Previously, these values would cause us
4529 to crash if received in a torrc file or over an authenticated
4530 control port. Bug found by Esteban Manchado Velázquez, and
4531 independently by Robert Connolly from Matta Consulting who further
4532 noted that it allows a post-authentication heap overflow. Patch
4533 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4534 bugfix on 0.2.0.16-alpha.
4535 - Fix a compile warning when using the --enable-openbsd-malloc
4536 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4537 - Directory caches no longer refuse to clean out descriptors because
4538 of missing v2 networkstatus documents, unless they're configured
4539 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
4540 0.2.2.26-beta. Patch by Daniel Bryg.
4541 - Update to the latest version of the tinytest unit testing framework.
4542 This includes a couple of bugfixes that can be relevant for
4543 running forked unit tests on Windows, and removes all reserved
4546 o Minor bugfixes (on 0.2.3.x):
4547 - On a failed pipe() call, don't leak file descriptors. Fixes bug
4548 4296; bugfix on 0.2.3.1-alpha.
4549 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
4550 until after we have received a CERTS cell. Fixes bug 4361; bugfix
4551 on 0.2.3.6-alpha. Patch by "frosty".
4552 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
4553 option, so that the IP stack doesn't decide to use it for IPv4
4554 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
4555 - Ensure that variables set in Tor's environment cannot override
4556 environment variables that Tor passes to a managed
4557 pluggable-transport proxy. Previously, Tor would pass every
4558 variable in its environment to managed proxies along with the new
4559 ones, in such a way that on many operating systems, the inherited
4560 environment variables would override those which Tor tried to
4561 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
4562 bugfix on 0.2.3.9-alpha for Windows.
4565 - A wide variety of new unit tests by Esteban Manchado Velázquez.
4566 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
4567 - Update to the March 6 2012 Maxmind GeoLite Country database.
4570 Changes in version 0.2.3.12-alpha - 2012-02-13
4571 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
4572 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
4573 when Tor is configured to use a pluggable transport like obfsproxy.
4576 - Fix builds when the path to sed, openssl, or sha1sum contains
4577 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4579 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
4580 connections. This change should allow busy exit relays to stop
4581 running out of available sockets as quickly. Fixes bug 4950;
4582 bugfix on 0.2.2.26-beta.
4583 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
4584 would ask the bridge for microdescriptors, which are only supported
4585 in 0.2.3.x, and then fail to bootstrap when it didn't get the
4586 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
4587 - Properly set up obfsproxy's environment when in managed mode. The
4588 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
4589 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
4590 5076 and 5082; bugfix on 0.2.3.6-alpha.
4593 - Use the dead_strip option when building Tor on OS X. This reduces
4594 binary size by almost 19% when linking openssl and libevent
4595 statically, which we do for Tor Browser Bundle.
4596 - Fix broken URLs in the sample torrc file, and tell readers about
4597 the OutboundBindAddress, ExitPolicyRejectPrivate, and
4598 PublishServerDescriptor options. Addresses bug 4652.
4599 - Update to the February 7 2012 Maxmind GeoLite Country database.
4602 - Downgrade the "We're missing a certificate" message from notice
4603 to info: people kept mistaking it for a real problem, whereas it
4604 is seldom the problem even when we are failing to bootstrap. Fixes
4605 bug 5067; bugfix on 0.2.0.10-alpha.
4606 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
4607 managed pluggable transport server proxy's environment.
4608 Previously, we would put it there, even though Tor doesn't
4609 implement an 'extended server port' yet, and even though Tor
4610 almost certainly isn't listening at that address. For now, we set
4611 it to an empty string to avoid crashing older obfsproxies. Bugfix
4613 - Log the heartbeat message every HeartbeatPeriod seconds, not every
4614 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
4615 0.2.3.1-alpha. Bug reported by Scott Bennett.
4616 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
4617 bugfix on 0.2.3.11-alpha.
4618 - Update "ClientOnly" man page entry to explain that there isn't
4619 really any point to messing with it. Resolves ticket 5005.
4620 - Use the correct CVE number for CVE-2011-4576 in our comments and
4621 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
4624 o Code simplifications and refactoring:
4625 - Use the _WIN32 macro throughout our code to detect Windows.
4626 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
4630 Changes in version 0.2.3.11-alpha - 2012-01-22
4631 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
4632 the last step of the plan to limit maximum circuit length, includes
4633 a wide variety of hidden service performance and correctness fixes,
4634 works around an OpenSSL security flaw if your distro is too stubborn
4635 to upgrade, and fixes a bunch of smaller issues.
4638 - Now that Tor 0.2.0.x is completely deprecated, enable the final
4639 part of "Proposal 110: Avoiding infinite length circuits" by
4640 refusing all circuit-extend requests that do not use a relay_early
4641 cell. This change helps Tor resist a class of denial-of-service
4642 attacks by limiting the maximum circuit length.
4643 - Adjust the number of introduction points that a hidden service
4644 will try to maintain based on how long its introduction points
4645 remain in use and how many introductions they handle. Fixes
4647 - Try to use system facilities for enumerating local interface
4648 addresses, before falling back to our old approach (which was
4649 binding a UDP socket, and calling getsockname() on it). That
4650 approach was scaring OS X users whose draconian firewall
4651 software warned about binding to UDP sockets, regardless of
4652 whether packets were sent. Now we try to use getifaddrs(),
4653 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
4654 system supports. Resolves ticket 1827.
4656 o Major security workaround:
4657 - When building or running with any version of OpenSSL earlier
4658 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4659 versions have a bug (CVE-2011-4576) in which their block cipher
4660 padding includes uninitialized data, potentially leaking sensitive
4661 information to any peer with whom they make a SSLv3 connection. Tor
4662 does not use SSL v3 by default, but a hostile client or server
4663 could force an SSLv3 connection in order to gain information that
4664 they shouldn't have been able to get. The best solution here is to
4665 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4666 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4667 to make sure that the bug can't happen.
4670 - Fix the SOCKET_OK test that we use to tell when socket
4671 creation fails so that it works on Win64. Fixes part of bug 4533;
4672 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4673 - Correct our replacements for the timeradd() and timersub() functions
4674 on platforms that lack them (for example, Windows). The timersub()
4675 function is used when expiring circuits, while timeradd() is
4676 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4677 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
4678 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
4679 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
4680 bug at runtime, not compile time, because some distributions hack
4681 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
4682 on 0.2.3.9-alpha. Found by Pascal.
4684 o Minor features (controller):
4685 - Use absolute path names when reporting the torrc filename in the
4686 control protocol, so a controller can more easily find the torrc
4687 file. Resolves bug 1101.
4688 - Extend the control protocol to report flags that control a circuit's
4689 path selection in CIRC events and in replies to 'GETINFO
4690 circuit-status'. Implements part of ticket 2411.
4691 - Extend the control protocol to report the hidden service address
4692 and current state of a hidden-service-related circuit in CIRC
4693 events and in replies to 'GETINFO circuit-status'. Implements part
4695 - When reporting the path to the cookie file to the controller,
4696 give an absolute path. Resolves ticket 4881.
4697 - Allow controllers to request an event notification whenever a
4698 circuit is cannibalized or its purpose is changed. Implements
4699 part of ticket 3457.
4700 - Include the creation time of a circuit in CIRC and CIRC2
4701 control-port events and the list produced by the 'GETINFO
4702 circuit-status' control-port command.
4704 o Minor features (directory authorities):
4705 - Directory authorities now reject versions of Tor older than
4706 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4707 inclusive. These versions accounted for only a small fraction of
4708 the Tor network, and have numerous known security issues. Resolves
4710 - Authority operators can now vote for all relays in a given
4711 set of countries to be BadDir/BadExit/Invalid/Rejected.
4712 - Provide two consensus parameters (FastFlagMinThreshold and
4713 FastFlagMaxThreshold) to control the range of allowable bandwidths
4714 for the Fast directory flag. These allow authorities to run
4715 experiments on appropriate requirements for being a "Fast" node.
4716 The AuthDirFastGuarantee config value still applies. Implements
4718 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4719 directory authority option (introduced in Tor 0.2.2.34).
4721 o Minor features (other):
4722 - Don't disable the DirPort when we cannot exceed our AccountingMax
4723 limit during this interval because the effective bandwidthrate is
4724 low enough. This is useful in a situation where AccountMax is only
4725 used as an additional safeguard or to provide statistics.
4726 - Prepend an informative header to generated dynamic_dh_params files.
4727 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
4728 EntryNodes will have no effect. Resolves issue 2571.
4729 - Log more useful messages when we fail to disable debugger
4731 - Log which authority we're missing votes from when we go to fetch
4732 them from the other auths.
4733 - Log (at debug level) whenever a circuit's purpose is changed.
4734 - Add missing documentation for the MaxClientCircuitsPending,
4735 UseMicrodescriptors, UserspaceIOCPBuffers, and
4736 _UseFilteringSSLBufferevents options, all introduced during
4738 - Update to the January 3 2012 Maxmind GeoLite Country database.
4740 o Minor bugfixes (hidden services):
4741 - Don't close hidden service client circuits which have almost
4742 finished connecting to their destination when they reach
4743 the normal circuit-build timeout. Previously, we would close
4744 introduction circuits which are waiting for an acknowledgement
4745 from the introduction point, and rendezvous circuits which have
4746 been specified in an INTRODUCE1 cell sent to a hidden service,
4747 after the normal CBT. Now, we mark them as 'timed out', and launch
4748 another rendezvous attempt in parallel. This behavior change can
4749 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
4750 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
4751 - Don't close hidden-service-side rendezvous circuits when they
4752 reach the normal circuit-build timeout. This behaviour change can
4753 be disabled using the new
4754 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
4755 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
4756 - Make sure we never mark the wrong rendezvous circuit as having
4757 had its introduction cell acknowleged by the introduction-point
4758 relay. Previously, when we received an INTRODUCE_ACK cell on a
4759 client-side hidden-service introduction circuit, we might have
4760 marked a rendezvous circuit other than the one we specified in
4761 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
4762 a warning message and interfered with the hidden service
4763 connection-establishment process. Fixes bug 4759; bugfix on
4764 0.2.3.3-alpha, when we added the stream-isolation feature which
4765 might cause Tor to open multiple rendezvous circuits for the same
4767 - Don't trigger an assertion failure when we mark a new client-side
4768 hidden-service introduction circuit for close during the process
4769 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
4772 o Minor bugfixes (log messages):
4773 - Correctly spell "connect" in a log message on failure to create a
4774 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
4776 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4777 Fixes bug 4856; bugfix on Tor 0.0.6.
4778 - Fix the log message describing how we work around discovering
4779 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
4780 4837; bugfix on 0.2.2.9-alpha.
4781 - When logging about a disallowed .exit name, do not also call it
4782 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
4784 o Minor bugfixes (build fixes):
4785 - During configure, detect when we're building with clang version
4786 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4787 CFLAGS. clang doesn't support them yet.
4788 - During configure, search for library containing cos function as
4789 libm lives in libcore on some platforms (BeOS/Haiku). Linking
4790 against libm was hard-coded before. Fixes the first part of bug
4791 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
4793 - Detect attempts to build Tor on (as yet hypothetical) versions
4794 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
4795 fix for bug 4533. Bugfix on 0.2.2.28-beta.
4796 - Preprocessor directives should not be put inside the arguments
4797 of a macro. This would break compilation with GCC releases prior
4798 to version 3.3. We would never recommend such an old GCC version,
4799 but it is apparently required for binary compatibility on some
4800 platforms (namely, certain builds of Haiku). Fixes the other part
4801 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
4804 o Minor bugfixes (other):
4805 - Older Linux kernels erroneously respond to strange nmap behavior
4806 by having accept() return successfully with a zero-length
4807 socket. When this happens, just close the connection. Previously,
4808 we would try harder to learn the remote address: but there was
4809 no such remote address to learn, and our method for trying to
4810 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4811 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4812 - Fix null-pointer access that could occur if TLS allocation failed.
4813 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
4814 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
4815 accidentally been reverted.
4816 - Fix our implementation of crypto_random_hostname() so it can't
4817 overflow on ridiculously large inputs. (No Tor version has ever
4818 provided this kind of bad inputs, but let's be correct in depth.)
4819 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
4820 - Find more places in the code that should have been testing for
4821 invalid sockets using the SOCKET_OK macro. Required for a fix
4822 for bug 4533. Bugfix on 0.2.2.28-beta.
4823 - Fix an assertion failure when, while running with bufferevents, a
4824 connection finishes connecting after it is marked for close, but
4825 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
4826 - test_util_spawn_background_ok() hardcoded the expected value
4827 for ENOENT to 2. This isn't portable as error numbers are
4828 platform specific, and particularly the hurd has ENOENT at
4829 0x40000002. Construct expected string at runtime, using the correct
4830 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
4831 - Reject attempts to disable DisableDebuggerAttachment while Tor is
4832 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
4833 - Use an appropriate-width type for sockets in tor-fw-helper on
4834 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
4837 - When sending or relaying a RELAY_EARLY cell, we used to convert
4838 it to a RELAY cell if the connection was using the v1 link
4839 protocol. This was a workaround for older versions of Tor, which
4840 didn't handle RELAY_EARLY cells properly. Now that all supported
4841 versions can handle RELAY_EARLY cells, and now that we're enforcing
4842 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4843 remove this workaround. Addresses bug 4786.
4845 o Code simplifications and refactoring:
4846 - Use OpenSSL's built-in SSL_state_string_long() instead of our
4847 own homebrewed ssl_state_to_string() replacement. Patch from
4848 Emile Snyder. Fixes bug 4653.
4849 - Use macros to indicate OpenSSL versions, so we don't need to worry
4850 about accidental hexadecimal bit shifts.
4851 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
4853 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
4854 - Use the smartlist_add_asprintf() alias more consistently.
4855 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
4856 invalid value, rather than just -1.
4857 - Rename a handful of old identifiers, mostly related to crypto
4858 structures and crypto functions. By convention, our "create an
4859 object" functions are called "type_new()", our "free an object"
4860 functions are called "type_free()", and our types indicate that
4861 they are types only with a final "_t". But a handful of older
4862 types and functions broke these rules, with function names like
4863 "type_create" or "subsystem_op_type", or with type names like
4867 Changes in version 0.2.3.10-alpha - 2011-12-16
4868 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
4869 Tor's buffers code. Absolutely everybody should upgrade.
4871 The bug relied on an incorrect calculation when making data continuous
4872 in one of our IO buffers, if the first chunk of the buffer was
4873 misaligned by just the wrong amount. The miscalculation would allow an
4874 attacker to overflow a piece of heap-allocated memory. To mount this
4875 attack, the attacker would need to either open a SOCKS connection to
4876 Tor's SocksPort (usually restricted to localhost), or target a Tor
4877 instance configured to make its connections through a SOCKS proxy
4878 (which Tor does not do by default).
4880 Good security practice requires that all heap-overflow bugs should be
4881 presumed to be exploitable until proven otherwise, so we are treating
4882 this as a potential code execution attack. Please upgrade immediately!
4883 This bug does not affect bufferevents-based builds of Tor. Special
4884 thanks to "Vektor" for reporting this issue to us!
4886 This release also contains a few minor bugfixes for issues discovered
4890 - Fix a heap overflow bug that could occur when trying to pull
4891 data into the first chunk of a buffer, when that chunk had
4892 already had some data drained from it. Fixes CVE-2011-2778;
4893 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4896 - If we can't attach streams to a rendezvous circuit when we
4897 finish connecting to a hidden service, clear the rendezvous
4898 circuit's stream-isolation state and try to attach streams
4899 again. Previously, we cleared rendezvous circuits' isolation
4900 state either too early (if they were freshly built) or not at all
4901 (if they had been built earlier and were cannibalized). Bugfix on
4902 0.2.3.3-alpha; fixes bug 4655.
4903 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
4904 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
4905 - Fix an assertion failure when a relay with accounting enabled
4906 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
4909 - Update to the December 6 2011 Maxmind GeoLite Country database.
4912 Changes in version 0.2.2.35 - 2011-12-16
4913 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
4914 buffers code. Absolutely everybody should upgrade.
4916 The bug relied on an incorrect calculation when making data continuous
4917 in one of our IO buffers, if the first chunk of the buffer was
4918 misaligned by just the wrong amount. The miscalculation would allow an
4919 attacker to overflow a piece of heap-allocated memory. To mount this
4920 attack, the attacker would need to either open a SOCKS connection to
4921 Tor's SocksPort (usually restricted to localhost), or target a Tor
4922 instance configured to make its connections through a SOCKS proxy
4923 (which Tor does not do by default).
4925 Good security practice requires that all heap-overflow bugs should be
4926 presumed to be exploitable until proven otherwise, so we are treating
4927 this as a potential code execution attack. Please upgrade immediately!
4928 This bug does not affect bufferevents-based builds of Tor. Special
4929 thanks to "Vektor" for reporting this issue to us!
4931 Tor 0.2.2.35 also fixes several bugs in previous versions, including
4932 crash bugs for unusual configurations, and a long-term bug that
4933 would prevent Tor from starting on Windows machines with draconian
4936 With this release, we remind everyone that 0.2.0.x has reached its
4937 formal end-of-life. Those Tor versions have many known flaws, and
4938 nobody should be using them. You should upgrade -- ideally to the
4939 0.2.2.x series. If you're using a Linux or BSD and its packages are
4940 obsolete, stop using those packages and upgrade anyway.
4942 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
4943 longer receive support after some time in early 2012.
4946 - Fix a heap overflow bug that could occur when trying to pull
4947 data into the first chunk of a buffer, when that chunk had
4948 already had some data drained from it. Fixes CVE-2011-2778;
4949 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4950 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4951 that it doesn't attempt to allocate a socketpair. This could cause
4952 some problems on Windows systems with overzealous firewalls. Fix for
4953 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4955 - If we mark an OR connection for close based on a cell we process,
4956 don't process any further cells on it. We already avoid further
4957 reads on marked-for-close connections, but now we also discard the
4958 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4959 which was the first version where we might mark a connection for
4960 close based on processing a cell on it.
4961 - Correctly sanity-check that we don't underflow on a memory
4962 allocation (and then assert) for hidden service introduction
4963 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4964 bugfix on 0.2.1.5-alpha.
4965 - Fix a memory leak when we check whether a hidden service
4966 descriptor has any usable introduction points left. Fixes bug
4967 4424. Bugfix on 0.2.2.25-alpha.
4968 - Don't crash when we're running as a relay and don't have a GeoIP
4969 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
4970 we've had in the 0.2.3.x branch already.
4971 - When running as a client, do not print a misleading (and plain
4972 wrong) log message that we're collecting "directory request"
4973 statistics: clients don't collect statistics. Also don't create a
4974 useless (because empty) stats file in the stats/ directory. Fixes
4975 bug 4353; bugfix on 0.2.2.34.
4978 - Detect failure to initialize Libevent. This fix provides better
4979 detection for future instances of bug 4457.
4980 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4981 function. This was eating up hideously large amounts of time on some
4982 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4983 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4984 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4986 - Don't warn about unused log_mutex in log.c when building with
4987 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4988 0.1.0.6-rc which introduced --disable-threads.
4989 - When configuring, starting, or stopping an NT service, stop
4990 immediately after the service configuration attempt has succeeded
4991 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4992 - When sending a NETINFO cell, include the original address
4993 received for the other side, not its canonical address. Found
4994 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4995 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
4996 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4997 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4998 occurred when a client tried to fetch a descriptor for a bridge
4999 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5000 - Backport fixes for a pair of compilation warnings on Windows.
5001 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
5002 - If we had ever tried to call tor_addr_to_str on an address of
5003 unknown type, we would have done a strdup on an uninitialized
5004 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5005 Reported by "troll_un".
5006 - Correctly detect and handle transient lookup failures from
5007 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5008 Reported by "troll_un".
5009 - Fix null-pointer access that could occur if TLS allocation failed.
5010 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5011 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5012 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5015 - Add two new config options for directory authorities:
5016 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5017 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5018 that is always sufficient to satisfy the bandwidth requirement for
5019 the Guard flag. Now it will be easier for researchers to simulate
5020 Tor networks with different values. Resolves ticket 4484.
5021 - When Tor ignores a hidden service specified in its configuration,
5022 include the hidden service's directory in the warning message.
5023 Previously, we would only tell the user that some hidden service
5024 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5025 - Update to the December 6 2011 Maxmind GeoLite Country database.
5027 o Packaging changes:
5028 - Make it easier to automate expert package builds on Windows,
5029 by removing an absolute path from makensis.exe command.
5032 Changes in version 0.2.1.32 - 2011-12-16
5033 Tor 0.2.1.32 backports important security and privacy fixes for
5034 oldstable. This release is intended only for package maintainers and
5035 others who cannot use the 0.2.2 stable series. All others should be
5036 using Tor 0.2.2.x or newer.
5038 The Tor 0.2.1.x series will reach formal end-of-life some time in
5039 early 2012; we will stop releasing patches for it then.
5041 o Major bugfixes (also included in 0.2.2.x):
5042 - Correctly sanity-check that we don't underflow on a memory
5043 allocation (and then assert) for hidden service introduction
5044 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5045 bugfix on 0.2.1.5-alpha.
5046 - Fix a heap overflow bug that could occur when trying to pull
5047 data into the first chunk of a buffer, when that chunk had
5048 already had some data drained from it. Fixes CVE-2011-2778;
5049 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5052 - Update to the December 6 2011 Maxmind GeoLite Country database.
5055 Changes in version 0.2.3.9-alpha - 2011-12-08
5056 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
5057 a "DisableNetwork" security feature that bundles can use to avoid
5058 touching the network until bridges are configured, moves forward on
5059 the pluggable transport design, fixes a flaw in the hidden service
5060 design that unnecessarily prevented clients with wrong clocks from
5061 reaching hidden services, and fixes a wide variety of other issues.
5064 - Clients can now connect to private bridges over IPv6. Bridges
5065 still need at least one IPv4 address in order to connect to
5066 other relays. Note that we don't yet handle the case where the
5067 user has two bridge lines for the same bridge (one IPv4, one
5068 IPv6). Implements parts of proposal 186.
5069 - New "DisableNetwork" config option to prevent Tor from launching any
5070 connections or accepting any connections except on a control port.
5071 Bundles and controllers can set this option before letting Tor talk
5072 to the rest of the network, for example to prevent any connections
5073 to a non-bridge address. Packages like Orbot can also use this
5074 option to instruct Tor to save power when the network is off.
5075 - Clients and bridges can now be configured to use a separate
5076 "transport" proxy. This approach makes the censorship arms race
5077 easier by allowing bridges to use protocol obfuscation plugins. It
5078 implements the "managed proxy" part of proposal 180 (ticket 3472).
5079 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
5080 implementation. It makes AES_CTR about 7% faster than our old one
5081 (which was about 10% faster than the one OpenSSL used to provide).
5082 Resolves ticket 4526.
5083 - Add a "tor2web mode" for clients that want to connect to hidden
5084 services non-anonymously (and possibly more quickly). As a safety
5085 measure to try to keep users from turning this on without knowing
5086 what they are doing, tor2web mode must be explicitly enabled at
5087 compile time, and a copy of Tor compiled to run in tor2web mode
5088 cannot be used as a normal Tor client. Implements feature 2553.
5089 - Add experimental support for running on Windows with IOCP and no
5090 kernel-space socket buffers. This feature is controlled by a new
5091 "UserspaceIOCPBuffers" config option (off by default), which has
5092 no effect unless Tor has been built with support for bufferevents,
5093 is running on Windows, and has enabled IOCP. This may, in the long
5094 run, help solve or mitigate bug 98.
5095 - Use a more secure consensus parameter voting algorithm. Now at
5096 least three directory authorities or a majority of them must
5097 vote on a given parameter before it will be included in the
5098 consensus. Implements proposal 178.
5101 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
5102 They used to check that the timestamp was within 30 minutes
5103 of their system clock, so they could cap the size of their
5104 replay-detection cache, but that approach unnecessarily refused
5105 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
5106 the v3 intro-point protocol (the first one which sent a timestamp
5107 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
5108 - Only use the EVP interface when AES acceleration is enabled,
5109 to avoid a 5-7% performance regression. Resolves issue 4525;
5110 bugfix on 0.2.3.8-alpha.
5112 o Privacy/anonymity features (bridge detection):
5113 - Make bridge SSL certificates a bit more stealthy by using random
5114 serial numbers, in the same fashion as OpenSSL when generating
5115 self-signed certificates. Implements ticket 4584.
5116 - Introduce a new config option "DynamicDHGroups", enabled by
5117 default, which provides each bridge with a unique prime DH modulus
5118 to be used during SSL handshakes. This option attempts to help
5119 against censors who might use the Apache DH modulus as a static
5120 identifier for bridges. Addresses ticket 4548.
5122 o Minor features (new/different config options):
5123 - New configuration option "DisableDebuggerAttachment" (on by default)
5124 to prevent basic debugging attachment attempts by other processes.
5125 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
5126 - Allow MapAddress directives to specify matches against super-domains,
5127 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
5128 Implements issue 933.
5129 - Slightly change behavior of "list" options (that is, config
5130 options that can appear more than once) when they appear both in
5131 torrc and on the command line. Previously, the command-line options
5132 would be appended to the ones from torrc. Now, the command-line
5133 options override the torrc options entirely. This new behavior
5134 allows the user to override list options (like exit policies and
5135 ports to listen on) from the command line, rather than simply
5136 appending to the list.
5137 - You can get the old (appending) command-line behavior for "list"
5138 options by prefixing the option name with a "+".
5139 - You can remove all the values for a "list" option from the command
5140 line without adding any new ones by prefixing the option name
5142 - Add experimental support for a "defaults" torrc file to be parsed
5143 before the regular torrc. Torrc options override the defaults file's
5144 options in the same way that the command line overrides the torrc.
5145 The SAVECONF controller command saves only those options which
5146 differ between the current configuration and the defaults file. HUP
5147 reloads both files. (Note: This is an experimental feature; its
5148 behavior will probably be refined in future 0.2.3.x-alpha versions
5149 to better meet packagers' needs.) Implements task 4552.
5152 - Try to make the introductory warning message that Tor prints on
5153 startup more useful for actually finding help and information.
5154 Resolves ticket 2474.
5155 - Running "make version" now displays the version of Tor that
5156 we're about to build. Idea from katmagic; resolves issue 4400.
5157 - Expire old or over-used hidden service introduction points.
5158 Required by fix for bug 3460.
5159 - Move the replay-detection cache for the RSA-encrypted parts of
5160 INTRODUCE2 cells to the introduction point data structures.
5161 Previously, we would use one replay-detection cache per hidden
5162 service. Required by fix for bug 3460.
5163 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
5164 public key replay-detection cache from 60 minutes to 5 minutes. This
5165 replay-detection cache is now used only to detect multiple
5166 INTRODUCE2 cells specifying the same rendezvous point, so we can
5167 avoid launching multiple simultaneous attempts to connect to it.
5169 o Minor bugfixes (on Tor 0.2.2.x and earlier):
5170 - Resolve an integer overflow bug in smartlist_ensure_capacity().
5171 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
5173 - Fix a minor formatting issue in one of tor-gencert's error messages.
5175 - Prevent a false positive from the check-spaces script, by disabling
5176 the "whitespace between function name and (" check for functions
5178 - Fix a log message suggesting that people contact a non-existent
5179 email address. Fixes bug 3448.
5180 - Fix null-pointer access that could occur if TLS allocation failed.
5181 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5182 - Report a real bootstrap problem to the controller on router
5183 identity mismatch. Previously we just said "foo", which probably
5184 made a lot of sense at the time. Fixes bug 4169; bugfix on
5186 - If we had ever tried to call tor_addr_to_str() on an address of
5187 unknown type, we would have done a strdup() on an uninitialized
5188 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5189 Reported by "troll_un".
5190 - Correctly detect and handle transient lookup failures from
5191 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5192 Reported by "troll_un".
5193 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5194 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5195 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
5196 bug 4532; found by "troll_un".
5198 o Minor bugfixes (on Tor 0.2.3.x):
5199 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
5201 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
5202 circuit for use as a hidden service client's rendezvous point.
5203 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
5204 with help from wanoskarnet.
5205 - Restore behavior of overriding SocksPort, ORPort, and similar
5206 options from the command line. Bugfix on 0.2.3.3-alpha.
5209 - Properly handle the case where the build-tree is not the same
5210 as the source tree when generating src/common/common_sha1.i,
5211 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
5212 bugfix on 0.2.0.1-alpha.
5214 o Code simplifications, cleanups, and refactorings:
5215 - Remove the pure attribute from all functions that used it
5216 previously. In many cases we assigned it incorrectly, because the
5217 functions might assert or call impure functions, and we don't have
5218 evidence that keeping the pure attribute is worthwhile. Implements
5219 changes suggested in ticket 4421.
5220 - Remove some dead code spotted by coverity. Fixes cid 432.
5221 Bugfix on 0.2.3.1-alpha, closes bug 4637.
5224 Changes in version 0.2.3.8-alpha - 2011-11-22
5225 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
5226 socketpair-related bug that has been bothering Windows users. It adds
5227 support to serve microdescriptors to controllers, so Vidalia's network
5228 map can resume listing relays (once Vidalia implements its side),
5229 and adds better support for hardware AES acceleration. Finally, it
5230 starts the process of adjusting the bandwidth cutoff for getting the
5231 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
5232 that tiny relays harm performance more than they help network capacity.
5235 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5236 that it doesn't attempt to allocate a socketpair. This could cause
5237 some problems on Windows systems with overzealous firewalls. Fix for
5238 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5240 - Correctly sanity-check that we don't underflow on a memory
5241 allocation (and then assert) for hidden service introduction
5242 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5243 bugfix on 0.2.1.5-alpha.
5244 - Remove the artificially low cutoff of 20KB to guarantee the Fast
5245 flag. In the past few years the average relay speed has picked
5246 up, and while the "top 7/8 of the network get the Fast flag" and
5247 "all relays with 20KB or more of capacity get the Fast flag" rules
5248 used to have the same result, now the top 7/8 of the network has
5249 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
5250 - Fix a rare assertion failure when checking whether a v0 hidden
5251 service descriptor has any usable introduction points left, and
5252 we don't have enough information to build a circuit to the first
5253 intro point named in the descriptor. The HS client code in
5254 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
5255 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
5256 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
5257 - Make bridge authorities not crash when they are asked for their own
5258 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
5259 - When running as a client, do not print a misleading (and plain
5260 wrong) log message that we're collecting "directory request"
5261 statistics: clients don't collect statistics. Also don't create a
5262 useless (because empty) stats file in the stats/ directory. Fixes
5263 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
5266 - Allow Tor controllers like Vidalia to obtain the microdescriptor
5267 for a relay by identity digest or nickname. Previously,
5268 microdescriptors were only available by their own digests, so a
5269 controller would have to ask for and parse the whole microdescriptor
5270 consensus in order to look up a single relay's microdesc. Fixes
5271 bug 3832; bugfix on 0.2.3.1-alpha.
5272 - Use OpenSSL's EVP interface for AES encryption, so that all AES
5273 operations can use hardware acceleration (if present). Resolves
5276 o Minor bugfixes (on 0.2.2.x and earlier):
5277 - Detect failure to initialize Libevent. This fix provides better
5278 detection for future instances of bug 4457.
5279 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
5280 function. This was eating up hideously large amounts of time on some
5281 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5282 - Don't warn about unused log_mutex in log.c when building with
5283 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5284 0.1.0.6-rc which introduced --disable-threads.
5285 - Allow manual 'authenticate' commands to the controller interface
5286 from netcat (nc) as well as telnet. We were rejecting them because
5287 they didn't come with the expected whitespace at the end of the
5288 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
5289 - Fix some (not actually triggerable) buffer size checks in usage of
5290 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
5292 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
5293 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
5294 - When configuring, starting, or stopping an NT service, stop
5295 immediately after the service configuration attempt has succeeded
5296 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5297 - When sending a NETINFO cell, include the original address
5298 received for the other side, not its canonical address. Found
5299 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5300 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
5301 can pick them up when the tests aren't disabled. Bugfix on
5302 0.2.2.4-alpha which introduced tinytest.
5303 - Fix a memory leak when we check whether a hidden service
5304 descriptor has any usable introduction points left. Fixes bug
5305 4424. Bugfix on 0.2.2.25-alpha.
5306 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5307 occurred when a client tried to fetch a descriptor for a bridge
5308 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5310 o Minor bugfixes (on 0.2.3.x):
5311 - Make util unit tests build correctly with MSVC. Bugfix on
5312 0.2.3.3-alpha. Patch by Gisle Vanem.
5313 - Successfully detect AUTH_CHALLENGE cells with no recognized
5314 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
5316 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
5317 it should still send a NETINFO cell to allow the connection to
5318 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
5320 - Log less loudly when we get an invalid authentication certificate
5321 from a source other than a directory authority: it's not unusual
5322 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
5324 - Tolerate servers with more clock skew in their authentication
5325 certificates than previously. Fixes bug 4371; bugfix on
5327 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
5328 on 0.2.3.4-alpha and 0.2.3.6-alpha.
5331 - Add two new config options for directory authorities:
5332 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5333 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5334 that is always sufficient to satisfy the bandwidth requirement for
5335 the Guard flag. Now it will be easier for researchers to simulate
5336 Tor networks with different values. Resolves ticket 4484.
5337 - When Tor ignores a hidden service specified in its configuration,
5338 include the hidden service's directory in the warning message.
5339 Previously, we would only tell the user that some hidden service
5340 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5341 - When we fail to initialize Libevent, retry with IOCP disabled so we
5342 don't need to turn on multi-threading support in Libevent, which in
5343 turn requires a working socketpair(). This is a workaround for bug
5344 4457, which affects Libevent versions from 2.0.1-alpha through
5346 - Detect when we try to build on a platform that doesn't define
5347 AF_UNSPEC to 0. We don't work there, so refuse to compile.
5348 - Update to the November 1 2011 Maxmind GeoLite Country database.
5350 o Packaging changes:
5351 - Make it easier to automate expert package builds on Windows,
5352 by removing an absolute path from makensis.exe command.
5354 o Code simplifications and refactoring:
5355 - Remove some redundant #include directives throughout the code.
5356 Patch from Andrea Gelmini.
5357 - Unconditionally use OpenSSL's AES implementation instead of our
5358 old built-in one. OpenSSL's AES has been better for a while, and
5359 relatively few servers should still be on any version of OpenSSL
5360 that doesn't have good optimized assembly AES.
5361 - Use the name "CERTS" consistently to refer to the new cell type;
5362 we were calling it CERT in some places and CERTS in others.
5365 - Numerous new unit tests for functions in util.c and address.c by
5367 - The long-disabled benchmark tests are now split into their own
5368 ./src/test/bench binary.
5369 - The benchmark tests can now use more accurate timers than
5370 gettimeofday() when such timers are available.
5373 Changes in version 0.2.3.7-alpha - 2011-10-30
5374 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
5375 the new v3 handshake. It also resolves yet another bridge address
5379 - If we mark an OR connection for close based on a cell we process,
5380 don't process any further cells on it. We already avoid further
5381 reads on marked-for-close connections, but now we also discard the
5382 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
5383 which was the first version where we might mark a connection for
5384 close based on processing a cell on it.
5385 - Fix a double-free bug that would occur when we received an invalid
5386 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
5387 bugfix on 0.2.3.6-alpha.
5388 - Bridges no longer include their address in NETINFO cells on outgoing
5389 OR connections, to allow them to blend in better with clients.
5390 Removes another avenue for enumerating bridges. Reported by
5391 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
5392 cells were introduced.
5395 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
5396 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
5399 Changes in version 0.2.3.6-alpha - 2011-10-26
5400 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
5401 anonymity vulnerability where an attacker can deanonymize Tor
5402 users. Everybody should upgrade.
5404 This release also features support for a new v3 connection handshake
5405 protocol, and fixes to make hidden service connections more robust.
5408 - Implement a new handshake protocol (v3) for authenticating Tors to
5409 each other over TLS. It should be more resistant to fingerprinting
5410 than previous protocols, and should require less TLS hacking for
5411 future Tor implementations. Implements proposal 176.
5412 - Allow variable-length padding cells to disguise the length of
5413 Tor's TLS records. Implements part of proposal 184.
5415 o Privacy/anonymity fixes (clients):
5416 - Clients and bridges no longer send TLS certificate chains on
5417 outgoing OR connections. Previously, each client or bridge would
5418 use the same cert chain for all outgoing OR connections until
5419 its IP address changes, which allowed any relay that the client
5420 or bridge contacted to determine which entry guards it is using.
5421 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5422 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5423 no longer considers that connection as suitable for satisfying a
5424 circuit EXTEND request. Now relays can protect clients from the
5425 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5426 - Directory authorities no longer assign the Guard flag to relays
5427 that haven't upgraded to the above "refuse EXTEND requests
5428 to client connections" fix. Now directory authorities can
5429 protect clients from the CVE-2011-2768 issue even if neither
5430 the clients nor the relays have upgraded yet. There's a new
5431 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5432 to let us transition smoothly, else tomorrow there would be no
5435 o Major bugfixes (hidden services):
5436 - Improve hidden service robustness: when an attempt to connect to
5437 a hidden service ends, be willing to refetch its hidden service
5438 descriptors from each of the HSDir relays responsible for them
5439 immediately. Previously, we would not consider refetching the
5440 service's descriptors from each HSDir for 15 minutes after the last
5441 fetch, which was inconvenient if the hidden service was not running
5442 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
5443 - When one of a hidden service's introduction points appears to be
5444 unreachable, stop trying it. Previously, we would keep trying
5445 to build circuits to the introduction point until we lost the
5446 descriptor, usually because the user gave up and restarted Tor.
5447 Partly fixes bug 3825.
5448 - Don't launch a useless circuit after failing to use one of a
5449 hidden service's introduction points. Previously, we would
5450 launch a new introduction circuit, but not set the hidden service
5451 which that circuit was intended to connect to, so it would never
5452 actually be used. A different piece of code would then create a
5453 new introduction circuit correctly. Bug reported by katmagic and
5454 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5456 o Major bugfixes (other):
5457 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5458 that they initiated. Relays could distinguish incoming bridge
5459 connections from client connections, creating another avenue for
5460 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5461 Found by "frosty_un".
5462 - Don't update the AccountingSoftLimitHitAt state file entry whenever
5463 tor gets started. This prevents a wrong average bandwidth
5464 estimate, which would cause relays to always start a new accounting
5465 interval at the earliest possible moment. Fixes bug 2003; bugfix
5466 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
5467 immensely in tracking this bug down.
5468 - Fix a crash bug when changing node restrictions while a DNS lookup
5469 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5472 o Minor bugfixes (on 0.2.2.x and earlier):
5473 - When a hidden service turns an extra service-side introduction
5474 circuit into a general-purpose circuit, free the rend_data and
5475 intro_key fields first, so we won't leak memory if the circuit
5476 is cannibalized for use as another service-side introduction
5477 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5478 - Rephrase the log message emitted if the TestSocks check is
5479 successful. Patch from Fabian Keil; fixes bug 4094.
5480 - Bridges now skip DNS self-tests, to act a little more stealthily.
5481 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5482 bridges. Patch by "warms0x".
5483 - Remove a confusing dollar sign from the example fingerprint in the
5484 man page, and also make the example fingerprint a valid one. Fixes
5485 bug 4309; bugfix on 0.2.1.3-alpha.
5486 - Fix internal bug-checking logic that was supposed to catch
5487 failures in digest generation so that it will fail more robustly
5488 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5489 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5490 - Report any failure in init_keys() calls launched because our
5491 IP address has changed. Spotted by Coverity Scan. Bugfix on
5492 0.1.1.4-alpha; fixes CID 484.
5494 o Minor bugfixes (on 0.2.3.x):
5495 - Fix a bug in configure.in that kept it from building a configure
5496 script with autoconf versions earlier than 2.61. Fixes bug 2430;
5497 bugfix on 0.2.3.1-alpha.
5498 - Don't warn users that they are exposing a client port to the
5499 Internet if they have specified an RFC1918 address. Previously,
5500 we would warn if the user had specified any non-loopback
5501 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
5502 - Fix memory leaks in the failing cases of the new SocksPort and
5503 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
5504 fixes coverity CIDs 485, 486, and 487.
5507 - When a hidden service's introduction point times out, consider
5508 trying it again during the next attempt to connect to the
5509 HS. Previously, we would not try it again unless a newly fetched
5510 descriptor contained it. Required by fixes for bugs 1297 and 3825.
5511 - The next version of Windows will be called Windows 8, and it has
5512 a major version of 6, minor version of 2. Correctly identify that
5513 version instead of calling it "Very recent version". Resolves
5514 ticket 4153; reported by funkstar.
5515 - The Bridge Authority now writes statistics on how many bridge
5516 descriptors it gave out in total, and how many unique descriptors
5517 it gave out. It also lists how often the most and least commonly
5518 fetched descriptors were given out, as well as the median and
5519 25th/75th percentile. Implements tickets 4200 and 4294.
5520 - Update to the October 4 2011 Maxmind GeoLite Country database.
5522 o Code simplifications and refactoring:
5523 - Remove some old code to remember statistics about which descriptors
5524 we've served as a directory mirror. The feature wasn't used and
5525 is outdated now that microdescriptors are around.
5526 - Rename Tor functions that turn strings into addresses, so that
5527 "parse" indicates that no hostname resolution occurs, and
5528 "lookup" indicates that hostname resolution may occur. This
5529 should help prevent mistakes in the future. Fixes bug 3512.
5532 Changes in version 0.2.2.34 - 2011-10-26
5533 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
5534 can deanonymize Tor users. Everybody should upgrade.
5536 The attack relies on four components: 1) Clients reuse their TLS cert
5537 when talking to different relays, so relays can recognize a user by
5538 the identity key in her cert. 2) An attacker who knows the client's
5539 identity key can probe each guard relay to see if that identity key
5540 is connected to that guard relay right now. 3) A variety of active
5541 attacks in the literature (starting from "Low-Cost Traffic Analysis
5542 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
5543 discover the guard relays that a Tor user visiting the website is using.
5544 4) Clients typically pick three guards at random, so the set of guards
5545 for a given user could well be a unique fingerprint for her. This
5546 release fixes components #1 and #2, which is enough to block the attack;
5547 the other two remain as open research problems. Special thanks to
5548 "frosty_un" for reporting the issue to us!
5550 Clients should upgrade so they are no longer recognizable by the TLS
5551 certs they present. Relays should upgrade so they no longer allow a
5552 remote attacker to probe them to test whether unpatched clients are
5553 currently connected to them.
5555 This release also fixes several vulnerabilities that allow an attacker
5556 to enumerate bridge relays. Some bridge enumeration attacks still
5557 remain; see for example proposal 188.
5559 o Privacy/anonymity fixes (clients):
5560 - Clients and bridges no longer send TLS certificate chains on
5561 outgoing OR connections. Previously, each client or bridge would
5562 use the same cert chain for all outgoing OR connections until
5563 its IP address changes, which allowed any relay that the client
5564 or bridge contacted to determine which entry guards it is using.
5565 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5566 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5567 no longer considers that connection as suitable for satisfying a
5568 circuit EXTEND request. Now relays can protect clients from the
5569 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5570 - Directory authorities no longer assign the Guard flag to relays
5571 that haven't upgraded to the above "refuse EXTEND requests
5572 to client connections" fix. Now directory authorities can
5573 protect clients from the CVE-2011-2768 issue even if neither
5574 the clients nor the relays have upgraded yet. There's a new
5575 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5576 to let us transition smoothly, else tomorrow there would be no
5579 o Privacy/anonymity fixes (bridge enumeration):
5580 - Bridge relays now do their directory fetches inside Tor TLS
5581 connections, like all the other clients do, rather than connecting
5582 directly to the DirPort like public relays do. Removes another
5583 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5584 - Bridges relays now build circuits for themselves in a more similar
5585 way to how clients build them. Removes another avenue for
5586 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5587 when bridges were introduced.
5588 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5589 that they initiated. Relays could distinguish incoming bridge
5590 connections from client connections, creating another avenue for
5591 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5592 Found by "frosty_un".
5595 - Fix a crash bug when changing node restrictions while a DNS lookup
5596 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5598 - Don't launch a useless circuit after failing to use one of a
5599 hidden service's introduction points. Previously, we would
5600 launch a new introduction circuit, but not set the hidden service
5601 which that circuit was intended to connect to, so it would never
5602 actually be used. A different piece of code would then create a
5603 new introduction circuit correctly. Bug reported by katmagic and
5604 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5607 - Change an integer overflow check in the OpenBSD_Malloc code so
5608 that GCC is less likely to eliminate it as impossible. Patch
5609 from Mansour Moufid. Fixes bug 4059.
5610 - When a hidden service turns an extra service-side introduction
5611 circuit into a general-purpose circuit, free the rend_data and
5612 intro_key fields first, so we won't leak memory if the circuit
5613 is cannibalized for use as another service-side introduction
5614 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5615 - Bridges now skip DNS self-tests, to act a little more stealthily.
5616 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5617 bridges. Patch by "warms0x".
5618 - Fix internal bug-checking logic that was supposed to catch
5619 failures in digest generation so that it will fail more robustly
5620 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5621 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5622 - Report any failure in init_keys() calls launched because our
5623 IP address has changed. Spotted by Coverity Scan. Bugfix on
5624 0.1.1.4-alpha; fixes CID 484.
5626 o Minor bugfixes (log messages and documentation):
5627 - Remove a confusing dollar sign from the example fingerprint in the
5628 man page, and also make the example fingerprint a valid one. Fixes
5629 bug 4309; bugfix on 0.2.1.3-alpha.
5630 - The next version of Windows will be called Windows 8, and it has
5631 a major version of 6, minor version of 2. Correctly identify that
5632 version instead of calling it "Very recent version". Resolves
5633 ticket 4153; reported by funkstar.
5634 - Downgrade log messages about circuit timeout calibration from
5635 "notice" to "info": they don't require or suggest any human
5636 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5637 bugfix on 0.2.2.14-alpha.
5640 - Turn on directory request statistics by default and include them in
5641 extra-info descriptors. Don't break if we have no GeoIP database.
5642 Backported from 0.2.3.1-alpha; implements ticket 3951.
5643 - Update to the October 4 2011 Maxmind GeoLite Country database.
5646 Changes in version 0.2.1.31 - 2011-10-26
5647 Tor 0.2.1.31 backports important security and privacy fixes for
5648 oldstable. This release is intended only for package maintainers and
5649 others who cannot use the 0.2.2 stable series. All others should be
5650 using Tor 0.2.2.x or newer.
5652 o Security fixes (also included in 0.2.2.x):
5653 - Replace all potentially sensitive memory comparison operations
5654 with versions whose runtime does not depend on the data being
5655 compared. This will help resist a class of attacks where an
5656 adversary can use variations in timing information to learn
5657 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5658 implementation by Robert Ransom based partially on code by DJB.)
5659 - Fix an assert in parsing router descriptors containing IPv6
5660 addresses. This one took down the directory authorities when
5661 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5663 o Privacy/anonymity fixes (also included in 0.2.2.x):
5664 - Clients and bridges no longer send TLS certificate chains on
5665 outgoing OR connections. Previously, each client or bridge would
5666 use the same cert chain for all outgoing OR connections until
5667 its IP address changes, which allowed any relay that the client
5668 or bridge contacted to determine which entry guards it is using.
5669 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5670 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5671 no longer considers that connection as suitable for satisfying a
5672 circuit EXTEND request. Now relays can protect clients from the
5673 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5674 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5675 that they initiated. Relays could distinguish incoming bridge
5676 connections from client connections, creating another avenue for
5677 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5678 Found by "frosty_un".
5679 - When receiving a hidden service descriptor, check that it is for
5680 the hidden service we wanted. Previously, Tor would store any
5681 hidden service descriptors that a directory gave it, whether it
5682 wanted them or not. This wouldn't have let an attacker impersonate
5683 a hidden service, but it did let directories pre-seed a client
5684 with descriptors that it didn't want. Bugfix on 0.0.6.
5685 - Avoid linkability based on cached hidden service descriptors: forget
5686 all hidden service descriptors cached as a client when processing a
5687 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5688 - Make the bridge directory authority refuse to answer directory
5689 requests for "all" descriptors. It used to include bridge
5690 descriptors in its answer, which was a major information leak.
5691 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5692 - Don't attach new streams to old rendezvous circuits after SIGNAL
5693 NEWNYM. Previously, we would keep using an existing rendezvous
5694 circuit if it remained open (i.e. if it were kept open by a
5695 long-lived stream, or if a new stream were attached to it before
5696 Tor could notice that it was old and no longer in use). Bugfix on
5697 0.1.1.15-rc; fixes bug 3375.
5699 o Minor bugfixes (also included in 0.2.2.x):
5700 - When we restart our relay, we might get a successful connection
5701 from the outside before we've started our reachability tests,
5702 triggering a warning: "ORPort found reachable, but I have no
5703 routerinfo yet. Failing to inform controller of success." This
5704 bug was harmless unless Tor is running under a controller
5705 like Vidalia, in which case the controller would never get a
5706 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5708 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5709 enabled. Fixes bug 1526.
5710 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5711 anything since 0.2.1.16-rc.
5712 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5713 None of the cases where we did this before were wrong, but by making
5714 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5715 - Fix a rare crash bug that could occur when a client was configured
5716 with a large number of bridges. Fixes bug 2629; bugfix on
5717 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5718 - Correct the warning displayed when a rendezvous descriptor exceeds
5719 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5721 - Fix an uncommon assertion failure when running with DNSPort under
5722 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5723 - When warning about missing zlib development packages during compile,
5724 give the correct package names. Bugfix on 0.2.0.1-alpha.
5725 - Require that introduction point keys and onion keys have public
5726 exponent 65537. Bugfix on 0.2.0.10-alpha.
5727 - Do not crash when our configuration file becomes unreadable, for
5728 example due to a permissions change, between when we start up
5729 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5731 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5733 - Always NUL-terminate the sun_path field of a sockaddr_un before
5734 passing it to the kernel. (Not a security issue: kernels are
5735 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5736 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5737 - Don't stack-allocate the list of supplementary GIDs when we're
5738 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5739 could take up to 256K, which is way too much stack. Found by
5740 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5742 o Minor bugfixes (only in 0.2.1.x):
5743 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
5744 rely on them. Bugfix on 0.2.1.30.
5745 - Use git revisions instead of svn revisions when generating our
5746 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5748 o Minor features (also included in 0.2.2.x):
5749 - Adjust the expiration time on our SSL session certificates to
5750 better match SSL certs seen in the wild. Resolves ticket 4014.
5751 - Allow nameservers with IPv6 address. Resolves bug 2574.
5752 - Update to the October 4 2011 Maxmind GeoLite Country database.
5755 Changes in version 0.2.3.5-alpha - 2011-09-28
5756 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
5757 bridge relays; fixes an assertion error that many users started hitting
5758 today; and adds the ability to refill token buckets more often than
5759 once per second, allowing significant performance improvements.
5762 - Bridge relays now do their directory fetches inside Tor TLS
5763 connections, like all the other clients do, rather than connecting
5764 directly to the DirPort like public relays do. Removes another
5765 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5766 - Bridges relays now build circuits for themselves in a more similar
5767 way to how clients build them. Removes another avenue for
5768 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5769 when bridges were introduced.
5772 - Fix an "Assertion md->held_by_node == 1 failed" error that could
5773 occur when the same microdescriptor was referenced by two node_t
5774 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
5776 o Major features (networking):
5777 - Add a new TokenBucketRefillInterval option to refill token buckets
5778 more frequently than once per second. This should improve network
5779 performance, alleviate queueing problems, and make traffic less
5780 bursty. Implements proposal 183; closes ticket 3630. Design by
5781 Florian Tschorsch and Björn Scheuermann; implementation by
5785 - Change an integer overflow check in the OpenBSD_Malloc code so
5786 that GCC is less likely to eliminate it as impossible. Patch
5787 from Mansour Moufid. Fixes bug 4059.
5789 o Minor bugfixes (usability):
5790 - Downgrade log messages about circuit timeout calibration from
5791 "notice" to "info": they don't require or suggest any human
5792 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5793 bugfix on 0.2.2.14-alpha.
5795 o Minor features (diagnostics):
5796 - When the system call to create a listener socket fails, log the
5797 error message explaining why. This may help diagnose bug 4027.
5800 Changes in version 0.2.3.4-alpha - 2011-09-13
5801 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
5802 tweak to Tor's TLS handshake that makes relays and bridges that run
5803 this new version reachable from Iran again. It also fixes a few new
5804 bugs in 0.2.3.x, and teaches relays to recognize when they're not
5805 listed in the network consensus and republish.
5807 o Major bugfixes (also part of 0.2.2.33):
5808 - Avoid an assertion failure when reloading a configuration with
5809 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5810 3923; bugfix on 0.2.2.25-alpha.
5812 o Minor features (security, also part of 0.2.2.33):
5813 - Check for replays of the public-key encrypted portion of an
5814 INTRODUCE1 cell, in addition to the current check for replays of
5815 the g^x value. This prevents a possible class of active attacks
5816 by an attacker who controls both an introduction point and a
5817 rendezvous point, and who uses the malleability of AES-CTR to
5818 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5819 that these attacks are infeasible (requiring the attacker to send
5820 on the order of zettabytes of altered cells in a short interval),
5821 but we'd rather block them off in case there are any classes of
5822 this attack that we missed. Reported by Willem Pinckaers.
5824 o Minor features (also part of 0.2.2.33):
5825 - Adjust the expiration time on our SSL session certificates to
5826 better match SSL certs seen in the wild. Resolves ticket 4014.
5827 - Change the default required uptime for a relay to be accepted as
5828 a HSDir (hidden service directory) from 24 hours to 25 hours.
5829 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5830 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5831 authorities to abstain from voting on assignment of the HSDir
5832 consensus flag. Related to bug 2649.
5833 - Update to the September 6 2011 Maxmind GeoLite Country database.
5835 o Minor bugfixes (also part of 0.2.2.33):
5836 - Demote the 'replay detected' log message emitted when a hidden
5837 service receives the same Diffie-Hellman public key in two different
5838 INTRODUCE2 cells to info level. A normal Tor client can cause that
5839 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5840 fixes part of bug 2442.
5841 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5842 level. There is nothing that a hidden service's operator can do
5843 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5845 - Clarify a log message specifying the characters permitted in
5846 HiddenServiceAuthorizeClient client names. Previously, the log
5847 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5848 given the impression that every ASCII character between "+" and "_"
5849 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5851 o Build fixes (also part of 0.2.2.33):
5852 - Clean up some code issues that prevented Tor from building on older
5853 BSDs. Fixes bug 3894; reported by "grarpamp".
5854 - Search for a platform-specific version of "ar" when cross-compiling.
5855 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5858 - Fix a bug where the SocksPort option (for example) would get
5859 ignored and replaced by the default if a SocksListenAddress
5860 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
5864 - Relays now try regenerating and uploading their descriptor more
5865 frequently if they are not listed in the consensus, or if the
5866 version of their descriptor listed in the consensus is too
5867 old. This fix should prevent situations where a server declines
5868 to re-publish itself because it has done so too recently, even
5869 though the authorities decided not to list its recent-enough
5870 descriptor. Fix for bug 3327.
5873 - Relays now include a reason for regenerating their descriptors
5874 in an HTTP header when uploading to the authorities. This will
5875 make it easier to debug descriptor-upload issues in the future.
5876 - When starting as root and then changing our UID via the User
5877 control option, and we have a ControlSocket configured, make sure
5878 that the ControlSocket is owned by the same account that Tor will
5879 run under. Implements ticket 3421; fix by Jérémy Bobbio.
5882 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
5883 utility function used in the control-port code). This shouldn't
5884 ever happen unless Tor is completely out of memory, but if it did
5885 happen and Tor somehow recovered from it, Tor could have sent a log
5886 message to a control port in the middle of a reply to a controller
5887 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
5888 - Make 'FetchUselessDescriptors' cause all descriptor types and
5889 all consensus types (including microdescriptors) to get fetched.
5890 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
5893 - Make a new "entry connection" struct as an internal subtype of "edge
5894 connection", to simplify the code and make exit connections smaller.
5897 Changes in version 0.2.2.33 - 2011-09-13
5898 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
5899 TLS handshake that makes relays and bridges that run this new version
5900 reachable from Iran again.
5903 - Avoid an assertion failure when reloading a configuration with
5904 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5905 3923; bugfix on 0.2.2.25-alpha.
5907 o Minor features (security):
5908 - Check for replays of the public-key encrypted portion of an
5909 INTRODUCE1 cell, in addition to the current check for replays of
5910 the g^x value. This prevents a possible class of active attacks
5911 by an attacker who controls both an introduction point and a
5912 rendezvous point, and who uses the malleability of AES-CTR to
5913 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5914 that these attacks are infeasible (requiring the attacker to send
5915 on the order of zettabytes of altered cells in a short interval),
5916 but we'd rather block them off in case there are any classes of
5917 this attack that we missed. Reported by Willem Pinckaers.
5920 - Adjust the expiration time on our SSL session certificates to
5921 better match SSL certs seen in the wild. Resolves ticket 4014.
5922 - Change the default required uptime for a relay to be accepted as
5923 a HSDir (hidden service directory) from 24 hours to 25 hours.
5924 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5925 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5926 authorities to abstain from voting on assignment of the HSDir
5927 consensus flag. Related to bug 2649.
5928 - Update to the September 6 2011 Maxmind GeoLite Country database.
5930 o Minor bugfixes (documentation and log messages):
5931 - Correct the man page to explain that HashedControlPassword and
5932 CookieAuthentication can both be set, in which case either method
5933 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5934 when we decided to allow these config options to both be set. Issue
5936 - Demote the 'replay detected' log message emitted when a hidden
5937 service receives the same Diffie-Hellman public key in two different
5938 INTRODUCE2 cells to info level. A normal Tor client can cause that
5939 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5940 fixes part of bug 2442.
5941 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5942 level. There is nothing that a hidden service's operator can do
5943 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5945 - Clarify a log message specifying the characters permitted in
5946 HiddenServiceAuthorizeClient client names. Previously, the log
5947 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5948 given the impression that every ASCII character between "+" and "_"
5949 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5952 - Provide a substitute implementation of lround() for MSVC, which
5953 apparently lacks it. Patch from Gisle Vanem.
5954 - Clean up some code issues that prevented Tor from building on older
5955 BSDs. Fixes bug 3894; reported by "grarpamp".
5956 - Search for a platform-specific version of "ar" when cross-compiling.
5957 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5960 Changes in version 0.2.3.3-alpha - 2011-09-01
5961 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
5962 security, and provides client-side support for the microdescriptor
5963 and optimistic data features introduced earlier in the 0.2.3.x
5964 series. It also includes numerous critical bugfixes in the (optional)
5965 bufferevent-based networking backend.
5967 o Major features (stream isolation):
5968 - You can now configure Tor so that streams from different
5969 applications are isolated on different circuits, to prevent an
5970 attacker who sees your streams as they leave an exit node from
5971 linking your sessions to one another. To do this, choose some way
5972 to distinguish the applications: have them connect to different
5973 SocksPorts, or have one of them use SOCKS4 while the other uses
5974 SOCKS5, or have them pass different authentication strings to the
5975 SOCKS proxy. Then, use the new SocksPort syntax to configure the
5976 degree of isolation you need. This implements Proposal 171.
5977 - There's a new syntax for specifying multiple client ports (such as
5978 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
5979 multiple *Port entries with full addr:port syntax on each.
5980 The old *ListenAddress format is still supported, but you can't
5981 mix it with the new *Port syntax.
5983 o Major features (other):
5984 - Enable microdescriptor fetching by default for clients. This allows
5985 clients to download a much smaller amount of directory information.
5986 To disable it (and go back to the old-style consensus and
5987 descriptors), set "UseMicrodescriptors 0" in your torrc file.
5988 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
5989 "PortForwarding" config option), now supports Windows.
5990 - When using an exit relay running 0.2.3.x, clients can now
5991 "optimistically" send data before the exit relay reports that
5992 the stream has opened. This saves a round trip when starting
5993 connections where the client speaks first (such as web browsing).
5994 This behavior is controlled by a consensus parameter (currently
5995 disabled). To turn it on or off manually, use the "OptimisticData"
5996 torrc option. Implements proposal 181; code by Ian Goldberg.
5998 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
5999 - When using IOCP on Windows, we need to enable Libevent windows
6001 - The IOCP backend now works even when the user has not specified
6002 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
6003 Fixes part of bug 3752.
6004 - Correctly record the bytes we've read and written when using
6005 bufferevents, so that we can include them in our bandwidth history
6006 and advertised bandwidth. Fixes bug 3803.
6007 - Apply rate-limiting only at the bottom of a chain of filtering
6008 bufferevents. This prevents us from filling up internal read
6009 buffers and violating rate-limits when filtering bufferevents
6010 are enabled. Fixes part of bug 3804.
6011 - Add high-watermarks to the output buffers for filtered
6012 bufferevents. This prevents us from filling up internal write
6013 buffers and wasting CPU cycles when filtering bufferevents are
6014 enabled. Fixes part of bug 3804.
6015 - Correctly notice when data has been written from a bufferevent
6016 without flushing it completely. Fixes bug 3805.
6017 - Fix a bug where server-side tunneled bufferevent-based directory
6018 streams would get closed prematurely. Fixes bug 3814.
6019 - Fix a use-after-free error with per-connection rate-limiting
6020 buckets. Fixes bug 3888.
6022 o Major bugfixes (also part of 0.2.2.31-rc):
6023 - If we're configured to write our ControlPorts to disk, only write
6024 them after switching UID and creating the data directory. This way,
6025 we don't fail when starting up with a nonexistent DataDirectory
6026 and a ControlPortWriteToFile setting based on that directory. Fixes
6027 bug 3747; bugfix on Tor 0.2.2.26-beta.
6030 - Added a new CONF_CHANGED event so that controllers can be notified
6031 of any configuration changes made by other controllers, or by the
6032 user. Implements ticket 1692.
6033 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
6034 leak when using bufferevents, and lets Libevent worry about how to
6035 best copy data out of a buffer.
6036 - Replace files in stats/ rather than appending to them. Now that we
6037 include statistics in extra-info descriptors, it makes no sense to
6038 keep old statistics forever. Implements ticket 2930.
6040 o Minor features (build compatibility):
6041 - Limited, experimental support for building with nmake and MSVC.
6042 - Provide a substitute implementation of lround() for MSVC, which
6043 apparently lacks it. Patch from Gisle Vanem.
6045 o Minor features (also part of 0.2.2.31-rc):
6046 - Update to the August 2 2011 Maxmind GeoLite Country database.
6048 o Minor bugfixes (on 0.2.3.x-alpha):
6049 - Fix a spurious warning when parsing SOCKS requests with
6050 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
6051 - Get rid of a harmless warning that could happen on relays running
6052 with bufferevents. The warning was caused by someone doing an http
6053 request to a relay's orport. Also don't warn for a few related
6054 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
6056 o Minor bugfixes (on 2.2.x and earlier):
6057 - Correct the man page to explain that HashedControlPassword and
6058 CookieAuthentication can both be set, in which case either method
6059 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
6060 when we decided to allow these config options to both be set. Issue
6062 - The "--quiet" and "--hush" options now apply not only to Tor's
6063 behavior before logs are configured, but also to Tor's behavior in
6064 the absense of configured logs. Fixes bug 3550; bugfix on
6067 o Minor bugfixes (also part of 0.2.2.31-rc):
6068 - Write several files in text mode, on OSes that distinguish text
6069 mode from binary mode (namely, Windows). These files are:
6070 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6071 that collect those statistics; 'client_keys' and 'hostname' for
6072 hidden services that use authentication; and (in the tor-gencert
6073 utility) newly generated identity and signing keys. Previously,
6074 we wouldn't specify text mode or binary mode, leading to an
6075 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6076 the DirRecordUsageByCountry option which would have triggered
6077 the assertion failure was added), although this assertion failure
6078 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6079 - Selectively disable deprecation warnings on OS X because Lion
6080 started deprecating the shipped copy of openssl. Fixes bug 3643.
6081 - Remove an extra pair of quotation marks around the error
6082 message in control-port STATUS_GENERAL BUG events. Bugfix on
6083 0.1.2.6-alpha; fixes bug 3732.
6084 - When unable to format an address as a string, report its value
6085 as "???" rather than reusing the last formatted address. Bugfix
6088 o Code simplifications and refactoring:
6089 - Rewrite the listener-selection logic so that parsing which ports
6090 we want to listen on is now separate from binding to the ports
6094 - Building Tor with bufferevent support now requires Libevent
6095 2.0.13-stable or later. Previous versions of Libevent had bugs in
6096 SSL-related bufferevents and related issues that would make Tor
6097 work badly with bufferevents. Requiring 2.0.13-stable also allows
6098 Tor with bufferevents to take advantage of Libevent APIs
6099 introduced after 2.0.8-rc.
6102 Changes in version 0.2.2.32 - 2011-08-27
6103 The Tor 0.2.2 release series is dedicated to the memory of Andreas
6104 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
6105 a founder of the PETS community, a leader in our field, a mentor,
6106 and a friend. He left us with these words: "I had the possibility
6107 to contribute to this world that is not as it should be. I hope I
6108 could help in some areas to make the world a better place, and that
6109 I could also encourage other people to be engaged in improving the
6110 world. Please, stay engaged. This world needs you, your love, your
6111 initiative -- now I cannot be part of that anymore."
6113 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
6114 ready. More than two years in the making, this release features improved
6115 client performance and hidden service reliability, better compatibility
6116 for Android, correct behavior for bridges that listen on more than
6117 one address, more extensible and flexible directory object handling,
6118 better reporting of network statistics, improved code security, and
6119 many many other features and bugfixes.
6122 Changes in version 0.2.2.31-rc - 2011-08-17
6123 Tor 0.2.2.31-rc is the second and hopefully final release candidate
6124 for the Tor 0.2.2.x series.
6127 - Remove an extra pair of quotation marks around the error
6128 message in control-port STATUS_GENERAL BUG events. Bugfix on
6129 0.1.2.6-alpha; fixes bug 3732.
6130 - If we're configured to write our ControlPorts to disk, only write
6131 them after switching UID and creating the data directory. This way,
6132 we don't fail when starting up with a nonexistent DataDirectory
6133 and a ControlPortWriteToFile setting based on that directory. Fixes
6134 bug 3747; bugfix on Tor 0.2.2.26-beta.
6137 - Update to the August 2 2011 Maxmind GeoLite Country database.
6140 - Allow GETINFO fingerprint to return a fingerprint even when
6141 we have not yet built a router descriptor. Fixes bug 3577;
6142 bugfix on 0.2.0.1-alpha.
6143 - Write several files in text mode, on OSes that distinguish text
6144 mode from binary mode (namely, Windows). These files are:
6145 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6146 that collect those statistics; 'client_keys' and 'hostname' for
6147 hidden services that use authentication; and (in the tor-gencert
6148 utility) newly generated identity and signing keys. Previously,
6149 we wouldn't specify text mode or binary mode, leading to an
6150 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6151 the DirRecordUsageByCountry option which would have triggered
6152 the assertion failure was added), although this assertion failure
6153 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6154 - Selectively disable deprecation warnings on OS X because Lion
6155 started deprecating the shipped copy of openssl. Fixes bug 3643.
6156 - When unable to format an address as a string, report its value
6157 as "???" rather than reusing the last formatted address. Bugfix
6161 Changes in version 0.2.3.2-alpha - 2011-07-18
6162 Tor 0.2.3.2-alpha introduces two new experimental features:
6163 microdescriptors and pluggable transports. It also continues cleaning
6164 up a variety of recently introduced features.
6167 - Clients can now use microdescriptors instead of regular descriptors
6168 to build circuits. Microdescriptors are authority-generated
6169 summaries of regular descriptors' contents, designed to change
6170 very rarely (see proposal 158 for details). This feature is
6171 designed to save bandwidth, especially for clients on slow internet
6172 connections. It's off by default for now, since nearly no caches
6173 support it, but it will be on-by-default for clients in a future
6174 version. You can use the UseMicrodescriptors option to turn it on.
6175 - Tor clients using bridges can now be configured to use a separate
6176 'transport' proxy for each bridge. This approach helps to resist
6177 censorship by allowing bridges to use protocol obfuscation
6178 plugins. It implements part of proposal 180. Implements ticket 2841.
6179 - While we're trying to bootstrap, record how many TLS connections
6180 fail in each state, and report which states saw the most failures
6181 in response to any bootstrap failures. This feature may speed up
6182 diagnosis of censorship events. Implements ticket 3116.
6184 o Major bugfixes (on 0.2.3.1-alpha):
6185 - When configuring a large set of nodes in EntryNodes (as with
6186 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
6187 random subset to be guards, and choose them in random
6188 order. Fixes bug 2798.
6189 - Tor could crash when remembering a consensus in a non-used consensus
6190 flavor without having a current consensus set. Fixes bug 3361.
6191 - Comparing an unknown address to a microdescriptor's shortened exit
6192 policy would always give a "rejected" result. Fixes bug 3599.
6193 - Using microdescriptors as a client no longer prevents Tor from
6194 uploading and downloading hidden service descriptors. Fixes
6198 - Allow nameservers with IPv6 address. Resolves bug 2574.
6199 - Accept attempts to include a password authenticator in the
6200 handshake, as supported by SOCKS5. This handles SOCKS clients that
6201 don't know how to omit a password when authenticating. Resolves
6203 - When configuring a large set of nodes in EntryNodes, and there are
6204 enough of them listed as Guard so that we don't need to consider
6205 the non-guard entries, prefer the ones listed with the Guard flag.
6206 - Check for and recover from inconsistency in the microdescriptor
6207 cache. This will make it harder for us to accidentally free a
6208 microdescriptor without removing it from the appropriate data
6209 structures. Fixes issue 3135; issue noted by "wanoskarnet".
6210 - Log SSL state transitions at log level DEBUG, log domain
6211 HANDSHAKE. This can be useful for debugging censorship events.
6212 Implements ticket 3264.
6213 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
6214 implements ticket 3439.
6216 o Minor bugfixes (on 0.2.3.1-alpha):
6217 - Do not free all general-purpose regular descriptors just
6218 because microdescriptor use is enabled. Fixes bug 3113.
6219 - Correctly link libevent_openssl when --enable-static-libevent
6220 is passed to configure. Fixes bug 3118.
6221 - Bridges should not complain during their heartbeat log messages that
6222 they are unlisted in the consensus: that's more or less the point
6223 of being a bridge. Fixes bug 3183.
6224 - Report a SIGNAL event to controllers when acting on a delayed
6225 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
6226 event to the controller if we acted on a SIGNAL NEWNYM command
6227 immediately, and otherwise not report a SIGNAL event for the
6228 command at all. Fixes bug 3349.
6229 - Fix a crash when handling the SIGNAL controller command or
6230 reporting ERR-level status events with bufferevents enabled. Found
6231 by Robert Ransom. Fixes bug 3367.
6232 - Always ship the tor-fw-helper manpage in our release tarballs.
6233 Fixes bug 3389. Reported by Stephen Walker.
6234 - Fix a class of double-mark-for-close bugs when bufferevents
6235 are enabled. Fixes bug 3403.
6236 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
6237 - Add SIGNAL to the list returned by the 'GETINFO events/names'
6238 control-port command. Fixes part of bug 3465.
6239 - Prevent using negative indices during unit test runs when read_all()
6240 fails. Spotted by coverity.
6241 - Fix a rare memory leak when checking the nodelist without it being
6242 present. Found by coverity.
6243 - Only try to download a microdescriptor-flavored consensus from
6244 a directory cache that provides them.
6246 o Minor bugfixes (on 0.2.2.x and earlier):
6247 - Assert that hidden-service-related operations are not performed
6248 using single-hop circuits. Previously, Tor would assert that
6249 client-side streams are not attached to single-hop circuits,
6250 but not that other sensitive operations on the client and service
6251 side are not performed using single-hop circuits. Fixes bug 3332;
6253 - Don't publish a new relay descriptor when we reload our onion key,
6254 unless the onion key has actually changed. Fixes bug 3263 and
6255 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
6256 - Allow GETINFO fingerprint to return a fingerprint even when
6257 we have not yet built a router descriptor. Fixes bug 3577;
6258 bugfix on 0.2.0.1-alpha.
6259 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
6260 on 0.2.2.4-alpha; fixes bug 3427.
6262 o Code simplification and refactoring:
6263 - Use tor_sscanf() in place of scanf() in more places through the
6264 code. This makes us a little more locale-independent, and
6265 should help shut up code-analysis tools that can't tell
6266 a safe sscanf string from a dangerous one.
6267 - Use tt_assert(), not tor_assert(), for checking for test failures.
6268 This makes the unit tests more able to go on in the event that
6270 - Split connection_about_to_close() into separate functions for each
6274 - On Windows, we now define the _WIN32_WINNT macros only if they
6275 are not already defined. This lets the person building Tor decide,
6276 if they want, to require a later version of Windows.
6279 Changes in version 0.2.2.30-rc - 2011-07-07
6280 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
6281 series. It fixes a few smaller bugs, but generally appears stable.
6282 Please test it and let us know whether it is!
6285 - Send a SUCCEEDED stream event to the controller when a reverse
6286 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
6287 discovered by katmagic.
6288 - Always NUL-terminate the sun_path field of a sockaddr_un before
6289 passing it to the kernel. (Not a security issue: kernels are
6290 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6291 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6292 - Don't stack-allocate the list of supplementary GIDs when we're
6293 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6294 could take up to 256K, which is way too much stack. Found by
6295 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6296 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
6297 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
6298 fixes part of bug 3465.
6299 - Fix a memory leak when receiving a descriptor for a hidden
6300 service we didn't ask for. Found by Coverity; CID #30. Bugfix
6304 - Update to the July 1 2011 Maxmind GeoLite Country database.
6307 Changes in version 0.2.2.29-beta - 2011-06-20
6308 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
6309 have bridge lines in their torrc but don't want to use them; gets
6310 us closer to having the control socket feature working on Debian;
6311 and fixes a variety of smaller bugs.
6314 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
6315 When we changed the default behavior to "use bridges if any
6316 are listed in the torrc", we surprised users who had bridges
6317 in their torrc files but who didn't actually want to use them.
6318 Partial resolution for bug 3354.
6321 - Don't attach new streams to old rendezvous circuits after SIGNAL
6322 NEWNYM. Previously, we would keep using an existing rendezvous
6323 circuit if it remained open (i.e. if it were kept open by a
6324 long-lived stream, or if a new stream were attached to it before
6325 Tor could notice that it was old and no longer in use). Bugfix on
6326 0.1.1.15-rc; fixes bug 3375.
6329 - Fix a bug when using ControlSocketsGroupWritable with User. The
6330 directory's group would be checked against the current group, not
6331 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
6332 bugfix on 0.2.2.26-beta.
6333 - Make connection_printf_to_buf()'s behaviour sane. Its callers
6334 expect it to emit a CRLF iff the format string ends with CRLF;
6335 it actually emitted a CRLF iff (a) the format string ended with
6336 CRLF or (b) the resulting string was over 1023 characters long or
6337 (c) the format string did not end with CRLF *and* the resulting
6338 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
6339 fixes part of bug 3407.
6340 - Make send_control_event_impl()'s behaviour sane. Its callers
6341 expect it to always emit a CRLF at the end of the string; it
6342 might have emitted extra control characters as well. Bugfix on
6343 0.1.1.9-alpha; fixes another part of bug 3407.
6344 - Make crypto_rand_int() check the value of its input correctly.
6345 Previously, it accepted values up to UINT_MAX, but could return a
6346 negative number if given a value above INT_MAX+1. Found by George
6347 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
6348 - Avoid a segfault when reading a malformed circuit build state
6349 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
6351 - When asked about a DNS record type we don't support via a
6352 client DNSPort, reply with NOTIMPL rather than an empty
6353 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
6354 - Fix a rare memory leak during stats writing. Found by coverity.
6357 - Update to the June 1 2011 Maxmind GeoLite Country database.
6359 o Code simplifications and refactoring:
6360 - Remove some dead code as indicated by coverity.
6361 - Remove a few dead assignments during router parsing. Found by
6363 - Add some forgotten return value checks during unit tests. Found
6365 - Don't use 1-bit wide signed bit fields. Found by coverity.
6368 Changes in version 0.2.2.28-beta - 2011-06-04
6369 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
6370 fixed a big bug in whether relays stay in the consensus consistently,
6371 we moved closer to handling bridges and hidden services correctly,
6372 and we started the process of better handling the dreaded "my Vidalia
6373 died, and now my Tor demands a password when I try to reconnect to it"
6377 - Don't decide to make a new descriptor when receiving a HUP signal.
6378 This bug has caused a lot of 0.2.2.x relays to disappear from the
6379 consensus periodically. Fixes the most common case of triggering
6380 bug 1810; bugfix on 0.2.2.7-alpha.
6381 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
6382 - Don't try to build descriptors if "ORPort auto" is set and we
6383 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
6385 - Resolve a crash that occurred when setting BridgeRelay to 1 with
6386 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
6387 - Apply circuit timeouts to opened hidden-service-related circuits
6388 based on the correct start time. Previously, we would apply the
6389 circuit build timeout based on time since the circuit's creation;
6390 it was supposed to be applied based on time since the circuit
6391 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
6392 - Use the same circuit timeout for client-side introduction
6393 circuits as for other four-hop circuits, rather than the timeout
6394 for single-hop directory-fetch circuits; the shorter timeout may
6395 have been appropriate with the static circuit build timeout in
6396 0.2.1.x and earlier, but caused many hidden service access attempts
6397 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
6398 on 0.2.2.2-alpha; fixes another part of bug 1297.
6399 - In ticket 2511 we fixed a case where you could use an unconfigured
6400 bridge if you had configured it as a bridge the last time you ran
6401 Tor. Now fix another edge case: if you had configured it as a bridge
6402 but then switched to a different bridge via the controller, you
6403 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
6407 - Add an __OwningControllerProcess configuration option and a
6408 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
6409 that when it exits, Tor will shut down. Implements feature 3049.
6410 - If "UseBridges 1" is set and no bridges are configured, Tor will
6411 now refuse to build any circuits until some bridges are set.
6412 If "UseBridges auto" is set, Tor will use bridges if they are
6413 configured and we are not running as a server, but otherwise will
6414 make circuits as usual. The new default is "auto". Patch by anonym,
6415 so the Tails LiveCD can stop automatically revealing you as a Tor
6419 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6420 - Remove a trailing asterisk from "exit-policy/default" in the
6421 output of the control port command "GETINFO info/names". Bugfix
6423 - Use a wide type to hold sockets when built for 64-bit Windows builds.
6425 - Warn when the user configures two HiddenServiceDir lines that point
6426 to the same directory. Bugfix on 0.0.6 (the version introducing
6427 HiddenServiceDir); fixes bug 3289.
6428 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
6429 part of bug 2748; bugfix on 0.2.0.10-alpha.
6430 - Log malformed requests for rendezvous descriptors as protocol
6431 warnings, not warnings. Also, use a more informative log message
6432 in case someone sees it at log level warning without prior
6433 info-level messages. Fixes the other part of bug 2748; bugfix
6435 - Clear the table recording the time of the last request for each
6436 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
6437 Previously, we would clear our HS descriptor cache on SIGNAL
6438 NEWNYM, but if we had previously retrieved a descriptor (or tried
6439 to) from every directory responsible for it, we would refuse to
6440 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
6442 - Fix a log message that said "bits" while displaying a value in
6443 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
6445 - When checking for 1024-bit keys, check for 1024 bits, not 128
6446 bytes. This allows Tor to correctly discard keys of length 1017
6447 through 1023. Bugfix on 0.0.9pre5.
6450 - Relays now log the reason for publishing a new relay descriptor,
6451 so we have a better chance of hunting down instances of bug 1810.
6452 Resolves ticket 3252.
6453 - Revise most log messages that refer to nodes by nickname to
6454 instead use the "$key=nickname at address" format. This should be
6455 more useful, especially since nicknames are less and less likely
6456 to be unique. Resolves ticket 3045.
6457 - Log (at info level) when purging pieces of hidden-service-client
6458 state because of SIGNAL NEWNYM.
6461 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6462 anything since 0.2.1.16-rc.
6465 Changes in version 0.2.2.27-beta - 2011-05-18
6466 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
6467 release, and also adds a few more general bugfixes.
6470 - Fix a crash bug when changing bridges in a running Tor process.
6471 Fixes bug 3213; bugfix on 0.2.2.26-beta.
6472 - When the controller configures a new bridge, don't wait 10 to 60
6473 seconds before trying to fetch its descriptor. Bugfix on
6474 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
6477 - Require that onion keys have exponent 65537 in microdescriptors too.
6478 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
6479 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
6480 Changed the limit to 512 characters by removing base64 newlines.
6481 Fixes bug 2752. Fix by Michael Yakubovich.
6482 - When a client starts or stops using bridges, never use a circuit
6483 that was built before the configuration change. This behavior could
6484 put at risk a user who uses bridges to ensure that her traffic
6485 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
6489 Changes in version 0.2.2.26-beta - 2011-05-17
6490 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
6491 also introduces a new "socksport auto" approach that should make it
6492 easier to run multiple Tors on the same system, and does a lot of
6493 cleanup to get us closer to a release candidate.
6495 o Security/privacy fixes:
6496 - Replace all potentially sensitive memory comparison operations
6497 with versions whose runtime does not depend on the data being
6498 compared. This will help resist a class of attacks where an
6499 adversary can use variations in timing information to learn
6500 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6501 implementation by Robert Ransom based partially on code by DJB.)
6502 - When receiving a hidden service descriptor, check that it is for
6503 the hidden service we wanted. Previously, Tor would store any
6504 hidden service descriptors that a directory gave it, whether it
6505 wanted them or not. This wouldn't have let an attacker impersonate
6506 a hidden service, but it did let directories pre-seed a client
6507 with descriptors that it didn't want. Bugfix on 0.0.6.
6508 - On SIGHUP, do not clear out all TrackHostExits mappings, client
6509 DNS cache entries, and virtual address mappings: that's what
6510 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
6513 - The options SocksPort, ControlPort, and so on now all accept a
6514 value "auto" that opens a socket on an OS-selected port. A
6515 new ControlPortWriteToFile option tells Tor to write its
6516 actual control port or ports to a chosen file. If the option
6517 ControlPortFileGroupReadable is set, the file is created as
6518 group-readable. Now users can run two Tor clients on the same
6519 system without needing to manually mess with parameters. Resolves
6520 part of ticket 3076.
6521 - Set SO_REUSEADDR on all sockets, not just listeners. This should
6522 help busy exit nodes avoid running out of useable ports just
6523 because all the ports have been used in the near past. Resolves
6527 - New "GETINFO net/listeners/(type)" controller command to return
6528 a list of addresses and ports that are bound for listeners for a
6529 given connection type. This is useful when the user has configured
6530 "SocksPort auto" and the controller needs to know which port got
6531 chosen. Resolves another part of ticket 3076.
6532 - Add a new ControlSocketsGroupWritable configuration option: when
6533 it is turned on, ControlSockets are group-writeable by the default
6534 group of the current user. Patch by Jérémy Bobbio; implements
6536 - Tor now refuses to create a ControlSocket in a directory that is
6537 world-readable (or group-readable if ControlSocketsGroupWritable
6538 is 0). This is necessary because some operating systems do not
6539 enforce permissions on an AF_UNIX sockets. Permissions on the
6540 directory holding the socket, however, seems to work everywhere.
6541 - Rate-limit a warning about failures to download v2 networkstatus
6542 documents. Resolves part of bug 1352.
6543 - Backport code from 0.2.3.x that allows directory authorities to
6544 clean their microdescriptor caches. Needed to resolve bug 2230.
6545 - When an HTTPS proxy reports "403 Forbidden", we now explain
6546 what it means rather than calling it an unexpected status code.
6547 Closes bug 2503. Patch from Michael Yakubovich.
6548 - Update to the May 1 2011 Maxmind GeoLite Country database.
6551 - Authorities now clean their microdesc cache periodically and when
6552 reading from disk initially, not only when adding new descriptors.
6553 This prevents a bug where we could lose microdescriptors. Bugfix
6554 on 0.2.2.6-alpha. Fixes bug 2230.
6555 - Do not crash when our configuration file becomes unreadable, for
6556 example due to a permissions change, between when we start up
6557 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6559 - Avoid a bug that would keep us from replacing a microdescriptor
6560 cache on Windows. (We would try to replace the file while still
6561 holding it open. That's fine on Unix, but Windows doesn't let us
6562 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
6563 - Add missing explanations for the authority-related torrc options
6564 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
6565 man page. Resolves issue 2379.
6566 - As an authority, do not upload our own vote or signature set to
6567 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
6568 it would get flagged as a duplicate. Resolves bug 3026.
6569 - Accept hidden service descriptors if we think we might be a hidden
6570 service directory, regardless of what our consensus says. This
6571 helps robustness, since clients and hidden services can sometimes
6572 have a more up-to-date view of the network consensus than we do,
6573 and if they think that the directory authorities list us a HSDir,
6574 we might actually be one. Related to bug 2732; bugfix on
6576 - When a controller changes TrackHostExits, remove mappings for
6577 hosts that should no longer have their exits tracked. Bugfix on
6579 - When a controller changes VirtualAddrNetwork, remove any mappings
6580 for hosts that were automapped to the old network. Bugfix on
6582 - When a controller changes one of the AutomapHosts* options, remove
6583 any mappings for hosts that should no longer be automapped. Bugfix
6585 - Do not reset the bridge descriptor download status every time we
6586 re-parse our configuration or get a configuration change. Fixes
6587 bug 3019; bugfix on 0.2.0.3-alpha.
6589 o Minor bugfixes (code cleanup):
6590 - When loading the microdesc journal, remember its current size.
6591 In 0.2.2, this helps prevent the microdesc journal from growing
6592 without limit on authorities (who are the only ones to use it in
6593 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6594 Fix posted by "cypherpunks."
6595 - The microdesc journal is supposed to get rebuilt only if it is
6596 at least _half_ the length of the store, not _twice_ the length
6597 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6598 - Fix a potential null-pointer dereference while computing a
6599 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
6601 - Avoid a possible null-pointer dereference when rebuilding the mdesc
6602 cache without actually having any descriptors to cache. Bugfix on
6603 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
6604 - If we fail to compute the identity digest of a v3 legacy keypair,
6605 warn, and don't use a buffer-full of junk instead. Bugfix on
6606 0.2.1.1-alpha; fixes bug 3106.
6607 - Resolve an untriggerable issue in smartlist_string_num_isin(),
6608 where if the function had ever in the future been used to check
6609 for the presence of a too-large number, it would have given an
6610 incorrect result. (Fortunately, we only used it for 16-bit
6611 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
6612 - Require that introduction point keys and onion handshake keys
6613 have a public exponent of 65537. Starts to fix bug 3207; bugfix
6617 - Caches no longer download and serve v2 networkstatus documents
6618 unless FetchV2Networkstatus flag is set: these documents haven't
6619 haven't been used by clients or relays since 0.2.0.x. Resolves
6623 Changes in version 0.2.3.1-alpha - 2011-05-05
6624 Tor 0.2.3.1-alpha adds some new experimental features, including support
6625 for an improved network IO backend, IOCP networking on Windows,
6626 microdescriptor caching, "fast-start" support for streams, and automatic
6627 home router configuration. There are also numerous internal improvements
6628 to try to make the code easier for developers to work with.
6630 This is the first alpha release in a new series, so expect there to be
6631 bugs. Users who would rather test out a more stable branch should
6632 stay with 0.2.2.x for now.
6635 - Tor can now optionally build with the "bufferevents" buffered IO
6636 backend provided by Libevent 2. To use this feature, make sure you
6637 have the latest possible version of Libevent, and pass the
6638 --enable-bufferevents flag to configure when building Tor from
6639 source. This feature will make our networking code more flexible,
6640 let us stack layers on each other, and let us use more efficient
6641 zero-copy transports where available.
6642 - As an experimental feature, Tor can use IOCP for networking on Windows.
6643 Once this code is tuned and optimized, it promises much better
6644 performance than the select-based backend we've used in the past. To
6645 try this feature, you must build Tor with Libevent 2, configure Tor
6646 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
6647 your torrc. There are known bugs here: only try this if you can help
6648 debug it as it breaks.
6649 - The EntryNodes option can now include country codes like {de} or IP
6650 addresses or network masks. Previously we had disallowed these options
6651 because we didn't have an efficient way to keep the list up to
6652 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
6653 - Exit nodes now accept and queue data on not-yet-connected streams.
6654 Previously, the client wasn't allowed to send data until the stream was
6655 connected, which slowed down all connections. This change will enable
6656 clients to perform a "fast-start" on streams and send data without
6657 having to wait for a confirmation that the stream has opened. (Patch
6658 from Ian Goldberg; implements the server side of Proposal 174.)
6659 - Tor now has initial support for automatic port mapping on the many
6660 home routers that support NAT-PMP or UPnP. (Not yet supported on
6661 Windows). To build the support code, you'll need to have libnatpnp
6662 library and/or the libminiupnpc library, and you'll need to enable the
6663 feature specifically by passing "--enable-upnp" and/or
6664 "--enable-natpnp" to configure. To turn it on, use the new
6665 PortForwarding option.
6666 - Caches now download, cache, and serve multiple "flavors" of the
6667 consensus, including a flavor that describes microdescriptors.
6668 - Caches now download, cache, and serve microdescriptors -- small
6669 summaries of router descriptors that are authenticated by all of the
6670 directory authorities. Once enough caches are running this code,
6671 clients will be able to save significant amounts of directory bandwidth
6672 by downloading microdescriptors instead of router descriptors.
6675 - Make logging resolution configurable with a new LogTimeGranularity
6676 option, and change the default from 1 millisecond to 1 second.
6677 Implements enhancement 1668.
6678 - We log which torrc file we're using on startup. Implements ticket
6680 - Ordinarily, Tor does not count traffic from private addresses (like
6681 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
6682 There is now a new option, CountPrivateBandwidth, to disable this
6683 behavior. Patch from Daniel Cagara.
6684 - New --enable-static-tor configure option for building Tor as
6685 statically as possible. Idea, general hackery and thoughts from
6686 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
6688 - If you set the NumCPUs option to 0, Tor will now try to detect how
6689 many CPUs you have. This is the new default behavior.
6690 - Turn on directory request statistics by default and include them in
6691 extra-info descriptors. Don't break if we have no GeoIP database.
6692 - Relays that set "ConnDirectionStatistics 1" write statistics on the
6693 bidirectional use of connections to disk every 24 hours.
6694 - Add a GeoIP file digest to the extra-info descriptor. Implements
6696 - The NodeFamily option -- which let you declare that you want to
6697 consider nodes to be part of a family whether they list themselves
6698 that way or not -- now allows IP address ranges and country codes.
6699 - Add a new 'Heartbeat' log message type to periodically log a message
6700 describing Tor's status at level Notice. This feature is meant for
6701 operators who log at notice, and want to make sure that their Tor
6702 server is still working. Implementation by George Kadianakis.
6704 o Minor bugfixes (on 0.2.2.25-alpha):
6705 - When loading the microdesc journal, remember its current size.
6706 In 0.2.2, this helps prevent the microdesc journal from growing
6707 without limit on authorities (who are the only ones to use it in
6708 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6709 Fix posted by "cypherpunks."
6710 - The microdesc journal is supposed to get rebuilt only if it is
6711 at least _half_ the length of the store, not _twice_ the length
6712 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6713 - If as an authority we fail to compute the identity digest of a v3
6714 legacy keypair, warn, and don't use a buffer-full of junk instead.
6715 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
6716 - Authorities now clean their microdesc cache periodically and when
6717 reading from disk initially, not only when adding new descriptors.
6718 This prevents a bug where we could lose microdescriptors. Bugfix
6721 o Minor features (controller):
6722 - Add a new SIGNAL event to the controller interface so that
6723 controllers can be notified when Tor handles a signal. Resolves
6724 issue 1955. Patch by John Brooks.
6725 - Add a new GETINFO option to get total bytes read and written. Patch
6726 from pipe, revised by atagar. Resolves ticket 2345.
6727 - Implement some GETINFO controller fields to provide information about
6728 the Tor process's pid, euid, username, and resource limits.
6731 - Our build system requires automake 1.6 or later to create the
6732 Makefile.in files. Previously, you could have used 1.4.
6733 This only affects developers and people building Tor from git;
6734 people who build Tor from the source distribution without changing
6735 the Makefile.am files should be fine.
6736 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
6737 so on. This is more robust against some of the failure modes
6738 associated with running the autotools pieces on their own.
6740 o Minor packaging issues:
6741 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
6742 already created. Patch from Andreas Stieger. Fixes bug 2573.
6744 o Code simplifications and refactoring:
6745 - A major revision to our internal node-selecting and listing logic.
6746 Tor already had at least two major ways to look at the question of
6747 "which Tor servers do we know about": a list of router descriptors,
6748 and a list of entries in the current consensus. With
6749 microdescriptors, we're adding a third. Having so many systems
6750 without an abstraction layer over them was hurting the codebase.
6751 Now, we have a new "node_t" abstraction that presents a consistent
6752 interface to a client's view of a Tor node, and holds (nearly) all
6753 of the mutable state formerly in routerinfo_t and routerstatus_t.
6754 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
6755 no longer link against Libevent: they never used it, but
6756 our library structure used to force them to link it.
6759 - Remove some old code to work around even older versions of Tor that
6760 used forked processes to handle DNS requests. Such versions of Tor
6761 are no longer in use as servers.
6763 o Documentation fixes:
6764 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
6765 - Add missing documentation for the authority-related torrc options
6766 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
6770 Changes in version 0.2.2.25-alpha - 2011-04-29
6771 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
6772 robust, routers no longer overreport their bandwidth, Win7 should crash
6773 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
6774 now prevents hidden service-related activity from being linkable. It
6775 provides more information to Vidalia so you can see if your bridge is
6776 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
6777 StrictNodes configuration options to make them more reliable, more
6778 understandable, and more regularly applied. If you use those options,
6779 please see the revised documentation for them in the manual page.
6782 - Relays were publishing grossly inflated bandwidth values because
6783 they were writing their state files wrong--now they write the
6784 correct value. Also, resume reading bandwidth history from the
6785 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
6786 - Improve hidden service robustness: When we find that we have
6787 extended a hidden service's introduction circuit to a relay not
6788 listed as an introduction point in the HS descriptor we currently
6789 have, retry with an introduction point from the current
6790 descriptor. Previously we would just give up. Fixes bugs 1024 and
6791 1930; bugfix on 0.2.0.10-alpha.
6792 - Clients now stop trying to use an exit node associated with a given
6793 destination by TrackHostExits if they fail to reach that exit node.
6794 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
6795 - Fix crash bug on platforms where gmtime and localtime can return
6796 NULL. Windows 7 users were running into this one. Fixes part of bug
6797 2077. Bugfix on all versions of Tor. Found by boboper.
6799 o Security and stability fixes:
6800 - Don't double-free a parsable, but invalid, microdescriptor, even if
6801 it is followed in the blob we're parsing by an unparsable
6802 microdescriptor. Fixes an issue reported in a comment on bug 2954.
6803 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
6804 - If the Nickname configuration option isn't given, Tor would pick a
6805 nickname based on the local hostname as the nickname for a relay.
6806 Because nicknames are not very important in today's Tor and the
6807 "Unnamed" nickname has been implemented, this is now problematic
6808 behavior: It leaks information about the hostname without being
6809 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
6810 introduced the Unnamed nickname. Reported by tagnaq.
6811 - Fix an uncommon assertion failure when running with DNSPort under
6812 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6813 - Avoid linkability based on cached hidden service descriptors: forget
6814 all hidden service descriptors cached as a client when processing a
6815 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6818 - Export GeoIP information on bridge usage to controllers even if we
6819 have not yet been running for 24 hours. Now Vidalia bridge operators
6820 can get more accurate and immediate feedback about their
6821 contributions to the network.
6823 o Major features and bugfixes (node selection):
6824 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
6825 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
6826 options. Previously, we had been ambiguous in describing what
6827 counted as an "exit" node, and what operations exactly "StrictNodes
6828 0" would permit. This created confusion when people saw nodes built
6829 through unexpected circuits, and made it hard to tell real bugs from
6830 surprises. Now the intended behavior is:
6831 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
6832 a node that delivers user traffic outside the Tor network.
6833 . "Entry", in the context of EntryNodes, means a node used as the
6834 first hop of a multihop circuit. It doesn't include direct
6835 connections to directory servers.
6836 . "ExcludeNodes" applies to all nodes.
6837 . "StrictNodes" changes the behavior of ExcludeNodes only. When
6838 StrictNodes is set, Tor should avoid all nodes listed in
6839 ExcludeNodes, even when it will make user requests fail. When
6840 StrictNodes is *not* set, then Tor should follow ExcludeNodes
6841 whenever it can, except when it must use an excluded node to
6842 perform self-tests, connect to a hidden service, provide a
6843 hidden service, fulfill a .exit request, upload directory
6844 information, or fetch directory information.
6845 Collectively, the changes to implement the behavior fix bug 1090.
6846 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
6847 a node is listed in both, it's treated as excluded.
6848 - ExcludeNodes now applies to directory nodes -- as a preference if
6849 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
6850 Don't exclude all the directory authorities and set StrictNodes to 1
6851 unless you really want your Tor to break.
6852 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
6853 - ExcludeExitNodes now overrides .exit requests.
6854 - We don't use bridges listed in ExcludeNodes.
6855 - When StrictNodes is 1:
6856 . We now apply ExcludeNodes to hidden service introduction points
6857 and to rendezvous points selected by hidden service users. This
6858 can make your hidden service less reliable: use it with caution!
6859 . If we have used ExcludeNodes on ourself, do not try relay
6860 reachability self-tests.
6861 . If we have excluded all the directory authorities, we will not
6862 even try to upload our descriptor if we're a relay.
6863 . Do not honor .exit requests to an excluded node.
6864 - Remove a misfeature that caused us to ignore the Fast/Stable flags
6865 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
6866 - When the set of permitted nodes changes, we now remove any mappings
6867 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
6869 - We never cannibalize a circuit that had excluded nodes on it, even
6870 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
6871 - Revert a change where we would be laxer about attaching streams to
6872 circuits than when building the circuits. This was meant to prevent
6873 a set of bugs where streams were never attachable, but our improved
6874 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
6875 - Keep track of how many times we launch a new circuit to handle a
6876 given stream. Too many launches could indicate an inconsistency
6877 between our "launch a circuit to handle this stream" logic and our
6878 "attach this stream to one of the available circuits" logic.
6879 - Improve log messages related to excluded nodes.
6882 - Fix a spurious warning when moving from a short month to a long
6883 month on relays with month-based BandwidthAccounting. Bugfix on
6884 0.2.2.17-alpha; fixes bug 3020.
6885 - When a client finds that an origin circuit has run out of 16-bit
6886 stream IDs, we now mark it as unusable for new streams. Previously,
6887 we would try to close the entire circuit. Bugfix on 0.0.6.
6888 - Add a forgotten cast that caused a compile warning on OS X 10.6.
6889 Bugfix on 0.2.2.24-alpha.
6890 - Be more careful about reporting the correct error from a failed
6891 connect() system call. Under some circumstances, it was possible to
6892 look at an incorrect value for errno when sending the end reason.
6893 Bugfix on 0.1.0.1-rc.
6894 - Correctly handle an "impossible" overflow cases in connection byte
6895 counting, where we write or read more than 4GB on an edge connection
6896 in a single second. Bugfix on 0.1.2.8-beta.
6897 - Correct the warning displayed when a rendezvous descriptor exceeds
6898 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6900 - Clients and hidden services now use HSDir-flagged relays for hidden
6901 service descriptor downloads and uploads even if the relays have no
6902 DirPort set and the client has disabled TunnelDirConns. This will
6903 eventually allow us to give the HSDir flag to relays with no
6904 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
6905 - Downgrade "no current certificates known for authority" message from
6906 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
6907 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
6908 2917. Bugfix on 0.1.1.1-alpha.
6909 - Only limit the lengths of single HS descriptors, even when multiple
6910 HS descriptors are published to an HSDir relay in a single POST
6911 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
6912 - Write the current time into the LastWritten line in our state file,
6913 rather than the time from the previous write attempt. Also, stop
6914 trying to use a time of -1 in our log statements. Fixes bug 3039;
6915 bugfix on 0.2.2.14-alpha.
6916 - Be more consistent in our treatment of file system paths. "~" should
6917 get expanded to the user's home directory in the Log config option.
6918 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
6919 feature for the -f and --DataDirectory options.
6922 - Make sure every relay writes a state file at least every 12 hours.
6923 Previously, a relay could go for weeks without writing its state
6924 file, and on a crash could lose its bandwidth history, capacity
6925 estimates, client country statistics, and so on. Addresses bug 3012.
6926 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
6927 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
6928 clients are already deprecated because of security bugs.
6929 - Don't allow v0 hidden service authorities to act as clients.
6930 Required by fix for bug 3000.
6931 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
6932 by fix for bug 3000.
6933 - Ensure that no empty [dirreq-](read|write)-history lines are added
6934 to an extrainfo document. Implements ticket 2497.
6936 o Code simplification and refactoring:
6937 - Remove workaround code to handle directory responses from servers
6938 that had bug 539 (they would send HTTP status 503 responses _and_
6939 send a body too). Since only server versions before
6940 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
6941 keep the workaround in place.
6942 - Remove the old 'fuzzy time' logic. It was supposed to be used for
6943 handling calculations where we have a known amount of clock skew and
6944 an allowed amount of unknown skew. But we only used it in three
6945 places, and we never adjusted the known/unknown skew values. This is
6946 still something we might want to do someday, but if we do, we'll
6947 want to do it differently.
6948 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6949 None of the cases where we did this before were wrong, but by making
6950 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6951 - Use GetTempDir to find the proper temporary directory location on
6952 Windows when generating temporary files for the unit tests. Patch by
6956 Changes in version 0.2.2.24-alpha - 2011-04-08
6957 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
6958 prevented Tor clients from effectively using "multihomed" bridges,
6959 that is, bridges that listen on multiple ports or IP addresses so users
6960 can continue to use some of their addresses even if others get blocked.
6963 - Fix a bug where bridge users who configure the non-canonical
6964 address of a bridge automatically switch to its canonical
6965 address. If a bridge listens at more than one address, it should be
6966 able to advertise those addresses independently and any non-blocked
6967 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
6969 - If you configured Tor to use bridge A, and then quit and
6970 configured Tor to use bridge B instead, it would happily continue
6971 to use bridge A if it's still reachable. While this behavior is
6972 a feature if your goal is connectivity, in some scenarios it's a
6973 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
6974 - Directory authorities now use data collected from their own
6975 uptime observations when choosing whether to assign the HSDir flag
6976 to relays, instead of trusting the uptime value the relay reports in
6977 its descriptor. This change helps prevent an attack where a small
6978 set of nodes with frequently-changing identity keys can blackhole
6979 a hidden service. (Only authorities need upgrade; others will be
6980 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
6983 - When we restart our relay, we might get a successful connection
6984 from the outside before we've started our reachability tests,
6985 triggering a warning: "ORPort found reachable, but I have no
6986 routerinfo yet. Failing to inform controller of success." This
6987 bug was harmless unless Tor is running under a controller
6988 like Vidalia, in which case the controller would never get a
6989 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6991 - Make directory authorities more accurate at recording when
6992 relays that have failed several reachability tests became
6993 unreachable, so we can provide more accuracy at assigning Stable,
6994 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
6995 - Fix an issue that prevented static linking of libevent on
6996 some platforms (notably Linux). Fixes bug 2698; bugfix on
6997 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
6998 the --with-static-libevent configure option).
6999 - We now ask the other side of a stream (the client or the exit)
7000 for more data on that stream when the amount of queued data on
7001 that stream dips low enough. Previously, we wouldn't ask the
7002 other side for more data until either it sent us more data (which
7003 it wasn't supposed to do if it had exhausted its window!) or we
7004 had completely flushed all our queued data. This flow control fix
7005 should improve throughput. Fixes bug 2756; bugfix on the earliest
7006 released versions of Tor (svn commit r152).
7007 - Avoid a double-mark-for-free warning when failing to attach a
7008 transparent proxy connection. (We thought we had fixed this in
7009 0.2.2.23-alpha, but it turns out our fix was checking the wrong
7010 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
7011 bug) and 0.2.2.23-alpha (the incorrect fix).
7012 - When warning about missing zlib development packages during compile,
7013 give the correct package names. Bugfix on 0.2.0.1-alpha.
7016 - Directory authorities now log the source of a rejected POSTed v3
7018 - Make compilation with clang possible when using
7019 --enable-gcc-warnings by removing two warning options that clang
7020 hasn't implemented yet and by fixing a few warnings. Implements
7022 - When expiring circuits, use microsecond timers rather than
7023 one-second timers. This can avoid an unpleasant situation where a
7024 circuit is launched near the end of one second and expired right
7025 near the beginning of the next, and prevent fluctuations in circuit
7027 - Use computed circuit-build timeouts to decide when to launch
7028 parallel introduction circuits for hidden services. (Previously,
7029 we would retry after 15 seconds.)
7030 - Update to the April 1 2011 Maxmind GeoLite Country database.
7033 - Create the /var/run/tor directory on startup on OpenSUSE if it is
7034 not already created. Patch from Andreas Stieger. Fixes bug 2573.
7036 o Documentation changes:
7037 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
7038 - Resolve all doxygen warnings except those for missing documentation.
7040 - Add doxygen documentation for more functions, fields, and types.
7043 Changes in version 0.2.2.23-alpha - 2011-03-08
7044 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
7045 they restart they don't lose their bandwidth capacity estimate. This
7046 release also fixes a diverse set of user-facing bugs, ranging from
7047 relays overrunning their rate limiting to clients falsely warning about
7048 clock skew to bridge descriptor leaks by our bridge directory authority.
7051 - Stop sending a CLOCK_SKEW controller status event whenever
7052 we fetch directory information from a relay that has a wrong clock.
7053 Instead, only inform the controller when it's a trusted authority
7054 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7055 the rest of bug 1074.
7056 - Fix an assert in parsing router descriptors containing IPv6
7057 addresses. This one took down the directory authorities when
7058 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7059 - Make the bridge directory authority refuse to answer directory
7060 requests for "all" descriptors. It used to include bridge
7061 descriptors in its answer, which was a major information leak.
7062 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7063 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7064 Tor would ignore their RelayBandwidthBurst setting,
7065 potentially using more bandwidth than expected. Bugfix on
7066 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7067 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7068 hidserv" in her torrc. The 'hidserv' argument never controlled
7069 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7072 - Relays now save observed peak bandwidth throughput rates to their
7073 state file (along with total usage, which was already saved)
7074 so that they can determine their correct estimated bandwidth on
7075 restart. Resolves bug 1863, where Tor relays would reset their
7076 estimated bandwidth to 0 after restarting.
7077 - Directory authorities now take changes in router IP address and
7078 ORPort into account when determining router stability. Previously,
7079 if a router changed its IP or ORPort, the authorities would not
7080 treat it as having any downtime for the purposes of stability
7081 calculation, whereas clients would experience downtime since the
7082 change could take a while to propagate to them. Resolves issue 1035.
7083 - Enable Address Space Layout Randomization (ASLR) and Data Execution
7084 Prevention (DEP) by default on Windows to make it harder for
7085 attackers to exploit vulnerabilities. Patch from John Brooks.
7087 o Minor bugfixes (on 0.2.1.x and earlier):
7088 - Fix a rare crash bug that could occur when a client was configured
7089 with a large number of bridges. Fixes bug 2629; bugfix on
7090 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7091 - Avoid a double mark-for-free warning when failing to attach a
7092 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
7094 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
7095 found by "cypherpunks". This bug was introduced before the first
7096 Tor release, in svn commit r110.
7097 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
7098 don't mention them in the manpage. Fixes bug 2450; issue
7099 spotted by keb and G-Lo.
7100 - Fix a bug in bandwidth history state parsing that could have been
7101 triggered if a future version of Tor ever changed the timing
7102 granularity at which bandwidth history is measured. Bugfix on
7104 - When a relay decides that its DNS is too broken for it to serve
7105 as an exit server, it advertised itself as a non-exit, but
7106 continued to act as an exit. This could create accidental
7107 partitioning opportunities for users. Instead, if a relay is
7108 going to advertise reject *:* as its exit policy, it should
7109 really act with exit policy "reject *:*". Fixes bug 2366.
7110 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
7111 - In the special case where you configure a public exit relay as your
7112 bridge, Tor would be willing to use that exit relay as the last
7113 hop in your circuit as well. Now we fail that circuit instead.
7114 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
7115 - Fix a bug with our locking implementation on Windows that couldn't
7116 correctly detect when a file was already locked. Fixes bug 2504,
7117 bugfix on 0.2.1.6-alpha.
7118 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
7119 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
7121 - Set target port in get_interface_address6() correctly. Bugfix
7122 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
7123 - Directory authorities are now more robust to hops back in time
7124 when calculating router stability. Previously, if a run of uptime
7125 or downtime appeared to be negative, the calculation could give
7126 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
7128 - Fix an assert that got triggered when using the TestingTorNetwork
7129 configuration option and then issuing a GETINFO config-text control
7130 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
7132 o Minor bugfixes (on 0.2.2.x):
7133 - Clients should not weight BadExit nodes as Exits in their node
7134 selection. Similarly, directory authorities should not count BadExit
7135 bandwidth as Exit bandwidth when computing bandwidth-weights.
7136 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
7137 - Correctly clear our dir_read/dir_write history when there is an
7138 error parsing any bw history value from the state file. Bugfix on
7140 - Resolve a bug in verifying signatures of directory objects
7141 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
7142 Fixes bug 2409. Found by "piebeer".
7143 - Bridge authorities no longer crash on SIGHUP when they try to
7144 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
7148 - Log less aggressively about circuit timeout changes, and improve
7149 some other circuit timeout messages. Resolves bug 2004.
7150 - Log a little more clearly about the times at which we're no longer
7151 accepting new connections. Resolves bug 2181.
7152 - Reject attempts at the client side to open connections to private
7153 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
7154 a randomly chosen exit node. Attempts to do so are always
7155 ill-defined, generally prevented by exit policies, and usually
7156 in error. This will also help to detect loops in transparent
7157 proxy configurations. You can disable this feature by setting
7158 "ClientRejectInternalAddresses 0" in your torrc.
7159 - Always treat failure to allocate an RSA key as an unrecoverable
7161 - Update to the March 1 2011 Maxmind GeoLite Country database.
7163 o Minor features (log subsystem):
7164 - Add documentation for configuring logging at different severities in
7165 different log domains. We've had this feature since 0.2.1.1-alpha,
7166 but for some reason it never made it into the manpage. Fixes
7168 - Make it simpler to specify "All log domains except for A and B".
7169 Previously you needed to say "[*,~A,~B]". Now you can just say
7171 - Add a "LogMessageDomains 1" option to include the domains of log
7172 messages along with the messages. Without this, there's no way
7173 to use log domains without reading the source or doing a lot
7176 o Packaging changes:
7177 - Stop shipping the Tor specs files and development proposal documents
7178 in the tarball. They are now in a separate git repository at
7179 git://git.torproject.org/torspec.git
7182 Changes in version 0.2.1.30 - 2011-02-23
7183 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
7184 change is a slight tweak to Tor's TLS handshake that makes relays
7185 and bridges that run this new version reachable from Iran again.
7186 We don't expect this tweak will win the arms race long-term, but it
7187 buys us time until we roll out a better solution.
7190 - Stop sending a CLOCK_SKEW controller status event whenever
7191 we fetch directory information from a relay that has a wrong clock.
7192 Instead, only inform the controller when it's a trusted authority
7193 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7194 the rest of bug 1074.
7195 - Fix a bounds-checking error that could allow an attacker to
7196 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7198 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7199 Tor would ignore their RelayBandwidthBurst setting,
7200 potentially using more bandwidth than expected. Bugfix on
7201 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7202 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7203 hidserv" in her torrc. The 'hidserv' argument never controlled
7204 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7207 - Adjust our TLS Diffie-Hellman parameters to match those used by
7209 - Update to the February 1 2011 Maxmind GeoLite Country database.
7212 - Check for and reject overly long directory certificates and
7213 directory tokens before they have a chance to hit any assertions.
7214 Bugfix on 0.2.1.28. Found by "doorss".
7215 - Bring the logic that gathers routerinfos and assesses the
7216 acceptability of circuits into line. This prevents a Tor OP from
7217 getting locked in a cycle of choosing its local OR as an exit for a
7218 path (due to a .exit request) and then rejecting the circuit because
7219 its OR is not listed yet. It also prevents Tor clients from using an
7220 OR running in the same instance as an exit (due to a .exit request)
7221 if the OR does not meet the same requirements expected of an OR
7222 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7224 o Packaging changes:
7225 - Stop shipping the Tor specs files and development proposal documents
7226 in the tarball. They are now in a separate git repository at
7227 git://git.torproject.org/torspec.git
7228 - Do not include Git version tags as though they are SVN tags when
7229 generating a tarball from inside a repository that has switched
7230 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7233 Changes in version 0.2.2.22-alpha - 2011-01-25
7234 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
7235 main other change is a slight tweak to Tor's TLS handshake that makes
7236 relays and bridges that run this new version reachable from Iran again.
7237 We don't expect this tweak will win the arms race long-term, but it
7238 will buy us a bit more time until we roll out a better solution.
7241 - Fix a bounds-checking error that could allow an attacker to
7242 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7244 - Don't assert when changing from bridge to relay or vice versa
7245 via the controller. The assert happened because we didn't properly
7246 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
7247 bug 2433. Reported by bastik.
7250 - Adjust our TLS Diffie-Hellman parameters to match those used by
7252 - Provide a log message stating which geoip file we're parsing
7253 instead of just stating that we're parsing the geoip file.
7254 Implements ticket 2432.
7257 - Check for and reject overly long directory certificates and
7258 directory tokens before they have a chance to hit any assertions.
7259 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
7262 Changes in version 0.2.2.21-alpha - 2011-01-15
7263 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
7264 continues our recent code security audit work. The main fix resolves
7265 a remote heap overflow vulnerability that can allow remote code
7266 execution (CVE-2011-0427). Other fixes address a variety of assert
7267 and crash bugs, most of which we think are hard to exploit remotely.
7269 o Major bugfixes (security), also included in 0.2.1.29:
7270 - Fix a heap overflow bug where an adversary could cause heap
7271 corruption. This bug probably allows remote code execution
7272 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7274 - Prevent a denial-of-service attack by disallowing any
7275 zlib-compressed data whose compression factor is implausibly
7276 high. Fixes part of bug 2324; reported by "doorss".
7277 - Zero out a few more keys in memory before freeing them. Fixes
7278 bug 2384 and part of bug 2385. These key instances found by
7279 "cypherpunks", based on Andrew Case's report about being able
7280 to find sensitive data in Tor's memory space if you have enough
7281 permissions. Bugfix on 0.0.2pre9.
7283 o Major bugfixes (crashes), also included in 0.2.1.29:
7284 - Prevent calls to Libevent from inside Libevent log handlers.
7285 This had potential to cause a nasty set of crashes, especially
7286 if running Libevent with debug logging enabled, and running
7287 Tor with a controller watching for low-severity log messages.
7288 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7289 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7290 underflow errors there too. Fixes the other part of bug 2324.
7291 - Fix a bug where we would assert if we ever had a
7292 cached-descriptors.new file (or another file read directly into
7293 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7294 on 0.2.1.25. Found by doorss.
7295 - Fix some potential asserts and parsing issues with grossly
7296 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7299 o Minor bugfixes (other), also included in 0.2.1.29:
7300 - Fix a bug with handling misformed replies to reverse DNS lookup
7301 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7302 bug reported by doorss.
7303 - Fix compilation on mingw when a pthreads compatibility library
7304 has been installed. (We don't want to use it, so we shouldn't
7305 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7306 - Fix a bug where we would declare that we had run out of virtual
7307 addresses when the address space was only half-exhausted. Bugfix
7309 - Correctly handle the case where AutomapHostsOnResolve is set but
7310 no virtual addresses are available. Fixes bug 2328; bugfix on
7311 0.1.2.1-alpha. Bug found by doorss.
7312 - Correctly handle wrapping around when we run out of virtual
7313 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
7315 o Minor features, also included in 0.2.1.29:
7316 - Update to the January 1 2011 Maxmind GeoLite Country database.
7317 - Introduce output size checks on all of our decryption functions.
7319 o Build changes, also included in 0.2.1.29:
7320 - Tor does not build packages correctly with Automake 1.6 and earlier;
7321 added a check to Makefile.am to make sure that we're building with
7322 Automake 1.7 or later.
7323 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7324 because we built it with a too-old version of automake. Thus that
7325 release broke ./configure --enable-openbsd-malloc, which is popular
7326 among really fast exit relays on Linux.
7328 o Major bugfixes, new in 0.2.2.21-alpha:
7329 - Prevent crash/heap corruption when the cbtnummodes consensus
7330 parameter is set to 0 or large values. Fixes bug 2317; bugfix
7333 o Major features, new in 0.2.2.21-alpha:
7334 - Introduce minimum/maximum values that clients will believe
7335 from the consensus. Now we'll have a better chance to avoid crashes
7336 or worse when a consensus param has a weird value.
7338 o Minor features, new in 0.2.2.21-alpha:
7339 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
7340 used on bridges, and it makes bridge scanning somewhat easier.
7341 - If writing the state file to disk fails, wait up to an hour before
7342 retrying again, rather than trying again each second. Fixes bug
7343 2346; bugfix on Tor 0.1.1.3-alpha.
7344 - Make Libevent log messages get delivered to controllers later,
7345 and not from inside the Libevent log handler. This prevents unsafe
7346 reentrant Libevent calls while still letting the log messages
7348 - Detect platforms that brokenly use a signed size_t, and refuse to
7349 build there. Found and analyzed by doorss and rransom.
7350 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
7353 o Minor bugfixes, new in 0.2.2.21-alpha:
7354 - Handle SOCKS messages longer than 128 bytes long correctly, rather
7355 than waiting forever for them to finish. Fixes bug 2330; bugfix
7356 on 0.2.0.16-alpha. Found by doorss.
7357 - Add assertions to check for overflow in arguments to
7358 base32_encode() and base32_decode(); fix a signed-unsigned
7359 comparison there too. These bugs are not actually reachable in Tor,
7360 but it's good to prevent future errors too. Found by doorss.
7361 - Correctly detect failures to create DNS requests when using Libevent
7362 versions before v2. (Before Libevent 2, we used our own evdns
7363 implementation. Its return values for Libevent's evdns_resolve_*()
7364 functions are not consistent with those from Libevent.) Fixes bug
7365 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
7367 o Documentation, new in 0.2.2.21-alpha:
7368 - Document the default socks host and port (127.0.0.1:9050) for
7372 Changes in version 0.2.1.29 - 2011-01-15
7373 Tor 0.2.1.29 continues our recent code security audit work. The main
7374 fix resolves a remote heap overflow vulnerability that can allow remote
7375 code execution. Other fixes address a variety of assert and crash bugs,
7376 most of which we think are hard to exploit remotely.
7378 o Major bugfixes (security):
7379 - Fix a heap overflow bug where an adversary could cause heap
7380 corruption. This bug probably allows remote code execution
7381 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7383 - Prevent a denial-of-service attack by disallowing any
7384 zlib-compressed data whose compression factor is implausibly
7385 high. Fixes part of bug 2324; reported by "doorss".
7386 - Zero out a few more keys in memory before freeing them. Fixes
7387 bug 2384 and part of bug 2385. These key instances found by
7388 "cypherpunks", based on Andrew Case's report about being able
7389 to find sensitive data in Tor's memory space if you have enough
7390 permissions. Bugfix on 0.0.2pre9.
7392 o Major bugfixes (crashes):
7393 - Prevent calls to Libevent from inside Libevent log handlers.
7394 This had potential to cause a nasty set of crashes, especially
7395 if running Libevent with debug logging enabled, and running
7396 Tor with a controller watching for low-severity log messages.
7397 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7398 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7399 underflow errors there too. Fixes the other part of bug 2324.
7400 - Fix a bug where we would assert if we ever had a
7401 cached-descriptors.new file (or another file read directly into
7402 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7403 on 0.2.1.25. Found by doorss.
7404 - Fix some potential asserts and parsing issues with grossly
7405 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7408 o Minor bugfixes (other):
7409 - Fix a bug with handling misformed replies to reverse DNS lookup
7410 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7411 bug reported by doorss.
7412 - Fix compilation on mingw when a pthreads compatibility library
7413 has been installed. (We don't want to use it, so we shouldn't
7414 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7415 - Fix a bug where we would declare that we had run out of virtual
7416 addresses when the address space was only half-exhausted. Bugfix
7418 - Correctly handle the case where AutomapHostsOnResolve is set but
7419 no virtual addresses are available. Fixes bug 2328; bugfix on
7420 0.1.2.1-alpha. Bug found by doorss.
7421 - Correctly handle wrapping around to when we run out of virtual
7422 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
7423 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7424 because we built it with a too-old version of automake. Thus that
7425 release broke ./configure --enable-openbsd-malloc, which is popular
7426 among really fast exit relays on Linux.
7429 - Update to the January 1 2011 Maxmind GeoLite Country database.
7430 - Introduce output size checks on all of our decryption functions.
7433 - Tor does not build packages correctly with Automake 1.6 and earlier;
7434 added a check to Makefile.am to make sure that we're building with
7435 Automake 1.7 or later.
7438 Changes in version 0.2.2.20-alpha - 2010-12-17
7439 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
7440 exploitable bugs. We also fix a variety of other significant bugs,
7441 change the IP address for one of our directory authorities, and update
7442 the minimum version that Tor relays must run to join the network.
7445 - Fix a remotely exploitable bug that could be used to crash instances
7446 of Tor remotely by overflowing on the heap. Remote-code execution
7447 hasn't been confirmed, but can't be ruled out. Everyone should
7448 upgrade. Bugfix on the 0.1.1 series and later.
7449 - Fix a bug that could break accounting on 64-bit systems with large
7450 time_t values, making them hibernate for impossibly long intervals.
7451 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
7452 - Fix a logic error in directory_fetches_from_authorities() that
7453 would cause all _non_-exits refusing single-hop-like circuits
7454 to fetch from authorities, when we wanted to have _exits_ fetch
7455 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
7457 - Fix a stream fairness bug that would cause newer streams on a given
7458 circuit to get preference when reading bytes from the origin or
7459 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
7460 introduced before the first Tor release, in svn revision r152.
7462 o Directory authority changes:
7463 - Change IP address and ports for gabelmoo (v3 directory authority).
7466 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
7467 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
7468 - Fix an off-by-one error in calculating some controller command
7469 argument lengths. Fortunately, this mistake is harmless since
7470 the controller code does redundant NUL termination too. Found by
7471 boboper. Bugfix on 0.1.1.1-alpha.
7472 - Do not dereference NULL if a bridge fails to build its
7473 extra-info descriptor. Found by an anonymous commenter on
7474 Trac. Bugfix on 0.2.2.19-alpha.
7477 - Update to the December 1 2010 Maxmind GeoLite Country database.
7478 - Directory authorities now reject relays running any versions of
7479 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
7480 known bugs that keep RELAY_EARLY cells from working on rendezvous
7481 circuits. Followup to fix for bug 2081.
7482 - Directory authorities now reject relays running any version of Tor
7483 older than 0.2.0.26-rc. That version is the earliest that fetches
7484 current directory information correctly. Fixes bug 2156.
7485 - Report only the top 10 ports in exit-port stats in order not to
7486 exceed the maximum extra-info descriptor length of 50 KB. Implements
7490 Changes in version 0.2.1.28 - 2010-12-17
7491 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
7492 exploitable bugs. We also took this opportunity to change the IP address
7493 for one of our directory authorities, and to update the geoip database
7497 - Fix a remotely exploitable bug that could be used to crash instances
7498 of Tor remotely by overflowing on the heap. Remote-code execution
7499 hasn't been confirmed, but can't be ruled out. Everyone should
7500 upgrade. Bugfix on the 0.1.1 series and later.
7502 o Directory authority changes:
7503 - Change IP address and ports for gabelmoo (v3 directory authority).
7506 - Update to the December 1 2010 Maxmind GeoLite Country database.
7509 Changes in version 0.2.1.27 - 2010-11-23
7510 Yet another OpenSSL security patch broke its compatibility with Tor:
7511 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
7512 also took this opportunity to fix several crash bugs, integrate a new
7513 directory authority, and update the bundled GeoIP database.
7516 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7517 No longer set the tlsext_host_name extension on server SSL objects;
7518 but continue to set it on client SSL objects. Our goal in setting
7519 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7520 bugfix on 0.2.1.1-alpha.
7521 - Do not log messages to the controller while shrinking buffer
7522 freelists. Doing so would sometimes make the controller connection
7523 try to allocate a buffer chunk, which would mess up the internals
7524 of the freelist and cause an assertion failure. Fixes bug 1125;
7525 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7526 - Learn our external IP address when we're a relay or bridge, even if
7527 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7528 where we introduced bridge relays that don't need to publish to
7529 be useful. Fixes bug 2050.
7530 - Do even more to reject (and not just ignore) annotations on
7531 router descriptors received anywhere but from the cache. Previously
7532 we would ignore such annotations at first, but cache them to disk
7533 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7534 - When you're using bridges and your network goes away and your
7535 bridges get marked as down, recover when you attempt a new socks
7536 connection (if the network is back), rather than waiting up to an
7537 hour to try fetching new descriptors for your bridges. Bugfix on
7538 0.2.0.3-alpha; fixes bug 1981.
7541 - Move to the November 2010 Maxmind GeoLite country db (rather
7542 than the June 2009 ip-to-country GeoIP db) for our statistics that
7543 count how many users relays are seeing from each country. Now we'll
7544 have more accurate data, especially for many African countries.
7546 o New directory authorities:
7547 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7551 - Fix an assertion failure that could occur in directory caches or
7552 bridge users when using a very short voting interval on a testing
7553 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
7555 - Enforce multiplicity rules when parsing annotations. Bugfix on
7556 0.2.0.8-alpha. Found by piebeer.
7557 - Allow handshaking OR connections to take a full KeepalivePeriod
7558 seconds to handshake. Previously, we would close them after
7559 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7560 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7562 - When building with --enable-gcc-warnings on OpenBSD, disable
7563 warnings in system headers. This makes --enable-gcc-warnings
7564 pass on OpenBSD 4.8.
7567 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7568 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7569 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7570 Servers can start sending this code when enough clients recognize
7571 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
7572 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7573 Patch from mingw-san.
7576 - Remove the old debian/ directory from the main Tor distribution.
7577 The official Tor-for-debian git repository lives at the URL
7578 https://git.torproject.org/debian/tor.git
7579 - Stop shipping the old doc/website/ directory in the tarball. We
7580 changed the website format in late 2010, and what we shipped in
7581 0.2.1.26 really wasn't that useful anyway.
7584 Changes in version 0.2.2.19-alpha - 2010-11-22
7585 Yet another OpenSSL security patch broke its compatibility with Tor:
7586 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
7589 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7590 No longer set the tlsext_host_name extension on server SSL objects;
7591 but continue to set it on client SSL objects. Our goal in setting
7592 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7593 bugfix on 0.2.1.1-alpha.
7596 - Try harder not to exceed the maximum length of 50 KB when writing
7597 statistics to extra-info descriptors. This bug was triggered by very
7598 fast relays reporting exit-port, entry, and dirreq statistics.
7599 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
7600 - Publish a router descriptor even if generating an extra-info
7601 descriptor fails. Previously we would not publish a router
7602 descriptor without an extra-info descriptor; this can cause fast
7603 exit relays collecting exit-port statistics to drop from the
7604 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
7607 Changes in version 0.2.2.18-alpha - 2010-11-16
7608 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
7609 us lately, makes unpublished bridge relays able to detect their IP
7610 address, and fixes a wide variety of other bugs to get us much closer
7611 to a stable release.
7614 - Do even more to reject (and not just ignore) annotations on
7615 router descriptors received anywhere but from the cache. Previously
7616 we would ignore such annotations at first, but cache them to disk
7617 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7618 - Do not log messages to the controller while shrinking buffer
7619 freelists. Doing so would sometimes make the controller connection
7620 try to allocate a buffer chunk, which would mess up the internals
7621 of the freelist and cause an assertion failure. Fixes bug 1125;
7622 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7623 - Learn our external IP address when we're a relay or bridge, even if
7624 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7625 where we introduced bridge relays that don't need to publish to
7626 be useful. Fixes bug 2050.
7627 - Maintain separate TLS contexts and certificates for incoming and
7628 outgoing connections in bridge relays. Previously we would use the
7629 same TLS contexts and certs for incoming and outgoing connections.
7630 Bugfix on 0.2.0.3-alpha; addresses bug 988.
7631 - Maintain separate identity keys for incoming and outgoing TLS
7632 contexts in bridge relays. Previously we would use the same
7633 identity keys for incoming and outgoing TLS contexts. Bugfix on
7634 0.2.0.3-alpha; addresses the other half of bug 988.
7635 - Avoid an assertion failure when we as an authority receive a
7636 duplicate upload of a router descriptor that we already have,
7637 but which we previously considered an obsolete descriptor.
7638 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
7639 - Avoid a crash bug triggered by looking at a dangling pointer while
7640 setting the network status consensus. Found by Robert Ransom.
7641 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
7642 - Fix a logic error where servers that _didn't_ act as exits would
7643 try to keep their server lists more aggressively up to date than
7644 exits, when it was supposed to be the other way around. Bugfix
7647 o Minor bugfixes (on Tor 0.2.1.x and earlier):
7648 - When we're trying to guess whether we know our IP address as
7649 a relay, we would log various ways that we failed to guess
7650 our address, but never log that we ended up guessing it
7651 successfully. Now add a log line to help confused and anxious
7652 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
7653 - Bring the logic that gathers routerinfos and assesses the
7654 acceptability of circuits into line. This prevents a Tor OP from
7655 getting locked in a cycle of choosing its local OR as an exit for a
7656 path (due to a .exit request) and then rejecting the circuit because
7657 its OR is not listed yet. It also prevents Tor clients from using an
7658 OR running in the same instance as an exit (due to a .exit request)
7659 if the OR does not meet the same requirements expected of an OR
7660 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7661 - Correctly describe errors that occur when generating a TLS object.
7662 Previously we would attribute them to a failure while generating a
7663 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
7665 - Enforce multiplicity rules when parsing annotations. Bugfix on
7666 0.2.0.8-alpha. Found by piebeer.
7667 - Fix warnings that newer versions of autoconf produced during
7668 ./autogen.sh. These warnings appear to be harmless in our case,
7669 but they were extremely verbose. Fixes bug 2020.
7671 o Minor bugfixes (on Tor 0.2.2.x):
7672 - Enable protection of small arrays whenever we build with gcc
7673 hardening features, not only when also building with warnings
7674 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
7677 - Make hidden services work better in private Tor networks by not
7678 requiring any uptime to join the hidden service descriptor
7679 DHT. Implements ticket 2088.
7680 - Rate-limit the "your application is giving Tor only an IP address"
7681 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
7682 - When AllowSingleHopExits is set, print a warning to explain to the
7683 relay operator why most clients are avoiding her relay.
7684 - Update to the November 1 2010 Maxmind GeoLite Country database.
7686 o Code simplifications and refactoring:
7687 - When we fixed bug 1038 we had to put in a restriction not to send
7688 RELAY_EARLY cells on rend circuits. This was necessary as long
7689 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
7690 active. Now remove this obsolete check. Resolves bug 2081.
7691 - Some options used different conventions for uppercasing of acronyms
7692 when comparing manpage and source. Fix those in favor of the
7693 manpage, as it makes sense to capitalize acronyms.
7694 - Remove the torrc.complete file. It hasn't been kept up to date
7695 and users will have better luck checking out the manpage.
7696 - Remove the obsolete "NoPublish" option; it has been flagged
7697 as obsolete and has produced a warning since 0.1.1.18-rc.
7698 - Remove everything related to building the expert bundle for OS X.
7699 It has confused many users, doesn't work right on OS X 10.6,
7700 and is hard to get rid of once installed. Resolves bug 1274.
7703 Changes in version 0.2.2.17-alpha - 2010-09-30
7704 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
7705 to use one-hop circuits (which can put the exit relays at higher risk,
7706 plus unbalance the network); fixes a big bug in bandwidth accounting
7707 for relays that want to limit their monthly bandwidth use; fixes a
7708 big pile of bugs in how clients tolerate temporary network failure;
7709 and makes our adaptive circuit build timeout feature (which improves
7710 client performance if your network is fast while not breaking things
7711 if your network is slow) better handle bad networks.
7714 - Exit relays now try harder to block exit attempts from unknown
7715 relays, to make it harder for people to use them as one-hop proxies
7716 a la tortunnel. Controlled by the refuseunknownexits consensus
7717 parameter (currently enabled), or you can override it on your
7718 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
7720 o Major bugfixes (0.2.1.x and earlier):
7721 - Fix a bug in bandwidth accounting that could make us use twice
7722 the intended bandwidth when our interval start changes due to
7723 daylight saving time. Now we tolerate skew in stored vs computed
7724 interval starts: if the start of the period changes by no more than
7725 50% of the period's duration, we remember bytes that we transferred
7726 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
7727 - Always search the Windows system directory for system DLLs, and
7728 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
7729 - When you're using bridges and your network goes away and your
7730 bridges get marked as down, recover when you attempt a new socks
7731 connection (if the network is back), rather than waiting up to an
7732 hour to try fetching new descriptors for your bridges. Bugfix on
7733 0.2.0.3-alpha; fixes bug 1981.
7735 o Major bugfixes (on 0.2.2.x):
7736 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
7738 - Fix a segfault that could happen when operating a bridge relay with
7739 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
7740 - The consensus bandwidth-weights (used by clients to choose fast
7741 relays) entered an unexpected edge case in September where
7742 Exits were much scarcer than Guards, resulting in bad weight
7743 recommendations. Now we compute them using new constraints that
7744 should succeed in all cases. Also alter directory authorities to
7745 not include the bandwidth-weights line if they fail to produce
7746 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
7747 - When weighting bridges during path selection, we used to trust
7748 the bandwidths they provided in their descriptor, only capping them
7749 at 10MB/s. This turned out to be problematic for two reasons:
7750 Bridges could claim to handle a lot more traffic then they
7751 actually would, thus making more clients pick them and have a
7752 pretty effective DoS attack. The other issue is that new bridges
7753 that might not have a good estimate for their bw capacity yet
7754 would not get used at all unless no other bridges are available
7755 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
7757 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
7758 - Ignore cannibalized circuits when recording circuit build times.
7759 This should provide for a minor performance improvement for hidden
7760 service users using 0.2.2.14-alpha, and should remove two spurious
7761 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
7762 - Simplify the logic that causes us to decide if the network is
7763 unavailable for purposes of recording circuit build times. If we
7764 receive no cells whatsoever for the entire duration of a circuit's
7765 full measured lifetime, the network is probably down. Also ignore
7766 one-hop directory fetching circuit timeouts when calculating our
7767 circuit build times. These changes should hopefully reduce the
7768 cases where we see ridiculous circuit build timeouts for people
7769 with spotty wireless connections. Fixes part of bug 1772; bugfix
7771 - Prevent the circuit build timeout from becoming larger than
7772 the maximum build time we have ever seen. Also, prevent the time
7773 period for measurement circuits from becoming larger than twice that
7774 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
7777 - When we run out of directory information such that we can't build
7778 circuits, but then get enough that we can build circuits, log when
7779 we actually construct a circuit, so the user has a better chance of
7780 knowing what's going on. Fixes bug 1362.
7781 - Be more generous with how much bandwidth we'd use up (with
7782 accounting enabled) before entering "soft hibernation". Previously,
7783 we'd refuse new connections and circuits once we'd used up 95% of
7784 our allotment. Now, we use up 95% of our allotment, AND make sure
7785 that we have no more than 500MB (or 3 hours of expected traffic,
7786 whichever is lower) remaining before we enter soft hibernation.
7787 - If we've configured EntryNodes and our network goes away and/or all
7788 our entrynodes get marked down, optimistically retry them all when
7789 a new socks application request appears. Fixes bug 1882.
7790 - Add some more defensive programming for architectures that can't
7791 handle unaligned integer accesses. We don't know of any actual bugs
7792 right now, but that's the best time to fix them. Fixes bug 1943.
7793 - Support line continuations in the torrc config file. If a line
7794 ends with a single backslash character, the newline is ignored, and
7795 the configuration value is treated as continuing on the next line.
7798 o Minor bugfixes (on 0.2.1.x and earlier):
7799 - For bandwidth accounting, calculate our expected bandwidth rate
7800 based on the time during which we were active and not in
7801 soft-hibernation during the last interval. Previously, we were
7802 also considering the time spent in soft-hibernation. If this
7803 was a long time, we would wind up underestimating our bandwidth
7804 by a lot, and skewing our wakeup time towards the start of the
7805 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
7807 o Minor bugfixes (on 0.2.2.x):
7808 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
7809 which were disabled by the circuit build timeout changes in
7810 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
7811 - Make sure we don't warn about missing bandwidth weights when
7812 choosing bridges or other relays not in the consensus. Bugfix on
7813 0.2.2.10-alpha; fixes bug 1805.
7814 - In our logs, do not double-report signatures from unrecognized
7815 authorities both as "from unknown authority" and "not
7816 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
7819 Changes in version 0.2.2.16-alpha - 2010-09-17
7820 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
7821 evident at exit relays), and also continues to resolve all the little
7822 bugs that have been filling up trac lately.
7824 o Major bugfixes (stream-level fairness):
7825 - When receiving a circuit-level SENDME for a blocked circuit, try
7826 to package cells fairly from all the streams that had previously
7827 been blocked on that circuit. Previously, we had started with the
7828 oldest stream, and allowed each stream to potentially exhaust
7829 the circuit's package window. This gave older streams on any
7830 given circuit priority over newer ones. Fixes bug 1937. Detected
7831 originally by Camilo Viecco. This bug was introduced before the
7832 first Tor release, in svn commit r152: it is the new winner of
7833 the longest-lived bug prize.
7834 - When the exit relay got a circuit-level sendme cell, it started
7835 reading on the exit streams, even if had 500 cells queued in the
7836 circuit queue already, so the circuit queue just grew and grew in
7837 some cases. We fix this by not re-enabling reading on receipt of a
7838 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
7839 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
7841 - Newly created streams were allowed to read cells onto circuits,
7842 even if the circuit's cell queue was blocked and waiting to drain.
7843 This created potential unfairness, as older streams would be
7844 blocked, but newer streams would gladly fill the queue completely.
7845 We add code to detect this situation and prevent any stream from
7846 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
7850 - Update to the September 1 2010 Maxmind GeoLite Country database.
7851 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
7852 not. This would lead to a cookie that is still not group readable.
7853 Closes bug 1843. Suggested by katmagic.
7854 - When logging a rate-limited warning, we now mention how many messages
7855 got suppressed since the last warning.
7856 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
7857 do individual connection-level rate limiting of clients. The torrc
7858 config options with the same names trump the consensus params, if
7859 both are present. Replaces the old "bwconnrate" and "bwconnburst"
7860 consensus params which were broken from 0.2.2.7-alpha through
7861 0.2.2.14-alpha. Closes bug 1947.
7862 - When a router changes IP address or port, authorities now launch
7863 a new reachability test for it. Implements ticket 1899.
7864 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
7865 2 no signature, 4 required" messages about consensus signatures
7866 easier to read, and make sure they get logged at the same severity
7867 as the messages explaining which keys are which. Fixes bug 1290.
7868 - Don't warn when we have a consensus that we can't verify because
7869 of missing certificates, unless those certificates are ones
7870 that we have been trying and failing to download. Fixes bug 1145.
7871 - If you configure your bridge with a known identity fingerprint,
7872 and the bridge authority is unreachable (as it is in at least
7873 one country now), fall back to directly requesting the descriptor
7874 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
7876 - When building with --enable-gcc-warnings on OpenBSD, disable
7877 warnings in system headers. This makes --enable-gcc-warnings
7878 pass on OpenBSD 4.8.
7880 o Minor bugfixes (on 0.2.1.x and earlier):
7881 - Authorities will now attempt to download consensuses if their
7882 own efforts to make a live consensus have failed. This change
7883 means authorities that restart will fetch a valid consensus, and
7884 it means authorities that didn't agree with the current consensus
7885 will still fetch and serve it if it has enough signatures. Bugfix
7886 on 0.2.0.9-alpha; fixes bug 1300.
7887 - Ensure DNS requests launched by "RESOLVE" commands from the
7888 controller respect the __LeaveStreamsUnattached setconf options. The
7889 same goes for requests launched via DNSPort or transparent
7890 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
7891 - Allow handshaking OR connections to take a full KeepalivePeriod
7892 seconds to handshake. Previously, we would close them after
7893 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7894 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7896 - Rate-limit "Failed to hand off onionskin" warnings.
7897 - Never relay a cell for a circuit we have already destroyed.
7898 Between marking a circuit as closeable and finally closing it,
7899 it may have been possible for a few queued cells to get relayed,
7900 even though they would have been immediately dropped by the next
7901 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
7902 - Never queue a cell for a circuit that's already been marked
7904 - Never vote for a server as "Running" if we have a descriptor for
7905 it claiming to be hibernating, and that descriptor was published
7906 more recently than our last contact with the server. Bugfix on
7907 0.2.0.3-alpha; fixes bug 911.
7908 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
7911 o Minor bugfixes (on 0.2.2.x):
7912 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
7913 down if a directory fetch fails and you've configured either
7914 bridges or EntryNodes. The intent was to mark the relay as down
7915 _unless_ you're using bridges or EntryNodes, since if you are
7916 then you could quickly run out of entry points.
7917 - Fix the Windows directory-listing code. A bug introduced in
7918 0.2.2.14-alpha could make Windows directory servers forget to load
7919 some of their cached v2 networkstatus files.
7920 - Really allow clients to use relays as bridges. Fixes bug 1776;
7921 bugfix on 0.2.2.15-alpha.
7922 - Demote a warn to info that happens when the CellStatistics option
7923 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
7924 Reported by Moritz Bartl.
7925 - On Windows, build correctly either with or without Unicode support.
7926 This is necessary so that Tor can support fringe platforms like
7927 Windows 98 (which has no Unicode), or Windows CE (which has no
7928 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
7931 - Add a unit test for cross-platform directory-listing code.
7934 Changes in version 0.2.2.15-alpha - 2010-08-18
7935 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
7936 fixes a variety of other bugs that were preventing performance
7937 experiments from moving forward, fixes several bothersome memory leaks,
7938 and generally closes a lot of smaller bugs that have been filling up
7942 - Stop assigning the HSDir flag to relays that disable their
7943 DirPort (and thus will refuse to answer directory requests). This
7944 fix should dramatically improve the reachability of hidden services:
7945 hidden services and hidden service clients pick six HSDir relays
7946 to store and retrieve the hidden service descriptor, and currently
7947 about half of the HSDir relays will refuse to work. Bugfix on
7948 0.2.0.10-alpha; fixes part of bug 1693.
7949 - The PerConnBWRate and Burst config options, along with the
7950 bwconnrate and bwconnburst consensus params, initialized each conn's
7951 token bucket values only when the connection is established. Now we
7952 update them if the config options change, and update them every time
7953 we get a new consensus. Otherwise we can encounter an ugly edge
7954 case where we initialize an OR conn to client-level bandwidth,
7955 but then later the relay joins the consensus and we leave it
7956 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
7957 - Fix a regression that caused Tor to rebind its ports if it receives
7958 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
7961 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
7962 should give us approximately 40-50% more Guard-flagged nodes,
7963 improving the anonymity the Tor network can provide and also
7964 decreasing the dropoff in throughput that relays experience when
7965 they first get the Guard flag.
7966 - Allow enabling or disabling the *Statistics config options while
7970 - Update to the August 1 2010 Maxmind GeoLite Country database.
7971 - Have the controller interface give a more useful message than
7972 "Internal Error" in response to failed GETINFO requests.
7973 - Warn when the same option is provided more than once in a torrc
7974 file, on the command line, or in a single SETCONF statement, and
7975 the option is one that only accepts a single line. Closes bug 1384.
7976 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7977 Patch from mingw-san.
7978 - Add support for the country code "{??}" in torrc options like
7979 ExcludeNodes, to indicate all routers of unknown country. Closes
7981 - Relays report the number of bytes spent on answering directory
7982 requests in extra-info descriptors similar to {read,write}-history.
7983 Implements enhancement 1790.
7985 o Minor bugfixes (on 0.2.1.x and earlier):
7986 - Complain if PublishServerDescriptor is given multiple arguments that
7987 include 0 or 1. This configuration will be rejected in the future.
7988 Bugfix on 0.2.0.1-alpha; closes bug 1107.
7989 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
7990 Bugfix on 0.2.0.13-alpha; closes bug 928.
7991 - Change "Application request when we're believed to be offline."
7992 notice to "Application request when we haven't used client
7993 functionality lately.", to clarify that it's not an error. Bugfix
7994 on 0.0.9.3; fixes bug 1222.
7995 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
7996 would return "551 Internal error" rather than "552 Unrecognized key
7997 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
7998 - Users can't configure a regular relay to be their bridge. It didn't
7999 work because when Tor fetched the bridge descriptor, it found
8000 that it already had it, and didn't realize that the purpose of the
8001 descriptor had changed. Now we replace routers with a purpose other
8002 than bridge with bridge descriptors when fetching them. Bugfix on
8003 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
8004 refetch the descriptor with router purpose 'general', disabling
8006 - Fix a rare bug in rend_fn unit tests: we would fail a test when
8007 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
8008 on 0.2.0.10-alpha; fixes bug 1808.
8009 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8010 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8011 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8012 Servers can start sending this code when enough clients recognize
8013 it. Also update the spec to reflect this new reason. Bugfix on
8014 0.1.0.1-rc; fixes part of bug 1793.
8015 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
8016 when we switch from being a public relay to a bridge. Otherwise
8017 there will still be clients that see the relay in their consensus,
8018 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
8020 - Instead of giving an assertion failure on an internal mismatch
8021 on estimated freelist size, just log a BUG warning and try later.
8022 Mitigates but does not fix bug 1125.
8023 - Fix an assertion failure that could occur in caches or bridge users
8024 when using a very short voting interval on a testing network.
8025 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
8027 o Minor bugfixes (on 0.2.2.x):
8028 - Alter directory authorities to always consider Exit-flagged nodes
8029 as potential Guard nodes in their votes. The actual decision to
8030 use Exits as Guards is done in the consensus bandwidth weights.
8031 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
8032 - When the controller is reporting the purpose of circuits that
8033 didn't finish building before the circuit build timeout, it was
8034 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
8035 - Our libevent version parsing code couldn't handle versions like
8036 1.4.14b-stable and incorrectly warned the user about using an
8037 old and broken version of libevent. Treat 1.4.14b-stable like
8038 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
8040 - Don't use substitution references like $(VAR:MOD) when
8041 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
8042 '$(:x)' to 'x' rather than the empty string. This bites us in
8043 doc/ when configured with --disable-asciidoc. Bugfix on
8044 0.2.2.9-alpha; fixes bug 1773.
8045 - Remove a spurious hidden service server-side log notice about
8046 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
8048 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
8050 - Correctly report written bytes on linked connections. Found while
8051 implementing 1790. Bugfix on 0.2.2.4-alpha.
8052 - Fix three memory leaks: one in circuit_build_times_parse_state(),
8053 one in dirvote_add_signatures_to_pending_consensus(), and one every
8054 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
8055 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
8057 o Code simplifications and refactoring:
8058 - Take a first step towards making or.h smaller by splitting out
8059 function definitions for all source files in src/or/. Leave
8060 structures and defines in or.h for now.
8061 - Remove a bunch of unused function declarations as well as a block of
8062 #if 0'd code from the unit tests. Closes bug 1824.
8063 - New unit tests for exit-port history statistics; refactored exit
8064 statistics code to be more easily tested.
8065 - Remove the old debian/ directory from the main Tor distribution.
8066 The official Tor-for-debian git repository lives at the URL
8067 https://git.torproject.org/debian/tor.git
8070 Changes in version 0.2.2.14-alpha - 2010-07-12
8071 Tor 0.2.2.14-alpha greatly improves client-side handling of
8072 circuit build timeouts, which are used to estimate speed and improve
8073 performance. We also move to a much better GeoIP database, port Tor to
8074 Windows CE, introduce new compile flags that improve code security,
8075 add an eighth v3 directory authority, and address a lot of more
8079 - Tor directory authorities no longer crash when started with a
8080 cached-microdesc-consensus file in their data directory. Bugfix
8081 on 0.2.2.6-alpha; fixes bug 1532.
8082 - Treat an unset $HOME like an empty $HOME rather than triggering an
8083 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
8084 - Ignore negative and large circuit build timeout values that can
8085 happen during a suspend or hibernate. These values caused various
8086 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
8087 - Alter calculation of Pareto distribution parameter 'Xm' for
8088 Circuit Build Timeout learning to use the weighted average of the
8089 top N=3 modes (because we have three entry guards). Considering
8090 multiple modes should improve the timeout calculation in some cases,
8091 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
8093 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
8094 right censored distribution model. This approach improves over the
8095 synthetic timeout generation approach that was producing insanely
8096 high timeout values. Now we calculate build timeouts using truncated
8097 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
8098 - Do not close circuits that are under construction when they reach
8099 the circuit build timeout. Instead, leave them building (but do not
8100 use them) for up until the time corresponding to the 95th percentile
8101 on the Pareto CDF or 60 seconds, whichever is greater. This is done
8102 to provide better data for the new Pareto model. This percentile
8103 can be controlled by the consensus.
8106 - Move to the June 2010 Maxmind GeoLite country db (rather than the
8107 June 2009 ip-to-country GeoIP db) for our statistics that count
8108 how many users relays are seeing from each country. Now we have
8109 more accurate data for many African countries.
8110 - Port Tor to build and run correctly on Windows CE systems, using
8111 the wcecompat library. Contributed by Valerio Lupi.
8112 - New "--enable-gcc-hardening" ./configure flag (off by default)
8113 to turn on gcc compile time hardening options. It ensures
8114 that signed ints have defined behavior (-fwrapv), enables
8115 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
8116 with canaries (-fstack-protector-all), turns on ASLR protection if
8117 supported by the kernel (-fPIE, -pie), and adds additional security
8118 related warnings. Verified to work on Mac OS X and Debian Lenny.
8119 - New "--enable-linker-hardening" ./configure flag (off by default)
8120 to turn on ELF specific hardening features (relro, now). This does
8121 not work with Mac OS X or any other non-ELF binary format.
8123 o New directory authorities:
8124 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8128 - New config option "WarnUnsafeSocks 0" disables the warning that
8129 occurs whenever Tor receives a socks handshake using a version of
8130 the socks protocol that can only provide an IP address (rather
8131 than a hostname). Setups that do DNS locally over Tor are fine,
8132 and we shouldn't spam the logs in that case.
8133 - Convert the HACKING file to asciidoc, and add a few new sections
8134 to it, explaining how we use Git, how we make changelogs, and
8135 what should go in a patch.
8136 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
8137 event, to give information on the current rate of circuit timeouts
8138 over our stored history.
8139 - Add ability to disable circuit build time learning via consensus
8140 parameter and via a LearnCircuitBuildTimeout config option. Also
8141 automatically disable circuit build time calculation if we are
8142 either a AuthoritativeDirectory, or if we fail to write our state
8143 file. Fixes bug 1296.
8144 - More gracefully handle corrupt state files, removing asserts
8145 in favor of saving a backup and resetting state.
8146 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
8150 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8152 - When a2x fails, mention that the user could disable manpages instead
8153 of trying to fix their asciidoc installation.
8154 - Where available, use Libevent 2.0's periodic timers so that our
8155 once-per-second cleanup code gets called even more closely to
8156 once per second than it would otherwise. Fixes bug 943.
8157 - If you run a bridge that listens on multiple IP addresses, and
8158 some user configures a bridge address that uses a different IP
8159 address than your bridge writes in its router descriptor, and the
8160 user doesn't specify an identity key, their Tor would discard the
8161 descriptor because "it isn't one of our configured bridges", and
8162 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
8163 Bugfix on 0.2.0.3-alpha.
8164 - If OpenSSL fails to make a duplicate of a private or public key, log
8165 an error message and try to exit cleanly. May help with debugging
8166 if bug 1209 ever remanifests.
8167 - Save a couple bytes in memory allocation every time we escape
8168 certain characters in a string. Patch from Florian Zumbiehl.
8169 - Make it explicit that we don't cannibalize one-hop circuits. This
8170 happens in the wild, but doesn't turn out to be a problem because
8171 we fortunately don't use those circuits. Many thanks to outofwords
8172 for the initial analysis and to swissknife who confirmed that
8173 two-hop circuits are actually created.
8174 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
8175 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
8176 - Eliminate a case where a circuit build time warning was displayed
8177 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
8180 Changes in version 0.2.1.26 - 2010-05-02
8181 Tor 0.2.1.26 addresses the recent connection and memory overload
8182 problems we've been seeing on relays, especially relays with their
8183 DirPort open. If your relay has been crashing, or you turned it off
8184 because it used too many resources, give this release a try.
8186 This release also fixes yet another instance of broken OpenSSL libraries
8187 that was causing some relays to drop out of the consensus.
8190 - Teach relays to defend themselves from connection overload. Relays
8191 now close idle circuits early if it looks like they were intended
8192 for directory fetches. Relays are also more aggressive about closing
8193 TLS connections that have no circuits on them. Such circuits are
8194 unlikely to be re-used, and tens of thousands of them were piling
8195 up at the fast relays, causing the relays to run out of sockets
8196 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8197 their directory fetches over TLS).
8198 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8199 that claim to be earlier than 0.9.8m, but which have in reality
8200 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8201 behavior. Possible fix for some cases of bug 1346.
8202 - Directory mirrors were fetching relay descriptors only from v2
8203 directory authorities, rather than v3 authorities like they should.
8204 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8205 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8208 - Finally get rid of the deprecated and now harmful notion of "clique
8209 mode", where directory authorities maintain TLS connections to
8213 - In the util/threads test, no longer free the test_mutex before all
8214 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8215 - The master thread could starve the worker threads quite badly on
8216 certain systems, causing them to run only partially in the allowed
8217 window. This resulted in test failures. Now the master thread sleeps
8218 occasionally for a few microseconds while the two worker-threads
8219 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8222 Changes in version 0.2.2.13-alpha - 2010-04-24
8223 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
8224 problems we've been seeing on relays, especially relays with their
8225 DirPort open. If your relay has been crashing, or you turned it off
8226 because it used too many resources, give this release a try.
8229 - Teach relays to defend themselves from connection overload. Relays
8230 now close idle circuits early if it looks like they were intended
8231 for directory fetches. Relays are also more aggressive about closing
8232 TLS connections that have no circuits on them. Such circuits are
8233 unlikely to be re-used, and tens of thousands of them were piling
8234 up at the fast relays, causing the relays to run out of sockets
8235 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8236 their directory fetches over TLS).
8239 - Finally get rid of the deprecated and now harmful notion of "clique
8240 mode", where directory authorities maintain TLS connections to
8242 - Directory authorities now do an immediate reachability check as soon
8243 as they hear about a new relay. This change should slightly reduce
8244 the time between setting up a relay and getting listed as running
8245 in the consensus. It should also improve the time between setting
8246 up a bridge and seeing use by bridge users.
8247 - Directory authorities no longer launch a TLS connection to every
8248 relay as they startup. Now that we have 2k+ descriptors cached,
8249 the resulting network hiccup is becoming a burden. Besides,
8250 authorities already avoid voting about Running for the first half
8251 hour of their uptime.
8254 Changes in version 0.2.2.12-alpha - 2010-04-20
8255 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
8256 handle and vote on descriptors. It was causing relays to drop out of
8260 - Many relays have been falling out of the consensus lately because
8261 not enough authorities know about their descriptor for them to get
8262 a majority of votes. When we deprecated the v2 directory protocol,
8263 we got rid of the only way that v3 authorities can hear from each
8264 other about other descriptors. Now authorities examine every v3
8265 vote for new descriptors, and fetch them from that authority. Bugfix
8267 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
8268 and a warning in or.h related to bandwidth_weight_rule_t that
8269 prevented clean compile on OS X. Fixes bug 1363; bugfix on
8271 - Fix a segfault on relays when DirReqStatistics is enabled
8272 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
8276 - Demote a confusing TLS warning that relay operators might get when
8277 someone tries to talk to their OrPort. It is neither the operator's
8278 fault nor can they do anything about it. Fixes bug 1364; bugfix
8282 Changes in version 0.2.2.11-alpha - 2010-04-15
8283 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
8284 libraries that was causing some relays to drop out of the consensus.
8287 - Directory mirrors were fetching relay descriptors only from v2
8288 directory authorities, rather than v3 authorities like they should.
8289 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8290 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8291 - Fix a parsing error that made every possible value of
8292 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
8293 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
8294 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
8295 about the option without breaking older ones.
8296 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8297 that claim to be earlier than 0.9.8m, but which have in reality
8298 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8299 behavior. Possible fix for some cases of bug 1346.
8302 - Experiment with a more aggressive approach to preventing clients
8303 from making one-hop exit streams. Exit relays who want to try it
8304 out can set "RefuseUnknownExits 1" in their torrc, and then look
8305 for "Attempt by %s to open a stream" log messages. Let us know
8307 - Add support for statically linking zlib by specifying
8308 --enable-static-zlib, to go with our support for statically linking
8309 openssl and libevent. Resolves bug 1358.
8312 - Fix a segfault that happens whenever a Tor client that is using
8313 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
8315 - When we cleaned up the contrib/tor-exit-notice.html file, we left
8316 out the first line. Fixes bug 1295.
8317 - When building the manpage from a tarball, we required asciidoc, but
8318 the asciidoc -> roff/html conversion was already done for the
8319 tarball. Make 'make' complain only when we need asciidoc (either
8320 because we're compiling directly from git, or because we altered
8321 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
8322 - When none of the directory authorities vote on any params, Tor
8323 segfaulted when trying to make the consensus from the votes. We
8324 didn't trigger the bug in practice, because authorities do include
8325 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
8328 - In the util/threads test, no longer free the test_mutex before all
8329 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8330 - The master thread could starve the worker threads quite badly on
8331 certain systems, causing them to run only partially in the allowed
8332 window. This resulted in test failures. Now the master thread sleeps
8333 occasionally for a few microseconds while the two worker-threads
8334 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8337 Changes in version 0.2.2.10-alpha - 2010-03-07
8338 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
8339 could prevent relays from guessing their IP address correctly. It also
8340 starts the groundwork for another client-side performance boost, since
8341 currently we're not making efficient use of relays that have both the
8342 Guard flag and the Exit flag.
8345 - Fix a regression from our patch for bug 1244 that caused relays
8346 to guess their IP address incorrectly if they didn't set Address
8347 in their torrc and/or their address fails to resolve. Bugfix on
8348 0.2.2.9-alpha; fixes bug 1269.
8350 o Major features (performance):
8351 - Directory authorities now compute consensus weightings that instruct
8352 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
8353 and no flag. Clients that use these weightings will distribute
8354 network load more evenly across these different relay types. The
8355 weightings are in the consensus so we can change them globally in
8356 the future. Extra thanks to "outofwords" for finding some nasty
8357 security bugs in the first implementation of this feature.
8359 o Minor features (performance):
8360 - Always perform router selections using weighted relay bandwidth,
8361 even if we don't need a high capacity circuit at the time. Non-fast
8362 circuits now only differ from fast ones in that they can use relays
8363 not marked with the Fast flag. This "feature" could turn out to
8364 be a horrible bug; we should investigate more before it goes into
8368 - Allow disabling building of the manpages. Skipping the manpage
8369 speeds up the build considerably.
8371 o Minor bugfixes (on 0.2.2.x):
8372 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
8373 Bugfix on 0.2.2.9-alpha.
8374 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
8375 config option. Bugfix on 0.2.2.7-alpha.
8376 - Ship the asciidoc-helper file in the tarball, so that people can
8377 build from source if they want to, and touching the .1.txt files
8378 doesn't break the build. Bugfix on 0.2.2.9-alpha.
8380 o Minor bugfixes (on 0.2.1.x or earlier):
8381 - Fix a dereference-then-NULL-check sequence when publishing
8382 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8384 - Fix another dereference-then-NULL-check sequence. Bugfix on
8385 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8386 - Make sure we treat potentially not NUL-terminated strings correctly.
8387 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8389 o Code simplifications and refactoring:
8390 - Fix some urls in the exit notice file and make it XHTML1.1 strict
8391 compliant. Based on a patch from Christian Kujau.
8392 - Don't use sed in asciidoc-helper anymore.
8393 - Make the build process fail if asciidoc cannot be found and
8394 building with asciidoc isn't disabled.
8397 Changes in version 0.2.2.9-alpha - 2010-02-22
8398 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
8399 location of a directory authority, and cleans up a bunch of small bugs.
8401 o Directory authority changes:
8402 - Change IP address for dannenberg (v3 directory authority), and
8403 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
8404 service directory authority) from the list.
8407 - Make Tor work again on the latest OS X: when deciding whether to
8408 use strange flags to turn TLS renegotiation on, detect the OpenSSL
8409 version at run-time, not compile time. We need to do this because
8410 Apple doesn't update its dev-tools headers when it updates its
8411 libraries in a security patch.
8412 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
8413 that could happen on 32-bit platforms with 64-bit time_t. Also fix
8414 a memory leak when requesting a hidden service descriptor we've
8415 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
8417 - Authorities could be tricked into giving out the Exit flag to relays
8418 that didn't allow exiting to any ports. This bug could screw
8419 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
8420 1238. Bug discovered by Martin Kowalczyk.
8421 - When freeing a session key, zero it out completely. We only zeroed
8422 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8423 patched by ekir. Fixes bug 1254.
8426 - Fix static compilation by listing the openssl libraries in the right
8427 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
8428 - Resume handling .exit hostnames in a special way: originally we
8429 stripped the .exit part and used the requested exit relay. In
8430 0.2.2.1-alpha we stopped treating them in any special way, meaning
8431 if you use a .exit address then Tor will pass it on to the exit
8432 relay. Now we reject the .exit stream outright, since that behavior
8433 might be more expected by the user. Found and diagnosed by Scott
8434 Bennett and Downie on or-talk.
8435 - Don't spam the controller with events when we have no file
8436 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
8437 for log messages was already solved from bug 748.)
8438 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
8440 - Make the DNSPort option work with libevent 2.x. Don't alter the
8441 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
8442 - Emit a GUARD DROPPED controller event for a case we missed.
8443 - Make more fields in the controller protocol case-insensitive, since
8444 control-spec.txt said they were.
8445 - Refactor resolve_my_address() to not use gethostbyname() anymore.
8446 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
8447 - Fix a spec conformance issue: the network-status-version token
8448 must be the first token in a v3 consensus or vote. Discovered by
8449 parakeep. Bugfix on 0.2.0.3-alpha.
8451 o Code simplifications and refactoring:
8452 - Generate our manpage and HTML documentation using Asciidoc. This
8453 change should make it easier to maintain the documentation, and
8455 - Remove the --enable-iphone option. According to reports from Marco
8456 Bonetti, Tor builds fine without any special tweaking on recent
8457 iPhone SDK versions.
8458 - Removed some unnecessary files from the source distribution. The
8459 AUTHORS file has now been merged into the people page on the
8460 website. The roadmaps and design doc can now be found in the
8461 projects directory in svn.
8462 - Enabled various circuit build timeout constants to be controlled
8463 by consensus parameters. Also set better defaults for these
8464 parameters based on experimentation on broadband and simulated
8468 - The 'EXTENDCIRCUIT' control port command can now be used with
8469 a circ id of 0 and no path. This feature will cause Tor to build
8470 a new 'fast' general purpose circuit using its own path selection
8472 - Added a BUILDTIMEOUT_SET controller event to describe changes
8473 to the circuit build timeout.
8474 - Future-proof the controller protocol a bit by ignoring keyword
8475 arguments we do not recognize.
8476 - Expand homedirs passed to tor-checkkey. This should silence a
8477 coverity complaint about passing a user-supplied string into
8478 open() without checking it.
8481 Changes in version 0.2.1.25 - 2010-03-16
8482 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
8483 prevent relays from guessing their IP address correctly. It also fixes
8484 several minor potential security bugs.
8487 - Fix a regression from our patch for bug 1244 that caused relays
8488 to guess their IP address incorrectly if they didn't set Address
8489 in their torrc and/or their address fails to resolve. Bugfix on
8490 0.2.1.23; fixes bug 1269.
8491 - When freeing a session key, zero it out completely. We only zeroed
8492 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8493 patched by ekir. Fixes bug 1254.
8496 - Fix a dereference-then-NULL-check sequence when publishing
8497 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8499 - Fix another dereference-then-NULL-check sequence. Bugfix on
8500 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8501 - Make sure we treat potentially not NUL-terminated strings correctly.
8502 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8506 Changes in version 0.2.1.24 - 2010-02-21
8507 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
8511 - Work correctly out-of-the-box with even more vendor-patched versions
8512 of OpenSSL. In particular, make it so Debian and OS X don't need
8513 customized patches to run/build.
8516 Changes in version 0.2.1.23 - 2010-02-13
8517 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
8518 again on the latest OS X, and updates the location of a directory
8521 o Major bugfixes (performance):
8522 - We were selecting our guards uniformly at random, and then weighting
8523 which of our guards we'd use uniformly at random. This imbalance
8524 meant that Tor clients were severely limited on throughput (and
8525 probably latency too) by the first hop in their circuit. Now we
8526 select guards weighted by currently advertised bandwidth. We also
8527 automatically discard guards picked using the old algorithm. Fixes
8528 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
8531 - Make Tor work again on the latest OS X: when deciding whether to
8532 use strange flags to turn TLS renegotiation on, detect the OpenSSL
8533 version at run-time, not compile time. We need to do this because
8534 Apple doesn't update its dev-tools headers when it updates its
8535 libraries in a security patch.
8536 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
8537 that could happen on 32-bit platforms with 64-bit time_t. Also fix
8538 a memory leak when requesting a hidden service descriptor we've
8539 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
8542 o Directory authority changes:
8543 - Change IP address for dannenberg (v3 directory authority), and
8544 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
8545 service directory authority) from the list.
8548 - Refactor resolve_my_address() to not use gethostbyname() anymore.
8549 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
8552 - Avoid a mad rush at the beginning of each month when each client
8553 rotates half of its guards. Instead we spread the rotation out
8554 throughout the month, but we still avoid leaving a precise timestamp
8555 in the state file about when we first picked the guard. Improves
8556 over the behavior introduced in 0.1.2.17.
8559 Changes in version 0.2.2.8-alpha - 2010-01-26
8560 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
8561 causing bridge relays to disappear. If you're running a bridge,
8565 - Fix a memory corruption bug on bridges that occured during the
8566 inclusion of stats data in extra-info descriptors. Also fix the
8567 interface for geoip_get_bridge_stats* to prevent similar bugs in
8568 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
8569 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
8572 - Ignore OutboundBindAddress when connecting to localhost.
8573 Connections to localhost need to come _from_ localhost, or else
8574 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
8578 Changes in version 0.2.2.7-alpha - 2010-01-19
8579 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
8580 as laying the groundwork for further relay-side performance fixes. It
8581 also starts cleaning up client behavior with respect to the EntryNodes,
8582 ExitNodes, and StrictNodes config options.
8584 This release also rotates two directory authority keys, due to a
8585 security breach of some of the Torproject servers.
8587 o Directory authority changes:
8588 - Rotate keys (both v3 identity and relay identity) for moria1
8591 o Major features (performance):
8592 - We were selecting our guards uniformly at random, and then weighting
8593 which of our guards we'd use uniformly at random. This imbalance
8594 meant that Tor clients were severely limited on throughput (and
8595 probably latency too) by the first hop in their circuit. Now we
8596 select guards weighted by currently advertised bandwidth. We also
8597 automatically discard guards picked using the old algorithm. Fixes
8598 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
8599 - When choosing which cells to relay first, relays can now favor
8600 circuits that have been quiet recently, to provide lower latency
8601 for low-volume circuits. By default, relays enable or disable this
8602 feature based on a setting in the consensus. You can override
8603 this default by using the new "CircuitPriorityHalflife" config
8604 option. Design and code by Ian Goldberg, Can Tang, and Chris
8606 - Add separate per-conn write limiting to go with the per-conn read
8607 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
8608 but never per-conn write limits.
8609 - New consensus params "bwconnrate" and "bwconnburst" to let us
8610 rate-limit client connections as they enter the network. It's
8611 controlled in the consensus so we can turn it on and off for
8612 experiments. It's starting out off. Based on proposal 163.
8614 o Major features (relay selection options):
8615 - Switch to a StrictNodes config option, rather than the previous
8616 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
8617 "StrictExcludeNodes" option.
8618 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
8619 change during a config reload, mark and discard all our origin
8620 circuits. This fix should address edge cases where we change the
8621 config options and but then choose a circuit that we created before
8623 - If EntryNodes or ExitNodes are set, be more willing to use an
8624 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
8626 - Make EntryNodes config option much more aggressive even when
8627 StrictNodes is not set. Before it would prepend your requested
8628 entrynodes to your list of guard nodes, but feel free to use others
8629 after that. Now it chooses only from your EntryNodes if any of
8630 those are available, and only falls back to others if a) they're
8631 all down and b) StrictNodes is not set.
8632 - Now we refresh your entry guards from EntryNodes at each consensus
8633 fetch -- rather than just at startup and then they slowly rot as
8634 the network changes.
8637 - Stop bridge directory authorities from answering dbg-stability.txt
8638 directory queries, which would let people fetch a list of all
8639 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8642 - Log a notice when we get a new control connection. Now it's easier
8643 for security-conscious users to recognize when a local application
8644 is knocking on their controller door. Suggested by bug 1196.
8645 - New config option "CircuitStreamTimeout" to override our internal
8646 timeout schedule for how many seconds until we detach a stream from
8647 a circuit and try a new circuit. If your network is particularly
8648 slow, you might want to set this to a number like 60.
8649 - New controller command "getinfo config-text". It returns the
8650 contents that Tor would write if you send it a SAVECONF command,
8651 so the controller can write the file to disk itself.
8652 - New options for SafeLogging to allow scrubbing only log messages
8653 generated while acting as a relay.
8654 - Ship the bridges spec file in the tarball too.
8655 - Avoid a mad rush at the beginning of each month when each client
8656 rotates half of its guards. Instead we spread the rotation out
8657 throughout the month, but we still avoid leaving a precise timestamp
8658 in the state file about when we first picked the guard. Improves
8659 over the behavior introduced in 0.1.2.17.
8661 o Minor bugfixes (compiling):
8662 - Fix compilation on OS X 10.3, which has a stub mlockall() but
8663 hides it. Bugfix on 0.2.2.6-alpha.
8664 - Fix compilation on Solaris by removing support for the
8665 DisableAllSwap config option. Solaris doesn't have an rlimit for
8666 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
8669 o Minor bugfixes (crashes):
8670 - Do not segfault when writing buffer stats when we haven't observed
8671 a single circuit to report about. Found by Fabian Lanze. Bugfix on
8673 - If we're in the pathological case where there's no exit bandwidth
8674 but there is non-exit bandwidth, or no guard bandwidth but there
8675 is non-guard bandwidth, don't crash during path selection. Bugfix
8677 - Fix an impossible-to-actually-trigger buffer overflow in relay
8678 descriptor generation. Bugfix on 0.1.0.15.
8680 o Minor bugfixes (privacy):
8681 - Fix an instance where a Tor directory mirror might accidentally
8682 log the IP address of a misbehaving Tor client. Bugfix on
8684 - Don't list Windows capabilities in relay descriptors. We never made
8685 use of them, and maybe it's a bad idea to publish them. Bugfix
8688 o Minor bugfixes (other):
8689 - Resolve an edge case in path weighting that could make us misweight
8690 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
8691 - Fix statistics on client numbers by country as seen by bridges that
8692 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
8693 intervals instead of variable 12-to-48-hour intervals.
8694 - After we free an internal connection structure, overwrite it
8695 with a different memory value than we use for overwriting a freed
8696 internal circuit structure. Should help with debugging. Suggested
8698 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
8702 - Remove the HSAuthorityRecordStats option that version 0 hidden
8703 service authorities could have used to track statistics of overall
8704 hidden service usage.
8707 Changes in version 0.2.1.22 - 2010-01-19
8708 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
8709 authorities -- it would tell you its whole history of bridge descriptors
8710 if you make the right directory request. This stable update also
8711 rotates two of the seven v3 directory authority keys and locations.
8713 o Directory authority changes:
8714 - Rotate keys (both v3 identity and relay identity) for moria1
8718 - Stop bridge directory authorities from answering dbg-stability.txt
8719 directory queries, which would let people fetch a list of all
8720 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8723 Changes in version 0.2.1.21 - 2009-12-21
8724 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
8725 library. If you use Tor on Linux / Unix and you're getting SSL
8726 renegotiation errors, upgrading should help. We also recommend an
8727 upgrade if you're an exit relay.
8730 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8731 handshake from working unless we explicitly tell OpenSSL that we
8732 are using SSL renegotiation safely. We are, of course, but OpenSSL
8733 0.9.8l won't work unless we say we are.
8734 - Avoid crashing if the client is trying to upload many bytes and the
8735 circuit gets torn down at the same time, or if the flip side
8736 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
8739 - Do not refuse to learn about authority certs and v2 networkstatus
8740 documents that are older than the latest consensus. This bug might
8741 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8742 Spotted and fixed by xmux.
8743 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
8744 trigger platform-specific option misparsing case found by Coverity
8746 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
8747 trigger assert. Fixes bug 1173.
8750 Changes in version 0.2.2.6-alpha - 2009-11-19
8751 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
8752 support for the new lower-footprint "microdescriptor" directory design,
8753 future-proofing our consensus format against new hash functions or
8754 other changes, and an Android port. It also makes Tor compatible with
8755 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
8758 - Directory authorities can now create, vote on, and serve multiple
8759 parallel formats of directory data as part of their voting process.
8760 Partially implements Proposal 162: "Publish the consensus in
8762 - Directory authorities can now agree on and publish small summaries
8763 of router information that clients can use in place of regular
8764 server descriptors. This transition will eventually allow clients
8765 to use far less bandwidth for downloading information about the
8766 network. Begins the implementation of Proposal 158: "Clients
8767 download consensus + microdescriptors".
8768 - The directory voting system is now extensible to use multiple hash
8769 algorithms for signatures and resource selection. Newer formats
8770 are signed with SHA256, with a possibility for moving to a better
8771 hash algorithm in the future.
8772 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
8773 current and future memory pages via mlockall(). On supported
8774 platforms (modern Linux and probably BSD but not Windows or OS X),
8775 this should effectively disable any and all attempts to page out
8776 memory. This option requires that you start your Tor as root --
8777 if you use DisableAllSwap, please consider using the User option
8778 to properly reduce the privileges of your Tor.
8779 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
8780 to help Tor build correctly for Android phones.
8783 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8784 handshake from working unless we explicitly tell OpenSSL that we
8785 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
8786 won't work unless we say we are.
8789 - Fix a crash bug when trying to initialize the evdns module in
8790 Libevent 2. Bugfix on 0.2.1.16-rc.
8791 - Stop logging at severity 'warn' when some other Tor client tries
8792 to establish a circuit with us using weak DH keys. It's a protocol
8793 violation, but that doesn't mean ordinary users need to hear about
8794 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
8795 - Do not refuse to learn about authority certs and v2 networkstatus
8796 documents that are older than the latest consensus. This bug might
8797 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8798 Spotted and fixed by xmux.
8799 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
8800 - If all authorities restart at once right before a consensus vote,
8801 nobody will vote about "Running", and clients will get a consensus
8802 with no usable relays. Instead, authorities refuse to build a
8803 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
8804 - If your relay can't keep up with the number of incoming create
8805 cells, it would log one warning per failure into your logs. Limit
8806 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
8807 - Bridges now use "reject *:*" as their default exit policy. Bugfix
8808 on 0.2.0.3-alpha; fixes bug 1113.
8809 - Fix a memory leak on directory authorities during voting that was
8810 introduced in 0.2.2.1-alpha. Found via valgrind.
8813 Changes in version 0.2.1.20 - 2009-10-15
8814 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
8815 services at once, prepares for more performance improvements, and
8816 fixes a bunch of smaller bugs.
8818 The Windows and OS X bundles also include a more recent Vidalia,
8819 and switch from Privoxy to Polipo.
8821 The OS X installers are now drag and drop. It's best to un-install
8822 Tor/Vidalia and then install this new bundle, rather than upgrade. If
8823 you want to upgrade, you'll need to update the paths for Tor and Polipo
8824 in the Vidalia Settings window.
8827 - Send circuit or stream sendme cells when our window has decreased
8828 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8829 by Karsten when testing the "reduce circuit window" performance
8830 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8831 before the release of Tor 0.0.0. This is the new winner of the
8833 - Fix a remotely triggerable memory leak when a consensus document
8834 contains more than one signature from the same voter. Bugfix on
8836 - Avoid segfault in rare cases when finishing an introduction circuit
8837 as a client and finding out that we don't have an introduction key
8838 for it. Fixes bug 1073. Reported by Aaron Swartz.
8841 - Tor now reads the "circwindow" parameter out of the consensus,
8842 and uses that value for its circuit package window rather than the
8843 default of 1000 cells. Begins the implementation of proposal 168.
8845 o New directory authorities:
8846 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8848 - Move moria1 and tonga to alternate IP addresses.
8851 - Fix a signed/unsigned compile warning in 0.2.1.19.
8852 - Fix possible segmentation fault on directory authorities. Bugfix on
8854 - Fix an extremely rare infinite recursion bug that could occur if
8855 we tried to log a message after shutting down the log subsystem.
8856 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8857 - Fix an obscure bug where hidden services on 64-bit big-endian
8858 systems might mis-read the timestamp in v3 introduce cells, and
8859 refuse to connect back to the client. Discovered by "rotor".
8860 Bugfix on 0.2.1.6-alpha.
8861 - We were triggering a CLOCK_SKEW controller status event whenever
8862 we connect via the v2 connection protocol to any relay that has
8863 a wrong clock. Instead, we should only inform the controller when
8864 it's a trusted authority that claims our clock is wrong. Bugfix
8865 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8866 - We were telling the controller about CHECKING_REACHABILITY and
8867 REACHABILITY_FAILED status events whenever we launch a testing
8868 circuit or notice that one has failed. Instead, only tell the
8869 controller when we want to inform the user of overall success or
8870 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8872 - Don't warn when we're using a circuit that ends with a node
8873 excluded in ExcludeExitNodes, but the circuit is not used to access
8874 the outside world. This should help fix bug 1090. Bugfix on
8876 - Work around a small memory leak in some versions of OpenSSL that
8877 stopped the memory used by the hostname TLS extension from being
8881 - Add a "getinfo status/accepted-server-descriptor" controller
8882 command, which is the recommended way for controllers to learn
8883 whether our server descriptor has been successfully received by at
8884 least on directory authority. Un-recommend good-server-descriptor
8885 getinfo and status events until we have a better design for them.
8888 Changes in version 0.2.2.5-alpha - 2009-10-11
8889 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
8892 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
8894 o Directory authorities:
8895 - Temporarily (just for this release) move dizum to an alternate
8899 Changes in version 0.2.2.4-alpha - 2009-10-10
8900 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
8901 introduces a new unit test framework, shifts directry authority
8902 addresses around to reduce the impact from recent blocking events,
8903 and fixes a few smaller bugs.
8906 - Fix several more asserts in the circuit_build_times code, for
8907 example one that causes Tor to fail to start once we have
8908 accumulated 5000 build times in the state file. Bugfixes on
8909 0.2.2.2-alpha; fixes bug 1108.
8911 o New directory authorities:
8912 - Move moria1 and Tonga to alternate IP addresses.
8915 - Log SSL state transitions at debug level during handshake, and
8916 include SSL states in error messages. This may help debug future
8917 SSL handshake issues.
8918 - Add a new "Handshake" log domain for activities that happen
8919 during the TLS handshake.
8920 - Revert to the "June 3 2009" ip-to-country file. The September one
8921 seems to have removed most US IP addresses.
8922 - Directory authorities now reject Tor relays with versions less than
8923 0.1.2.14. This step cuts out four relays from the current network,
8924 none of which are very big.
8927 - Fix a couple of smaller issues with gathering statistics. Bugfixes
8929 - Fix two memory leaks in the error case of
8930 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
8931 - Don't count one-hop circuits when we're estimating how long it
8932 takes circuits to build on average. Otherwise we'll set our circuit
8933 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
8934 - Directory authorities no longer change their opinion of, or vote on,
8935 whether a router is Running, unless they have themselves been
8936 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
8939 o Code simplifications and refactoring:
8940 - Revise our unit tests to use the "tinytest" framework, so we
8941 can run tests in their own processes, have smarter setup/teardown
8942 code, and so on. The unit test code has moved to its own
8943 subdirectory, and has been split into multiple modules.
8946 Changes in version 0.2.2.3-alpha - 2009-09-23
8947 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
8950 - Fix an overzealous assert in our new circuit build timeout code.
8951 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
8954 - If the networkstatus consensus tells us that we should use a
8955 negative circuit package window, ignore it. Otherwise we'll
8956 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
8959 Changes in version 0.2.2.2-alpha - 2009-09-21
8960 Tor 0.2.2.2-alpha introduces our latest performance improvement for
8961 clients: Tor tracks the average time it takes to build a circuit, and
8962 avoids using circuits that take too long to build. For fast connections,
8963 this feature can cut your expected latency in half. For slow or flaky
8964 connections, it could ruin your Tor experience. Let us know if it does!
8967 - Tor now tracks how long it takes to build client-side circuits
8968 over time, and adapts its timeout to local network performance.
8969 Since a circuit that takes a long time to build will also provide
8970 bad performance, we get significant latency improvements by
8971 discarding the slowest 20% of circuits. Specifically, Tor creates
8972 circuits more aggressively than usual until it has enough data
8973 points for a good timeout estimate. Implements proposal 151.
8974 We are especially looking for reports (good and bad) from users with
8975 both EDGE and broadband connections that can move from broadband
8976 to EDGE and find out if the build-time data in the .tor/state gets
8977 reset without loss of Tor usability. You should also see a notice
8978 log message telling you that Tor has reset its timeout.
8979 - Directory authorities can now vote on arbitary integer values as
8980 part of the consensus process. This is designed to help set
8981 network-wide parameters. Implements proposal 167.
8982 - Tor now reads the "circwindow" parameter out of the consensus,
8983 and uses that value for its circuit package window rather than the
8984 default of 1000 cells. Begins the implementation of proposal 168.
8987 - Fix a remotely triggerable memory leak when a consensus document
8988 contains more than one signature from the same voter. Bugfix on
8992 - Fix an extremely rare infinite recursion bug that could occur if
8993 we tried to log a message after shutting down the log subsystem.
8994 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8995 - Fix parsing for memory or time units given without a space between
8996 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
8997 - A networkstatus vote must contain exactly one signature. Spec
8998 conformance issue. Bugfix on 0.2.0.3-alpha.
8999 - Fix an obscure bug where hidden services on 64-bit big-endian
9000 systems might mis-read the timestamp in v3 introduce cells, and
9001 refuse to connect back to the client. Discovered by "rotor".
9002 Bugfix on 0.2.1.6-alpha.
9003 - We were triggering a CLOCK_SKEW controller status event whenever
9004 we connect via the v2 connection protocol to any relay that has
9005 a wrong clock. Instead, we should only inform the controller when
9006 it's a trusted authority that claims our clock is wrong. Bugfix
9007 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9008 - We were telling the controller about CHECKING_REACHABILITY and
9009 REACHABILITY_FAILED status events whenever we launch a testing
9010 circuit or notice that one has failed. Instead, only tell the
9011 controller when we want to inform the user of overall success or
9012 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9014 - Don't warn when we're using a circuit that ends with a node
9015 excluded in ExcludeExitNodes, but the circuit is not used to access
9016 the outside world. This should help fix bug 1090, but more problems
9017 remain. Bugfix on 0.2.1.6-alpha.
9018 - Work around a small memory leak in some versions of OpenSSL that
9019 stopped the memory used by the hostname TLS extension from being
9021 - Make our 'torify' script more portable; if we have only one of
9022 'torsocks' or 'tsocks' installed, don't complain to the user;
9023 and explain our warning about tsocks better.
9026 - Add a "getinfo status/accepted-server-descriptor" controller
9027 command, which is the recommended way for controllers to learn
9028 whether our server descriptor has been successfully received by at
9029 least on directory authority. Un-recommend good-server-descriptor
9030 getinfo and status events until we have a better design for them.
9031 - Update to the "September 4 2009" ip-to-country file.
9034 Changes in version 0.2.2.1-alpha - 2009-08-26
9035 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
9036 Tor clients to bootstrap on networks where only port 80 is reachable,
9037 makes it more straightforward to support hardware crypto accelerators,
9038 and starts the groundwork for gathering stats safely at relays.
9041 - Start the process of disabling ".exit" address notation, since it
9042 can be used for a variety of esoteric application-level attacks
9043 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
9046 o New directory authorities:
9047 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9051 - New AccelName and AccelDir options add support for dynamic OpenSSL
9052 hardware crypto acceleration engines.
9053 - Tor now supports tunneling all of its outgoing connections over
9054 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
9055 configuration options. Code by Christopher Davis.
9058 - Send circuit or stream sendme cells when our window has decreased
9059 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9060 by Karsten when testing the "reduce circuit window" performance
9061 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9062 before the release of Tor 0.0.0. This is the new winner of the
9065 o New options for gathering stats safely:
9066 - Directory mirrors that set "DirReqStatistics 1" write statistics
9067 about directory requests to disk every 24 hours. As compared to the
9068 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
9069 1) stats are written to disk exactly every 24 hours; 2) estimated
9070 shares of v2 and v3 requests are determined as mean values, not at
9071 the end of a measurement period; 3) unresolved requests are listed
9072 with country code '??'; 4) directories also measure download times.
9073 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
9074 number of exit streams and transferred bytes per port to disk every
9076 - Relays that set "CellStatistics 1" write statistics on how long
9077 cells spend in their circuit queues to disk every 24 hours.
9078 - Entry nodes that set "EntryStatistics 1" write statistics on the
9079 rough number and origins of connecting clients to disk every 24
9081 - Relays that write any of the above statistics to disk and set
9082 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
9083 their extra-info documents.
9086 - New --digests command-line switch to output the digests of the
9087 source files Tor was built with.
9088 - The "torify" script now uses torsocks where available.
9089 - The memarea code now uses a sentinel value at the end of each area
9090 to make sure nothing writes beyond the end of an area. This might
9091 help debug some conceivable causes of bug 930.
9092 - Time and memory units in the configuration file can now be set to
9093 fractional units. For example, "2.5 GB" is now a valid value for
9095 - Certain Tor clients (such as those behind check.torproject.org) may
9096 want to fetch the consensus in an extra early manner. To enable this
9097 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
9098 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
9099 as only certain clients who must have this information sooner should
9101 - Instead of adding the svn revision to the Tor version string, report
9102 the git commit (when we're building from a git checkout).
9105 - If any of the v3 certs we download are unparseable, we should
9106 actually notice the failure so we don't retry indefinitely. Bugfix
9107 on 0.2.0.x; reported by "rotator".
9108 - If the cached cert file is unparseable, warn but don't exit.
9109 - Fix possible segmentation fault on directory authorities. Bugfix on
9111 - When Tor fails to parse a descriptor of any kind, dump it to disk.
9112 Might help diagnosing bug 1051.
9114 o Deprecated and removed features:
9115 - The controller no longer accepts the old obsolete "addr-mappings/"
9116 or "unregistered-servers-" GETINFO values.
9117 - Hidden services no longer publish version 0 descriptors, and clients
9118 do not request or use version 0 descriptors. However, the old hidden
9119 service authorities still accept and serve version 0 descriptors
9120 when contacted by older hidden services/clients.
9121 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
9122 always on; using them is necessary for correct forward-compatible
9124 - Remove support for .noconnect style addresses. Nobody was using
9125 them, and they provided another avenue for detecting Tor users
9126 via application-level web tricks.
9128 o Packaging changes:
9129 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
9130 installer bundles. See
9131 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
9132 for details of what's new in Vidalia 0.2.3.
9133 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
9134 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
9135 configuration file, rather than the old Privoxy.
9136 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
9137 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
9138 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
9139 better compatibility with OS X 10.6, aka Snow Leopard.
9140 - OS X Vidalia Bundle: The multi-package installer is now replaced
9141 by a simple drag and drop to the /Applications folder. This change
9142 occurred with the upgrade to Vidalia 0.2.3.
9145 Changes in version 0.2.1.19 - 2009-07-28
9146 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
9147 services on Tor 0.2.1.3-alpha through 0.2.1.18.
9150 - Make accessing hidden services on 0.2.1.x work right again.
9151 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
9152 part of patch provided by "optimist".
9155 - When a relay/bridge is writing out its identity key fingerprint to
9156 the "fingerprint" file and to its logs, write it without spaces. Now
9157 it will look like the fingerprints in our bridges documentation,
9158 and confuse fewer users.
9161 - Relays no longer publish a new server descriptor if they change
9162 their MaxAdvertisedBandwidth config option but it doesn't end up
9163 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
9164 fixes bug 1026. Patch from Sebastian.
9165 - Avoid leaking memory every time we get a create cell but we have
9166 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
9167 fixes bug 1034. Reported by BarkerJr.
9170 Changes in version 0.2.1.18 - 2009-07-24
9171 Tor 0.2.1.18 lays the foundations for performance improvements,
9172 adds status events to help users diagnose bootstrap problems, adds
9173 optional authentication/authorization for hidden services, fixes a
9174 variety of potential anonymity problems, and includes a huge pile of
9175 other features and bug fixes.
9178 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
9181 Changes in version 0.2.1.17-rc - 2009-07-07
9182 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
9183 candidate for the 0.2.1.x series. It lays the groundwork for further
9184 client performance improvements, and also fixes a big bug with directory
9185 authorities that were causing them to assign Guard and Stable flags
9188 The Windows bundles also finally include the geoip database that we
9189 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
9190 should actually install Torbutton rather than giving you a cryptic
9191 failure message (oops).
9194 - Clients now use the bandwidth values in the consensus, rather than
9195 the bandwidth values in each relay descriptor. This approach opens
9196 the door to more accurate bandwidth estimates once the directory
9197 authorities start doing active measurements. Implements more of
9201 - When Tor clients restart after 1-5 days, they discard all their
9202 cached descriptors as too old, but they still use the cached
9203 consensus document. This approach is good for robustness, but
9204 bad for performance: since they don't know any bandwidths, they
9205 end up choosing at random rather than weighting their choice by
9206 speed. Fixed by the above feature of putting bandwidths in the
9207 consensus. Bugfix on 0.2.0.x.
9208 - Directory authorities were neglecting to mark relays down in their
9209 internal histories if the relays fall off the routerlist without
9210 ever being found unreachable. So there were relays in the histories
9211 that haven't been seen for eight months, and are listed as being
9212 up for eight months. This wreaked havoc on the "median wfu"
9213 and "median mtbf" calculations, in turn making Guard and Stable
9214 flags very wrong, hurting network performance. Fixes bugs 696 and
9215 969. Bugfix on 0.2.0.6-alpha.
9218 - Serve the DirPortFrontPage page even when we have been approaching
9219 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
9220 - The control port would close the connection before flushing long
9221 replies, such as the network consensus, if a QUIT command was issued
9222 before the reply had completed. Now, the control port flushes all
9223 pending replies before closing the connection. Also fixed a spurious
9224 warning when a QUIT command is issued after a malformed or rejected
9225 AUTHENTICATE command, but before the connection was closed. Patch
9226 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
9227 - When we can't find an intro key for a v2 hidden service descriptor,
9228 fall back to the v0 hidden service descriptor and log a bug message.
9229 Workaround for bug 1024.
9230 - Fix a log message that did not respect the SafeLogging option.
9234 - If we're a relay and we change our IP address, be more verbose
9235 about the reason that made us change. Should help track down
9236 further bugs for relays on dynamic IP addresses.
9239 Changes in version 0.2.0.35 - 2009-06-24
9241 - Avoid crashing in the presence of certain malformed descriptors.
9242 Found by lark, and by automated fuzzing.
9243 - Fix an edge case where a malicious exit relay could convince a
9244 controller that the client's DNS question resolves to an internal IP
9245 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9248 - Finally fix the bug where dynamic-IP relays disappear when their
9249 IP address changes: directory mirrors were mistakenly telling
9250 them their old address if they asked via begin_dir, so they
9251 never got an accurate answer about their new address, so they
9252 just vanished after a day. For belt-and-suspenders, relays that
9253 don't set Address in their config now avoid using begin_dir for
9254 all direct connections. Should fix bugs 827, 883, and 900.
9255 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9256 that would occur on some exit nodes when DNS failures and timeouts
9257 occurred in certain patterns. Fix for bug 957.
9260 - When starting with a cache over a few days old, do not leak
9261 memory for the obsolete router descriptors in it. Bugfix on
9262 0.2.0.33; fixes bug 672.
9263 - Hidden service clients didn't use a cached service descriptor that
9264 was older than 15 minutes, but wouldn't fetch a new one either,
9265 because there was already one in the cache. Now, fetch a v2
9266 descriptor unless the same descriptor was added to the cache within
9267 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9270 Changes in version 0.2.1.16-rc - 2009-06-20
9271 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
9272 a bunch of minor bugs.
9275 - Fix an edge case where a malicious exit relay could convince a
9276 controller that the client's DNS question resolves to an internal IP
9277 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9279 o Major performance improvements (on 0.2.0.x):
9280 - Disable and refactor some debugging checks that forced a linear scan
9281 over the whole server-side DNS cache. These accounted for over 50%
9282 of CPU time on a relatively busy exit node's gprof profile. Found
9284 - Disable some debugging checks that appeared in exit node profile
9288 - Update to the "June 3 2009" ip-to-country file.
9289 - Do not have tor-resolve automatically refuse all .onion addresses;
9290 if AutomapHostsOnResolve is set in your torrc, this will work fine.
9292 o Minor bugfixes (on 0.2.0.x):
9293 - Log correct error messages for DNS-related network errors on
9295 - Fix a race condition that could cause crashes or memory corruption
9296 when running as a server with a controller listening for log
9298 - Avoid crashing when we have a policy specified in a DirPolicy or
9299 SocksPolicy or ReachableAddresses option with ports set on it,
9300 and we re-load the policy. May fix bug 996.
9301 - Hidden service clients didn't use a cached service descriptor that
9302 was older than 15 minutes, but wouldn't fetch a new one either,
9303 because there was already one in the cache. Now, fetch a v2
9304 descriptor unless the same descriptor was added to the cache within
9305 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9307 o Minor bugfixes (on 0.2.1.x):
9308 - Don't warn users about low port and hibernation mix when they
9309 provide a *ListenAddress directive to fix that. Bugfix on
9311 - When switching back and forth between bridge mode, do not start
9312 gathering GeoIP data until two hours have passed.
9313 - Do not complain that the user has requested an excluded node as
9314 an exit when the node is not really an exit. This could happen
9315 because the circuit was for testing, or an introduction point.
9319 Changes in version 0.2.1.15-rc - 2009-05-25
9320 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
9321 series. It fixes a major bug on fast exit relays, as well as a variety
9324 o Major bugfixes (on 0.2.0.x):
9325 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9326 that would occur on some exit nodes when DNS failures and timeouts
9327 occurred in certain patterns. Fix for bug 957.
9329 o Minor bugfixes (on 0.2.0.x):
9330 - Actually return -1 in the error case for read_bandwidth_usage().
9331 Harmless bug, since we currently don't care about the return value
9332 anywhere. Bugfix on 0.2.0.9-alpha.
9333 - Provide a more useful log message if bug 977 (related to buffer
9334 freelists) ever reappears, and do not crash right away.
9335 - Fix an assertion failure on 64-bit platforms when we allocated
9336 memory right up to the end of a memarea, then realigned the memory
9337 one step beyond the end. Fixes a possible cause of bug 930.
9338 - Protect the count of open sockets with a mutex, so we can't
9339 corrupt it when two threads are closing or opening sockets at once.
9340 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
9341 - Don't allow a bridge to publish its router descriptor to a
9342 non-bridge directory authority. Fixes part of bug 932.
9343 - When we change to or from being a bridge, reset our counts of
9344 client usage by country. Fixes bug 932.
9345 - Fix a bug that made stream bandwidth get misreported to the
9347 - Stop using malloc_usable_size() to use more area than we had
9348 actually allocated: it was safe, but made valgrind really unhappy.
9349 - Fix a memory leak when v3 directory authorities load their keys
9350 and cert from disk. Bugfix on 0.2.0.1-alpha.
9352 o Minor bugfixes (on 0.2.1.x):
9353 - Fix use of freed memory when deciding to mark a non-addable
9354 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
9357 Changes in version 0.2.1.14-rc - 2009-04-12
9358 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
9359 series. It begins fixing some major performance problems, and also
9360 finally addresses the bug that was causing relays on dynamic IP
9361 addresses to fall out of the directory.
9364 - Clients replace entry guards that were chosen more than a few months
9365 ago. This change should significantly improve client performance,
9366 especially once more people upgrade, since relays that have been
9367 a guard for a long time are currently overloaded.
9369 o Major bugfixes (on 0.2.0):
9370 - Finally fix the bug where dynamic-IP relays disappear when their
9371 IP address changes: directory mirrors were mistakenly telling
9372 them their old address if they asked via begin_dir, so they
9373 never got an accurate answer about their new address, so they
9374 just vanished after a day. For belt-and-suspenders, relays that
9375 don't set Address in their config now avoid using begin_dir for
9376 all direct connections. Should fix bugs 827, 883, and 900.
9377 - Relays were falling out of the networkstatus consensus for
9378 part of a day if they changed their local config but the
9379 authorities discarded their new descriptor as "not sufficiently
9380 different". Now directory authorities accept a descriptor as changed
9381 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
9383 - Avoid crashing in the presence of certain malformed descriptors.
9384 Found by lark, and by automated fuzzing.
9387 - When generating circuit events with verbose nicknames for
9388 controllers, try harder to look up nicknames for routers on a
9389 circuit. (Previously, we would look in the router descriptors we had
9390 for nicknames, but not in the consensus.) Partial fix for bug 941.
9391 - If the bridge config line doesn't specify a port, assume 443.
9392 This makes bridge lines a bit smaller and easier for users to
9394 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
9395 bytes (aka 20KB/s), to match our documentation. Also update
9396 directory authorities so they always assign the Fast flag to relays
9397 with 20KB/s of capacity. Now people running relays won't suddenly
9398 find themselves not seeing any use, if the network gets faster
9400 - Update to the "April 3 2009" ip-to-country file.
9403 - Avoid trying to print raw memory to the logs when we decide to
9404 give up on downloading a given relay descriptor. Bugfix on
9406 - In tor-resolve, when the Tor client to use is specified by
9407 <hostname>:<port>, actually use the specified port rather than
9408 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
9409 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
9410 - When starting with a cache over a few days old, do not leak
9411 memory for the obsolete router descriptors in it. Bugfix on
9413 - Avoid double-free on list of successfully uploaded hidden
9414 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
9415 - Change memarea_strndup() implementation to work even when
9416 duplicating a string at the end of a page. This bug was
9417 harmless for now, but could have meant crashes later. Fix by
9418 lark. Bugfix on 0.2.1.1-alpha.
9419 - Limit uploaded directory documents to be 16M rather than 500K.
9420 The directory authorities were refusing v3 consensus votes from
9421 other authorities, since the votes are now 504K. Fixes bug 959;
9422 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
9423 - Directory authorities should never send a 503 "busy" response to
9424 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
9428 Changes in version 0.2.1.13-alpha - 2009-03-09
9429 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
9430 cleanups. We're finally getting close to a release candidate.
9433 - Correctly update the list of which countries we exclude as
9434 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
9435 lark. Bugfix on 0.2.1.6-alpha.
9437 o Minor bugfixes (on 0.2.0.x and earlier):
9438 - Automatically detect MacOSX versions earlier than 10.4.0, and
9439 disable kqueue from inside Tor when running with these versions.
9440 We previously did this from the startup script, but that was no
9441 help to people who didn't use the startup script. Resolves bug 863.
9442 - When we had picked an exit node for a connection, but marked it as
9443 "optional", and it turned out we had no onion key for the exit,
9444 stop wanting that exit and try again. This situation may not
9445 be possible now, but will probably become feasible with proposal
9446 158. Spotted by rovv. Fixes another case of bug 752.
9447 - Clients no longer cache certificates for authorities they do not
9448 recognize. Bugfix on 0.2.0.9-alpha.
9449 - When we can't transmit a DNS request due to a network error, retry
9450 it after a while, and eventually transmit a failing response to
9451 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
9452 - If the controller claimed responsibility for a stream, but that
9453 stream never finished making its connection, it would live
9454 forever in circuit_wait state. Now we close it after SocksTimeout
9455 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
9456 - Drop begin cells to a hidden service if they come from the middle
9457 of a circuit. Patch from lark.
9458 - When we erroneously receive two EXTEND cells for the same circuit
9459 ID on the same connection, drop the second. Patch from lark.
9460 - Fix a crash that occurs on exit nodes when a nameserver request
9461 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
9462 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
9464 - Do not assume that a stack-allocated character array will be
9465 64-bit aligned on platforms that demand that uint64_t access is
9466 aligned. Possible fix for bug 604.
9467 - Parse dates and IPv4 addresses in a locale- and libc-independent
9468 manner, to avoid platform-dependent behavior on malformed input.
9469 - Build correctly when configured to build outside the main source
9470 path. Patch from Michael Gold.
9471 - We were already rejecting relay begin cells with destination port
9472 of 0. Now also reject extend cells with destination port or address
9473 of 0. Suggested by lark.
9475 o Minor bugfixes (on 0.2.1.x):
9476 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
9477 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
9478 - If we're an exit node, scrub the IP address to which we are exiting
9479 in the logs. Bugfix on 0.2.1.8-alpha.
9482 - On Linux, use the prctl call to re-enable core dumps when the user
9484 - New controller event NEWCONSENSUS that lists the networkstatus
9485 lines for every recommended relay. Now controllers like Torflow
9486 can keep up-to-date on which relays they should be using.
9487 - Update to the "February 26 2009" ip-to-country file.
9490 Changes in version 0.2.0.34 - 2009-02-08
9491 Tor 0.2.0.34 features several more security-related fixes. You should
9492 upgrade, especially if you run an exit relay (remote crash) or a
9493 directory authority (remote infinite loop), or you're on an older
9494 (pre-XP) or not-recently-patched Windows (remote exploit).
9496 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
9497 have many known flaws, and nobody should be using them. You should
9498 upgrade. If you're using a Linux or BSD and its packages are obsolete,
9499 stop using those packages and upgrade anyway.
9502 - Fix an infinite-loop bug on handling corrupt votes under certain
9503 circumstances. Bugfix on 0.2.0.8-alpha.
9504 - Fix a temporary DoS vulnerability that could be performed by
9505 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9506 - Avoid a potential crash on exit nodes when processing malformed
9507 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
9508 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9509 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9512 - Fix compilation on systems where time_t is a 64-bit integer.
9513 Patch from Matthias Drochner.
9514 - Don't consider expiring already-closed client connections. Fixes
9515 bug 893. Bugfix on 0.0.2pre20.
9518 Changes in version 0.2.1.12-alpha - 2009-02-08
9519 Tor 0.2.1.12-alpha features several more security-related fixes. You
9520 should upgrade, especially if you run an exit relay (remote crash) or
9521 a directory authority (remote infinite loop), or you're on an older
9522 (pre-XP) or not-recently-patched Windows (remote exploit). It also
9523 includes a big pile of minor bugfixes and cleanups.
9526 - Fix an infinite-loop bug on handling corrupt votes under certain
9527 circumstances. Bugfix on 0.2.0.8-alpha.
9528 - Fix a temporary DoS vulnerability that could be performed by
9529 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9530 - Avoid a potential crash on exit nodes when processing malformed
9531 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
9534 - Let controllers actually ask for the "clients_seen" event for
9535 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
9536 reported by Matt Edman.
9537 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
9539 - Fix a bug in address parsing that was preventing bridges or hidden
9540 service targets from being at IPv6 addresses.
9541 - Solve a bug that kept hardware crypto acceleration from getting
9542 enabled when accounting was turned on. Fixes bug 907. Bugfix on
9544 - Remove a bash-ism from configure.in to build properly on non-Linux
9545 platforms. Bugfix on 0.2.1.1-alpha.
9546 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
9547 headers. Bugfix on 0.2.0.10-alpha.
9548 - Don't consider expiring already-closed client connections. Fixes
9549 bug 893. Bugfix on 0.0.2pre20.
9550 - Fix another interesting corner-case of bug 891 spotted by rovv:
9551 Previously, if two hosts had different amounts of clock drift, and
9552 one of them created a new connection with just the wrong timing,
9553 the other might decide to deprecate the new connection erroneously.
9554 Bugfix on 0.1.1.13-alpha.
9555 - Resolve a very rare crash bug that could occur when the user forced
9556 a nameserver reconfiguration during the middle of a nameserver
9557 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
9558 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
9559 Bugfix on 0.2.1.7-alpha.
9560 - If we're using bridges and our network goes away, be more willing
9561 to forgive our bridges and try again when we get an application
9562 request. Bugfix on 0.2.0.x.
9565 - Support platforms where time_t is 64 bits long. (Congratulations,
9566 NetBSD!) Patch from Matthias Drochner.
9567 - Add a 'getinfo status/clients-seen' controller command, in case
9568 controllers want to hear clients_seen events but connect late.
9571 - Disable GCC's strict alias optimization by default, to avoid the
9572 likelihood of its introducing subtle bugs whenever our code violates
9573 the letter of C99's alias rules.
9576 Changes in version 0.2.0.33 - 2009-01-21
9577 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
9578 useful to users. It also finally fixes a bug where a relay or client
9579 that's been off for many days would take a long time to bootstrap.
9581 This update also fixes an important security-related bug reported by
9582 Ilja van Sprundel. You should upgrade. (We'll send out more details
9583 about the bug once people have had some time to upgrade.)
9586 - Fix a heap-corruption bug that may be remotely triggerable on
9587 some platforms. Reported by Ilja van Sprundel.
9590 - When a stream at an exit relay is in state "resolving" or
9591 "connecting" and it receives an "end" relay cell, the exit relay
9592 would silently ignore the end cell and not close the stream. If
9593 the client never closes the circuit, then the exit relay never
9594 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
9596 - When sending CREATED cells back for a given circuit, use a 64-bit
9597 connection ID to find the right connection, rather than an addr:port
9598 combination. Now that we can have multiple OR connections between
9599 the same ORs, it is no longer possible to use addr:port to uniquely
9600 identify a connection.
9601 - Bridge relays that had DirPort set to 0 would stop fetching
9602 descriptors shortly after startup, and then briefly resume
9603 after a new bandwidth test and/or after publishing a new bridge
9604 descriptor. Bridge users that try to bootstrap from them would
9605 get a recent networkstatus but would get descriptors from up to
9606 18 hours earlier, meaning most of the descriptors were obsolete
9607 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9608 - Prevent bridge relays from serving their 'extrainfo' document
9609 to anybody who asks, now that extrainfo docs include potentially
9610 sensitive aggregated client geoip summaries. Bugfix on
9612 - If the cached networkstatus consensus is more than five days old,
9613 discard it rather than trying to use it. In theory it could be
9614 useful because it lists alternate directory mirrors, but in practice
9615 it just means we spend many minutes trying directory mirrors that
9616 are long gone from the network. Also discard router descriptors as
9617 we load them if they are more than five days old, since the onion
9618 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
9621 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9622 could make gcc generate non-functional binary search code. Bugfix
9624 - Build correctly on platforms without socklen_t.
9625 - Compile without warnings on solaris.
9626 - Avoid potential crash on internal error during signature collection.
9627 Fixes bug 864. Patch from rovv.
9628 - Correct handling of possible malformed authority signing key
9629 certificates with internal signature types. Fixes bug 880.
9630 Bugfix on 0.2.0.3-alpha.
9631 - Fix a hard-to-trigger resource leak when logging credential status.
9633 - When we can't initialize DNS because the network is down, do not
9634 automatically stop Tor from starting. Instead, we retry failed
9635 dns_init() every 10 minutes, and change the exit policy to reject
9636 *:* until one succeeds. Fixes bug 691.
9637 - Use 64 bits instead of 32 bits for connection identifiers used with
9638 the controller protocol, to greatly reduce risk of identifier reuse.
9639 - When we're choosing an exit node for a circuit, and we have
9640 no pending streams, choose a good general exit rather than one that
9641 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9642 - Fix another case of assuming, when a specific exit is requested,
9643 that we know more than the user about what hosts it allows.
9644 Fixes one case of bug 752. Patch from rovv.
9645 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9646 seconds. Warn the user if lower values are given in the
9647 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9648 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9649 user if lower values are given in the configuration. Bugfix on
9650 0.1.1.17-rc. Patch by Sebastian.
9651 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
9652 the cache because we already had a v0 descriptor with the same ID.
9653 Bugfix on 0.2.0.18-alpha.
9654 - Fix a race condition when freeing keys shared between main thread
9655 and CPU workers that could result in a memory leak. Bugfix on
9656 0.1.0.1-rc. Fixes bug 889.
9657 - Send a valid END cell back when a client tries to connect to a
9658 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9659 840. Patch from rovv.
9660 - Check which hops rendezvous stream cells are associated with to
9661 prevent possible guess-the-streamid injection attacks from
9662 intermediate hops. Fixes another case of bug 446. Based on patch
9664 - If a broken client asks a non-exit router to connect somewhere,
9665 do not even do the DNS lookup before rejecting the connection.
9666 Fixes another case of bug 619. Patch from rovv.
9667 - When a relay gets a create cell it can't decrypt (e.g. because it's
9668 using the wrong onion key), we were dropping it and letting the
9669 client time out. Now actually answer with a destroy cell. Fixes
9670 bug 904. Bugfix on 0.0.2pre8.
9672 o Minor bugfixes (hidden services):
9673 - Do not throw away existing introduction points on SIGHUP. Bugfix on
9674 0.0.6pre1. Patch by Karsten. Fixes bug 874.
9677 - Report the case where all signatures in a detached set are rejected
9678 differently than the case where there is an error handling the
9680 - When we realize that another process has modified our cached
9681 descriptors, print out a more useful error message rather than
9682 triggering an assertion. Fixes bug 885. Patch from Karsten.
9683 - Implement the 0x20 hack to better resist DNS poisoning: set the
9684 case on outgoing DNS requests randomly, and reject responses that do
9685 not match the case correctly. This logic can be disabled with the
9686 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
9687 of servers that do not reliably preserve case in replies. See
9688 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9690 - Check DNS replies for more matching fields to better resist DNS
9692 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9693 compress cells, which are basically all encrypted, compressed, or
9697 Changes in version 0.2.1.11-alpha - 2009-01-20
9698 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
9699 week it will take a long time to bootstrap again" bug. It also fixes
9700 an important security-related bug reported by Ilja van Sprundel. You
9701 should upgrade. (We'll send out more details about the bug once people
9702 have had some time to upgrade.)
9705 - Fix a heap-corruption bug that may be remotely triggerable on
9706 some platforms. Reported by Ilja van Sprundel.
9709 - Discard router descriptors as we load them if they are more than
9710 five days old. Otherwise if Tor is off for a long time and then
9711 starts with cached descriptors, it will try to use the onion
9712 keys in those obsolete descriptors when building circuits. Bugfix
9713 on 0.2.0.x. Fixes bug 887.
9716 - Try to make sure that the version of Libevent we're running with
9717 is binary-compatible with the one we built with. May address bug
9719 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
9720 for bug 905. Bugfix on 0.2.1.7-alpha.
9721 - Add a new --enable-local-appdata configuration switch to change
9722 the default location of the datadir on win32 from APPDATA to
9723 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
9724 entirely. Patch from coderman.
9727 - Make outbound DNS packets respect the OutboundBindAddress setting.
9728 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
9729 - When our circuit fails at the first hop (e.g. we get a destroy
9730 cell back), avoid using that OR connection anymore, and also
9731 tell all the one-hop directory requests waiting for it that they
9732 should fail. Bugfix on 0.2.1.3-alpha.
9733 - In the torify(1) manpage, mention that tsocks will leak your
9737 Changes in version 0.2.1.10-alpha - 2009-01-06
9738 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
9739 would make the bridge relay not so useful if it had DirPort set to 0,
9740 and one that could let an attacker learn a little bit of information
9741 about the bridge's users), and a bug that would cause your Tor relay
9742 to ignore a circuit create request it can't decrypt (rather than reply
9743 with an error). It also fixes a wide variety of other bugs.
9746 - If the cached networkstatus consensus is more than five days old,
9747 discard it rather than trying to use it. In theory it could
9748 be useful because it lists alternate directory mirrors, but in
9749 practice it just means we spend many minutes trying directory
9750 mirrors that are long gone from the network. Helps bug 887 a bit;
9752 - Bridge relays that had DirPort set to 0 would stop fetching
9753 descriptors shortly after startup, and then briefly resume
9754 after a new bandwidth test and/or after publishing a new bridge
9755 descriptor. Bridge users that try to bootstrap from them would
9756 get a recent networkstatus but would get descriptors from up to
9757 18 hours earlier, meaning most of the descriptors were obsolete
9758 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9759 - Prevent bridge relays from serving their 'extrainfo' document
9760 to anybody who asks, now that extrainfo docs include potentially
9761 sensitive aggregated client geoip summaries. Bugfix on
9765 - New controller event "clients_seen" to report a geoip-based summary
9766 of which countries we've seen clients from recently. Now controllers
9767 like Vidalia can show bridge operators that they're actually making
9769 - Build correctly against versions of OpenSSL 0.9.8 or later built
9770 without support for deprecated functions.
9771 - Update to the "December 19 2008" ip-to-country file.
9773 o Minor bugfixes (on 0.2.0.x):
9774 - Authorities now vote for the Stable flag for any router whose
9775 weighted MTBF is at least 5 days, regardless of the mean MTBF.
9776 - Do not remove routers as too old if we do not have any consensus
9777 document. Bugfix on 0.2.0.7-alpha.
9778 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9779 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9780 - When an exit relay resolves a stream address to a local IP address,
9781 do not just keep retrying that same exit relay over and
9782 over. Instead, just close the stream. Addresses bug 872. Bugfix
9783 on 0.2.0.32. Patch from rovv.
9784 - If a hidden service sends us an END cell, do not consider
9785 retrying the connection; just close it. Patch from rovv.
9786 - When we made bridge authorities stop serving bridge descriptors over
9787 unencrypted links, we also broke DirPort reachability testing for
9788 bridges. So bridges with a non-zero DirPort were printing spurious
9789 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
9790 - When a relay gets a create cell it can't decrypt (e.g. because it's
9791 using the wrong onion key), we were dropping it and letting the
9792 client time out. Now actually answer with a destroy cell. Fixes
9793 bug 904. Bugfix on 0.0.2pre8.
9794 - Squeeze 2-5% out of client performance (according to oprofile) by
9795 improving the implementation of some policy-manipulation functions.
9797 o Minor bugfixes (on 0.2.1.x):
9798 - Make get_interface_address() function work properly again; stop
9799 guessing the wrong parts of our address as our address.
9800 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
9801 send on that circuit. Otherwise we might violate the proposal-110
9802 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
9804 - When we're sending non-EXTEND cells to the first hop in a circuit,
9805 for example to use an encrypted directory connection, we don't need
9806 to use RELAY_EARLY cells: the first hop knows what kind of cell
9807 it is, and nobody else can even see the cell type. Conserving
9808 RELAY_EARLY cells makes it easier to cannibalize circuits like
9810 - Stop logging nameserver addresses in reverse order.
9811 - If we are retrying a directory download slowly over and over, do
9812 not automatically give up after the 254th failure. Bugfix on
9814 - Resume reporting accurate "stream end" reasons to the local control
9815 port. They were lost in the changes for Proposal 148. Bugfix on
9818 o Deprecated and removed features:
9819 - The old "tor --version --version" command, which would print out
9820 the subversion "Id" of most of the source files, is now removed. It
9821 turned out to be less useful than we'd expected, and harder to
9824 o Code simplifications and refactoring:
9825 - Change our header file guard macros to be less likely to conflict
9826 with system headers. Adam Langley noticed that we were conflicting
9827 with log.h on Android.
9828 - Tool-assisted documentation cleanup. Nearly every function or
9829 static variable in Tor should have its own documentation now.
9832 Changes in version 0.2.1.9-alpha - 2008-12-25
9833 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
9835 o New directory authorities:
9836 - gabelmoo (the authority run by Karsten Loesing) now has a new
9840 - Never use a connection with a mismatched address to extend a
9841 circuit, unless that connection is canonical. A canonical
9842 connection is one whose address is authenticated by the router's
9843 identity key, either in a NETINFO cell or in a router descriptor.
9844 - Avoid a possible memory corruption bug when receiving hidden service
9845 descriptors. Bugfix on 0.2.1.6-alpha.
9848 - Fix a logic error that would automatically reject all but the first
9849 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
9850 part of bug 813/868. Bug spotted by coderman.
9851 - When a stream at an exit relay is in state "resolving" or
9852 "connecting" and it receives an "end" relay cell, the exit relay
9853 would silently ignore the end cell and not close the stream. If
9854 the client never closes the circuit, then the exit relay never
9855 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
9857 - When we can't initialize DNS because the network is down, do not
9858 automatically stop Tor from starting. Instead, retry failed
9859 dns_init() every 10 minutes, and change the exit policy to reject
9860 *:* until one succeeds. Fixes bug 691.
9863 - Give a better error message when an overzealous init script says
9864 "sudo -u username tor --user username". Makes Bug 882 easier for
9866 - When a directory authority gives us a new guess for our IP address,
9867 log which authority we used. Hopefully this will help us debug
9868 the recent complaints about bad IP address guesses.
9869 - Detect svn revision properly when we're using git-svn.
9870 - Try not to open more than one descriptor-downloading connection
9871 to an authority at once. This should reduce load on directory
9872 authorities. Fixes bug 366.
9873 - Add cross-certification to newly generated certificates, so that
9874 a signing key is enough information to look up a certificate.
9875 Partial implementation of proposal 157.
9876 - Start serving certificates by <identity digest, signing key digest>
9877 pairs. Partial implementation of proposal 157.
9878 - Clients now never report any stream end reason except 'MISC'.
9879 Implements proposal 148.
9880 - On platforms with a maximum syslog string length, truncate syslog
9881 messages to that length ourselves, rather than relying on the
9882 system to do it for us.
9883 - Optimize out calls to time(NULL) that occur for every IO operation,
9884 or for every cell. On systems where time() is a slow syscall,
9885 this fix will be slightly helpful.
9886 - Exit servers can now answer resolve requests for ip6.arpa addresses.
9887 - When we download a descriptor that we then immediately (as
9888 a directory authority) reject, do not retry downloading it right
9889 away. Should save some bandwidth on authorities. Fix for bug
9890 888. Patch by Sebastian Hahn.
9891 - When a download gets us zero good descriptors, do not notify
9892 Tor that new directory information has arrived.
9893 - Avoid some nasty corner cases in the logic for marking connections
9894 as too old or obsolete or noncanonical for circuits. Partial
9897 o Minor features (controller):
9898 - New CONSENSUS_ARRIVED event to note when a new consensus has
9899 been fetched and validated.
9900 - When we realize that another process has modified our cached
9901 descriptors file, print out a more useful error message rather
9902 than triggering an assertion. Fixes bug 885. Patch from Karsten.
9903 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
9904 controllers to prevent SIGHUP from reloading the
9905 configuration. Fixes bug 856.
9908 - Resume using the correct "REASON=" stream when telling the
9909 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
9910 - When a canonical connection appears later in our internal list
9911 than a noncanonical one for a given OR ID, always use the
9912 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
9914 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9915 seconds. Warn the user if lower values are given in the
9916 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9917 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9918 user if lower values are given in the configuration. Bugfix on
9919 0.1.1.17-rc. Patch by Sebastian.
9920 - Fix a race condition when freeing keys shared between main thread
9921 and CPU workers that could result in a memory leak. Bugfix on
9922 0.1.0.1-rc. Fixes bug 889.
9924 o Minor bugfixes (hidden services):
9925 - Do not throw away existing introduction points on SIGHUP (bugfix on
9926 0.0.6pre1); also, do not stall hidden services because we're
9927 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
9928 by John Brooks. Patch by Karsten. Fixes bug 874.
9929 - Fix a memory leak when we decline to add a v2 rendezvous
9930 descriptor to the cache because we already had a v0 descriptor
9931 with the same ID. Bugfix on 0.2.0.18-alpha.
9933 o Deprecated and removed features:
9934 - RedirectExits has been removed. It was deprecated since
9936 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
9937 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
9938 - Cell pools are now always enabled; --disable-cell-pools is ignored.
9940 o Code simplifications and refactoring:
9941 - Rename the confusing or_is_obsolete field to the more appropriate
9942 is_bad_for_new_circs, and move it to or_connection_t where it
9944 - Move edge-only flags from connection_t to edge_connection_t: not
9945 only is this better coding, but on machines of plausible alignment,
9946 it should save 4-8 bytes per connection_t. "Every little bit helps."
9947 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
9948 for consistency; keep old option working for backward compatibility.
9949 - Simplify the code for finding connections to use for a circuit.
9952 Changes in version 0.2.1.8-alpha - 2008-12-08
9953 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
9954 builds better on unusual platforms like Solaris and old OS X, and
9955 fixes a variety of other issues.
9958 - New DirPortFrontPage option that takes an html file and publishes
9959 it as "/" on the DirPort. Now relay operators can provide a
9960 disclaimer without needing to set up a separate webserver. There's
9961 a sample disclaimer in contrib/tor-exit-notice.html.
9964 - When the client is choosing entry guards, now it selects at most
9965 one guard from a given relay family. Otherwise we could end up with
9966 all of our entry points into the network run by the same operator.
9967 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
9970 - Fix a DOS opportunity during the voting signature collection process
9971 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9972 - Fix a possible segfault when establishing an exit connection. Bugfix
9976 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
9978 - Made Tor a little less aggressive about deleting expired
9979 certificates. Partial fix for bug 854.
9980 - Stop doing unaligned memory access that generated bus errors on
9981 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
9982 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
9983 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
9984 - Make USR2 log-level switch take effect immediately. Bugfix on
9986 - If one win32 nameserver fails to get added, continue adding the
9987 rest, and don't automatically fail.
9988 - Use fcntl() for locking when flock() is not available. Should fix
9989 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
9990 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9991 could make gcc generate non-functional binary search code. Bugfix
9993 - Build correctly on platforms without socklen_t.
9994 - Avoid potential crash on internal error during signature collection.
9995 Fixes bug 864. Patch from rovv.
9996 - Do not use C's stdio library for writing to log files. This will
9997 improve logging performance by a minute amount, and will stop
9998 leaking fds when our disk is full. Fixes bug 861.
9999 - Stop erroneous use of O_APPEND in cases where we did not in fact
10000 want to re-seek to the end of a file before every last write().
10001 - Correct handling of possible malformed authority signing key
10002 certificates with internal signature types. Fixes bug 880. Bugfix
10004 - Fix a hard-to-trigger resource leak when logging credential status.
10008 - Directory mirrors no longer fetch the v1 directory or
10009 running-routers files. They are obsolete, and nobody asks for them
10010 anymore. This is the first step to making v1 authorities obsolete.
10012 o Minor features (controller):
10013 - Return circuit purposes in response to GETINFO circuit-status. Fixes
10017 Changes in version 0.2.0.32 - 2008-11-20
10018 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
10019 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10020 a smaller security flaw that might allow an attacker to access local
10021 services, further improves hidden service performance, and fixes a
10022 variety of other issues.
10025 - The "User" and "Group" config options did not clear the
10026 supplementary group entries for the Tor process. The "User" option
10027 is now more robust, and we now set the groups to the specified
10028 user's primary group. The "Group" option is now ignored. For more
10029 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10030 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10031 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
10032 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10033 consistently obeyed: if an exit relay refuses a stream because its
10034 exit policy doesn't allow it, we would remember what IP address
10035 the relay said the destination address resolves to, even if it's
10036 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10039 - Fix a DOS opportunity during the voting signature collection process
10040 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
10042 o Major bugfixes (hidden services):
10043 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10044 we were failing the whole hidden service request when the v0
10045 descriptor fetch fails, even if the v2 fetch is still pending and
10046 might succeed. Similarly, if the last v2 fetch fails, we were
10047 failing the whole hidden service request even if a v0 fetch is
10048 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10049 - When extending a circuit to a hidden service directory to upload a
10050 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10051 requests failed, because the router descriptor has not been
10052 downloaded yet. In these cases, do not attempt to upload the
10053 rendezvous descriptor, but wait until the router descriptor is
10054 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
10055 descriptor from a hidden service directory for which the router
10056 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
10060 - Fix several infrequent memory leaks spotted by Coverity.
10061 - When testing for libevent functions, set the LDFLAGS variable
10062 correctly. Found by Riastradh.
10063 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10064 bootstrapping with tunneled directory connections. Bugfix on
10065 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10066 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10067 and we know that server B rejects most-but-not all connections to
10068 port 80, we would previously reject the connection. Now, we assume
10069 the user knows what they were asking for. Fixes bug 752. Bugfix
10070 on 0.0.9rc5. Diagnosed by BarkerJr.
10071 - If we overrun our per-second write limits a little, count this as
10072 having used up our write allocation for the second, and choke
10073 outgoing directory writes. Previously, we had only counted this when
10074 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
10075 Bugfix on 0.2.0.x (??).
10076 - Remove the old v2 directory authority 'lefkada' from the default
10077 list. It has been gone for many months.
10078 - Stop doing unaligned memory access that generated bus errors on
10079 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
10080 - Make USR2 log-level switch take effect immediately. Bugfix on
10083 o Minor bugfixes (controller):
10084 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
10085 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
10088 Changes in version 0.2.1.7-alpha - 2008-11-08
10089 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
10090 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10091 a smaller security flaw that might allow an attacker to access local
10092 services, adds better defense against DNS poisoning attacks on exit
10093 relays, further improves hidden service performance, and fixes a
10094 variety of other issues.
10097 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10098 consistently obeyed: if an exit relay refuses a stream because its
10099 exit policy doesn't allow it, we would remember what IP address
10100 the relay said the destination address resolves to, even if it's
10101 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10102 - The "User" and "Group" config options did not clear the
10103 supplementary group entries for the Tor process. The "User" option
10104 is now more robust, and we now set the groups to the specified
10105 user's primary group. The "Group" option is now ignored. For more
10106 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10107 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10108 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
10109 - Do not use or believe expired v3 authority certificates. Patch
10110 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
10113 - Now NodeFamily and MyFamily config options allow spaces in
10114 identity fingerprints, so it's easier to paste them in.
10115 Suggested by Lucky Green.
10116 - Implement the 0x20 hack to better resist DNS poisoning: set the
10117 case on outgoing DNS requests randomly, and reject responses that do
10118 not match the case correctly. This logic can be disabled with the
10119 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
10120 of servers that do not reliably preserve case in replies. See
10121 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10123 - Preserve case in replies to DNSPort requests in order to support
10124 the 0x20 hack for resisting DNS poisoning attacks.
10126 o Hidden service performance improvements:
10127 - When the client launches an introduction circuit, retry with a
10128 new circuit after 30 seconds rather than 60 seconds.
10129 - Launch a second client-side introduction circuit in parallel
10130 after a delay of 15 seconds (based on work by Christian Wilms).
10131 - Hidden services start out building five intro circuits rather
10132 than three, and when the first three finish they publish a service
10133 descriptor using those. Now we publish our service descriptor much
10134 faster after restart.
10137 - Minor fix in the warning messages when you're having problems
10138 bootstrapping; also, be more forgiving of bootstrap problems when
10139 we're still making incremental progress on a given bootstrap phase.
10140 - When we're choosing an exit node for a circuit, and we have
10141 no pending streams, choose a good general exit rather than one that
10142 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10143 - Send a valid END cell back when a client tries to connect to a
10144 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10145 840. Patch from rovv.
10146 - If a broken client asks a non-exit router to connect somewhere,
10147 do not even do the DNS lookup before rejecting the connection.
10148 Fixes another case of bug 619. Patch from rovv.
10149 - Fix another case of assuming, when a specific exit is requested,
10150 that we know more than the user about what hosts it allows.
10151 Fixes another case of bug 752. Patch from rovv.
10152 - Check which hops rendezvous stream cells are associated with to
10153 prevent possible guess-the-streamid injection attacks from
10154 intermediate hops. Fixes another case of bug 446. Based on patch
10156 - Avoid using a negative right-shift when comparing 32-bit
10157 addresses. Possible fix for bug 845 and bug 811.
10158 - Make the assert_circuit_ok() function work correctly on circuits that
10159 have already been marked for close.
10160 - Fix read-off-the-end-of-string error in unit tests when decoding
10161 introduction points.
10162 - Fix uninitialized size field for memory area allocation: may improve
10163 memory performance during directory parsing.
10164 - Treat duplicate certificate fetches as failures, so that we do
10165 not try to re-fetch an expired certificate over and over and over.
10166 - Do not say we're fetching a certificate when we'll in fact skip it
10167 because of a pending download.
10170 Changes in version 0.2.1.6-alpha - 2008-09-30
10171 Tor 0.2.1.6-alpha further improves performance and robustness of
10172 hidden services, starts work on supporting per-country relay selection,
10173 and fixes a variety of smaller issues.
10176 - Implement proposal 121: make it possible to build hidden services
10177 that only certain clients are allowed to connect to. This is
10178 enforced at several points, so that unauthorized clients are unable
10179 to send INTRODUCE cells to the service, or even (depending on the
10180 type of authentication) to learn introduction points. This feature
10181 raises the bar for certain kinds of active attacks against hidden
10182 services. Code by Karsten Loesing.
10183 - Relays now store and serve v2 hidden service descriptors by default,
10184 i.e., the new default value for HidServDirectoryV2 is 1. This is
10185 the last step in proposal 114, which aims to make hidden service
10186 lookups more reliable.
10187 - Start work to allow node restrictions to include country codes. The
10188 syntax to exclude nodes in a country with country code XX is
10189 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
10190 refinement to decide what config options should take priority if
10191 you ask to both use a particular node and exclude it.
10192 - Allow ExitNodes list to include IP ranges and country codes, just
10193 like the Exclude*Nodes lists. Patch from Robert Hogan.
10196 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
10197 Tor to fail to start if you had it configured to use a bridge
10198 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
10199 - When extending a circuit to a hidden service directory to upload a
10200 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10201 requests failed, because the router descriptor had not been
10202 downloaded yet. In these cases, we now wait until the router
10203 descriptor is downloaded, and then retry. Likewise, clients
10204 now skip over a hidden service directory if they don't yet have
10205 its router descriptor, rather than futilely requesting it and
10206 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
10208 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10209 we were failing the whole hidden service request when the v0
10210 descriptor fetch fails, even if the v2 fetch is still pending and
10211 might succeed. Similarly, if the last v2 fetch fails, we were
10212 failing the whole hidden service request even if a v0 fetch is
10213 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10214 - DNS replies need to have names matching their requests, but
10215 these names should be in the questions section, not necessarily
10216 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
10219 - Update to the "September 1 2008" ip-to-country file.
10220 - Allow ports 465 and 587 in the default exit policy again. We had
10221 rejected them in 0.1.0.15, because back in 2005 they were commonly
10222 misconfigured and ended up as spam targets. We hear they are better
10223 locked down these days.
10224 - Use a lockfile to make sure that two Tor processes are not
10225 simultaneously running with the same datadir.
10226 - Serve the latest v3 networkstatus consensus via the control
10227 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
10228 - Better logging about stability/reliability calculations on directory
10230 - Drop the requirement to have an open dir port for storing and
10231 serving v2 hidden service descriptors.
10232 - Directory authorities now serve a /tor/dbg-stability.txt URL to
10233 help debug WFU and MTBF calculations.
10234 - Implement most of Proposal 152: allow specialized servers to permit
10235 single-hop circuits, and clients to use those servers to build
10236 single-hop circuits when using a specialized controller. Patch
10237 from Josh Albrecht. Resolves feature request 768.
10238 - Add a -p option to tor-resolve for specifying the SOCKS port: some
10239 people find host:port too confusing.
10240 - Make TrackHostExit mappings expire a while after their last use, not
10241 after their creation. Patch from Robert Hogan.
10242 - Provide circuit purposes along with circuit events to the controller.
10245 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
10247 - Fixed some memory leaks -- some quite frequent, some almost
10248 impossible to trigger -- based on results from Coverity.
10249 - When testing for libevent functions, set the LDFLAGS variable
10250 correctly. Found by Riastradh.
10251 - Fix an assertion bug in parsing policy-related options; possible fix
10253 - Catch and report a few more bootstrapping failure cases when Tor
10254 fails to establish a TCP connection. Cleanup on 0.2.1.x.
10255 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10256 bootstrapping with tunneled directory connections. Bugfix on
10257 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10258 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10259 and we know that server B rejects most-but-not all connections to
10260 port 80, we would previously reject the connection. Now, we assume
10261 the user knows what they were asking for. Fixes bug 752. Bugfix
10262 on 0.0.9rc5. Diagnosed by BarkerJr.
10263 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
10264 service directories if they have no advertised dir port. Bugfix
10266 - If we overrun our per-second write limits a little, count this as
10267 having used up our write allocation for the second, and choke
10268 outgoing directory writes. Previously, we had only counted this when
10269 we had met our limits precisely. Fixes bug 824. Patch by rovv.
10270 Bugfix on 0.2.0.x (??).
10271 - Avoid a "0 divided by 0" calculation when calculating router uptime
10272 at directory authorities. Bugfix on 0.2.0.8-alpha.
10273 - Make DNS resolved controller events into "CLOSED", not
10274 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
10276 - Fix a bug where an unreachable relay would establish enough
10277 reachability testing circuits to do a bandwidth test -- if
10278 we already have a connection to the middle hop of the testing
10279 circuit, then it could establish the last hop by using the existing
10280 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
10281 circuits no longer use entry guards in 0.2.1.3-alpha.
10282 - If we have correct permissions on $datadir, we complain to stdout
10283 and fail to start. But dangerous permissions on
10284 $datadir/cached-status/ would cause us to open a log and complain
10285 there. Now complain to stdout and fail to start in both cases. Fixes
10286 bug 820, reported by seeess.
10287 - Remove the old v2 directory authority 'lefkada' from the default
10288 list. It has been gone for many months.
10290 o Code simplifications and refactoring:
10291 - Revise the connection_new functions so that a more typesafe variant
10292 exists. This will work better with Coverity, and let us find any
10293 actual mistakes we're making here.
10294 - Refactor unit testing logic so that dmalloc can be used sensibly
10295 with unit tests to check for memory leaks.
10296 - Move all hidden-service related fields from connection and circuit
10297 structure to substructures: this way they won't eat so much memory.
10300 Changes in version 0.2.0.31 - 2008-09-03
10301 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10302 a big bug we're seeing where in rare cases traffic from one Tor stream
10303 gets mixed into another stream, and fixes a variety of smaller issues.
10306 - Make sure that two circuits can never exist on the same connection
10307 with the same circuit ID, even if one is marked for close. This
10308 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10309 - Relays now reject risky extend cells: if the extend cell includes
10310 a digest of all zeroes, or asks to extend back to the relay that
10311 sent the extend cell, tear down the circuit. Ideas suggested
10313 - If not enough of our entry guards are available so we add a new
10314 one, we might use the new one even if it overlapped with the
10315 current circuit's exit relay (or its family). Anonymity bugfix
10316 pointed out by rovv.
10319 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10320 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10321 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10322 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10323 - Pick size of default geoip filename string correctly on windows.
10324 Fixes bug 806. Bugfix on 0.2.0.30.
10325 - Make the autoconf script accept the obsolete --with-ssl-dir
10326 option as an alias for the actually-working --with-openssl-dir
10327 option. Fix the help documentation to recommend --with-openssl-dir.
10328 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10329 - When using the TransPort option on OpenBSD, and using the User
10330 option to change UID and drop privileges, make sure to open
10331 /dev/pf before dropping privileges. Fixes bug 782. Patch from
10332 Christopher Davis. Bugfix on 0.1.2.1-alpha.
10333 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10334 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10335 on the client side when connecting to a hidden service. Bugfix
10336 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10337 - When closing an application-side connection because its circuit is
10338 getting torn down, generate the stream event correctly. Bugfix on
10339 0.1.2.x. Anonymous patch.
10342 Changes in version 0.2.1.5-alpha - 2008-08-31
10343 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
10344 in a lot of the infrastructure for adding authorization to hidden
10345 services, lays the groundwork for having clients read their load
10346 balancing information out of the networkstatus consensus rather than
10347 the individual router descriptors, addresses two potential anonymity
10348 issues, and fixes a variety of smaller issues.
10351 - Convert many internal address representations to optionally hold
10353 - Generate and accept IPv6 addresses in many protocol elements.
10354 - Make resolver code handle nameservers located at ipv6 addresses.
10355 - Begin implementation of proposal 121 ("Client authorization for
10356 hidden services"): configure hidden services with client
10357 authorization, publish descriptors for them, and configure
10358 authorization data for hidden services at clients. The next
10359 step is to actually access hidden services that perform client
10361 - More progress toward proposal 141: Network status consensus
10362 documents and votes now contain bandwidth information for each
10363 router and a summary of that router's exit policy. Eventually this
10364 will be used by clients so that they do not have to download every
10365 known descriptor before building circuits.
10367 o Major bugfixes (on 0.2.0.x and before):
10368 - When sending CREATED cells back for a given circuit, use a 64-bit
10369 connection ID to find the right connection, rather than an addr:port
10370 combination. Now that we can have multiple OR connections between
10371 the same ORs, it is no longer possible to use addr:port to uniquely
10372 identify a connection.
10373 - Relays now reject risky extend cells: if the extend cell includes
10374 a digest of all zeroes, or asks to extend back to the relay that
10375 sent the extend cell, tear down the circuit. Ideas suggested
10377 - If not enough of our entry guards are available so we add a new
10378 one, we might use the new one even if it overlapped with the
10379 current circuit's exit relay (or its family). Anonymity bugfix
10380 pointed out by rovv.
10383 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10384 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10385 - When using the TransPort option on OpenBSD, and using the User
10386 option to change UID and drop privileges, make sure to open /dev/pf
10387 before dropping privileges. Fixes bug 782. Patch from Christopher
10388 Davis. Bugfix on 0.1.2.1-alpha.
10389 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10390 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10391 - Add a missing safe_str() call for a debug log message.
10392 - Use 64 bits instead of 32 bits for connection identifiers used with
10393 the controller protocol, to greatly reduce risk of identifier reuse.
10394 - Make the autoconf script accept the obsolete --with-ssl-dir
10395 option as an alias for the actually-working --with-openssl-dir
10396 option. Fix the help documentation to recommend --with-openssl-dir.
10397 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10400 - Rate-limit too-many-sockets messages: when they happen, they happen
10401 a lot. Resolves bug 748.
10402 - Resist DNS poisoning a little better by making sure that names in
10403 answer sections match.
10404 - Print the SOCKS5 error message string as well as the error code
10405 when a tor-resolve request fails. Patch from Jacob.
10408 Changes in version 0.2.1.4-alpha - 2008-08-04
10409 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
10412 - The address part of exit policies was not correctly written
10413 to router descriptors. This generated router descriptors that failed
10414 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
10416 - Tor triggered a false assert when extending a circuit to a relay
10417 but we already have a connection open to that relay. Noticed by
10418 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
10421 - Fix a hidden service logging bug: in some edge cases, the router
10422 descriptor of a previously picked introduction point becomes
10423 obsolete and we need to give up on it rather than continually
10424 complaining that it has become obsolete. Observed by xiando. Bugfix
10427 o Removed features:
10428 - Take out the TestVia config option, since it was a workaround for
10429 a bug that was fixed in Tor 0.1.1.21.
10432 Changes in version 0.2.1.3-alpha - 2008-08-03
10433 Tor 0.2.1.3-alpha implements most of the pieces to prevent
10434 infinite-length circuit attacks (see proposal 110); fixes a bug that
10435 might cause exit relays to corrupt streams they send back; allows
10436 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
10437 ExcludeExitNodes config options; and fixes a big pile of bugs.
10439 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
10440 - Send a bootstrap problem "warn" event on the first problem if the
10441 reason is NO_ROUTE (that is, our network is down).
10444 - Implement most of proposal 110: The first K cells to be sent
10445 along a circuit are marked as special "early" cells; only K "early"
10446 cells will be allowed. Once this code is universal, we can block
10447 certain kinds of DOS attack by requiring that EXTEND commands must
10448 be sent using an "early" cell.
10451 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10452 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10453 on the client side when connecting to a hidden service. Bugfix
10454 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10455 - Ensure that two circuits can never exist on the same connection
10456 with the same circuit ID, even if one is marked for close. This
10457 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
10460 - When relays do their initial bandwidth measurement, don't limit
10461 to just our entry guards for the test circuits. Otherwise we tend
10462 to have multiple test circuits going through a single entry guard,
10463 which makes our bandwidth test less accurate. Fixes part of bug 654;
10464 patch contributed by Josh Albrecht.
10465 - Add an ExcludeExitNodes option so users can list a set of nodes
10466 that should be be excluded from the exit node position, but
10467 allowed elsewhere. Implements proposal 151.
10468 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
10469 ExcludeNodes and ExcludeExitNodes lists.
10470 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
10471 be more efficient. Formerly it was quadratic in the number of
10472 servers; now it should be linear. Fixes bug 509.
10473 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
10474 and n_conn_id_digest fields into a separate structure that's
10475 only needed when the circuit has not yet attached to an n_conn.
10478 - Change the contrib/tor.logrotate script so it makes the new
10479 logs as "_tor:_tor" rather than the default, which is generally
10480 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
10481 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
10482 warnings (occasionally), but it can also cause the compiler to
10483 eliminate error-checking code. Suggested by Peter Gutmann.
10484 - When a hidden service is giving up on an introduction point candidate
10485 that was not included in the last published rendezvous descriptor,
10486 don't reschedule publication of the next descriptor. Fixes bug 763.
10488 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
10489 HiddenServiceExcludeNodes as obsolete: they never worked properly,
10490 and nobody claims to be using them. Fixes bug 754. Bugfix on
10491 0.1.0.1-rc. Patch from Christian Wilms.
10492 - Fix a small alignment and memory-wasting bug on buffer chunks.
10495 o Minor bugfixes (controller):
10496 - When closing an application-side connection because its circuit
10497 is getting torn down, generate the stream event correctly.
10498 Bugfix on 0.1.2.x. Anonymous patch.
10500 o Removed features:
10501 - Remove all backward-compatibility code to support relays running
10502 versions of Tor so old that they no longer work at all on the
10506 Changes in version 0.2.0.30 - 2008-07-15
10508 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
10509 warnings (occasionally), but it can also cause the compiler to
10510 eliminate error-checking code. Suggested by Peter Gutmann.
10513 Changes in version 0.2.0.29-rc - 2008-07-08
10514 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
10515 hidden-service performance bugs, and fixes a bunch of smaller bugs.
10518 - If you have more than one bridge but don't know their keys,
10519 you would only launch a request for the descriptor of the first one
10520 on your list. (Tor considered launching requests for the others, but
10521 found that it already had a connection on the way for $0000...0000
10522 so it didn't open another.) Bugfix on 0.2.0.x.
10523 - If you have more than one bridge but don't know their keys, and the
10524 connection to one of the bridges failed, you would cancel all
10525 pending bridge connections. (After all, they all have the same
10526 digest.) Bugfix on 0.2.0.x.
10527 - When a hidden service was trying to establish an introduction point,
10528 and Tor had built circuits preemptively for such purposes, we
10529 were ignoring all the preemptive circuits and launching a new one
10530 instead. Bugfix on 0.2.0.14-alpha.
10531 - When a hidden service was trying to establish an introduction point,
10532 and Tor *did* manage to reuse one of the preemptively built
10533 circuits, it didn't correctly remember which one it used,
10534 so it asked for another one soon after, until there were no
10535 more preemptive circuits, at which point it launched one from
10536 scratch. Bugfix on 0.0.9.x.
10537 - Make directory servers include the X-Your-Address-Is: http header in
10538 their responses even for begin_dir conns. Now clients who only
10539 ever use begin_dir connections still have a way to learn their IP
10540 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
10543 - Fix a macro/CPP interaction that was confusing some compilers:
10544 some GCCs don't like #if/#endif pairs inside macro arguments.
10546 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
10547 Fixes bug 704; fix from Steven Murdoch.
10548 - When opening /dev/null in finish_daemonize(), do not pass the
10549 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
10550 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
10551 - Correctly detect transparent proxy support on Linux hosts that
10552 require in.h to be included before netfilter_ipv4.h. Patch
10554 - Disallow session resumption attempts during the renegotiation
10555 stage of the v2 handshake protocol. Clients should never be trying
10556 session resumption at this point, but apparently some did, in
10557 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
10558 found by Geoff Goodell.
10561 Changes in version 0.2.1.2-alpha - 2008-06-20
10562 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
10563 make it easier to set up your own private Tor network; fixes several
10564 big bugs with using more than one bridge relay; fixes a big bug with
10565 offering hidden services quickly after Tor starts; and uses a better
10566 API for reporting potential bootstrapping problems to the controller.
10569 - New TestingTorNetwork config option to allow adjustment of
10570 previously constant values that, while reasonable, could slow
10571 bootstrapping. Implements proposal 135. Patch from Karsten.
10574 - If you have more than one bridge but don't know their digests,
10575 you would only learn a request for the descriptor of the first one
10576 on your list. (Tor considered launching requests for the others, but
10577 found that it already had a connection on the way for $0000...0000
10578 so it didn't open another.) Bugfix on 0.2.0.x.
10579 - If you have more than one bridge but don't know their digests,
10580 and the connection to one of the bridges failed, you would cancel
10581 all pending bridge connections. (After all, they all have the
10582 same digest.) Bugfix on 0.2.0.x.
10583 - When establishing a hidden service, introduction points that
10584 originate from cannibalized circuits are completely ignored and not
10585 included in rendezvous service descriptors. This might be another
10586 reason for delay in making a hidden service available. Bugfix
10587 from long ago (0.0.9.x?)
10590 - Allow OpenSSL to use dynamic locks if it wants.
10591 - When building a consensus, do not include routers that are down.
10592 This will cut down 30% to 40% on consensus size. Implements
10594 - In directory authorities' approved-routers files, allow
10595 fingerprints with or without space.
10596 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
10597 controller can query our current bootstrap state in case it attaches
10598 partway through and wants to catch up.
10599 - Send an initial "Starting" bootstrap status event, so we have a
10600 state to start out in.
10603 - Asking for a conditional consensus at .../consensus/<fingerprints>
10604 would crash a dirserver if it did not already have a
10605 consensus. Bugfix on 0.2.1.1-alpha.
10606 - Clean up some macro/CPP interactions: some GCC versions don't like
10607 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
10610 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
10611 - Directory authorities shouldn't complain about bootstrapping
10612 problems just because they do a lot of reachability testing and
10613 some of the connection attempts fail.
10614 - Start sending "count" and "recommendation" key/value pairs in
10615 bootstrap problem status events, so the controller can hear about
10616 problems even before Tor decides they're worth reporting for sure.
10617 - If you're using bridges, generate "bootstrap problem" warnings
10618 as soon as you run out of working bridges, rather than waiting
10619 for ten failures -- which will never happen if you have less than
10621 - If we close our OR connection because there's been a circuit
10622 pending on it for too long, we were telling our bootstrap status
10623 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
10626 Changes in version 0.2.1.1-alpha - 2008-06-13
10627 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
10628 were making the Tor process bloat especially on Linux; makes our TLS
10629 handshake blend in better; sends "bootstrap phase" status events to
10630 the controller, so it can keep the user informed of progress (and
10631 problems) fetching directory information and establishing circuits;
10632 and adds a variety of smaller features.
10635 - More work on making our TLS handshake blend in: modify the list
10636 of ciphers advertised by OpenSSL in client mode to even more
10637 closely resemble a common web browser. We cheat a little so that
10638 we can advertise ciphers that the locally installed OpenSSL doesn't
10640 - Start sending "bootstrap phase" status events to the controller,
10641 so it can keep the user informed of progress fetching directory
10642 information and establishing circuits. Also inform the controller
10643 if we think we're stuck at a particular bootstrap phase. Implements
10645 - Resume using OpenSSL's RAND_poll() for better (and more portable)
10646 cross-platform entropy collection again. We used to use it, then
10647 stopped using it because of a bug that could crash systems that
10648 called RAND_poll when they had a lot of fds open. It looks like the
10649 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
10650 at startup, and to call RAND_poll() when we reseed later only if
10651 we have a non-buggy OpenSSL version.
10654 - When we choose to abandon a new entry guard because we think our
10655 older ones might be better, close any circuits pending on that
10656 new entry guard connection. This fix should make us recover much
10657 faster when our network is down and then comes back. Bugfix on
10658 0.1.2.8-beta; found by lodger.
10660 o Memory fixes and improvements:
10661 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
10662 to avoid unused RAM in buffer chunks and memory pools.
10663 - Speed up parsing and cut down on memory fragmentation by using
10664 stack-style allocations for parsing directory objects. Previously,
10665 this accounted for over 40% of allocations from within Tor's code
10666 on a typical directory cache.
10667 - Use a Bloom filter rather than a digest-based set to track which
10668 descriptors we need to keep around when we're cleaning out old
10669 router descriptors. This speeds up the computation significantly,
10670 and may reduce fragmentation.
10671 - Reduce the default smartlist size from 32 to 16; it turns out that
10672 most smartlists hold around 8-12 elements tops.
10673 - Make dumpstats() log the fullness and size of openssl-internal
10675 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
10676 patch to their OpenSSL, turn it on to save memory on servers. This
10677 patch will (with any luck) get included in a mainline distribution
10679 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10680 compress cells, which are basically all encrypted, compressed,
10684 - Stop reloading the router list from disk for no reason when we
10685 run out of reachable directory mirrors. Once upon a time reloading
10686 it would set the 'is_running' flag back to 1 for them. It hasn't
10687 done that for a long time.
10688 - In very rare situations new hidden service descriptors were
10689 published earlier than 30 seconds after the last change to the
10690 service. (We currently think that a hidden service descriptor
10691 that's been stable for 30 seconds is worth publishing.)
10694 - Allow separate log levels to be configured for different logging
10695 domains. For example, this allows one to log all notices, warnings,
10696 or errors, plus all memory management messages of level debug or
10697 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
10698 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
10699 and stop using a warning that had become unfixably verbose under
10701 - New --hush command-line option similar to --quiet. While --quiet
10702 disables all logging to the console on startup, --hush limits the
10703 output to messages of warning and error severity.
10704 - Servers support a new URL scheme for consensus downloads that
10705 allows the client to specify which authorities are trusted.
10706 The server then only sends the consensus if the client will trust
10707 it. Otherwise a 404 error is sent back. Clients use this
10708 new scheme when the server supports it (meaning it's running
10709 0.2.1.1-alpha or later). Implements proposal 134.
10710 - New configure/torrc options (--enable-geoip-stats,
10711 DirRecordUsageByCountry) to record how many IPs we've served
10712 directory info to in each country code, how many status documents
10713 total we've sent to each country code, and what share of the total
10714 directory requests we should expect to see.
10715 - Use the TLS1 hostname extension to more closely resemble browser
10717 - Lots of new unit tests.
10718 - Add a macro to implement the common pattern of iterating through
10719 two parallel lists in lockstep.
10722 Changes in version 0.2.0.28-rc - 2008-06-13
10723 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
10724 performance bug, and fixes a bunch of smaller bugs.
10727 - Fix a bug where, when we were choosing the 'end stream reason' to
10728 put in our relay end cell that we send to the exit relay, Tor
10729 clients on Windows were sometimes sending the wrong 'reason'. The
10730 anonymity problem is that exit relays may be able to guess whether
10731 the client is running Windows, thus helping partition the anonymity
10732 set. Down the road we should stop sending reasons to exit relays,
10733 or otherwise prevent future versions of this bug.
10736 - While setting up a hidden service, some valid introduction circuits
10737 were overlooked and abandoned. This might be the reason for
10738 the long delay in making a hidden service available. Bugfix on
10742 - Update to the "June 9 2008" ip-to-country file.
10743 - Run 'make test' as part of 'make dist', so we stop releasing so
10744 many development snapshots that fail their unit tests.
10747 - When we're checking if we have enough dir info for each relay
10748 to begin establishing circuits, make sure that we actually have
10749 the descriptor listed in the consensus, not just any descriptor.
10751 - Bridge relays no longer print "xx=0" in their extrainfo document
10752 for every single country code in the geoip db. Bugfix on
10754 - Only warn when we fail to load the geoip file if we were planning to
10755 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
10756 - If we change our MaxAdvertisedBandwidth and then reload torrc,
10757 Tor won't realize it should publish a new relay descriptor. Fixes
10758 bug 688, reported by mfr. Bugfix on 0.1.2.x.
10759 - When we haven't had any application requests lately, don't bother
10760 logging that we have expired a bunch of descriptors. Bugfix
10762 - Make relay cells written on a connection count as non-padding when
10763 tracking how long a connection has been in use. Bugfix on
10764 0.2.0.1-alpha. Spotted by lodger.
10765 - Fix unit tests in 0.2.0.27-rc.
10766 - Fix compile on Windows.
10769 Changes in version 0.2.0.27-rc - 2008-06-03
10770 Tor 0.2.0.27-rc adds a few features we left out of the earlier
10771 release candidates. In particular, we now include an IP-to-country
10772 GeoIP database, so controllers can easily look up what country a
10773 given relay is in, and so bridge relays can give us some sanitized
10774 summaries about which countries are making use of bridges. (See proposal
10775 126-geoip-fetching.txt for details.)
10778 - Include an IP-to-country GeoIP file in the tarball, so bridge
10779 relays can report sanitized summaries of the usage they're seeing.
10782 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
10783 Robert Hogan. Fixes the first part of bug 681.
10784 - Make bridge authorities never serve extrainfo docs.
10785 - Add support to detect Libevent versions in the 1.4.x series
10787 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
10788 - Include a new contrib/tor-exit-notice.html file that exit relay
10789 operators can put on their website to help reduce abuse queries.
10792 - When tunneling an encrypted directory connection, and its first
10793 circuit fails, do not leave it unattached and ask the controller
10794 to deal. Fixes the second part of bug 681.
10795 - Make bridge authorities correctly expire old extrainfo documents
10799 Changes in version 0.2.0.26-rc - 2008-05-13
10800 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
10801 in Debian's OpenSSL packages. All users running any 0.2.0.x version
10802 should upgrade, whether they're running Debian or not.
10804 o Major security fixes:
10805 - Use new V3 directory authority keys on the tor26, gabelmoo, and
10806 moria1 V3 directory authorities. The old keys were generated with
10807 a vulnerable version of Debian's OpenSSL package, and must be
10808 considered compromised. Other authorities' keys were not generated
10809 with an affected version of OpenSSL.
10812 - List authority signatures as "unrecognized" based on DirServer
10813 lines, not on cert cache. Bugfix on 0.2.0.x.
10816 - Add a new V3AuthUseLegacyKey option to make it easier for
10817 authorities to change their identity keys if they have to.
10820 Changes in version 0.2.0.25-rc - 2008-04-23
10821 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
10824 - Remember to initialize threading before initializing logging.
10825 Otherwise, many BSD-family implementations will crash hard on
10826 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
10829 - Authorities correctly free policies on bad servers on
10830 exit. Fixes bug 672. Bugfix on 0.2.0.x.
10833 Changes in version 0.2.0.24-rc - 2008-04-22
10834 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
10835 v3 directory authority, makes relays with dynamic IP addresses and no
10836 DirPort notice more quickly when their IP address changes, fixes a few
10837 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
10839 o New directory authorities:
10840 - Take lefkada out of the list of v3 directory authorities, since
10841 it has been down for months.
10842 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
10846 - Detect address changes more quickly on non-directory mirror
10847 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
10849 o Minor features (security):
10850 - Reject requests for reverse-dns lookup of names that are in
10851 a private address space. Patch from lodger.
10852 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
10855 o Minor bugfixes (crashes):
10856 - Avoid a rare assert that can trigger when Tor doesn't have much
10857 directory information yet and it tries to fetch a v2 hidden
10858 service descriptor. Fixes bug 651, reported by nwf.
10859 - Initialize log mutex before initializing dmalloc. Otherwise,
10860 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
10861 - Use recursive pthread mutexes in order to avoid deadlock when
10862 logging debug-level messages to a controller. Bug spotted by nwf,
10863 bugfix on 0.2.0.16-alpha.
10865 o Minor bugfixes (resource management):
10866 - Keep address policies from leaking memory: start their refcount
10867 at 1, not 2. Bugfix on 0.2.0.16-alpha.
10868 - Free authority certificates on exit, so they don't look like memory
10869 leaks. Bugfix on 0.2.0.19-alpha.
10870 - Free static hashtables for policy maps and for TLS connections on
10871 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
10872 - Avoid allocating extra space when computing consensuses on 64-bit
10873 platforms. Bug spotted by aakova.
10875 o Minor bugfixes (misc):
10876 - Do not read the configuration file when we've only been told to
10877 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
10878 based on patch from Sebastian Hahn.
10879 - Exit relays that are used as a client can now reach themselves
10880 using the .exit notation, rather than just launching an infinite
10881 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
10882 - When attempting to open a logfile fails, tell us why.
10883 - Fix a dumb bug that was preventing us from knowing that we should
10884 preemptively build circuits to handle expected directory requests.
10885 Fixes bug 660. Bugfix on 0.1.2.x.
10886 - Warn less verbosely about clock skew from netinfo cells from
10887 untrusted sources. Fixes bug 663.
10888 - Make controller stream events for DNS requests more consistent,
10889 by adding "new stream" events for DNS requests, and removing
10890 spurious "stream closed" events" for cached reverse resolves.
10891 Patch from mwenge. Fixes bug 646.
10892 - Correctly notify one-hop connections when a circuit build has
10893 failed. Possible fix for bug 669. Found by lodger.
10896 Changes in version 0.2.0.23-rc - 2008-03-24
10897 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
10898 makes bootstrapping faster if the first directory mirror you contact
10899 is down. The bundles also include the new Vidalia 0.1.2 release.
10902 - When a tunneled directory request is made to a directory server
10903 that's down, notice after 30 seconds rather than 120 seconds. Also,
10904 fail any begindir streams that are pending on it, so they can
10905 retry elsewhere. This was causing multi-minute delays on bootstrap.
10908 Changes in version 0.2.0.22-rc - 2008-03-18
10909 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
10910 enables encrypted directory connections by default for non-relays, fixes
10911 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
10912 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
10915 - Enable encrypted directory connections by default for non-relays,
10916 so censor tools that block Tor directory connections based on their
10917 plaintext patterns will no longer work. This means Tor works in
10918 certain censored countries by default again.
10921 - Make sure servers always request certificates from clients during
10922 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
10923 - Do not enter a CPU-eating loop when a connection is closed in
10924 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
10925 diagnosed by lodger; bugfix on 0.2.0.20-rc.
10926 - Fix assertion failure that could occur when a blocked circuit
10927 became unblocked, and it had pending client DNS requests. Bugfix
10928 on 0.2.0.1-alpha. Fixes bug 632.
10930 o Minor bugfixes (on 0.1.2.x):
10931 - Generate "STATUS_SERVER" events rather than misspelled
10932 "STATUS_SEVER" events. Caught by mwenge.
10933 - When counting the number of bytes written on a TLS connection,
10934 look at the BIO actually used for writing to the network, not
10935 at the BIO used (sometimes) to buffer data for the network.
10936 Looking at different BIOs could result in write counts on the
10937 order of ULONG_MAX. Fixes bug 614.
10938 - On Windows, correctly detect errors when listing the contents of
10939 a directory. Fix from lodger.
10941 o Minor bugfixes (on 0.2.0.x):
10942 - Downgrade "sslv3 alert handshake failure" message to INFO.
10943 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
10944 left BandwidthRate and BandwidthBurst at the default, we would be
10945 silently limited by those defaults. Now raise them to match the
10946 RelayBandwidth* values.
10947 - Fix the SVK version detection logic to work correctly on a branch.
10948 - Make --enable-openbsd-malloc work correctly on Linux with alpha
10949 CPUs. Fixes bug 625.
10950 - Logging functions now check that the passed severity is sane.
10951 - Use proper log levels in the testsuite call of
10952 get_interface_address6().
10953 - When using a nonstandard malloc, do not use the platform values for
10954 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
10955 - Make the openbsd malloc code use 8k pages on alpha CPUs and
10957 - Detect mismatched page sizes when using --enable-openbsd-malloc.
10958 - Avoid double-marked-for-close warning when certain kinds of invalid
10959 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
10960 for bug 617. Bugfix on 0.2.0.1-alpha.
10961 - Make sure that the "NULL-means-reject *:*" convention is followed by
10962 all the policy manipulation functions, avoiding some possible crash
10963 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
10964 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
10965 actually works, and doesn't warn about every single reverse lookup.
10966 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
10969 - Only log guard node status when guard node status has changed.
10970 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
10971 make "INFO" 75% less verbose.
10974 Changes in version 0.2.0.21-rc - 2008-03-02
10975 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
10976 makes Tor work well with Vidalia again, fixes a rare assert bug,
10977 and fixes a pair of more minor bugs. The bundles also include Vidalia
10978 0.1.0 and Torbutton 1.1.16.
10981 - The control port should declare that it requires password auth
10982 when HashedControlSessionPassword is set too. Patch from Matt Edman;
10983 bugfix on 0.2.0.20-rc. Fixes bug 615.
10984 - Downgrade assert in connection_buckets_decrement() to a log message.
10985 This may help us solve bug 614, and in any case will make its
10986 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
10987 - We were sometimes miscounting the number of bytes read from the
10988 network, causing our rate limiting to not be followed exactly.
10989 Bugfix on 0.2.0.16-alpha. Reported by lodger.
10992 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
10993 OpenSSL versions should have been working fine. Diagnosis and patch
10994 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
10995 Bugfix on 0.2.0.20-rc.
10998 Changes in version 0.2.0.20-rc - 2008-02-24
10999 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
11000 makes more progress towards normalizing Tor's TLS handshake, makes
11001 hidden services work better again, helps relays bootstrap if they don't
11002 know their IP address, adds optional support for linking in openbsd's
11003 allocator or tcmalloc, allows really fast relays to scale past 15000
11004 sockets, and fixes a bunch of minor bugs reported by Veracode.
11007 - Enable the revised TLS handshake based on the one designed by
11008 Steven Murdoch in proposal 124, as revised in proposal 130. It
11009 includes version negotiation for OR connections as described in
11010 proposal 105. The new handshake is meant to be harder for censors
11011 to fingerprint, and it adds the ability to detect certain kinds of
11012 man-in-the-middle traffic analysis attacks. The version negotiation
11013 feature will allow us to improve Tor's link protocol more safely
11015 - Choose which bridge to use proportional to its advertised bandwidth,
11016 rather than uniformly at random. This should speed up Tor for
11017 bridge users. Also do this for people who set StrictEntryNodes.
11018 - When a TrackHostExits-chosen exit fails too many times in a row,
11019 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
11022 - Resolved problems with (re-)fetching hidden service descriptors.
11023 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
11024 and 0.2.0.19-alpha.
11025 - If we only ever used Tor for hidden service lookups or posts, we
11026 would stop building circuits and start refusing connections after
11027 24 hours, since we falsely believed that Tor was dormant. Reported
11028 by nwf; bugfix on 0.1.2.x.
11029 - Servers that don't know their own IP address should go to the
11030 authorities for their first directory fetch, even if their DirPort
11031 is off or if they don't know they're reachable yet. This will help
11032 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
11033 - When counting the number of open sockets, count not only the number
11034 of sockets we have received from the socket() call, but also
11035 the number we've gotten from accept() and socketpair(). This bug
11036 made us fail to count all sockets that we were using for incoming
11037 connections. Bugfix on 0.2.0.x.
11038 - Fix code used to find strings within buffers, when those strings
11039 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
11040 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
11041 - Add a new __HashedControlSessionPassword option for controllers
11042 to use for one-off session password hashes that shouldn't get
11043 saved to disk by SAVECONF --- Vidalia users were accumulating a
11044 pile of HashedControlPassword lines in their torrc files, one for
11045 each time they had restarted Tor and then clicked Save. Make Tor
11046 automatically convert "HashedControlPassword" to this new option but
11047 only when it's given on the command line. Partial fix for bug 586.
11049 o Minor features (performance):
11050 - Tune parameters for cell pool allocation to minimize amount of
11052 - Add OpenBSD malloc code from phk as an optional malloc
11053 replacement on Linux: some glibc libraries do very poorly
11054 with Tor's memory allocation patterns. Pass
11055 --enable-openbsd-malloc to get the replacement malloc code.
11056 - Add a --with-tcmalloc option to the configure script to link
11057 against tcmalloc (if present). Does not yet search for
11058 non-system include paths.
11059 - Stop imposing an arbitrary maximum on the number of file descriptors
11060 used for busy servers. Bug reported by Olaf Selke; patch from
11063 o Minor features (other):
11064 - When SafeLogging is disabled, log addresses along with all TLS
11066 - When building with --enable-gcc-warnings, check for whether Apple's
11067 warning "-Wshorten-64-to-32" is available.
11068 - Add a --passphrase-fd argument to the tor-gencert command for
11071 o Minor bugfixes (memory leaks and code problems):
11072 - We were leaking a file descriptor if Tor started with a zero-length
11073 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
11074 - Detect size overflow in zlib code. Reported by Justin Ferguson and
11076 - We were comparing the raw BridgePassword entry with a base64'ed
11077 version of it, when handling a "/tor/networkstatus-bridges"
11078 directory request. Now compare correctly. Noticed by Veracode.
11079 - Recover from bad tracked-since value in MTBF-history file.
11080 Should fix bug 537.
11081 - Alter the code that tries to recover from unhandled write
11082 errors, to not try to flush onto a socket that's given us
11083 unhandled errors. Bugfix on 0.1.2.x.
11084 - Make Unix controlsockets work correctly on OpenBSD. Patch from
11085 tup. Bugfix on 0.2.0.3-alpha.
11087 o Minor bugfixes (other):
11088 - If we have an extra-info document for our server, always make
11089 it available on the control port, even if we haven't gotten
11090 a copy of it from an authority yet. Patch from mwenge.
11091 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
11092 - Directory mirrors no longer include a guess at the client's IP
11093 address if the connection appears to be coming from the same /24
11094 network; it was producing too many wrong guesses.
11095 - Make the new hidden service code respect the SafeLogging setting.
11096 Bugfix on 0.2.0.x. Patch from Karsten.
11097 - When starting as an authority, do not overwrite all certificates
11098 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
11099 - If we're trying to flush the last bytes on a connection (for
11100 example, when answering a directory request), reset the
11101 time-to-give-up timeout every time we manage to write something
11102 on the socket. Bugfix on 0.1.2.x.
11103 - Change the behavior of "getinfo status/good-server-descriptor"
11104 so it doesn't return failure when any authority disappears.
11105 - Even though the man page said that "TrackHostExits ." should
11106 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
11107 - Report TLS "zero return" case as a "clean close" and "IO error"
11108 as a "close". Stop calling closes "unexpected closes": existing
11109 Tors don't use SSL_close(), so having a connection close without
11110 the TLS shutdown handshake is hardly unexpected.
11111 - Send NAMESERVER_STATUS messages for a single failed nameserver
11114 o Code simplifications and refactoring:
11115 - Remove the tor_strpartition function: its logic was confused,
11116 and it was only used for one thing that could be implemented far
11120 Changes in version 0.2.0.19-alpha - 2008-02-09
11121 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
11122 handshake, makes path selection for relays more secure and IP address
11123 guessing more robust, and generally fixes a lot of bugs in preparation
11124 for calling the 0.2.0 branch stable.
11127 - Do not include recognizeable strings in the commonname part of
11128 Tor's x509 certificates.
11131 - If we're a relay, avoid picking ourselves as an introduction point,
11132 a rendezvous point, or as the final hop for internal circuits. Bug
11133 reported by taranis and lodger. Bugfix on 0.1.2.x.
11134 - Patch from "Andrew S. Lists" to catch when we contact a directory
11135 mirror at IP address X and he says we look like we're coming from
11136 IP address X. Bugfix on 0.1.2.x.
11138 o Minor features (security):
11139 - Be more paranoid about overwriting sensitive memory on free(),
11140 as a defensive programming tactic to ensure forward secrecy.
11142 o Minor features (directory authority):
11143 - Actually validate the options passed to AuthDirReject,
11144 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
11145 - Reject router descriptors with out-of-range bandwidthcapacity or
11146 bandwidthburst values.
11148 o Minor features (controller):
11149 - Reject controller commands over 1MB in length. This keeps rogue
11150 processes from running us out of memory.
11152 o Minor features (misc):
11153 - Give more descriptive well-formedness errors for out-of-range
11154 hidden service descriptor/protocol versions.
11155 - Make memory debugging information describe more about history
11156 of cell allocation, so we can help reduce our memory use.
11158 o Deprecated features (controller):
11159 - The status/version/num-versioning and status/version/num-concurring
11160 GETINFO options are no longer useful in the v3 directory protocol:
11161 treat them as deprecated, and warn when they're used.
11164 - When our consensus networkstatus has been expired for a while, stop
11165 being willing to build circuits using it. Fixes bug 401. Bugfix
11167 - Directory caches now fetch certificates from all authorities
11168 listed in a networkstatus consensus, even when they do not
11169 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
11170 - When connecting to a bridge without specifying its key, insert
11171 the connection into the identity-to-connection map as soon as
11172 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
11173 - Detect versions of OS X where malloc_good_size() is present in the
11174 library but never actually declared. Resolves bug 587. Bugfix
11176 - Stop incorrectly truncating zlib responses to directory authority
11177 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
11178 - Stop recommending that every server operator send mail to tor-ops.
11179 Resolves bug 597. Bugfix on 0.1.2.x.
11180 - Don't trigger an assert if we start a directory authority with a
11181 private IP address (like 127.0.0.1).
11182 - Avoid possible failures when generating a directory with routers
11183 with over-long versions strings, or too many flags set. Bugfix
11185 - If an attempt to launch a DNS resolve request over the control
11186 port fails because we have overrun the limit on the number of
11187 connections, tell the controller that the request has failed.
11188 - Avoid using too little bandwidth when our clock skips a few
11189 seconds. Bugfix on 0.1.2.x.
11190 - Fix shell error when warning about missing packages in configure
11191 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
11192 - Do not become confused when receiving a spurious VERSIONS-like
11193 cell from a confused v1 client. Bugfix on 0.2.0.x.
11194 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
11195 introduction points for a hidden service have failed. Patch from
11196 Karsten Loesing. Bugfix on 0.2.0.x.
11198 o Code simplifications and refactoring:
11199 - Remove some needless generality from cpuworker code, for improved
11201 - Stop overloading the circuit_t.onionskin field for both "onionskin
11202 from a CREATE cell that we are waiting for a cpuworker to be
11203 assigned" and "onionskin from an EXTEND cell that we are going to
11204 send to an OR as soon as we are connected". Might help with bug 600.
11205 - Add an in-place version of aes_crypt() so that we can avoid doing a
11206 needless memcpy() call on each cell payload.
11209 Changes in version 0.2.0.18-alpha - 2008-01-25
11210 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
11211 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
11212 that can warn or reject connections to ports generally associated with
11213 vulnerable-plaintext protocols.
11215 o New directory authorities:
11216 - Set up dannenberg (run by CCC) as the sixth v3 directory
11220 - Fix a major memory leak when attempting to use the v2 TLS
11221 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
11222 - We accidentally enabled the under-development v2 TLS handshake
11223 code, which was causing log entries like "TLS error while
11224 renegotiating handshake". Disable it again. Resolves bug 590.
11225 - We were computing the wrong Content-Length: header for directory
11226 responses that need to be compressed on the fly, causing clients
11227 asking for those items to always fail. Bugfix on 0.2.0.x; partially
11231 - Avoid going directly to the directory authorities even if you're a
11232 relay, if you haven't found yourself reachable yet or if you've
11233 decided not to advertise your dirport yet. Addresses bug 556.
11234 - If we've gone 12 hours since our last bandwidth check, and we
11235 estimate we have less than 50KB bandwidth capacity but we could
11236 handle more, do another bandwidth test.
11237 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
11238 Tor can warn and/or refuse connections to ports commonly used with
11239 vulnerable-plaintext protocols. Currently we warn on ports 23,
11240 109, 110, and 143, but we don't reject any.
11243 - When we setconf ClientOnly to 1, close any current OR and Dir
11244 listeners. Reported by mwenge.
11245 - When we get a consensus that's been signed by more people than
11246 we expect, don't log about it; it's not a big deal. Reported
11250 - Don't answer "/tor/networkstatus-bridges" directory requests if
11251 the request isn't encrypted.
11252 - Make "ClientOnly 1" config option disable directory ports too.
11253 - Patches from Karsten Loesing to make v2 hidden services more
11254 robust: work even when there aren't enough HSDir relays available;
11255 retry when a v2 rend desc fetch fails; but don't retry if we
11256 already have a usable v0 rend desc.
11259 Changes in version 0.2.0.17-alpha - 2008-01-17
11260 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
11263 - Make the tor-gencert man page get included correctly in the tarball.
11266 Changes in version 0.2.0.16-alpha - 2008-01-17
11267 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
11268 Loesing, and generally cleans up a lot of features and minor bugs.
11270 o New directory authorities:
11271 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
11274 o Major performance improvements:
11275 - Switch our old ring buffer implementation for one more like that
11276 used by free Unix kernels. The wasted space in a buffer with 1mb
11277 of data will now be more like 8k than 1mb. The new implementation
11278 also avoids realloc();realloc(); patterns that can contribute to
11279 memory fragmentation.
11282 - Configuration files now accept C-style strings as values. This
11283 helps encode characters not allowed in the current configuration
11284 file format, such as newline or #. Addresses bug 557.
11285 - Although we fixed bug 539 (where servers would send HTTP status 503
11286 responses _and_ send a body too), there are still servers out
11287 there that haven't upgraded. Therefore, make clients parse such
11288 bodies when they receive them.
11289 - When we're not serving v2 directory information, there is no reason
11290 to actually keep any around. Remove the obsolete files and directory
11291 on startup if they are very old and we aren't going to serve them.
11293 o Minor performance improvements:
11294 - Reference-count and share copies of address policy entries; only 5%
11295 of them were actually distinct.
11296 - Never walk through the list of logs if we know that no log is
11297 interested in a given message.
11300 - When an authority has not signed a consensus, do not try to
11301 download a nonexistent "certificate with key 00000000". Bugfix
11302 on 0.2.0.x. Fixes bug 569.
11303 - Fix a rare assert error when we're closing one of our threads:
11304 use a mutex to protect the list of logs, so we never write to the
11305 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
11306 bug 575, which is kind of the revenge of bug 222.
11307 - Patch from Karsten Loesing to complain less at both the client
11308 and the relay when a relay used to have the HSDir flag but doesn't
11309 anymore, and we try to upload a hidden service descriptor.
11310 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
11312 - Do not try to download missing certificates until we have tried
11313 to check our fallback consensus. Fixes bug 583.
11314 - Make bridges round reported GeoIP stats info up to the nearest
11315 estimate, not down. Now we can distinguish between "0 people from
11316 this country" and "1 person from this country".
11317 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
11318 - Avoid possible segfault if key generation fails in
11319 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
11320 - Avoid segfault in the case where a badly behaved v2 versioning
11321 directory sends a signed networkstatus with missing client-versions.
11323 - Avoid segfaults on certain complex invocations of
11324 router_get_by_hexdigest(). Bugfix on 0.1.2.
11325 - Correct bad index on array access in parse_http_time(). Bugfix
11327 - Fix possible bug in vote generation when server versions are present
11328 but client versions are not.
11329 - Fix rare bug on REDIRECTSTREAM control command when called with no
11330 port set: it could erroneously report an error when none had
11332 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
11333 compressing large objects and find ourselves with more than 4k
11334 left over. Bugfix on 0.2.0.
11335 - Fix a small memory leak when setting up a hidden service.
11336 - Fix a few memory leaks that could in theory happen under bizarre
11338 - Fix an assert if we post a general-purpose descriptor via the
11339 control port but that descriptor isn't mentioned in our current
11340 network consensus. Bug reported by Jon McLachlan; bugfix on
11343 o Minor features (controller):
11344 - Get NS events working again. Patch from tup.
11345 - The GETCONF command now escapes and quotes configuration values
11346 that don't otherwise fit into the torrc file.
11347 - The SETCONF command now handles quoted values correctly.
11349 o Minor features (directory authorities):
11350 - New configuration options to override default maximum number of
11351 servers allowed on a single IP address. This is important for
11352 running a test network on a single host.
11353 - Actually implement the -s option to tor-gencert.
11354 - Add a manual page for tor-gencert.
11356 o Minor features (bridges):
11357 - Bridge authorities no longer serve bridge descriptors over
11358 unencrypted connections.
11360 o Minor features (other):
11361 - Add hidden services and DNSPorts to the list of things that make
11362 Tor accept that it has running ports. Change starting Tor with no
11363 ports from a fatal error to a warning; we might change it back if
11364 this turns out to confuse anybody. Fixes bug 579.
11367 Changes in version 0.1.2.19 - 2008-01-17
11368 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
11369 exit policy a little bit more conservative so it's safer to run an
11370 exit relay on a home system, and fixes a variety of smaller issues.
11373 - Exit policies now reject connections that are addressed to a
11374 relay's public (external) IP address too, unless
11375 ExitPolicyRejectPrivate is turned off. We do this because too
11376 many relays are running nearby to services that trust them based
11377 on network address.
11380 - When the clock jumps forward a lot, do not allow the bandwidth
11381 buckets to become negative. Fixes bug 544.
11382 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11383 on every successful resolve. Reported by Mike Perry.
11384 - Purge old entries from the "rephist" database and the hidden
11385 service descriptor database even when DirPort is zero.
11386 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11387 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11388 crashing or mis-answering these requests.
11389 - When we decide to send a 503 response to a request for servers, do
11390 not then also send the server descriptors: this defeats the whole
11391 purpose. Fixes bug 539.
11394 - Changing the ExitPolicyRejectPrivate setting should cause us to
11395 rebuild our server descriptor.
11396 - Fix handling of hex nicknames when answering controller requests for
11397 networkstatus by name, or when deciding whether to warn about
11398 unknown routers in a config option. (Patch from mwenge.)
11399 - Fix a couple of hard-to-trigger autoconf problems that could result
11400 in really weird results on platforms whose sys/types.h files define
11401 nonstandard integer types.
11402 - Don't try to create the datadir when running --verify-config or
11403 --hash-password. Resolves bug 540.
11404 - If we were having problems getting a particular descriptor from the
11405 directory caches, and then we learned about a new descriptor for
11406 that router, we weren't resetting our failure count. Reported
11408 - Although we fixed bug 539 (where servers would send HTTP status 503
11409 responses _and_ send a body too), there are still servers out there
11410 that haven't upgraded. Therefore, make clients parse such bodies
11411 when they receive them.
11412 - Run correctly on systems where rlim_t is larger than unsigned long.
11413 This includes some 64-bit systems.
11414 - Run correctly on platforms (like some versions of OS X 10.5) where
11415 the real limit for number of open files is OPEN_FILES, not rlim_max
11416 from getrlimit(RLIMIT_NOFILES).
11417 - Avoid a spurious free on base64 failure.
11418 - Avoid segfaults on certain complex invocations of
11419 router_get_by_hexdigest().
11420 - Fix rare bug on REDIRECTSTREAM control command when called with no
11421 port set: it could erroneously report an error when none had
11425 Changes in version 0.2.0.15-alpha - 2007-12-25
11426 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
11427 features added in 0.2.0.13-alpha.
11430 - Fix several remotely triggerable asserts based on DirPort requests
11431 for a v2 or v3 networkstatus object before we were prepared. This
11432 was particularly bad for 0.2.0.13 and later bridge relays, who
11433 would never have a v2 networkstatus and would thus always crash
11434 when used. Bugfixes on 0.2.0.x.
11435 - Estimate the v3 networkstatus size more accurately, rather than
11436 estimating it at zero bytes and giving it artificially high priority
11437 compared to other directory requests. Bugfix on 0.2.0.x.
11440 - Fix configure.in logic for cross-compilation.
11441 - When we load a bridge descriptor from the cache, and it was
11442 previously unreachable, mark it as retriable so we won't just
11443 ignore it. Also, try fetching a new copy immediately. Bugfixes
11445 - The bridge GeoIP stats were counting other relays, for example
11446 self-reachability and authority-reachability tests.
11449 - Support compilation to target iPhone; patch from cjacker huang.
11450 To build for iPhone, pass the --enable-iphone option to configure.
11453 Changes in version 0.2.0.14-alpha - 2007-12-23
11455 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
11456 without a datadirectory from a previous Tor install. Reported
11458 - Fix a crash when we fetch a descriptor that turns out to be
11459 unexpected (it used to be in our networkstatus when we started
11460 fetching it, but it isn't in our current networkstatus), and we
11461 aren't using bridges. Bugfix on 0.2.0.x.
11462 - Fix a crash when accessing hidden services: it would work the first
11463 time you use a given introduction point for your service, but
11464 on subsequent requests we'd be using garbage memory. Fixed by
11465 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
11466 - Fix a crash when we load a bridge descriptor from disk but we don't
11467 currently have a Bridge line for it in our torrc. Bugfix on
11471 - If bridge authorities set BridgePassword, they will serve a
11472 snapshot of known bridge routerstatuses from their DirPort to
11473 anybody who knows that password. Unset by default.
11476 - Make the unit tests build again.
11477 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
11478 - Make PublishServerDescriptor default to 1, so the default doesn't
11479 have to change as we invent new directory protocol versions.
11480 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
11481 be included unless sys/time.h is already included. Fixes
11482 bug 553. Bugfix on 0.2.0.x.
11483 - If we receive a general-purpose descriptor and then receive an
11484 identical bridge-purpose descriptor soon after, don't discard
11485 the next one as a duplicate.
11488 - If BridgeRelay is set to 1, then the default for
11489 PublishServerDescriptor is now "bridge" rather than "v2,v3".
11490 - If the user sets RelayBandwidthRate but doesn't set
11491 RelayBandwidthBurst, then make them equal rather than erroring out.
11494 Changes in version 0.2.0.13-alpha - 2007-12-21
11495 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
11496 Goodell, fixes many more bugs, and adds a lot of infrastructure for
11499 o New directory authorities:
11500 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
11504 - Only update guard status (usable / not usable) once we have
11505 enough directory information. This was causing us to always pick
11506 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
11507 causing us to discard all our guards on startup if we hadn't been
11508 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
11509 - Purge old entries from the "rephist" database and the hidden
11510 service descriptor databases even when DirPort is zero. Bugfix
11512 - We were ignoring our RelayBandwidthRate for the first 30 seconds
11513 after opening a circuit -- even a relayed circuit. Bugfix on
11515 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11516 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11517 crashing or mis-answering these types of requests.
11518 - Relays were publishing their server descriptor to v1 and v2
11519 directory authorities, but they didn't try publishing to v3-only
11520 authorities. Fix this; and also stop publishing to v1 authorities.
11522 - When we were reading router descriptors from cache, we were ignoring
11523 the annotations -- so for example we were reading in bridge-purpose
11524 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
11525 - When we decided to send a 503 response to a request for servers, we
11526 were then also sending the server descriptors: this defeats the
11527 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
11530 - Bridge relays now behave like clients with respect to time
11531 intervals for downloading new consensus documents -- otherwise they
11532 stand out. Bridge users now wait until the end of the interval,
11533 so their bridge relay will be sure to have a new consensus document.
11534 - Three new config options (AlternateDirAuthority,
11535 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
11536 user selectively replace the default directory authorities by type,
11537 rather than the all-or-nothing replacement that DirServer offers.
11538 - Tor can now be configured to read a GeoIP file from disk in one
11539 of two formats. This can be used by controllers to map IP addresses
11540 to countries. Eventually, it may support exit-by-country.
11541 - When possible, bridge relays remember which countries users
11542 are coming from, and report aggregate information in their
11543 extra-info documents, so that the bridge authorities can learn
11544 where Tor is blocked.
11545 - Bridge directory authorities now do reachability testing on the
11546 bridges they know. They provide router status summaries to the
11547 controller via "getinfo ns/purpose/bridge", and also dump summaries
11548 to a file periodically.
11549 - Stop fetching directory info so aggressively if your DirPort is
11550 on but your ORPort is off; stop fetching v2 dir info entirely.
11551 You can override these choices with the new FetchDirInfoEarly
11555 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
11556 consensus documents when there are too many relays at a single
11557 IP address. Now clear it in v2 network status documents too, and
11558 also clear it in routerinfo_t when the relay is no longer listed
11559 in the relevant networkstatus document.
11560 - Don't crash if we get an unexpected value for the
11561 PublishServerDescriptor config option. Reported by Matt Edman;
11562 bugfix on 0.2.0.9-alpha.
11563 - Our new v2 hidden service descriptor format allows descriptors
11564 that have no introduction points. But Tor crashed when we tried
11565 to build a descriptor with no intro points (and it would have
11566 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
11567 by Karsten Loesing.
11568 - Fix building with dmalloc 5.5.2 with glibc.
11569 - Reject uploaded descriptors and extrainfo documents if they're
11570 huge. Otherwise we'll cache them all over the network and it'll
11571 clog everything up. Reported by Aljosha Judmayer.
11572 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
11573 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
11574 - When the DANGEROUS_VERSION controller status event told us we're
11575 running an obsolete version, it used the string "OLD" to describe
11576 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
11577 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
11578 - If we can't expand our list of entry guards (e.g. because we're
11579 using bridges or we have StrictEntryNodes set), don't mark relays
11580 down when they fail a directory request. Otherwise we're too quick
11581 to mark all our entry points down. Bugfix on 0.1.2.x.
11582 - Fix handling of hex nicknames when answering controller requests for
11583 networkstatus by name, or when deciding whether to warn about unknown
11584 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
11585 - Fix a couple of hard-to-trigger autoconf problems that could result
11586 in really weird results on platforms whose sys/types.h files define
11587 nonstandard integer types. Bugfix on 0.1.2.x.
11588 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
11589 - Don't crash on name lookup when we have no current consensus. Fixes
11590 bug 538; bugfix on 0.2.0.x.
11591 - Only Tors that want to mirror the v2 directory info should
11592 create the "cached-status" directory in their datadir. (All Tors
11593 used to create it.) Bugfix on 0.2.0.9-alpha.
11594 - Directory authorities should only automatically download Extra Info
11595 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
11598 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
11599 consumers. (We already do this on HUP.)
11600 - Authorities and caches fetch the v2 networkstatus documents
11601 less often, now that v3 is encouraged.
11602 - Add a new config option BridgeRelay that specifies you want to
11603 be a bridge relay. Right now the only difference is that it makes
11604 you answer begin_dir requests, and it makes you cache dir info,
11605 even if your DirPort isn't on.
11606 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
11607 ask about source, timestamp of arrival, purpose, etc. We need
11608 something like this to help Vidalia not do GeoIP lookups on bridge
11610 - Allow multiple HashedControlPassword config lines, to support
11611 multiple controller passwords.
11612 - Authorities now decide whether they're authoritative for a given
11613 router based on the router's purpose.
11614 - New config options AuthDirBadDir and AuthDirListBadDirs for
11615 authorities to mark certain relays as "bad directories" in the
11616 networkstatus documents. Also supports the "!baddir" directive in
11617 the approved-routers file.
11620 Changes in version 0.2.0.12-alpha - 2007-11-16
11621 This twelfth development snapshot fixes some more build problems as
11622 well as a few minor bugs.
11625 - Make it build on OpenBSD again. Patch from tup.
11626 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
11627 package-building for Red Hat, OS X, etc.
11629 o Minor bugfixes (on 0.1.2.x):
11630 - Changing the ExitPolicyRejectPrivate setting should cause us to
11631 rebuild our server descriptor.
11633 o Minor bugfixes (on 0.2.0.x):
11634 - When we're lacking a consensus, don't try to perform rendezvous
11635 operations. Reported by Karsten Loesing.
11636 - Fix a small memory leak whenever we decide against using a
11637 newly picked entry guard. Reported by Mike Perry.
11638 - When authorities detected more than two relays running on the same
11639 IP address, they were clearing all the status flags but forgetting
11640 to clear the "hsdir" flag. So clients were being told that a
11641 given relay was the right choice for a v2 hsdir lookup, yet they
11642 never had its descriptor because it was marked as 'not running'
11644 - If we're trying to fetch a bridge descriptor and there's no way
11645 the bridge authority could help us (for example, we don't know
11646 a digest, or there is no bridge authority), don't be so eager to
11647 fall back to asking the bridge authority.
11648 - If we're using bridges or have strictentrynodes set, and our
11649 chosen exit is in the same family as all our bridges/entry guards,
11650 then be flexible about families.
11653 - When we negotiate a v2 link-layer connection (not yet implemented),
11654 accept RELAY_EARLY cells and turn them into RELAY cells if we've
11655 negotiated a v1 connection for their next step. Initial code for
11659 Changes in version 0.2.0.11-alpha - 2007-11-12
11660 This eleventh development snapshot fixes some build problems with
11661 the previous snapshot. It also includes a more secure-by-default exit
11662 policy for relays, fixes an enormous memory leak for exit relays, and
11663 fixes another bug where servers were falling out of the directory list.
11666 - Exit policies now reject connections that are addressed to a
11667 relay's public (external) IP address too, unless
11668 ExitPolicyRejectPrivate is turned off. We do this because too
11669 many relays are running nearby to services that trust them based
11670 on network address. Bugfix on 0.1.2.x.
11673 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11674 on every successful resolve. Reported by Mike Perry; bugfix
11676 - On authorities, never downgrade to old router descriptors simply
11677 because they're listed in the consensus. This created a catch-22
11678 where we wouldn't list a new descriptor because there was an
11679 old one in the consensus, and we couldn't get the new one in the
11680 consensus because we wouldn't list it. Possible fix for bug 548.
11681 Also, this might cause bug 543 to appear on authorities; if so,
11682 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
11684 o Packaging fixes on 0.2.0.10-alpha:
11685 - We were including instructions about what to do with the
11686 src/config/fallback-consensus file, but we weren't actually
11687 including it in the tarball. Disable all of that for now.
11690 - Allow people to say PreferTunnelledDirConns rather than
11691 PreferTunneledDirConns, for those alternate-spellers out there.
11694 - Don't reevaluate all the information from our consensus document
11695 just because we've downloaded a v2 networkstatus that we intend
11696 to cache. Fixes bug 545; bugfix on 0.2.0.x.
11699 Changes in version 0.2.0.10-alpha - 2007-11-10
11700 This tenth development snapshot adds a third v3 directory authority
11701 run by Mike Perry, adds most of Karsten Loesing's new hidden service
11702 descriptor format, fixes a bad crash bug and new bridge bugs introduced
11703 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
11704 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
11705 addresses many more minor issues.
11707 o New directory authorities:
11708 - Set up ides (run by Mike Perry) as the third v3 directory authority.
11711 - Allow tunnelled directory connections to ask for an encrypted
11712 "begin_dir" connection or an anonymized "uses a full Tor circuit"
11713 connection independently. Now we can make anonymized begin_dir
11714 connections for (e.g.) more secure hidden service posting and
11716 - More progress on proposal 114: code from Karsten Loesing to
11717 implement new hidden service descriptor format.
11718 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
11719 accommodate the growing number of servers that use the default
11720 and are reaching it.
11721 - Directory authorities use a new formula for selecting which nodes
11722 to advertise as Guards: they must be in the top 7/8 in terms of
11723 how long we have known about them, and above the median of those
11724 nodes in terms of weighted fractional uptime.
11725 - Make "not enough dir info yet" warnings describe *why* Tor feels
11726 it doesn't have enough directory info yet.
11729 - Stop servers from crashing if they set a Family option (or
11730 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
11732 - Make bridge users work again -- the move to v3 directories in
11733 0.2.0.9-alpha had introduced a number of bugs that made bridges
11734 no longer work for clients.
11735 - When the clock jumps forward a lot, do not allow the bandwidth
11736 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
11738 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
11739 - When the consensus lists a router descriptor that we previously were
11740 mirroring, but that we considered non-canonical, reload the
11741 descriptor as canonical. This fixes bug 543 where Tor servers
11742 would start complaining after a few days that they don't have
11743 enough directory information to build a circuit.
11744 - Consider replacing the current consensus when certificates arrive
11745 that make the pending consensus valid. Previously, we were only
11746 considering replacement when the new certs _didn't_ help.
11747 - Fix an assert error on startup if we didn't already have the
11748 consensus and certs cached in our datadirectory: we were caching
11749 the consensus in consensus_waiting_for_certs but then free'ing it
11751 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
11752 Request) if we need more v3 certs but we've already got pending
11753 requests for all of them.
11754 - Correctly back off from failing certificate downloads. Fixes
11756 - Authorities don't vote on the Running flag if they have been running
11757 for less than 30 minutes themselves. Fixes bug 547, where a newly
11758 started authority would vote that everyone was down.
11760 o New requirements:
11761 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
11762 it, it had no AES, and it hasn't seen any security patches since
11766 - Clients now hold circuitless TLS connections open for 1.5 times
11767 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
11768 rebuild a new circuit over them within that timeframe. Previously,
11769 they held them open only for KeepalivePeriod (5 minutes).
11770 - Use "If-Modified-Since" to avoid retrieving consensus
11771 networkstatuses that we already have.
11772 - When we have no consensus, check FallbackNetworkstatusFile (defaults
11773 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
11774 we start knowing some directory caches.
11775 - When we receive a consensus from the future, warn about skew.
11776 - Improve skew reporting: try to give the user a better log message
11777 about how skewed they are, and how much this matters.
11778 - When we have a certificate for an authority, believe that
11779 certificate's claims about the authority's IP address.
11780 - New --quiet command-line option to suppress the default console log.
11781 Good in combination with --hash-password.
11782 - Authorities send back an X-Descriptor-Not-New header in response to
11783 an accepted-but-discarded descriptor upload. Partially implements
11785 - Make the log message for "tls error. breaking." more useful.
11786 - Better log messages about certificate downloads, to attempt to
11787 track down the second incarnation of bug 546.
11789 o Minor features (bridges):
11790 - If bridge users set UpdateBridgesFromAuthority, but the digest
11791 they ask for is a 404 from the bridge authority, they now fall
11792 back to trying the bridge directly.
11793 - Bridges now use begin_dir to publish their server descriptor to
11794 the bridge authority, even when they haven't set TunnelDirConns.
11796 o Minor features (controller):
11797 - When reporting clock skew, and we know that the clock is _at least
11798 as skewed_ as some value, but we don't know the actual value,
11799 report the value as a "minimum skew."
11802 - Update linux-tor-prio.sh script to allow QoS based on the uid of
11803 the Tor process. Patch from Marco Bonetti with tweaks from Mike
11807 - Refuse to start if both ORPort and UseBridges are set. Bugfix
11808 on 0.2.0.x, suggested by Matt Edman.
11809 - Don't stop fetching descriptors when FetchUselessDescriptors is
11810 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
11811 reported by tup and ioerror.
11812 - Better log message on vote from unknown authority.
11813 - Don't log "Launching 0 request for 0 router" message.
11815 o Minor bugfixes (memory leaks):
11816 - Stop leaking memory every time we parse a v3 certificate. Bugfix
11818 - Stop leaking memory every time we load a v3 certificate. Bugfix
11819 on 0.2.0.1-alpha. Fixes bug 536.
11820 - Stop leaking a cached networkstatus on exit. Bugfix on
11822 - Stop leaking voter information every time we free a consensus.
11823 Bugfix on 0.2.0.3-alpha.
11824 - Stop leaking signed data every time we check a voter signature.
11825 Bugfix on 0.2.0.3-alpha.
11826 - Stop leaking a signature every time we fail to parse a consensus or
11827 a vote. Bugfix on 0.2.0.3-alpha.
11828 - Stop leaking v2_download_status_map on shutdown. Bugfix on
11830 - Stop leaking conn->nickname every time we make a connection to a
11831 Tor relay without knowing its expected identity digest (e.g. when
11832 using bridges). Bugfix on 0.2.0.3-alpha.
11834 - Minor bugfixes (portability):
11835 - Run correctly on platforms where rlim_t is larger than unsigned
11836 long, and/or where the real limit for number of open files is
11837 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
11838 particular, these may be needed for OS X 10.5.
11841 Changes in version 0.1.2.18 - 2007-10-28
11842 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
11843 hidden service introduction that were causing huge delays, and a big
11844 bug that was causing some servers to disappear from the network status
11845 lists for a few hours each day.
11847 o Major bugfixes (crashes):
11848 - If a connection is shut down abruptly because of something that
11849 happened inside connection_flushed_some(), do not call
11850 connection_finished_flushing(). Should fix bug 451:
11851 "connection_stop_writing: Assertion conn->write_event failed"
11852 Bugfix on 0.1.2.7-alpha.
11853 - Fix possible segfaults in functions called from
11854 rend_process_relay_cell().
11856 o Major bugfixes (hidden services):
11857 - Hidden services were choosing introduction points uniquely by
11858 hexdigest, but when constructing the hidden service descriptor
11859 they merely wrote the (potentially ambiguous) nickname.
11860 - Clients now use the v2 intro format for hidden service
11861 connections: they specify their chosen rendezvous point by identity
11862 digest rather than by (potentially ambiguous) nickname. These
11863 changes could speed up hidden service connections dramatically.
11865 o Major bugfixes (other):
11866 - Stop publishing a new server descriptor just because we get a
11867 HUP signal. This led (in a roundabout way) to some servers getting
11868 dropped from the networkstatus lists for a few hours each day.
11869 - When looking for a circuit to cannibalize, consider family as well
11870 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11871 circuit cannibalization).
11872 - When a router wasn't listed in a new networkstatus, we were leaving
11873 the flags for that router alone -- meaning it remained Named,
11874 Running, etc -- even though absence from the networkstatus means
11875 that it shouldn't be considered to exist at all anymore. Now we
11876 clear all the flags for routers that fall out of the networkstatus
11877 consensus. Fixes bug 529.
11880 - Don't try to access (or alter) the state file when running
11881 --list-fingerprint or --verify-config or --hash-password. Resolves
11883 - When generating information telling us how to extend to a given
11884 router, do not try to include the nickname if it is
11885 absent. Resolves bug 467.
11886 - Fix a user-triggerable segfault in expand_filename(). (There isn't
11887 a way to trigger this remotely.)
11888 - When sending a status event to the controller telling it that an
11889 OR address is reachable, set the port correctly. (Previously we
11890 were reporting the dir port.)
11891 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11892 command. Bugfix on 0.1.2.17.
11893 - When loading bandwidth history, do not believe any information in
11894 the future. Fixes bug 434.
11895 - When loading entry guard information, do not believe any information
11897 - When we have our clock set far in the future and generate an
11898 onion key, then re-set our clock to be correct, we should not stop
11899 the onion key from getting rotated.
11900 - On some platforms, accept() can return a broken address. Detect
11901 this more quietly, and deal accordingly. Fixes bug 483.
11902 - It's not actually an error to find a non-pending entry in the DNS
11903 cache when canceling a pending resolve. Don't log unless stuff
11904 is fishy. Resolves bug 463.
11905 - Don't reset trusted dir server list when we set a configuration
11906 option. Patch from Robert Hogan.
11907 - Don't try to create the datadir when running --verify-config or
11908 --hash-password. Resolves bug 540.
11911 Changes in version 0.2.0.9-alpha - 2007-10-24
11912 This ninth development snapshot switches clients to the new v3 directory
11913 system; allows servers to be listed in the network status even when they
11914 have the same nickname as a registered server; and fixes many other
11915 bugs including a big one that was causing some servers to disappear
11916 from the network status lists for a few hours each day.
11918 o Major features (directory system):
11919 - Clients now download v3 consensus networkstatus documents instead
11920 of v2 networkstatus documents. Clients and caches now base their
11921 opinions about routers on these consensus documents. Clients only
11922 download router descriptors listed in the consensus.
11923 - Authorities now list servers who have the same nickname as
11924 a different named server, but list them with a new flag,
11925 "Unnamed". Now we can list servers that happen to pick the same
11926 nickname as a server that registered two years ago and then
11927 disappeared. Partially implements proposal 122.
11928 - If the consensus lists a router as "Unnamed", the name is assigned
11929 to a different router: do not identify the router by that name.
11930 Partially implements proposal 122.
11931 - Authorities can now come to a consensus on which method to use to
11932 compute the consensus. This gives us forward compatibility.
11935 - Stop publishing a new server descriptor just because we HUP or
11936 when we find our DirPort to be reachable but won't actually publish
11937 it. New descriptors without any real changes are dropped by the
11938 authorities, and can screw up our "publish every 18 hours" schedule.
11940 - When a router wasn't listed in a new networkstatus, we were leaving
11941 the flags for that router alone -- meaning it remained Named,
11942 Running, etc -- even though absence from the networkstatus means
11943 that it shouldn't be considered to exist at all anymore. Now we
11944 clear all the flags for routers that fall out of the networkstatus
11945 consensus. Fixes bug 529; bugfix on 0.1.2.x.
11946 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
11947 extrainfo documents and then discard them immediately for not
11948 matching the latest router. Bugfix on 0.2.0.1-alpha.
11950 o Minor features (v3 directory protocol):
11951 - Allow tor-gencert to generate a new certificate without replacing
11953 - Allow certificates to include an address.
11954 - When we change our directory-cache settings, reschedule all voting
11955 and download operations.
11956 - Reattempt certificate downloads immediately on failure, as long as
11957 we haven't failed a threshold number of times yet.
11958 - Delay retrying consensus downloads while we're downloading
11959 certificates to verify the one we just got. Also, count getting a
11960 consensus that we already have (or one that isn't valid) as a failure,
11961 and count failing to get the certificates after 20 minutes as a
11963 - Build circuits and download descriptors even if our consensus is a
11964 little expired. (This feature will go away once authorities are
11967 o Minor features (router descriptor cache):
11968 - If we find a cached-routers file that's been sitting around for more
11969 than 28 days unmodified, then most likely it's a leftover from
11970 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
11972 - When we (as a cache) download a descriptor because it was listed
11973 in a consensus, remember when the consensus was supposed to expire,
11974 and don't expire the descriptor until then.
11976 o Minor features (performance):
11977 - Call routerlist_remove_old_routers() much less often. This should
11978 speed startup, especially on directory caches.
11979 - Don't try to launch new descriptor downloads quite so often when we
11980 already have enough directory information to build circuits.
11981 - Base64 decoding was actually showing up on our profile when parsing
11982 the initial descriptor file; switch to an in-process all-at-once
11983 implementation that's about 3.5x times faster than calling out to
11986 o Minor features (compilation):
11987 - Detect non-ASCII platforms (if any still exist) and refuse to
11988 build there: some of our code assumes that 'A' is 65 and so on.
11990 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
11991 - Make the "next period" votes into "current period" votes immediately
11992 after publishing the consensus; avoid a heisenbug that made them
11993 stick around indefinitely.
11994 - When we discard a vote as a duplicate, do not report this as
11996 - Treat missing v3 keys or certificates as an error when running as a
11997 v3 directory authority.
11998 - When we're configured to be a v3 authority, but we're only listed
11999 as a non-v3 authority in our DirServer line for ourself, correct
12001 - If an authority doesn't have a qualified hostname, just put
12002 its address in the vote. This fixes the problem where we referred to
12003 "moria on moria:9031."
12004 - Distinguish between detached signatures for the wrong period, and
12005 detached signatures for a divergent vote.
12006 - Fix a small memory leak when computing a consensus.
12007 - When there's no concensus, we were forming a vote every 30
12008 minutes, but writing the "valid-after" line in our vote based
12009 on our configured V3AuthVotingInterval: so unless the intervals
12010 matched up, we immediately rejected our own vote because it didn't
12011 start at the voting interval that caused us to construct a vote.
12013 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
12014 - Delete unverified-consensus when the real consensus is set.
12015 - Consider retrying a consensus networkstatus fetch immediately
12016 after one fails: don't wait 60 seconds to notice.
12017 - When fetching a consensus as a cache, wait until a newer consensus
12018 should exist before trying to replace the current one.
12019 - Use a more forgiving schedule for retrying failed consensus
12020 downloads than for other types.
12022 o Minor bugfixes (other directory issues):
12023 - Correct the implementation of "download votes by digest." Bugfix on
12025 - Authorities no longer send back "400 you're unreachable please fix
12026 it" errors to Tor servers that aren't online all the time. We're
12027 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
12029 o Minor bugfixes (controller):
12030 - Don't reset trusted dir server list when we set a configuration
12031 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
12032 - Respond to INT and TERM SIGNAL commands before we execute the
12033 signal, in case the signal shuts us down. We had a patch in
12034 0.1.2.1-alpha that tried to do this by queueing the response on
12035 the connection's buffer before shutting down, but that really
12036 isn't the same thing at all. Bug located by Matt Edman.
12038 o Minor bugfixes (misc):
12039 - Correctly check for bad options to the "PublishServerDescriptor"
12040 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
12041 - Stop leaking memory on failing case of base32_decode, and make
12042 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
12043 - Don't try to download extrainfo documents when we're trying to
12044 fetch enough directory info to build a circuit: having enough
12045 info should get priority. Bugfix on 0.2.0.x.
12046 - Don't complain that "your server has not managed to confirm that its
12047 ports are reachable" if we haven't been able to build any circuits
12048 yet. Bug found by spending four hours without a v3 consensus. Bugfix
12050 - Detect the reason for failing to mmap a descriptor file we just
12051 wrote, and give a more useful log message. Fixes bug 533. Bugfix
12054 o Code simplifications and refactoring:
12055 - Remove support for the old bw_accounting file: we've been storing
12056 bandwidth accounting information in the state file since
12057 0.1.2.5-alpha. This may result in bandwidth accounting errors
12058 if you try to upgrade from 0.1.1.x or earlier, or if you try to
12059 downgrade to 0.1.1.x or earlier.
12060 - New convenience code to locate a file within the DataDirectory.
12061 - Move non-authority functionality out of dirvote.c.
12062 - Refactor the arguments for router_pick_{directory_|trusteddir}server
12063 so that they all take the same named flags.
12066 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
12067 Unix users an easy way to script their Tor process (e.g. by
12068 adjusting bandwidth based on the time of the day).
12071 Changes in version 0.2.0.8-alpha - 2007-10-12
12072 This eighth development snapshot fixes a crash bug that's been bothering
12073 us since February 2007, lets bridge authorities store a list of bridge
12074 descriptors they've seen, gets v3 directory voting closer to working,
12075 starts caching v3 directory consensus documents on directory mirrors,
12076 and fixes a variety of smaller issues including some minor memory leaks.
12078 o Major features (router descriptor cache):
12079 - Store routers in a file called cached-descriptors instead of in
12080 cached-routers. Initialize cached-descriptors from cached-routers
12081 if the old format is around. The new format allows us to store
12082 annotations along with descriptors.
12083 - Use annotations to record the time we received each descriptor, its
12084 source, and its purpose.
12085 - Disable the SETROUTERPURPOSE controller command: it is now
12087 - Controllers should now specify cache=no or cache=yes when using
12088 the +POSTDESCRIPTOR command.
12089 - Bridge authorities now write bridge descriptors to disk, meaning
12090 we can export them to other programs and begin distributing them
12093 o Major features (directory authorities):
12094 - When a v3 authority is missing votes or signatures, it now tries
12096 - Directory authorities track weighted fractional uptime as well as
12097 weighted mean-time-between failures. WFU is suitable for deciding
12098 whether a node is "usually up", while MTBF is suitable for deciding
12099 whether a node is "likely to stay up." We need both, because
12100 "usually up" is a good requirement for guards, while "likely to
12101 stay up" is a good requirement for long-lived connections.
12103 o Major features (v3 directory system):
12104 - Caches now download v3 network status documents as needed,
12105 and download the descriptors listed in them.
12106 - All hosts now attempt to download and keep fresh v3 authority
12107 certificates, and re-attempt after failures.
12108 - More internal-consistency checks for vote parsing.
12110 o Major bugfixes (crashes):
12111 - If a connection is shut down abruptly because of something that
12112 happened inside connection_flushed_some(), do not call
12113 connection_finished_flushing(). Should fix bug 451. Bugfix on
12116 o Major bugfixes (performance):
12117 - Fix really bad O(n^2) performance when parsing a long list of
12118 routers: Instead of searching the entire list for an "extra-info "
12119 string which usually wasn't there, once for every routerinfo
12120 we read, just scan lines forward until we find one we like.
12122 - When we add data to a write buffer in response to the data on that
12123 write buffer getting low because of a flush, do not consider the
12124 newly added data as a candidate for immediate flushing, but rather
12125 make it wait until the next round of writing. Otherwise, we flush
12126 and refill recursively, and a single greedy TLS connection can
12127 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
12129 o Minor features (v3 authority system):
12130 - Add more ways for tools to download the votes that lead to the
12132 - Send a 503 when low on bandwidth and a vote, consensus, or
12133 certificate is requested.
12134 - If-modified-since is now implemented properly for all kinds of
12135 certificate requests.
12137 o Minor bugfixes (network statuses):
12138 - Tweak the implementation of proposal 109 slightly: allow at most
12139 two Tor servers on the same IP address, except if it's the location
12140 of a directory authority, in which case allow five. Bugfix on
12143 o Minor bugfixes (controller):
12144 - When sending a status event to the controller telling it that an
12145 OR address is reachable, set the port correctly. (Previously we
12146 were reporting the dir port.) Bugfix on 0.1.2.x.
12148 o Minor bugfixes (v3 directory system):
12149 - Fix logic to look up a cert by its signing key digest. Bugfix on
12151 - Only change the reply to a vote to "OK" if it's not already
12152 set. This gets rid of annoying "400 OK" log messages, which may
12153 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
12154 - When we get a valid consensus, recompute the voting schedule.
12155 - Base the valid-after time of a vote on the consensus voting
12156 schedule, not on our preferred schedule.
12157 - Make the return values and messages from signature uploads and
12158 downloads more sensible.
12159 - Fix a memory leak when serving votes and consensus documents, and
12160 another when serving certificates.
12162 o Minor bugfixes (performance):
12163 - Use a slightly simpler string hashing algorithm (copying Python's
12164 instead of Java's) and optimize our digest hashing algorithm to take
12165 advantage of 64-bit platforms and to remove some possibly-costly
12167 - Fix a minor memory leak whenever we parse guards from our state
12168 file. Bugfix on 0.2.0.7-alpha.
12169 - Fix a minor memory leak whenever we write out a file. Bugfix on
12171 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
12172 command. Bugfix on 0.2.0.5-alpha.
12174 o Minor bugfixes (portability):
12175 - On some platforms, accept() can return a broken address. Detect
12176 this more quietly, and deal accordingly. Fixes bug 483.
12177 - Stop calling tor_strlower() on uninitialized memory in some cases.
12178 Bugfix in 0.2.0.7-alpha.
12180 o Minor bugfixes (usability):
12181 - Treat some 403 responses from directory servers as INFO rather than
12182 WARN-severity events.
12183 - It's not actually an error to find a non-pending entry in the DNS
12184 cache when canceling a pending resolve. Don't log unless stuff is
12185 fishy. Resolves bug 463.
12187 o Minor bugfixes (anonymity):
12188 - Never report that we've used more bandwidth than we're willing to
12189 relay: it leaks how much non-relay traffic we're using. Resolves
12191 - When looking for a circuit to cannibalize, consider family as well
12192 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12193 circuit cannibalization).
12195 o Code simplifications and refactoring:
12196 - Make a bunch of functions static. Remove some dead code.
12197 - Pull out about a third of the really big routerlist.c; put it in a
12198 new module, networkstatus.c.
12199 - Merge the extra fields in local_routerstatus_t back into
12200 routerstatus_t: we used to need one routerstatus_t for each
12201 authority's opinion, plus a local_routerstatus_t for the locally
12202 computed consensus opinion. To save space, we put the locally
12203 modified fields into local_routerstatus_t, and only the common
12204 stuff into routerstatus_t. But once v3 directories are in use,
12205 clients and caches will no longer need to hold authority opinions;
12206 thus, the rationale for keeping the types separate is now gone.
12207 - Make the code used to reschedule and reattempt downloads more
12209 - Turn all 'Are we a directory server/mirror?' logic into a call to
12211 - Remove the code to generate the oldest (v1) directory format.
12212 The code has been disabled since 0.2.0.5-alpha.
12215 Changes in version 0.2.0.7-alpha - 2007-09-21
12216 This seventh development snapshot makes bridges work again, makes bridge
12217 authorities work for the first time, fixes two huge performance flaws
12218 in hidden services, and fixes a variety of minor issues.
12220 o New directory authorities:
12221 - Set up moria1 and tor26 as the first v3 directory authorities. See
12222 doc/spec/dir-spec.txt for details on the new directory design.
12224 o Major bugfixes (crashes):
12225 - Fix possible segfaults in functions called from
12226 rend_process_relay_cell(). Bugfix on 0.1.2.x.
12228 o Major bugfixes (bridges):
12229 - Fix a bug that made servers send a "404 Not found" in response to
12230 attempts to fetch their server descriptor. This caused Tor servers
12231 to take many minutes to establish reachability for their DirPort,
12232 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
12233 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
12234 users configure that and specify a bridge with an identity
12235 fingerprint, now they will lookup the bridge descriptor at the
12236 default bridge authority via a one-hop tunnel, but once circuits
12237 are established they will switch to a three-hop tunnel for later
12238 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
12240 o Major bugfixes (hidden services):
12241 - Hidden services were choosing introduction points uniquely by
12242 hexdigest, but when constructing the hidden service descriptor
12243 they merely wrote the (potentially ambiguous) nickname.
12244 - Clients now use the v2 intro format for hidden service
12245 connections: they specify their chosen rendezvous point by identity
12246 digest rather than by (potentially ambiguous) nickname. Both
12247 are bugfixes on 0.1.2.x, and they could speed up hidden service
12248 connections dramatically. Thanks to Karsten Loesing.
12250 o Minor features (security):
12251 - As a client, do not believe any server that tells us that an
12252 address maps to an internal address space.
12253 - Make it possible to enable HashedControlPassword and
12254 CookieAuthentication at the same time.
12256 o Minor features (guard nodes):
12257 - Tag every guard node in our state file with the version that
12258 we believe added it, or with our own version if we add it. This way,
12259 if a user temporarily runs an old version of Tor and then switches
12260 back to a new one, she doesn't automatically lose her guards.
12262 o Minor features (speed):
12263 - When implementing AES counter mode, update only the portions of the
12264 counter buffer that need to change, and don't keep separate
12265 network-order and host-order counters when they are the same (i.e.,
12266 on big-endian hosts.)
12268 o Minor features (controller):
12269 - Accept LF instead of CRLF on controller, since some software has a
12270 hard time generating real Internet newlines.
12271 - Add GETINFO values for the server status events
12272 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
12275 o Removed features:
12276 - Routers no longer include bandwidth-history lines in their
12277 descriptors; this information is already available in extra-info
12278 documents, and including it in router descriptors took up 60%
12279 (!) of compressed router descriptor downloads. Completes
12280 implementation of proposal 104.
12281 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
12282 and TorControl.py, as they use the old v0 controller protocol,
12283 and are obsoleted by TorFlow anyway.
12284 - Drop support for v1 rendezvous descriptors, since we never used
12285 them anyway, and the code has probably rotted by now. Based on
12286 patch from Karsten Loesing.
12287 - On OSX, stop warning the user that kqueue support in libevent is
12288 "experimental", since it seems to have worked fine for ages.
12291 - When generating information telling us how to extend to a given
12292 router, do not try to include the nickname if it is absent. Fixes
12293 bug 467. Bugfix on 0.2.0.3-alpha.
12294 - Fix a user-triggerable (but not remotely-triggerable) segfault
12295 in expand_filename(). Bugfix on 0.1.2.x.
12296 - Fix a memory leak when freeing incomplete requests from DNSPort.
12297 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
12298 - Don't try to access (or alter) the state file when running
12299 --list-fingerprint or --verify-config or --hash-password. (Resolves
12300 bug 499.) Bugfix on 0.1.2.x.
12301 - Servers used to decline to publish their DirPort if their
12302 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
12303 were below a threshold. Now they only look at BandwidthRate and
12304 RelayBandwidthRate. Bugfix on 0.1.2.x.
12305 - Remove an optimization in the AES counter-mode code that assumed
12306 that the counter never exceeded 2^68. When the counter can be set
12307 arbitrarily as an IV (as it is by Karsten's new hidden services
12308 code), this assumption no longer holds. Bugfix on 0.1.2.x.
12309 - Resume listing "AUTHORITY" flag for authorities in network status.
12310 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
12312 o Code simplifications and refactoring:
12313 - Revamp file-writing logic so we don't need to have the entire
12314 contents of a file in memory at once before we write to disk. Tor,
12316 - Turn "descriptor store" into a full-fledged type.
12317 - Move all NT services code into a separate source file.
12318 - Unify all code that computes medians, percentile elements, etc.
12319 - Get rid of a needless malloc when parsing address policies.
12322 Changes in version 0.1.2.17 - 2007-08-30
12323 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
12324 X bundles. Vidalia 0.0.14 makes authentication required for the
12325 ControlPort in the default configuration, which addresses important
12326 security risks. Everybody who uses Vidalia (or another controller)
12329 In addition, this Tor update fixes major load balancing problems with
12330 path selection, which should speed things up a lot once many people
12333 o Major bugfixes (security):
12334 - We removed support for the old (v0) control protocol. It has been
12335 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
12336 become more of a headache than it's worth.
12338 o Major bugfixes (load balancing):
12339 - When choosing nodes for non-guard positions, weight guards
12340 proportionally less, since they already have enough load. Patch
12342 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
12343 will allow fast Tor servers to get more attention.
12344 - When we're upgrading from an old Tor version, forget our current
12345 guards and pick new ones according to the new weightings. These
12346 three load balancing patches could raise effective network capacity
12347 by a factor of four. Thanks to Mike Perry for measurements.
12349 o Major bugfixes (stream expiration):
12350 - Expire not-yet-successful application streams in all cases if
12351 they've been around longer than SocksTimeout. Right now there are
12352 some cases where the stream will live forever, demanding a new
12353 circuit every 15 seconds. Fixes bug 454; reported by lodger.
12355 o Minor features (controller):
12356 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
12357 is valid before any authentication has been received. It tells
12358 a controller what kind of authentication is expected, and what
12359 protocol is spoken. Implements proposal 119.
12361 o Minor bugfixes (performance):
12362 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
12363 greatly speeding up loading cached-routers from disk on startup.
12364 - Disable sentinel-based debugging for buffer code: we squashed all
12365 the bugs that this was supposed to detect a long time ago, and now
12366 its only effect is to change our buffer sizes from nice powers of
12367 two (which platform mallocs tend to like) to values slightly over
12368 powers of two (which make some platform mallocs sad).
12370 o Minor bugfixes (misc):
12371 - If exit bandwidth ever exceeds one third of total bandwidth, then
12372 use the correct formula to weight exit nodes when choosing paths.
12373 Based on patch from Mike Perry.
12374 - Choose perfectly fairly among routers when choosing by bandwidth and
12375 weighting by fraction of bandwidth provided by exits. Previously, we
12376 would choose with only approximate fairness, and correct ourselves
12377 if we ran off the end of the list.
12378 - If we require CookieAuthentication but we fail to write the
12379 cookie file, we would warn but not exit, and end up in a state
12380 where no controller could authenticate. Now we exit.
12381 - If we require CookieAuthentication, stop generating a new cookie
12382 every time we change any piece of our config.
12383 - Refuse to start with certain directory authority keys, and
12384 encourage people using them to stop.
12385 - Terminate multi-line control events properly. Original patch
12387 - Fix a minor memory leak when we fail to find enough suitable
12388 servers to choose a circuit.
12389 - Stop leaking part of the descriptor when we run into a particularly
12390 unparseable piece of it.
12393 Changes in version 0.2.0.6-alpha - 2007-08-26
12394 This sixth development snapshot features a new Vidalia version in the
12395 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
12396 the ControlPort in the default configuration, which addresses important
12399 In addition, this snapshot fixes major load balancing problems
12400 with path selection, which should speed things up a lot once many
12401 people have upgraded. The directory authorities also use a new
12402 mean-time-between-failure approach to tracking which servers are stable,
12403 rather than just looking at the most recent uptime.
12405 o New directory authorities:
12406 - Set up Tonga as the default bridge directory authority.
12409 - Directory authorities now track servers by weighted
12410 mean-times-between-failures. When we have 4 or more days of data,
12411 use measured MTBF rather than declared uptime to decide whether
12412 to call a router Stable. Implements proposal 108.
12414 o Major bugfixes (load balancing):
12415 - When choosing nodes for non-guard positions, weight guards
12416 proportionally less, since they already have enough load. Patch
12418 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
12419 will allow fast Tor servers to get more attention.
12420 - When we're upgrading from an old Tor version, forget our current
12421 guards and pick new ones according to the new weightings. These
12422 three load balancing patches could raise effective network capacity
12423 by a factor of four. Thanks to Mike Perry for measurements.
12425 o Major bugfixes (descriptor parsing):
12426 - Handle unexpected whitespace better in malformed descriptors. Bug
12427 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
12430 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
12431 GETINFO for Torstat to use until it can switch to using extrainfos.
12432 - Optionally (if built with -DEXPORTMALLINFO) export the output
12433 of mallinfo via http, as tor/mallinfo.txt. Only accessible
12437 - Do not intermix bridge routers with controller-added
12438 routers. (Bugfix on 0.2.0.x)
12439 - Do not fail with an assert when accept() returns an unexpected
12440 address family. Addresses but does not wholly fix bug 483. (Bugfix
12442 - Let directory authorities startup even when they can't generate
12443 a descriptor immediately, e.g. because they don't know their
12445 - Stop putting the authentication cookie in a file called "0"
12446 in your working directory if you don't specify anything for the
12447 new CookieAuthFile option. Reported by Matt Edman.
12448 - Make it possible to read the PROTOCOLINFO response in a way that
12449 conforms to our control-spec. Reported by Matt Edman.
12450 - Fix a minor memory leak when we fail to find enough suitable
12451 servers to choose a circuit. Bugfix on 0.1.2.x.
12452 - Stop leaking part of the descriptor when we run into a particularly
12453 unparseable piece of it. Bugfix on 0.1.2.x.
12454 - Unmap the extrainfo cache file on exit.
12457 Changes in version 0.2.0.5-alpha - 2007-08-19
12458 This fifth development snapshot fixes compilation on Windows again;
12459 fixes an obnoxious client-side bug that slowed things down and put
12460 extra load on the network; gets us closer to using the v3 directory
12461 voting scheme; makes it easier for Tor controllers to use cookie-based
12462 authentication; and fixes a variety of other bugs.
12464 o Removed features:
12465 - Version 1 directories are no longer generated in full. Instead,
12466 authorities generate and serve "stub" v1 directories that list
12467 no servers. This will stop Tor versions 0.1.0.x and earlier from
12468 working, but (for security reasons) nobody should be running those
12471 o Major bugfixes (compilation, 0.2.0.x):
12472 - Try to fix Win32 compilation again: improve checking for IPv6 types.
12473 - Try to fix MSVC compilation: build correctly on platforms that do
12474 not define s6_addr16 or s6_addr32.
12475 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
12478 o Major bugfixes (stream expiration):
12479 - Expire not-yet-successful application streams in all cases if
12480 they've been around longer than SocksTimeout. Right now there are
12481 some cases where the stream will live forever, demanding a new
12482 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
12483 reported by lodger.
12485 o Minor features (directory servers):
12486 - When somebody requests a list of statuses or servers, and we have
12487 none of those, return a 404 rather than an empty 200.
12489 o Minor features (directory voting):
12490 - Store v3 consensus status consensuses on disk, and reload them
12493 o Minor features (security):
12494 - Warn about unsafe ControlPort configurations.
12495 - Refuse to start with certain directory authority keys, and
12496 encourage people using them to stop.
12498 o Minor features (controller):
12499 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
12500 is valid before any authentication has been received. It tells
12501 a controller what kind of authentication is expected, and what
12502 protocol is spoken. Implements proposal 119.
12503 - New config option CookieAuthFile to choose a new location for the
12504 cookie authentication file, and config option
12505 CookieAuthFileGroupReadable to make it group-readable.
12507 o Minor features (unit testing):
12508 - Add command-line arguments to unit-test executable so that we can
12509 invoke any chosen test from the command line rather than having
12510 to run the whole test suite at once; and so that we can turn on
12511 logging for the unit tests.
12513 o Minor bugfixes (on 0.1.2.x):
12514 - If we require CookieAuthentication but we fail to write the
12515 cookie file, we would warn but not exit, and end up in a state
12516 where no controller could authenticate. Now we exit.
12517 - If we require CookieAuthentication, stop generating a new cookie
12518 every time we change any piece of our config.
12519 - When loading bandwidth history, do not believe any information in
12520 the future. Fixes bug 434.
12521 - When loading entry guard information, do not believe any information
12523 - When we have our clock set far in the future and generate an
12524 onion key, then re-set our clock to be correct, we should not stop
12525 the onion key from getting rotated.
12526 - Clean up torrc sample config file.
12527 - Do not automatically run configure from autogen.sh. This
12528 non-standard behavior tended to annoy people who have built other
12531 o Minor bugfixes (on 0.2.0.x):
12532 - Fix a bug with AutomapHostsOnResolve that would always cause
12533 the second request to fail. Bug reported by Kate. Bugfix on
12535 - Fix a bug in ADDRMAP controller replies that would sometimes
12536 try to print a NULL. Patch from tup.
12537 - Read v3 directory authority keys from the right location.
12538 - Numerous bugfixes to directory voting code.
12541 Changes in version 0.1.2.16 - 2007-08-01
12542 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
12543 remote attacker in certain situations to rewrite the user's torrc
12544 configuration file. This can completely compromise anonymity of users
12545 in most configurations, including those running the Vidalia bundles,
12546 TorK, etc. Or worse.
12548 o Major security fixes:
12549 - Close immediately after missing authentication on control port;
12550 do not allow multiple authentication attempts.
12553 Changes in version 0.2.0.4-alpha - 2007-08-01
12554 This fourth development snapshot fixes a critical security vulnerability
12555 for most users, specifically those running Vidalia, TorK, etc. Everybody
12556 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
12558 o Major security fixes:
12559 - Close immediately after missing authentication on control port;
12560 do not allow multiple authentication attempts.
12562 o Major bugfixes (compilation):
12563 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
12566 o Minor features (performance):
12567 - Be even more aggressive about releasing RAM from small
12568 empty buffers. Thanks to our free-list code, this shouldn't be too
12569 performance-intensive.
12570 - Disable sentinel-based debugging for buffer code: we squashed all
12571 the bugs that this was supposed to detect a long time ago, and
12572 now its only effect is to change our buffer sizes from nice
12573 powers of two (which platform mallocs tend to like) to values
12574 slightly over powers of two (which make some platform mallocs sad).
12575 - Log malloc statistics from mallinfo() on platforms where it
12579 Changes in version 0.2.0.3-alpha - 2007-07-29
12580 This third development snapshot introduces new experimental
12581 blocking-resistance features and a preliminary version of the v3
12582 directory voting design, and includes many other smaller features
12586 - The first pieces of our "bridge" design for blocking-resistance
12587 are implemented. People can run bridge directory authorities;
12588 people can run bridges; and people can configure their Tor clients
12589 with a set of bridges to use as the first hop into the Tor network.
12590 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
12592 - Create listener connections before we setuid to the configured
12593 User and Group. Now non-Windows users can choose port values
12594 under 1024, start Tor as root, and have Tor bind those ports
12595 before it changes to another UID. (Windows users could already
12597 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
12598 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
12599 on "vserver" accounts. (Patch from coderman.)
12600 - Be even more aggressive about separating local traffic from relayed
12601 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
12603 o Major features (experimental):
12604 - First cut of code for "v3 dir voting": directory authorities will
12605 vote on a common network status document rather than each publishing
12606 their own opinion. This code needs more testing and more corner-case
12607 handling before it's ready for use.
12610 - Directory authorities now call routers Fast if their bandwidth is
12611 at least 100KB/s, and consider their bandwidth adequate to be a
12612 Guard if it is at least 250KB/s, no matter the medians. This fix
12613 complements proposal 107. [Bugfix on 0.1.2.x]
12614 - Directory authorities now never mark more than 3 servers per IP as
12615 Valid and Running. (Implements proposal 109, by Kevin Bauer and
12617 - Minor change to organizationName and commonName generation
12618 procedures in TLS certificates during Tor handshakes, to invalidate
12619 some earlier censorware approaches. This is not a long-term
12620 solution, but applying it will give us a bit of time to look into
12621 the epidemiology of countermeasures as they spread.
12623 o Major bugfixes (directory):
12624 - Rewrite directory tokenization code to never run off the end of
12625 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
12627 o Minor features (controller):
12628 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
12629 match requests to applications. (Patch from Robert Hogan.)
12630 - Report address and port correctly on connections to DNSPort. (Patch
12631 from Robert Hogan.)
12632 - Add a RESOLVE command to launch hostname lookups. (Original patch
12633 from Robert Hogan.)
12634 - Add GETINFO status/enough-dir-info to let controllers tell whether
12635 Tor has downloaded sufficient directory information. (Patch
12637 - You can now use the ControlSocket option to tell Tor to listen for
12638 controller connections on Unix domain sockets on systems that
12639 support them. (Patch from Peter Palfrader.)
12640 - STREAM NEW events are generated for DNSPort requests and for
12641 tunneled directory connections. (Patch from Robert Hogan.)
12642 - New "GETINFO address-mappings/*" command to get address mappings
12643 with expiry information. "addr-mappings/*" is now deprecated.
12646 o Minor features (misc):
12647 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
12649 - The tor-gencert tool for v3 directory authorities now creates all
12650 files as readable to the file creator only, and write-protects
12651 the authority identity key.
12652 - When dumping memory usage, list bytes used in buffer memory
12654 - When running with dmalloc, dump more stats on hup and on exit.
12655 - Directory authorities now fail quickly and (relatively) harmlessly
12656 if they generate a network status document that is somehow
12659 o Traffic load balancing improvements:
12660 - If exit bandwidth ever exceeds one third of total bandwidth, then
12661 use the correct formula to weight exit nodes when choosing paths.
12662 (Based on patch from Mike Perry.)
12663 - Choose perfectly fairly among routers when choosing by bandwidth and
12664 weighting by fraction of bandwidth provided by exits. Previously, we
12665 would choose with only approximate fairness, and correct ourselves
12666 if we ran off the end of the list. [Bugfix on 0.1.2.x]
12668 o Performance improvements:
12669 - Be more aggressive with freeing buffer RAM or putting it on the
12671 - Use Critical Sections rather than Mutexes for synchronizing threads
12672 on win32; Mutexes are heavier-weight, and designed for synchronizing
12675 o Deprecated and removed features:
12676 - RedirectExits is now deprecated.
12677 - Stop allowing address masks that do not correspond to bit prefixes.
12678 We have warned about these for a really long time; now it's time
12679 to reject them. (Patch from croup.)
12681 o Minor bugfixes (directory):
12682 - Fix another crash bug related to extra-info caching. (Bug found by
12683 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
12684 - Directories no longer return a "304 not modified" when they don't
12685 have the networkstatus the client asked for. Also fix a memory
12686 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
12687 - We had accidentally labelled 0.1.2.x directory servers as not
12688 suitable for begin_dir requests, and had labelled no directory
12689 servers as suitable for uploading extra-info documents. [Bugfix
12692 o Minor bugfixes (dns):
12693 - Fix a crash when DNSPort is set more than once. (Patch from Robert
12694 Hogan.) [Bugfix on 0.2.0.2-alpha]
12695 - Add DNSPort connections to the global connection list, so that we
12696 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
12698 - Fix a dangling reference that could lead to a crash when DNSPort is
12699 changed or closed (Patch from Robert Hogan.) [Bugfix on
12702 o Minor bugfixes (controller):
12703 - Provide DNS expiry times in GMT, not in local time. For backward
12704 compatibility, ADDRMAP events only provide GMT expiry in an extended
12705 field. "GETINFO address-mappings" always does the right thing.
12706 - Use CRLF line endings properly in NS events.
12707 - Terminate multi-line control events properly. (Original patch
12708 from tup.) [Bugfix on 0.1.2.x-alpha]
12709 - Do not include spaces in SOURCE_ADDR fields in STREAM
12710 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
12713 Changes in version 0.1.2.15 - 2007-07-17
12714 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
12715 problems, fixes compilation on BSD, and fixes a variety of other
12716 bugs. Everybody should upgrade.
12718 o Major bugfixes (compilation):
12719 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
12721 o Major bugfixes (crashes):
12722 - Try even harder not to dereference the first character after
12723 an mmap(). Reported by lodger.
12724 - Fix a crash bug in directory authorities when we re-number the
12725 routerlist while inserting a new router.
12726 - When the cached-routers file is an even multiple of the page size,
12727 don't run off the end and crash. (Fixes bug 455; based on idea
12729 - Fix eventdns.c behavior on Solaris: It is critical to include
12730 orconfig.h _before_ sys/types.h, so that we can get the expected
12731 definition of _FILE_OFFSET_BITS.
12733 o Major bugfixes (security):
12734 - Fix a possible buffer overrun when using BSD natd support. Bug
12736 - When sending destroy cells from a circuit's origin, don't include
12737 the reason for tearing down the circuit. The spec says we didn't,
12738 and now we actually don't. Reported by lodger.
12739 - Keep streamids from different exits on a circuit separate. This
12740 bug may have allowed other routers on a given circuit to inject
12741 cells into streams. Reported by lodger; fixes bug 446.
12742 - If there's a never-before-connected-to guard node in our list,
12743 never choose any guards past it. This way we don't expand our
12744 guard list unless we need to.
12746 o Minor bugfixes (guard nodes):
12747 - Weight guard selection by bandwidth, so that low-bandwidth nodes
12748 don't get overused as guards.
12750 o Minor bugfixes (directory):
12751 - Correctly count the number of authorities that recommend each
12752 version. Previously, we were under-counting by 1.
12753 - Fix a potential crash bug when we load many server descriptors at
12754 once and some of them make others of them obsolete. Fixes bug 458.
12756 o Minor bugfixes (hidden services):
12757 - Stop tearing down the whole circuit when the user asks for a
12758 connection to a port that the hidden service didn't configure.
12761 o Minor bugfixes (misc):
12762 - On Windows, we were preventing other processes from reading
12763 cached-routers while Tor was running. Reported by janbar.
12764 - Fix a possible (but very unlikely) bug in picking routers by
12765 bandwidth. Add a log message to confirm that it is in fact
12766 unlikely. Patch from lodger.
12767 - Backport a couple of memory leak fixes.
12768 - Backport miscellaneous cosmetic bugfixes.
12771 Changes in version 0.2.0.2-alpha - 2007-06-02
12772 o Major bugfixes on 0.2.0.1-alpha:
12773 - Fix an assertion failure related to servers without extra-info digests.
12774 Resolves bugs 441 and 442.
12776 o Minor features (directory):
12777 - Support "If-Modified-Since" when answering HTTP requests for
12778 directories, running-routers documents, and network-status documents.
12779 (There's no need to support it for router descriptors, since those
12780 are downloaded by descriptor digest.)
12782 o Minor build issues:
12783 - Clear up some MIPSPro compiler warnings.
12784 - When building from a tarball on a machine that happens to have SVK
12785 installed, report the micro-revision as whatever version existed
12786 in the tarball, not as "x".
12789 Changes in version 0.2.0.1-alpha - 2007-06-01
12790 This early development snapshot provides new features for people running
12791 Tor as both a client and a server (check out the new RelayBandwidth
12792 config options); lets Tor run as a DNS proxy; and generally moves us
12793 forward on a lot of fronts.
12795 o Major features, server usability:
12796 - New config options RelayBandwidthRate and RelayBandwidthBurst:
12797 a separate set of token buckets for relayed traffic. Right now
12798 relayed traffic is defined as answers to directory requests, and
12799 OR connections that don't have any local circuits on them.
12801 o Major features, client usability:
12802 - A client-side DNS proxy feature to replace the need for
12803 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
12804 for DNS requests on port 9999, use the Tor network to resolve them
12805 anonymously, and send the reply back like a regular DNS server.
12806 The code still only implements a subset of DNS.
12807 - Make PreferTunneledDirConns and TunnelDirConns work even when
12808 we have no cached directory info. This means Tor clients can now
12809 do all of their connections protected by TLS.
12811 o Major features, performance and efficiency:
12812 - Directory authorities accept and serve "extra info" documents for
12813 routers. These documents contain fields from router descriptors
12814 that aren't usually needed, and that use a lot of excess
12815 bandwidth. Once these fields are removed from router descriptors,
12816 the bandwidth savings should be about 60%. [Partially implements
12818 - Servers upload extra-info documents to any authority that accepts
12819 them. Authorities (and caches that have been configured to download
12820 extra-info documents) download them as needed. [Partially implements
12822 - Change the way that Tor buffers data that it is waiting to write.
12823 Instead of queueing data cells in an enormous ring buffer for each
12824 client->OR or OR->OR connection, we now queue cells on a separate
12825 queue for each circuit. This lets us use less slack memory, and
12826 will eventually let us be smarter about prioritizing different kinds
12828 - Use memory pools to allocate cells with better speed and memory
12829 efficiency, especially on platforms where malloc() is inefficient.
12830 - Stop reading on edge connections when their corresponding circuit
12831 buffers are full; start again as the circuits empty out.
12833 o Major features, other:
12834 - Add an HSAuthorityRecordStats option that hidden service authorities
12835 can use to track statistics of overall hidden service usage without
12836 logging information that would be very useful to an attacker.
12837 - Start work implementing multi-level keys for directory authorities:
12838 Add a standalone tool to generate key certificates. (Proposal 103.)
12841 - Directory authorities now call routers Stable if they have an
12842 uptime of at least 30 days, even if that's not the median uptime
12843 in the network. Implements proposal 107, suggested by Kevin Bauer
12846 o Minor fixes (resource management):
12847 - Count the number of open sockets separately from the number
12848 of active connection_t objects. This will let us avoid underusing
12849 our allocated connection limit.
12850 - We no longer use socket pairs to link an edge connection to an
12851 anonymous directory connection or a DirPort test connection.
12852 Instead, we track the link internally and transfer the data
12853 in-process. This saves two sockets per "linked" connection (at the
12854 client and at the server), and avoids the nasty Windows socketpair()
12856 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
12857 for every single inactive connection_t. Free items from the
12858 4k/16k-buffer free lists when they haven't been used for a while.
12860 o Minor features (build):
12861 - Make autoconf search for libevent, openssl, and zlib consistently.
12862 - Update deprecated macros in configure.in.
12863 - When warning about missing headers, tell the user to let us
12864 know if the compile succeeds anyway, so we can downgrade the
12866 - Include the current subversion revision as part of the version
12867 string: either fetch it directly if we're in an SVN checkout, do
12868 some magic to guess it if we're in an SVK checkout, or use
12869 the last-detected version if we're building from a .tar.gz.
12870 Use this version consistently in log messages.
12872 o Minor features (logging):
12873 - Always prepend "Bug: " to any log message about a bug.
12874 - Put a platform string (e.g. "Linux i686") in the startup log
12875 message, so when people paste just their logs, we know if it's
12876 OpenBSD or Windows or what.
12877 - When logging memory usage, break down memory used in buffers by
12880 o Minor features (directory system):
12881 - New config option V2AuthoritativeDirectory that all directory
12882 authorities should set. This will let future authorities choose
12883 not to serve V2 directory information.
12884 - Directory authorities allow multiple router descriptors and/or extra
12885 info documents to be uploaded in a single go. This will make
12886 implementing proposal 104 simpler.
12888 o Minor features (controller):
12889 - Add a new config option __DisablePredictedCircuits designed for
12890 use by the controller, when we don't want Tor to build any circuits
12892 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
12893 so we can exit from the middle of the circuit.
12894 - Implement "getinfo status/circuit-established".
12895 - Implement "getinfo status/version/..." so a controller can tell
12896 whether the current version is recommended, and whether any versions
12897 are good, and how many authorities agree. (Patch from shibz.)
12899 o Minor features (hidden services):
12900 - Allow multiple HiddenServicePort directives with the same virtual
12901 port; when they occur, the user is sent round-robin to one
12902 of the target ports chosen at random. Partially fixes bug 393 by
12903 adding limited ad-hoc round-robining.
12905 o Minor features (other):
12907 - Add a new AutomapHostsOnResolve option: when it is enabled, any
12908 resolve request for hosts matching a given pattern causes Tor to
12909 generate an internal virtual address mapping for that host. This
12910 allows DNSPort to work sensibly with hidden service users. By
12911 default, .exit and .onion addresses are remapped; the list of
12912 patterns can be reconfigured with AutomapHostsSuffixes.
12913 - Add an "-F" option to tor-resolve to force a resolve for a .onion
12914 address. Thanks to the AutomapHostsOnResolve option, this is no
12915 longer a completely silly thing to do.
12916 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
12917 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
12918 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
12919 minus 1 byte: the actual maximum declared bandwidth.
12921 o Removed features:
12922 - Removed support for the old binary "version 0" controller protocol.
12923 This has been deprecated since 0.1.1, and warnings have been issued
12924 since 0.1.2. When we encounter a v0 control message, we now send
12925 back an error and close the connection.
12926 - Remove the old "dns worker" server DNS code: it hasn't been default
12927 since 0.1.2.2-alpha, and all the servers seem to be using the new
12930 o Minor bugfixes (portability):
12931 - Even though Windows is equally happy with / and \ as path separators,
12932 try to use \ consistently on Windows and / consistently on Unix: it
12933 makes the log messages nicer.
12934 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
12935 - Read resolv.conf files correctly on platforms where read() returns
12936 partial results on small file reads.
12938 o Minor bugfixes (directory):
12939 - Correctly enforce that elements of directory objects do not appear
12940 more often than they are allowed to appear.
12941 - When we are reporting the DirServer line we just parsed, we were
12942 logging the second stanza of the key fingerprint, not the first.
12944 o Minor bugfixes (logging):
12945 - When we hit an EOF on a log (probably because we're shutting down),
12946 don't try to remove the log from the list: just mark it as
12947 unusable. (Bulletproofs against bug 222.)
12949 o Minor bugfixes (other):
12950 - In the exitlist script, only consider the most recently published
12951 server descriptor for each server. Also, when the user requests
12952 a list of servers that _reject_ connections to a given address,
12953 explicitly exclude the IPs that also have servers that accept
12954 connections to that address. (Resolves bug 405.)
12955 - Stop allowing hibernating servers to be "stable" or "fast".
12956 - On Windows, we were preventing other processes from reading
12957 cached-routers while Tor was running. (Reported by janbar)
12958 - Make the NodeFamilies config option work. (Reported by
12959 lodger -- it has never actually worked, even though we added it
12961 - Check return values from pthread_mutex functions.
12962 - Don't save non-general-purpose router descriptors to the disk cache,
12963 because we have no way of remembering what their purpose was when
12965 - Add even more asserts to hunt down bug 417.
12966 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
12967 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
12968 Add a log message to confirm that it is in fact unlikely.
12970 o Minor bugfixes (controller):
12971 - Make 'getinfo fingerprint' return a 551 error if we're not a
12972 server, so we match what the control spec claims we do. Reported
12974 - Fix a typo in an error message when extendcircuit fails that
12975 caused us to not follow the \r\n-based delimiter protocol. Reported
12978 o Code simplifications and refactoring:
12979 - Stop passing around circuit_t and crypt_path_t pointers that are
12980 implicit in other procedure arguments.
12981 - Drop the old code to choke directory connections when the
12982 corresponding OR connections got full: thanks to the cell queue
12983 feature, OR conns don't get full any more.
12984 - Make dns_resolve() handle attaching connections to circuits
12985 properly, so the caller doesn't have to.
12986 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
12987 - Keep the connection array as a dynamic smartlist_t, rather than as
12988 a fixed-sized array. This is important, as the number of connections
12989 is becoming increasingly decoupled from the number of sockets.
12992 Changes in version 0.1.2.14 - 2007-05-25
12993 Tor 0.1.2.14 changes the addresses of two directory authorities (this
12994 change especially affects those who serve or use hidden services),
12995 and fixes several other crash- and security-related bugs.
12997 o Directory authority changes:
12998 - Two directory authorities (moria1 and moria2) just moved to new
12999 IP addresses. This change will particularly affect those who serve
13000 or use hidden services.
13002 o Major bugfixes (crashes):
13003 - If a directory server runs out of space in the connection table
13004 as it's processing a begin_dir request, it will free the exit stream
13005 but leave it attached to the circuit, leading to unpredictable
13006 behavior. (Reported by seeess, fixes bug 425.)
13007 - Fix a bug in dirserv_remove_invalid() that would cause authorities
13008 to corrupt memory under some really unlikely scenarios.
13009 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
13010 - Avoid segfaults when reading from mmaped descriptor file. (Reported
13013 o Major bugfixes (security):
13014 - When choosing an entry guard for a circuit, avoid using guards
13015 that are in the same family as the chosen exit -- not just guards
13016 that are exactly the chosen exit. (Reported by lodger.)
13018 o Major bugfixes (resource management):
13019 - If a directory authority is down, skip it when deciding where to get
13020 networkstatus objects or descriptors. Otherwise we keep asking
13021 every 10 seconds forever. Fixes bug 384.
13022 - Count it as a failure if we fetch a valid network-status but we
13023 don't want to keep it. Otherwise we'll keep fetching it and keep
13024 not wanting to keep it. Fixes part of bug 422.
13025 - If all of our dirservers have given us bad or no networkstatuses
13026 lately, then stop hammering them once per minute even when we
13027 think they're failed. Fixes another part of bug 422.
13030 - Actually set the purpose correctly for descriptors inserted with
13031 purpose=controller.
13032 - When we have k non-v2 authorities in our DirServer config,
13033 we ignored the last k authorities in the list when updating our
13035 - Correctly back-off from requesting router descriptors that we are
13036 having a hard time downloading.
13037 - Read resolv.conf files correctly on platforms where read() returns
13038 partial results on small file reads.
13039 - Don't rebuild the entire router store every time we get 32K of
13040 routers: rebuild it when the journal gets very large, or when
13041 the gaps in the store get very large.
13044 - When routers publish SVN revisions in their router descriptors,
13045 authorities now include those versions correctly in networkstatus
13047 - Warn when using a version of libevent before 1.3b to run a server on
13048 OSX or BSD: these versions interact badly with userspace threads.
13051 Changes in version 0.1.2.13 - 2007-04-24
13052 This release features some major anonymity fixes, such as safer path
13053 selection; better client performance; faster bootstrapping, better
13054 address detection, and better DNS support for servers; write limiting as
13055 well as read limiting to make servers easier to run; and a huge pile of
13056 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
13058 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
13059 of the Freenode IRC network, remembering his patience and vision for
13060 free speech on the Internet.
13063 - Fix a memory leak when we ask for "all" networkstatuses and we
13064 get one we don't recognize.
13065 - Add more asserts to hunt down bug 417.
13066 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
13069 Changes in version 0.1.2.12-rc - 2007-03-16
13071 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
13072 directory information requested inside Tor connections (i.e. via
13073 begin_dir cells). It only triggered when the same connection was
13074 serving other data at the same time. Reported by seeess.
13077 - When creating a circuit via the controller, send a 'launched'
13078 event when we're done, so we follow the spec better.
13081 Changes in version 0.1.2.11-rc - 2007-03-15
13082 o Minor bugfixes (controller), reported by daejees:
13083 - Correct the control spec to match how the code actually responds
13084 to 'getinfo addr-mappings/*'.
13085 - The control spec described a GUARDS event, but the code
13086 implemented a GUARD event. Standardize on GUARD, but let people
13087 ask for GUARDS too.
13090 Changes in version 0.1.2.10-rc - 2007-03-07
13091 o Major bugfixes (Windows):
13092 - Do not load the NT services library functions (which may not exist)
13093 just to detect if we're a service trying to shut down. Now we run
13094 on Win98 and friends again.
13096 o Minor bugfixes (other):
13097 - Clarify a couple of log messages.
13098 - Fix a misleading socks5 error number.
13101 Changes in version 0.1.2.9-rc - 2007-03-02
13102 o Major bugfixes (Windows):
13103 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
13104 of the usual GCC "%llu". This prevents a bug when saving 64-bit
13105 int configuration values: the high-order 32 bits would get
13106 truncated. In particular, we were being bitten by the default
13107 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
13108 and maybe also bug 397.)
13110 o Minor bugfixes (performance):
13111 - Use OpenSSL's AES implementation on platforms where it's faster.
13112 This could save us as much as 10% CPU usage.
13114 o Minor bugfixes (server):
13115 - Do not rotate onion key immediately after setting it for the first
13118 o Minor bugfixes (directory authorities):
13119 - Stop calling servers that have been hibernating for a long time
13120 "stable". Also, stop letting hibernating or obsolete servers affect
13121 uptime and bandwidth cutoffs.
13122 - Stop listing hibernating servers in the v1 directory.
13124 o Minor bugfixes (hidden services):
13125 - Upload hidden service descriptors slightly less often, to reduce
13126 load on authorities.
13128 o Minor bugfixes (other):
13129 - Fix an assert that could trigger if a controller quickly set then
13130 cleared EntryNodes. Bug found by Udo van den Heuvel.
13131 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
13133 - Fix a potential race condition in the rpm installer. Found by
13135 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
13136 of 2 as indicating that the server is completely bad; it sometimes
13137 means that the server is just bad for the request in question. (may fix
13138 the last of bug 326.)
13139 - Disable encrypted directory connections when we don't have a server
13140 descriptor for the destination. We'll get this working again in
13144 Changes in version 0.1.2.8-beta - 2007-02-26
13145 o Major bugfixes (crashes):
13146 - Stop crashing when the controller asks us to resetconf more than
13147 one config option at once. (Vidalia 0.0.11 does this.)
13148 - Fix a crash that happened on Win98 when we're given command-line
13149 arguments: don't try to load NT service functions from advapi32.dll
13150 except when we need them. (Bug introduced in 0.1.2.7-alpha;
13152 - Fix a longstanding obscure crash bug that could occur when
13153 we run out of DNS worker processes. (Resolves bug 390.)
13155 o Major bugfixes (hidden services):
13156 - Correctly detect whether hidden service descriptor downloads are
13157 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
13159 o Major bugfixes (accounting):
13160 - When we start during an accounting interval before it's time to wake
13161 up, remember to wake up at the correct time. (May fix bug 342.)
13163 o Minor bugfixes (controller):
13164 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
13165 clear the corresponding on_circuit variable, and remember later
13166 that we don't need to send a redundant CLOSED event. Resolves part
13168 - Report events where a resolve succeeded or where we got a socks
13169 protocol error correctly, rather than calling both of them
13171 - Change reported stream target addresses to IP consistently when
13172 we finally get the IP from an exit node.
13173 - Send log messages to the controller even if they happen to be very
13176 o Minor bugfixes (other):
13177 - Display correct results when reporting which versions are
13178 recommended, and how recommended they are. (Resolves bug 383.)
13179 - Improve our estimates for directory bandwidth to be less random:
13180 guess that an unrecognized directory will have the average bandwidth
13181 from all known directories, not that it will have the average
13182 bandwidth from those directories earlier than it on the list.
13183 - If we start a server with ClientOnly 1, then set ClientOnly to 0
13184 and hup, stop triggering an assert based on an empty onion_key.
13185 - On platforms with no working mmap() equivalent, don't warn the
13186 user when cached-routers doesn't exist.
13187 - Warn the user when mmap() [or its equivalent] fails for some reason
13188 other than file-not-found.
13189 - Don't warn the user when cached-routers.new doesn't exist: that's
13190 perfectly fine when starting up for the first time.
13191 - When EntryNodes are configured, rebuild the guard list to contain,
13192 in order: the EntryNodes that were guards before; the rest of the
13193 EntryNodes; the nodes that were guards before.
13194 - Mask out all signals in sub-threads; only the libevent signal
13195 handler should be processing them. This should prevent some crashes
13196 on some machines using pthreads. (Patch from coderman.)
13197 - Fix switched arguments on memset in the implementation of
13198 tor_munmap() for systems with no mmap() call.
13199 - When Tor receives a router descriptor that it asked for, but
13200 no longer wants (because it has received fresh networkstatuses
13201 in the meantime), do not warn the user. Cache the descriptor if
13202 we're a cache; drop it if we aren't.
13203 - Make earlier entry guards _really_ get retried when the network
13205 - On a malformed DNS reply, always give an error to the corresponding
13207 - Build with recent libevents on platforms that do not define the
13208 nonstandard types "u_int8_t" and friends.
13210 o Minor features (controller):
13211 - Warn the user when an application uses the obsolete binary v0
13212 control protocol. We're planning to remove support for it during
13213 the next development series, so it's good to give people some
13215 - Add STREAM_BW events to report per-entry-stream bandwidth
13216 use. (Patch from Robert Hogan.)
13217 - Rate-limit SIGNEWNYM signals in response to controllers that
13218 impolitely generate them for every single stream. (Patch from
13219 mwenge; closes bug 394.)
13220 - Make REMAP stream events have a SOURCE (cache or exit), and
13221 make them generated in every case where we get a successful
13222 connected or resolved cell.
13224 o Minor bugfixes (performance):
13225 - Call router_have_min_dir_info half as often. (This is showing up in
13226 some profiles, but not others.)
13227 - When using GCC, make log_debug never get called at all, and its
13228 arguments never get evaluated, when no debug logs are configured.
13229 (This is showing up in some profiles, but not others.)
13232 - Remove some never-implemented options. Mark PathlenCoinWeight as
13234 - Implement proposal 106: Stop requiring clients to have well-formed
13235 certificates; stop checking nicknames in certificates. (Clients
13236 have certificates so that they can look like Tor servers, but in
13237 the future we might want to allow them to look like regular TLS
13238 clients instead. Nicknames in certificates serve no purpose other
13239 than making our protocol easier to recognize on the wire.)
13240 - Revise messages on handshake failure again to be even more clear about
13241 which are incoming connections and which are outgoing.
13242 - Discard any v1 directory info that's over 1 month old (for
13243 directories) or over 1 week old (for running-routers lists).
13244 - Do not warn when individual nodes in the configuration's EntryNodes,
13245 ExitNodes, etc are down: warn only when all possible nodes
13246 are down. (Fixes bug 348.)
13247 - Always remove expired routers and networkstatus docs before checking
13248 whether we have enough information to build circuits. (Fixes
13250 - Put a lower-bound on MaxAdvertisedBandwidth.
13253 Changes in version 0.1.2.7-alpha - 2007-02-06
13254 o Major bugfixes (rate limiting):
13255 - Servers decline directory requests much more aggressively when
13256 they're low on bandwidth. Otherwise they end up queueing more and
13257 more directory responses, which can't be good for latency.
13258 - But never refuse directory requests from local addresses.
13259 - Fix a memory leak when sending a 503 response for a networkstatus
13261 - Be willing to read or write on local connections (e.g. controller
13262 connections) even when the global rate limiting buckets are empty.
13263 - If our system clock jumps back in time, don't publish a negative
13264 uptime in the descriptor. Also, don't let the global rate limiting
13265 buckets go absurdly negative.
13266 - Flush local controller connection buffers periodically as we're
13267 writing to them, so we avoid queueing 4+ megabytes of data before
13270 o Major bugfixes (NT services):
13271 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
13272 command-line flag so that admins can override the default by saying
13273 "tor --service install --user "SomeUser"". This will not affect
13274 existing installed services. Also, warn the user that the service
13275 will look for its configuration file in the service user's
13276 %appdata% directory. (We can't do the 'hardwire the user's appdata
13277 directory' trick any more, since we may not have read access to that
13280 o Major bugfixes (other):
13281 - Previously, we would cache up to 16 old networkstatus documents
13282 indefinitely, if they came from nontrusted authorities. Now we
13283 discard them if they are more than 10 days old.
13284 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
13286 - Detect and reject malformed DNS responses containing circular
13288 - If exits are rare enough that we're not marking exits as guards,
13289 ignore exit bandwidth when we're deciding the required bandwidth
13291 - When we're handling a directory connection tunneled over Tor,
13292 don't fill up internal memory buffers with all the data we want
13293 to tunnel; instead, only add it if the OR connection that will
13294 eventually receive it has some room for it. (This can lead to
13295 slowdowns in tunneled dir connections; a better solution will have
13296 to wait for 0.2.0.)
13298 o Minor bugfixes (dns):
13299 - Add some defensive programming to eventdns.c in an attempt to catch
13300 possible memory-stomping bugs.
13301 - Detect and reject DNS replies containing IPv4 or IPv6 records with
13302 an incorrect number of bytes. (Previously, we would ignore the
13304 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
13305 in the correct order, and doesn't crash.
13306 - Free memory held in recently-completed DNS lookup attempts on exit.
13307 This was not a memory leak, but may have been hiding memory leaks.
13308 - Handle TTL values correctly on reverse DNS lookups.
13309 - Treat failure to parse resolv.conf as an error.
13311 o Minor bugfixes (other):
13312 - Fix crash with "tor --list-fingerprint" (reported by seeess).
13313 - When computing clock skew from directory HTTP headers, consider what
13314 time it was when we finished asking for the directory, not what
13316 - Expire socks connections if they spend too long waiting for the
13317 handshake to finish. Previously we would let them sit around for
13318 days, if the connecting application didn't close them either.
13319 - And if the socks handshake hasn't started, don't send a
13320 "DNS resolve socks failed" handshake reply; just close it.
13321 - Stop using C functions that OpenBSD's linker doesn't like.
13322 - Don't launch requests for descriptors unless we have networkstatuses
13323 from at least half of the authorities. This delays the first
13324 download slightly under pathological circumstances, but can prevent
13325 us from downloading a bunch of descriptors we don't need.
13326 - Do not log IPs with TLS failures for incoming TLS
13327 connections. (Fixes bug 382.)
13328 - If the user asks to use invalid exit nodes, be willing to use
13330 - Stop using the reserved ac_cv namespace in our configure script.
13331 - Call stat() slightly less often; use fstat() when possible.
13332 - Refactor the way we handle pending circuits when an OR connection
13333 completes or fails, in an attempt to fix a rare crash bug.
13334 - Only rewrite a conn's address based on X-Forwarded-For: headers
13335 if it's a parseable public IP address; and stop adding extra quotes
13336 to the resulting address.
13339 - Weight directory requests by advertised bandwidth. Now we can
13340 let servers enable write limiting but still allow most clients to
13341 succeed at their directory requests. (We still ignore weights when
13342 choosing a directory authority; I hope this is a feature.)
13345 - Create a new file ReleaseNotes which was the old ChangeLog. The
13346 new ChangeLog file now includes the summaries for all development
13348 - Check for addresses with invalid characters at the exit as well
13349 as at the client, and warn less verbosely when they fail. You can
13350 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
13351 - Adapt a patch from goodell to let the contrib/exitlist script
13352 take arguments rather than require direct editing.
13353 - Inform the server operator when we decide not to advertise a
13354 DirPort due to AccountingMax enabled or a low BandwidthRate. It
13355 was confusing Zax, so now we're hopefully more helpful.
13356 - Bring us one step closer to being able to establish an encrypted
13357 directory tunnel without knowing a descriptor first. Still not
13358 ready yet. As part of the change, now assume we can use a
13359 create_fast cell if we don't know anything about a router.
13360 - Allow exit nodes to use nameservers running on ports other than 53.
13361 - Servers now cache reverse DNS replies.
13362 - Add an --ignore-missing-torrc command-line option so that we can
13363 get the "use sensible defaults if the configuration file doesn't
13364 exist" behavior even when specifying a torrc location on the command
13367 o Minor features (controller):
13368 - Track reasons for OR connection failure; make these reasons
13369 available via the controller interface. (Patch from Mike Perry.)
13370 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
13371 can learn when clients are sending malformed hostnames to Tor.
13372 - Clean up documentation for controller status events.
13373 - Add a REMAP status to stream events to note that a stream's
13374 address has changed because of a cached address or a MapAddress
13378 Changes in version 0.1.2.6-alpha - 2007-01-09
13380 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
13381 connection handles more than 4 gigs in either direction, we crash.
13382 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
13383 advertised exit node, somebody might try to exit from us when
13384 we're bootstrapping and before we've built our descriptor yet.
13385 Refuse the connection rather than crashing.
13388 - Warn if we (as a server) find that we've resolved an address that we
13389 weren't planning to resolve.
13390 - Warn that using select() on any libevent version before 1.1 will be
13391 unnecessarily slow (even for select()).
13392 - Flush ERR-level controller status events just like we currently
13393 flush ERR-level log events, so that a Tor shutdown doesn't prevent
13394 the controller from learning about current events.
13396 o Minor features (more controller status events):
13397 - Implement EXTERNAL_ADDRESS server status event so controllers can
13398 learn when our address changes.
13399 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
13400 can learn when directories reject our descriptor.
13401 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
13402 can learn when a client application is speaking a non-socks protocol
13404 - Implement DANGEROUS_SOCKS client status event so controllers
13405 can learn when a client application is leaking DNS addresses.
13406 - Implement BUG general status event so controllers can learn when
13407 Tor is unhappy about its internal invariants.
13408 - Implement CLOCK_SKEW general status event so controllers can learn
13409 when Tor thinks the system clock is set incorrectly.
13410 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
13411 server status events so controllers can learn when their descriptors
13412 are accepted by a directory.
13413 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
13414 server status events so controllers can learn about Tor's progress in
13415 deciding whether it's reachable from the outside.
13416 - Implement BAD_LIBEVENT general status event so controllers can learn
13417 when we have a version/method combination in libevent that needs to
13419 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
13420 and DNS_USELESS server status events so controllers can learn
13421 about changes to DNS server status.
13423 o Minor features (directory):
13424 - Authorities no longer recommend exits as guards if this would shift
13425 too much load to the exit nodes.
13428 Changes in version 0.1.2.5-alpha - 2007-01-06
13430 - Enable write limiting as well as read limiting. Now we sacrifice
13431 capacity if we're pushing out lots of directory traffic, rather
13432 than overrunning the user's intended bandwidth limits.
13433 - Include TLS overhead when counting bandwidth usage; previously, we
13434 would count only the bytes sent over TLS, but not the bytes used
13436 - Support running the Tor service with a torrc not in the same
13437 directory as tor.exe and default to using the torrc located in
13438 the %appdata%\Tor\ of the user who installed the service. Patch
13440 - Servers now check for the case when common DNS requests are going to
13441 wildcarded addresses (i.e. all getting the same answer), and change
13442 their exit policy to reject *:* if it's happening.
13443 - Implement BEGIN_DIR cells, so we can connect to the directory
13444 server via TLS to do encrypted directory requests rather than
13445 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
13446 config options if you like.
13448 o Minor features (config and docs):
13449 - Start using the state file to store bandwidth accounting data:
13450 the bw_accounting file is now obsolete. We'll keep generating it
13451 for a while for people who are still using 0.1.2.4-alpha.
13452 - Try to batch changes to the state file so that we do as few
13453 disk writes as possible while still storing important things in
13455 - The state file and the bw_accounting file get saved less often when
13456 the AvoidDiskWrites config option is set.
13457 - Make PIDFile work on Windows (untested).
13458 - Add internal descriptions for a bunch of configuration options:
13459 accessible via controller interface and in comments in saved
13461 - Reject *:563 (NNTPS) in the default exit policy. We already reject
13462 NNTP by default, so this seems like a sensible addition.
13463 - Clients now reject hostnames with invalid characters. This should
13464 avoid some inadvertent info leaks. Add an option
13465 AllowNonRFC953Hostnames to disable this behavior, in case somebody
13466 is running a private network with hosts called @, !, and #.
13467 - Add a maintainer script to tell us which options are missing
13468 documentation: "make check-docs".
13469 - Add a new address-spec.txt document to describe our special-case
13470 addresses: .exit, .onion, and .noconnnect.
13472 o Minor features (DNS):
13473 - Ongoing work on eventdns infrastructure: now it has dns server
13474 and ipv6 support. One day Tor will make use of it.
13475 - Add client-side caching for reverse DNS lookups.
13476 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
13477 - When we change nameservers or IP addresses, reset and re-launch
13478 our tests for DNS hijacking.
13480 o Minor features (directory):
13481 - Authorities now specify server versions in networkstatus. This adds
13482 about 2% to the size of compressed networkstatus docs, and allows
13483 clients to tell which servers support BEGIN_DIR and which don't.
13484 The implementation is forward-compatible with a proposed future
13485 protocol version scheme not tied to Tor versions.
13486 - DirServer configuration lines now have an orport= option so
13487 clients can open encrypted tunnels to the authorities without
13488 having downloaded their descriptors yet. Enabled for moria1,
13489 moria2, tor26, and lefkada now in the default configuration.
13490 - Directory servers are more willing to send a 503 "busy" if they
13491 are near their write limit, especially for v1 directory requests.
13492 Now they can use their limited bandwidth for actual Tor traffic.
13493 - Clients track responses with status 503 from dirservers. After a
13494 dirserver has given us a 503, we try not to use it until an hour has
13495 gone by, or until we have no dirservers that haven't given us a 503.
13496 - When we get a 503 from a directory, and we're not a server, we don't
13497 count the failure against the total number of failures allowed
13498 for the thing we're trying to download.
13499 - Report X-Your-Address-Is correctly from tunneled directory
13500 connections; don't report X-Your-Address-Is when it's an internal
13501 address; and never believe reported remote addresses when they're
13503 - Protect against an unlikely DoS attack on directory servers.
13504 - Add a BadDirectory flag to network status docs so that authorities
13505 can (eventually) tell clients about caches they believe to be
13508 o Minor features (controller):
13509 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
13510 - Reimplement GETINFO so that info/names stays in sync with the
13512 - Implement "GETINFO fingerprint".
13513 - Implement "SETEVENTS GUARD" so controllers can get updates on
13514 entry guard status as it changes.
13516 o Minor features (clean up obsolete pieces):
13517 - Remove some options that have been deprecated since at least
13518 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
13519 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
13520 to set log options.
13521 - We no longer look for identity and onion keys in "identity.key" and
13522 "onion.key" -- these were replaced by secret_id_key and
13523 secret_onion_key in 0.0.8pre1.
13524 - We no longer require unrecognized directory entries to be
13527 o Major bugfixes (security):
13528 - Stop sending the HttpProxyAuthenticator string to directory
13529 servers when directory connections are tunnelled through Tor.
13530 - Clients no longer store bandwidth history in the state file.
13531 - Do not log introduction points for hidden services if SafeLogging
13533 - When generating bandwidth history, round down to the nearest
13534 1k. When storing accounting data, round up to the nearest 1k.
13535 - When we're running as a server, remember when we last rotated onion
13536 keys, so that we will rotate keys once they're a week old even if
13537 we never stay up for a week ourselves.
13539 o Major bugfixes (other):
13540 - Fix a longstanding bug in eventdns that prevented the count of
13541 timed-out resolves from ever being reset. This bug caused us to
13542 give up on a nameserver the third time it timed out, and try it
13543 10 seconds later... and to give up on it every time it timed out
13545 - Take out the '5 second' timeout from the connection retry
13546 schedule. Now the first connect attempt will wait a full 10
13547 seconds before switching to a new circuit. Perhaps this will help
13548 a lot. Based on observations from Mike Perry.
13549 - Fix a bug on the Windows implementation of tor_mmap_file() that
13550 would prevent the cached-routers file from ever loading. Reported
13554 - Fix an assert failure when a directory authority sets
13555 AuthDirRejectUnlisted and then receives a descriptor from an
13556 unlisted router. Reported by seeess.
13557 - Avoid a double-free when parsing malformed DirServer lines.
13558 - Fix a bug when a BSD-style PF socket is first used. Patch from
13560 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
13561 to resolve an address at a given exit node even when they ask for
13563 - Servers no longer ever list themselves in their "family" line,
13564 even if configured to do so. This makes it easier to configure
13565 family lists conveniently.
13566 - When running as a server, don't fall back to 127.0.0.1 when no
13567 nameservers are configured in /etc/resolv.conf; instead, make the
13568 user fix resolv.conf or specify nameservers explicitly. (Resolves
13570 - Stop accepting certain malformed ports in configured exit policies.
13571 - Don't re-write the fingerprint file every restart, unless it has
13573 - Stop warning when a single nameserver fails: only warn when _all_ of
13574 our nameservers have failed. Also, when we only have one nameserver,
13575 raise the threshold for deciding that the nameserver is dead.
13576 - Directory authorities now only decide that routers are reachable
13577 if their identity keys are as expected.
13578 - When the user uses bad syntax in the Log config line, stop
13579 suggesting other bad syntax as a replacement.
13580 - Correctly detect ipv6 DNS capability on OpenBSD.
13582 o Minor bugfixes (controller):
13583 - Report the circuit number correctly in STREAM CLOSED events. Bug
13584 reported by Mike Perry.
13585 - Do not report bizarre values for results of accounting GETINFOs
13586 when the last second's write or read exceeds the allotted bandwidth.
13587 - Report "unrecognized key" rather than an empty string when the
13588 controller tries to fetch a networkstatus that doesn't exist.
13591 Changes in version 0.1.1.26 - 2006-12-14
13592 o Security bugfixes:
13593 - Stop sending the HttpProxyAuthenticator string to directory
13594 servers when directory connections are tunnelled through Tor.
13595 - Clients no longer store bandwidth history in the state file.
13596 - Do not log introduction points for hidden services if SafeLogging
13600 - Fix an assert failure when a directory authority sets
13601 AuthDirRejectUnlisted and then receives a descriptor from an
13602 unlisted router (reported by seeess).
13605 Changes in version 0.1.2.4-alpha - 2006-12-03
13607 - Add support for using natd; this allows FreeBSDs earlier than
13608 5.1.2 to have ipfw send connections through Tor without using
13609 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
13612 - Make all connections to addresses of the form ".noconnect"
13613 immediately get closed. This lets application/controller combos
13614 successfully test whether they're talking to the same Tor by
13615 watching for STREAM events.
13616 - Make cross.sh cross-compilation script work even when autogen.sh
13617 hasn't been run. (Patch from Michael Mohr.)
13618 - Statistics dumped by -USR2 now include a breakdown of public key
13619 operations, for profiling.
13622 - Fix a major leak when directory authorities parse their
13623 approved-routers list, a minor memory leak when we fail to pick
13624 an exit node, and a few rare leaks on errors.
13625 - Handle TransPort connections even when the server sends data before
13626 the client sends data. Previously, the connection would just hang
13627 until the client sent data. (Patch from tup based on patch from
13629 - Avoid assert failure when our cached-routers file is empty on
13633 - Don't log spurious warnings when we see a circuit close reason we
13634 don't recognize; it's probably just from a newer version of Tor.
13635 - Have directory authorities allow larger amounts of drift in uptime
13636 without replacing the server descriptor: previously, a server that
13637 restarted every 30 minutes could have 48 "interesting" descriptors
13639 - Start linking to the Tor specification and Tor reference manual
13640 correctly in the Windows installer.
13641 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13642 Tor/Privoxy we also uninstall Vidalia.
13643 - Resume building on Irix64, and fix a lot of warnings from its
13644 MIPSpro C compiler.
13645 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
13646 when we're running as a client.
13649 Changes in version 0.1.1.25 - 2006-11-04
13651 - When a client asks us to resolve (rather than connect to)
13652 an address, and we have a cached answer, give them the cached
13653 answer. Previously, we would give them no answer at all.
13654 - We were building exactly the wrong circuits when we predict
13655 hidden service requirements, meaning Tor would have to build all
13656 its circuits on demand.
13657 - If none of our live entry guards have a high uptime, but we
13658 require a guard with a high uptime, try adding a new guard before
13659 we give up on the requirement. This patch should make long-lived
13660 connections more stable on average.
13661 - When testing reachability of our DirPort, don't launch new
13662 tests when there's already one in progress -- unreachable
13663 servers were stacking up dozens of testing streams.
13665 o Security bugfixes:
13666 - When the user sends a NEWNYM signal, clear the client-side DNS
13667 cache too. Otherwise we continue to act on previous information.
13670 - Avoid a memory corruption bug when creating a hash table for
13672 - Avoid possibility of controller-triggered crash when misusing
13673 certain commands from a v0 controller on platforms that do not
13674 handle printf("%s",NULL) gracefully.
13675 - Avoid infinite loop on unexpected controller input.
13676 - Don't log spurious warnings when we see a circuit close reason we
13677 don't recognize; it's probably just from a newer version of Tor.
13678 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13679 Tor/Privoxy we also uninstall Vidalia.
13682 Changes in version 0.1.2.3-alpha - 2006-10-29
13684 - Prepare for servers to publish descriptors less often: never
13685 discard a descriptor simply for being too old until either it is
13686 recommended by no authorities, or until we get a better one for
13687 the same router. Make caches consider retaining old recommended
13688 routers for even longer.
13689 - If most authorities set a BadExit flag for a server, clients
13690 don't think of it as a general-purpose exit. Clients only consider
13691 authorities that advertise themselves as listing bad exits.
13692 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
13693 headers for content, so that we can work better in the presence of
13694 caching HTTP proxies.
13695 - Allow authorities to list nodes as bad exits by fingerprint or by
13698 o Minor features, controller:
13699 - Add a REASON field to CIRC events; for backward compatibility, this
13700 field is sent only to controllers that have enabled the extended
13701 event format. Also, add additional reason codes to explain why
13702 a given circuit has been destroyed or truncated. (Patches from
13704 - Add a REMOTE_REASON field to extended CIRC events to tell the
13705 controller about why a remote OR told us to close a circuit.
13706 - Stream events also now have REASON and REMOTE_REASON fields,
13707 working much like those for circuit events.
13708 - There's now a GETINFO ns/... field so that controllers can ask Tor
13709 about the current status of a router.
13710 - A new event type "NS" to inform a controller when our opinion of
13711 a router's status has changed.
13712 - Add a GETINFO events/names and GETINFO features/names so controllers
13713 can tell which events and features are supported.
13714 - A new CLEARDNSCACHE signal to allow controllers to clear the
13715 client-side DNS cache without expiring circuits.
13717 o Security bugfixes:
13718 - When the user sends a NEWNYM signal, clear the client-side DNS
13719 cache too. Otherwise we continue to act on previous information.
13722 - Avoid sending junk to controllers or segfaulting when a controller
13723 uses EVENT_NEW_DESC with verbose nicknames.
13724 - Stop triggering asserts if the controller tries to extend hidden
13725 service circuits (reported by mwenge).
13726 - Avoid infinite loop on unexpected controller input.
13727 - When the controller does a "GETINFO network-status", tell it
13728 about even those routers whose descriptors are very old, and use
13729 long nicknames where appropriate.
13730 - Change NT service functions to be loaded on demand. This lets us
13731 build with MinGW without breaking Tor for Windows 98 users.
13732 - Do DirPort reachability tests less often, since a single test
13733 chews through many circuits before giving up.
13734 - In the hidden service example in torrc.sample, stop recommending
13735 esoteric and discouraged hidden service options.
13736 - When stopping an NT service, wait up to 10 sec for it to actually
13737 stop. Patch from Matt Edman; resolves bug 295.
13738 - Fix handling of verbose nicknames with ORCONN controller events:
13739 make them show up exactly when requested, rather than exactly when
13741 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
13742 printing a duplicate "$" in the keys we send (reported by mwenge).
13743 - Correctly set maximum connection limit on Cygwin. (This time
13745 - Try to detect Windows correctly when cross-compiling.
13746 - Detect the size of the routers file correctly even if it is
13747 corrupted (on systems without mmap) or not page-aligned (on systems
13748 with mmap). This bug was harmless.
13749 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
13750 to open a stream fails; now we do in more cases. This should
13751 make clients able to find a good exit faster in some cases, since
13752 unhandleable requests will now get an error rather than timing out.
13753 - Resolve two memory leaks when rebuilding the on-disk router cache
13754 (reported by fookoowa).
13755 - Clean up minor code warnings suggested by the MIPSpro C compiler,
13756 and reported by some Centos users.
13757 - Controller signals now work on non-Unix platforms that don't define
13758 SIGUSR1 and SIGUSR2 the way we expect.
13759 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
13760 values before failing, and always enables eventdns.
13761 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
13762 Try to fix this in configure.in by checking for most functions
13763 before we check for libevent.
13766 Changes in version 0.1.2.2-alpha - 2006-10-07
13768 - Make our async eventdns library on-by-default for Tor servers,
13769 and plan to deprecate the separate dnsworker threads.
13770 - Add server-side support for "reverse" DNS lookups (using PTR
13771 records so clients can determine the canonical hostname for a given
13772 IPv4 address). Only supported by servers using eventdns; servers
13773 now announce in their descriptors whether they support eventdns.
13774 - Specify and implement client-side SOCKS5 interface for reverse DNS
13775 lookups (see doc/socks-extensions.txt).
13776 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
13777 connect to directory servers through Tor. Previously, clients needed
13778 to find Tor exits to make private connections to directory servers.
13779 - Avoid choosing Exit nodes for entry or middle hops when the
13780 total bandwidth available from non-Exit nodes is much higher than
13781 the total bandwidth available from Exit nodes.
13782 - Workaround for name servers (like Earthlink's) that hijack failing
13783 DNS requests and replace the no-such-server answer with a "helpful"
13784 redirect to an advertising-driven search portal. Also work around
13785 DNS hijackers who "helpfully" decline to hijack known-invalid
13786 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
13787 lets you turn it off.
13788 - Send out a burst of long-range padding cells once we've established
13789 that we're reachable. Spread them over 4 circuits, so hopefully
13790 a few will be fast. This exercises our bandwidth and bootstraps
13791 us into the directory more quickly.
13793 o New/improved config options:
13794 - Add new config option "ResolvConf" to let the server operator
13795 choose an alternate resolve.conf file when using eventdns.
13796 - Add an "EnforceDistinctSubnets" option to control our "exclude
13797 servers on the same /16" behavior. It's still on by default; this
13798 is mostly for people who want to operate private test networks with
13799 all the machines on the same subnet.
13800 - If one of our entry guards is on the ExcludeNodes list, or the
13801 directory authorities don't think it's a good guard, treat it as
13802 if it were unlisted: stop using it as a guard, and throw it off
13803 the guards list if it stays that way for a long time.
13804 - Allow directory authorities to be marked separately as authorities
13805 for the v1 directory protocol, the v2 directory protocol, and
13806 as hidden service directories, to make it easier to retire old
13807 authorities. V1 authorities should set "HSAuthoritativeDir 1"
13808 to continue being hidden service authorities too.
13809 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
13811 o Minor features, controller:
13812 - Fix CIRC controller events so that controllers can learn the
13813 identity digests of non-Named servers used in circuit paths.
13814 - Let controllers ask for more useful identifiers for servers. Instead
13815 of learning identity digests for un-Named servers and nicknames
13816 for Named servers, the new identifiers include digest, nickname,
13817 and indication of Named status. Off by default; see control-spec.txt
13818 for more information.
13819 - Add a "getinfo address" controller command so it can display Tor's
13820 best guess to the user.
13821 - New controller event to alert the controller when our server
13822 descriptor has changed.
13823 - Give more meaningful errors on controller authentication failure.
13825 o Minor features, other:
13826 - When asked to resolve a hostname, don't use non-exit servers unless
13827 requested to do so. This allows servers with broken DNS to be
13828 useful to the network.
13829 - Divide eventdns log messages into warn and info messages.
13830 - Reserve the nickname "Unnamed" for routers that can't pick
13831 a hostname: any router can call itself Unnamed; directory
13832 authorities will never allocate Unnamed to any particular router;
13833 clients won't believe that any router is the canonical Unnamed.
13834 - Only include function names in log messages for info/debug messages.
13835 For notice/warn/err, the content of the message should be clear on
13836 its own, and printing the function name only confuses users.
13837 - Avoid some false positives during reachability testing: don't try
13838 to test via a server that's on the same /24 as us.
13839 - If we fail to build a circuit to an intended enclave, and it's
13840 not mandatory that we use that enclave, stop wanting it.
13841 - When eventdns is enabled, allow multithreaded builds on NetBSD and
13842 OpenBSD. (We had previously disabled threads on these platforms
13843 because they didn't have working thread-safe resolver functions.)
13845 o Major bugfixes, anonymity/security:
13846 - If a client asked for a server by name, and there's a named server
13847 in our network-status but we don't have its descriptor yet, we
13848 could return an unnamed server instead.
13849 - Fix NetBSD bug that could allow someone to force uninitialized RAM
13850 to be sent to a server's DNS resolver. This only affects NetBSD
13851 and other platforms that do not bounds-check tolower().
13852 - Reject (most) attempts to use Tor circuits with length one. (If
13853 many people start using Tor as a one-hop proxy, exit nodes become
13854 a more attractive target for compromise.)
13855 - Just because your DirPort is open doesn't mean people should be
13856 able to remotely teach you about hidden service descriptors. Now
13857 only accept rendezvous posts if you've got HSAuthoritativeDir set.
13859 o Major bugfixes, other:
13860 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
13861 - When a client asks the server to resolve (not connect to)
13862 an address, and it has a cached answer, give them the cached answer.
13863 Previously, the server would give them no answer at all.
13864 - Allow really slow clients to not hang up five minutes into their
13865 directory downloads (suggested by Adam J. Richter).
13866 - We were building exactly the wrong circuits when we anticipated
13867 hidden service requirements, meaning Tor would have to build all
13868 its circuits on demand.
13869 - Avoid crashing when we mmap a router cache file of size 0.
13870 - When testing reachability of our DirPort, don't launch new
13871 tests when there's already one in progress -- unreachable
13872 servers were stacking up dozens of testing streams.
13874 o Minor bugfixes, correctness:
13875 - If we're a directory mirror and we ask for "all" network status
13876 documents, we would discard status documents from authorities
13877 we don't recognize.
13878 - Avoid a memory corruption bug when creating a hash table for
13880 - Avoid controller-triggered crash when misusing certain commands
13881 from a v0 controller on platforms that do not handle
13882 printf("%s",NULL) gracefully.
13883 - Don't crash when a controller sends a third argument to an
13884 "extendcircuit" request.
13885 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13886 response; fix error code when "getinfo dir/status/" fails.
13887 - Avoid crash when telling controller stream-status and a stream
13889 - Patch from Adam Langley to fix assert() in eventdns.c.
13890 - Fix a debug log message in eventdns to say "X resolved to Y"
13891 instead of "X resolved to X".
13892 - Make eventdns give strings for DNS errors, not just error numbers.
13893 - Track unreachable entry guards correctly: don't conflate
13894 'unreachable by us right now' with 'listed as down by the directory
13895 authorities'. With the old code, if a guard was unreachable by
13896 us but listed as running, it would clog our guard list forever.
13897 - Behave correctly in case we ever have a network with more than
13898 2GB/s total advertised capacity.
13899 - Make TrackExitHosts case-insensitive, and fix the behavior of
13900 ".suffix" TrackExitHosts items to avoid matching in the middle of
13902 - Finally fix the openssl warnings from newer gccs that believe that
13903 ignoring a return value is okay, but casting a return value and
13904 then ignoring it is a sign of madness.
13905 - Prevent the contrib/exitlist script from printing the same
13906 result more than once.
13907 - Patch from Steve Hildrey: Generate network status correctly on
13908 non-versioning dirservers.
13909 - Don't listen to the X-Your-Address-Is hint if you did the lookup
13910 via Tor; otherwise you'll think you're the exit node's IP address.
13912 o Minor bugfixes, performance:
13913 - Two small performance improvements on parsing descriptors.
13914 - Major performance improvement on inserting descriptors: change
13915 algorithm from O(n^2) to O(n).
13916 - Make the common memory allocation path faster on machines where
13917 malloc(0) returns a pointer.
13918 - Start remembering X-Your-Address-Is directory hints even if you're
13919 a client, so you can become a server more smoothly.
13920 - Avoid duplicate entries on MyFamily line in server descriptor.
13922 o Packaging, features:
13923 - Remove architecture from OS X builds. The official builds are
13924 now universal binaries.
13925 - The Debian package now uses --verify-config when (re)starting,
13926 to distinguish configuration errors from other errors.
13927 - Update RPMs to require libevent 1.1b.
13929 o Packaging, bugfixes:
13930 - Patches so Tor builds with MinGW on Windows.
13931 - Patches so Tor might run on Cygwin again.
13932 - Resume building on non-gcc compilers and ancient gcc. Resume
13933 building with the -O0 compile flag. Resume building cleanly on
13935 - Run correctly on OS X platforms with case-sensitive filesystems.
13936 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
13937 - Add autoconf checks so Tor can build on Solaris x86 again.
13940 - Documented (and renamed) ServerDNSSearchDomains and
13941 ServerDNSResolvConfFile options.
13942 - Be clearer that the *ListenAddress directives can be repeated
13946 Changes in version 0.1.1.24 - 2006-09-29
13948 - Allow really slow clients to not hang up five minutes into their
13949 directory downloads (suggested by Adam J. Richter).
13950 - Fix major performance regression from 0.1.0.x: instead of checking
13951 whether we have enough directory information every time we want to
13952 do something, only check when the directory information has changed.
13953 This should improve client CPU usage by 25-50%.
13954 - Don't crash if, after a server has been running for a while,
13955 it can't resolve its hostname.
13958 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13959 - Don't crash when the controller receives a third argument to an
13960 "extendcircuit" request.
13961 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13962 response; fix error code when "getinfo dir/status/" fails.
13963 - Fix configure.in to not produce broken configure files with
13964 more recent versions of autoconf. Thanks to Clint for his auto*
13966 - Fix security bug on NetBSD that could allow someone to force
13967 uninitialized RAM to be sent to a server's DNS resolver. This
13968 only affects NetBSD and other platforms that do not bounds-check
13970 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
13971 methods: these are known to be buggy.
13972 - If we're a directory mirror and we ask for "all" network status
13973 documents, we would discard status documents from authorities
13974 we don't recognize.
13977 Changes in version 0.1.2.1-alpha - 2006-08-27
13979 - Add "eventdns" async dns library from Adam Langley, tweaked to
13980 build on OSX and Windows. Only enabled if you pass the
13981 --enable-eventdns argument to configure.
13982 - Allow servers with no hostname or IP address to learn their
13983 IP address by asking the directory authorities. This code only
13984 kicks in when you would normally have exited with a "no address"
13985 error. Nothing's authenticated, so use with care.
13986 - Rather than waiting a fixed amount of time between retrying
13987 application connections, we wait only 5 seconds for the first,
13988 10 seconds for the second, and 15 seconds for each retry after
13989 that. Hopefully this will improve the expected user experience.
13990 - Patch from Tup to add support for transparent AP connections:
13991 this basically bundles the functionality of trans-proxy-tor
13992 into the Tor mainline. Now hosts with compliant pf/netfilter
13993 implementations can redirect TCP connections straight to Tor
13994 without diverting through SOCKS. Needs docs.
13995 - Busy directory servers save lots of memory by spooling server
13996 descriptors, v1 directories, and v2 networkstatus docs to buffers
13997 as needed rather than en masse. Also mmap the cached-routers
13998 files, so we don't need to keep the whole thing in memory too.
13999 - Automatically avoid picking more than one node from the same
14000 /16 network when constructing a circuit.
14001 - Revise and clean up the torrc.sample that we ship with; add
14002 a section for BandwidthRate and BandwidthBurst.
14005 - Split circuit_t into origin_circuit_t and or_circuit_t, and
14006 split connection_t into edge, or, dir, control, and base structs.
14007 These will save quite a bit of memory on busy servers, and they'll
14008 also help us track down bugs in the code and bugs in the spec.
14009 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
14010 or later. Log when we are doing this, so we can diagnose it when
14011 it fails. (Also, recommend libevent 1.1b for kqueue and
14012 win32 methods; deprecate libevent 1.0b harder; make libevent
14013 recommendation system saner.)
14014 - Start being able to build universal binaries on OS X (thanks
14016 - Export the default exit policy via the control port, so controllers
14017 don't need to guess what it is / will be later.
14018 - Add a man page entry for ProtocolWarnings.
14019 - Add TestVia config option to the man page.
14020 - Remove even more protocol-related warnings from Tor server logs,
14021 such as bad TLS handshakes and malformed begin cells.
14022 - Stop fetching descriptors if you're not a dir mirror and you
14023 haven't tried to establish any circuits lately. [This currently
14024 causes some dangerous behavior, because when you start up again
14025 you'll use your ancient server descriptors.]
14026 - New DirPort behavior: if you have your dirport set, you download
14027 descriptors aggressively like a directory mirror, whether or not
14028 your ORPort is set.
14029 - Get rid of the router_retry_connections notion. Now routers
14030 no longer try to rebuild long-term connections to directory
14031 authorities, and directory authorities no longer try to rebuild
14032 long-term connections to all servers. We still don't hang up
14033 connections in these two cases though -- we need to look at it
14034 more carefully to avoid flapping, and we likely need to wait til
14035 0.1.1.x is obsolete.
14036 - Drop compatibility with obsolete Tors that permit create cells
14037 to have the wrong circ_id_type.
14038 - Re-enable per-connection rate limiting. Get rid of the "OP
14039 bandwidth" concept. Lay groundwork for "bandwidth classes" --
14040 separate global buckets that apply depending on what sort of conn
14042 - Start publishing one minute or so after we find our ORPort
14043 to be reachable. This will help reduce the number of descriptors
14044 we have for ourselves floating around, since it's quite likely
14045 other things (e.g. DirPort) will change during that minute too.
14046 - Fork the v1 directory protocol into its own spec document,
14047 and mark dir-spec.txt as the currently correct (v2) spec.
14050 - When we find our DirPort to be reachable, publish a new descriptor
14051 so we'll tell the world (reported by pnx).
14052 - Publish a new descriptor after we hup/reload. This is important
14053 if our config has changed such that we'll want to start advertising
14054 our DirPort now, etc.
14055 - Allow Tor to start when RunAsDaemon is set but no logs are set.
14056 - When we have a state file we cannot parse, tell the user and
14057 move it aside. Now we avoid situations where the user starts
14058 Tor in 1904, Tor writes a state file with that timestamp in it,
14059 the user fixes her clock, and Tor refuses to start.
14060 - Fix configure.in to not produce broken configure files with
14061 more recent versions of autoconf. Thanks to Clint for his auto*
14063 - "tor --verify-config" now exits with -1(255) or 0 depending on
14064 whether the config options are bad or good.
14065 - Resolve bug 321 when using dnsworkers: append a period to every
14066 address we resolve at the exit node, so that we do not accidentally
14067 pick up local addresses, and so that failing searches are retried
14068 in the resolver search domains. (This is already solved for
14069 eventdns.) (This breaks Blossom servers for now.)
14070 - If we are using an exit enclave and we can't connect, e.g. because
14071 its webserver is misconfigured to not listen on localhost, then
14072 back off and try connecting from somewhere else before we fail.
14075 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
14076 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
14077 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
14078 when the IP address is mapped through MapAddress to a hostname.
14079 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
14080 useless IPv6 DNS resolves.
14081 - Patch suggested by Karsten Loesing: respond to SIGNAL command
14082 before we execute the signal, in case the signal shuts us down.
14083 - Clean up AllowInvalidNodes man page entry.
14084 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
14085 - Add more asserts to track down an assert error on a windows Tor
14086 server with connection_add being called with socket == -1.
14087 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
14088 - Fix misleading log messages: an entry guard that is "unlisted",
14089 as well as not known to be "down" (because we've never heard
14090 of it), is not therefore "up".
14091 - Remove code to special-case "-cvs" ending, since it has not
14092 actually mattered since 0.0.9.
14093 - Make our socks5 handling more robust to broken socks clients:
14094 throw out everything waiting on the buffer in between socks
14095 handshake phases, since they can't possibly (so the theory
14096 goes) have predicted what we plan to respond to them.
14099 Changes in version 0.1.1.23 - 2006-07-30
14101 - Fast Tor servers, especially exit nodes, were triggering asserts
14102 due to a bug in handling the list of pending DNS resolves. Some
14103 bugs still remain here; we're hunting them.
14104 - Entry guards could crash clients by sending unexpected input.
14105 - More fixes on reachability testing: if you find yourself reachable,
14106 then don't ever make any client requests (so you stop predicting
14107 circuits), then hup or have your clock jump, then later your IP
14108 changes, you won't think circuits are working, so you won't try to
14109 test reachability, so you won't publish.
14112 - Avoid a crash if the controller does a resetconf firewallports
14113 and then a setconf fascistfirewall=1.
14114 - Avoid an integer underflow when the dir authority decides whether
14115 a router is stable: we might wrongly label it stable, and compute
14116 a slightly wrong median stability, when a descriptor is published
14118 - Fix a place where we might trigger an assert if we can't build our
14119 own server descriptor yet.
14122 Changes in version 0.1.1.22 - 2006-07-05
14124 - Fix a big bug that was causing servers to not find themselves
14125 reachable if they changed IP addresses. Since only 0.1.1.22+
14126 servers can do reachability testing correctly, now we automatically
14127 make sure to test via one of these.
14128 - Fix to allow clients and mirrors to learn directory info from
14129 descriptor downloads that get cut off partway through.
14130 - Directory authorities had a bug in deciding if a newly published
14131 descriptor was novel enough to make everybody want a copy -- a few
14132 servers seem to be publishing new descriptors many times a minute.
14134 - Fix a rare bug that was causing some servers to complain about
14135 "closing wedged cpuworkers" and skip some circuit create requests.
14136 - Make the Exit flag in directory status documents actually work.
14139 Changes in version 0.1.1.21 - 2006-06-10
14140 o Crash and assert fixes from 0.1.1.20:
14141 - Fix a rare crash on Tor servers that have enabled hibernation.
14142 - Fix a seg fault on startup for Tor networks that use only one
14143 directory authority.
14144 - Fix an assert from a race condition that occurs on Tor servers
14145 while exiting, where various threads are trying to log that they're
14146 exiting, and delete the logs, at the same time.
14147 - Make our unit tests pass again on certain obscure platforms.
14150 - Add support for building SUSE RPM packages.
14151 - Speed up initial bootstrapping for clients: if we are making our
14152 first ever connection to any entry guard, then don't mark it down
14154 - When only one Tor server in the network is labelled as a guard,
14155 and we've already picked him, we would cycle endlessly picking him
14156 again, being unhappy about it, etc. Now we specifically exclude
14157 current guards when picking a new guard.
14158 - Servers send create cells more reliably after the TLS connection
14159 is established: we were sometimes forgetting to send half of them
14160 when we had more than one pending.
14161 - If we get a create cell that asks us to extend somewhere, but the
14162 Tor server there doesn't match the expected digest, we now send
14163 a destroy cell back, rather than silently doing nothing.
14164 - Make options->RedirectExit work again.
14165 - Make cookie authentication for the controller work again.
14166 - Stop being picky about unusual characters in the arguments to
14167 mapaddress. It's none of our business.
14168 - Add a new config option "TestVia" that lets you specify preferred
14169 middle hops to use for test circuits. Perhaps this will let me
14170 debug the reachability problems better.
14172 o Log / documentation fixes:
14173 - If we're a server and some peer has a broken TLS certificate, don't
14174 log about it unless ProtocolWarnings is set, i.e., we want to hear
14175 about protocol violations by others.
14176 - Fix spelling of VirtualAddrNetwork in man page.
14177 - Add a better explanation at the top of the autogenerated torrc file
14178 about what happened to our old torrc.
14181 Changes in version 0.1.1.20 - 2006-05-23
14183 - Downgrade a log severity where servers complain that they're
14185 - Avoid a compile warning on FreeBSD.
14186 - Remove string size limit on NEWDESC messages; solve bug 291.
14187 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
14188 more thoroughly when we're running on windows.
14191 Changes in version 0.1.1.19-rc - 2006-05-03
14193 - Regenerate our local descriptor if it's dirty and we try to use
14194 it locally (e.g. if it changes during reachability detection).
14195 - If we setconf our ORPort to 0, we continued to listen on the
14196 old ORPort and receive connections.
14197 - Avoid a second warning about machine/limits.h on Debian
14199 - Be willing to add our own routerinfo into the routerlist.
14200 Now authorities will include themselves in their directories
14201 and network-statuses.
14202 - Stop trying to upload rendezvous descriptors to every
14203 directory authority: only try the v1 authorities.
14204 - Servers no longer complain when they think they're not
14205 registered with the directory authorities. There were too many
14207 - Backport dist-rpm changes so rpms can be built without errors.
14210 - Implement an option, VirtualAddrMask, to set which addresses
14211 get handed out in response to mapaddress requests. This works
14212 around a bug in tsocks where 127.0.0.0/8 is never socksified.
14215 Changes in version 0.1.1.18-rc - 2006-04-10
14217 - Work harder to download live network-statuses from all the
14218 directory authorities we know about. Improve the threshold
14219 decision logic so we're more robust to edge cases.
14220 - When fetching rendezvous descriptors, we were willing to ask
14221 v2 authorities too, which would always return 404.
14224 - Stop listing down or invalid nodes in the v1 directory. This will
14225 reduce its bulk by about 1/3, and reduce load on directory
14227 - When deciding whether a router is Fast or Guard-worthy, consider
14228 his advertised BandwidthRate and not just the BandwidthCapacity.
14229 - No longer ship INSTALL and README files -- they are useless now.
14230 - Force rpmbuild to behave and honor target_cpu.
14231 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
14232 - Start to include translated versions of the tor-doc-*.html
14233 files, along with the screenshots. Still needs more work.
14234 - Start sending back 512 and 451 errors if mapaddress fails,
14235 rather than not sending anything back at all.
14236 - When we fail to bind or listen on an incoming or outgoing
14237 socket, we should close it before failing. otherwise we just
14238 leak it. (thanks to weasel for finding.)
14239 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
14240 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
14241 - Make NoPublish (even though deprecated) work again.
14242 - Fix a minor security flaw where a versioning auth dirserver
14243 could list a recommended version many times in a row to make
14244 clients more convinced that it's recommended.
14245 - Fix crash bug if there are two unregistered servers running
14246 with the same nickname, one of them is down, and you ask for
14247 them by nickname in your EntryNodes or ExitNodes. Also, try
14248 to pick the one that's running rather than an arbitrary one.
14249 - Fix an infinite loop we could hit if we go offline for too long.
14250 - Complain when we hit WSAENOBUFS on recv() or write() too.
14251 Perhaps this will help us hunt the bug.
14252 - If you're not a versioning dirserver, don't put the string
14253 "client-versions \nserver-versions \n" in your network-status.
14254 - Lower the minimum required number of file descriptors to 1000,
14255 so we can have some overhead for Valgrind on Linux, where the
14256 default ulimit -n is 1024.
14259 - Add tor.dizum.com as the fifth authoritative directory server.
14260 - Add a new config option FetchUselessDescriptors, off by default,
14261 for when you plan to run "exitlist" on your client and you want
14262 to know about even the non-running descriptors.
14265 Changes in version 0.1.1.17-rc - 2006-03-28
14267 - Clients and servers since 0.1.1.10-alpha have been expiring
14268 connections whenever they are idle for 5 minutes and they *do*
14269 have circuits on them. Oops. With this new version, clients will
14270 discard their previous entry guard choices and avoid choosing
14271 entry guards running these flawed versions.
14272 - Fix memory leak when uncompressing concatenated zlib streams. This
14273 was causing substantial leaks over time on Tor servers.
14274 - The v1 directory was including servers as much as 48 hours old,
14275 because that's how the new routerlist->routers works. Now only
14276 include them if they're 20 hours old or less.
14279 - Resume building on irix64, netbsd 2.0, etc.
14280 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
14282 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
14283 and it is confusing some users.
14284 - Mirrors stop caching the v1 directory so often.
14285 - Make the max number of old descriptors that a cache will hold
14286 rise with the number of directory authorities, so we can scale.
14287 - Change our win32 uname() hack to be more forgiving about what
14288 win32 versions it thinks it's found.
14291 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
14293 - When the controller's *setconf commands fail, collect an error
14294 message in a string and hand it back to the controller.
14295 - Make the v2 dir's "Fast" flag based on relative capacity, just
14296 like "Stable" is based on median uptime. Name everything in the
14297 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
14298 - Log server fingerprint on startup, so new server operators don't
14299 have to go hunting around their filesystem for it.
14300 - Return a robots.txt on our dirport to discourage google indexing.
14301 - Let the controller ask for GETINFO dir/status/foo so it can ask
14302 directly rather than connecting to the dir port. Only works when
14303 dirport is set for now.
14305 o New config options rather than constants in the code:
14306 - SocksTimeout: How long do we let a socks connection wait
14307 unattached before we fail it?
14308 - CircuitBuildTimeout: Cull non-open circuits that were born
14309 at least this many seconds ago.
14310 - CircuitIdleTimeout: Cull open clean circuits that were born
14311 at least this many seconds ago.
14314 Changes in version 0.1.1.16-rc - 2006-03-18
14315 o Bugfixes on 0.1.1.15-rc:
14316 - Fix assert when the controller asks to attachstream a connect-wait
14317 or resolve-wait stream.
14318 - Now do address rewriting when the controller asks us to attach
14319 to a particular circuit too. This will let Blossom specify
14320 "moria2.exit" without having to learn what moria2's IP address is.
14321 - Make the "tor --verify-config" command-line work again, so people
14322 can automatically check if their torrc will parse.
14323 - Authoritative dirservers no longer require an open connection from
14324 a server to consider him "reachable". We need this change because
14325 when we add new auth dirservers, old servers won't know not to
14327 - Let Tor build on Sun CC again.
14328 - Fix an off-by-one buffer size in dirserv.c that magically never
14329 hit our three authorities but broke sjmurdoch's own tor network.
14330 - If we as a directory mirror don't know of any v1 directory
14331 authorities, then don't try to cache any v1 directories.
14332 - Stop warning about unknown servers in our family when they are
14333 given as hex digests.
14334 - Stop complaining as quickly to the server operator that he
14335 hasn't registered his nickname/key binding.
14336 - Various cleanups so we can add new V2 Auth Dirservers.
14337 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
14338 reflect the updated flags in our v2 dir protocol.
14339 - Resume allowing non-printable characters for exit streams (both
14340 for connecting and for resolving). Now we tolerate applications
14341 that don't follow the RFCs. But continue to block malformed names
14344 o Bugfixes on 0.1.0.x:
14345 - Fix assert bug in close_logs(): when we close and delete logs,
14346 remove them all from the global "logfiles" list.
14347 - Fix minor integer overflow in calculating when we expect to use up
14348 our bandwidth allocation before hibernating.
14349 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
14350 there are multiple SSLs installed with different versions.
14351 - When we try to be a server and Address is not explicitly set and
14352 our hostname resolves to a private IP address, try to use an
14353 interface address if it has a public address. Now Windows machines
14354 that think of themselves as localhost can work by default.
14357 - Let the controller ask for GETINFO dir/server/foo so it can ask
14358 directly rather than connecting to the dir port.
14359 - Let the controller tell us about certain router descriptors
14360 that it doesn't want Tor to use in circuits. Implement
14361 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
14362 - New config option SafeSocks to reject all application connections
14363 using unsafe socks protocols. Defaults to off.
14366 Changes in version 0.1.1.15-rc - 2006-03-11
14367 o Bugfixes and cleanups:
14368 - When we're printing strings from the network, don't try to print
14369 non-printable characters. This protects us against shell escape
14370 sequence exploits, and also against attacks to fool humans into
14371 misreading their logs.
14372 - Fix a bug where Tor would fail to establish any connections if you
14373 left it off for 24 hours and then started it: we were happy with
14374 the obsolete network statuses, but they all referred to router
14375 descriptors that were too old to fetch, so we ended up with no
14376 valid router descriptors.
14377 - Fix a seg fault in the controller's "getinfo orconn-status"
14378 command while listing status on incoming handshaking connections.
14379 Introduce a status name "NEW" for these connections.
14380 - If we get a linelist or linelist_s config option from the torrc
14381 (e.g. ExitPolicy) and it has no value, warn and skip rather than
14382 silently resetting it to its default.
14383 - Don't abandon entry guards until they've been down or gone for
14385 - Cleaner and quieter log messages.
14388 - New controller signal NEWNYM that makes new application requests
14389 use clean circuits.
14390 - Add a new circuit purpose 'controller' to let the controller ask
14391 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
14392 controller command to let you specify the purpose if you're
14393 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
14394 command to let you change a circuit's purpose after it's been
14396 - Accept "private:*" in routerdesc exit policies; not generated yet
14397 because older Tors do not understand it.
14398 - Add BSD-style contributed startup script "rc.subr" from Peter
14402 Changes in version 0.1.1.14-alpha - 2006-02-20
14403 o Bugfixes on 0.1.1.x:
14404 - Don't die if we ask for a stdout or stderr log (even implicitly)
14405 and we're set to RunAsDaemon -- just warn.
14406 - We still had a few bugs in the OR connection rotation code that
14407 caused directory servers to slowly aggregate connections to other
14408 fast Tor servers. This time for sure!
14409 - Make log entries on Win32 include the name of the function again.
14410 - We were treating a pair of exit policies if they were equal even
14411 if one said accept and the other said reject -- causing us to
14412 not always publish a new descriptor since we thought nothing
14414 - Retry pending server downloads as well as pending networkstatus
14415 downloads when we unexpectedly get a socks request.
14416 - We were ignoring the IS_FAST flag in the directory status,
14417 meaning we were willing to pick trivial-bandwidth nodes for "fast"
14419 - If the controller's SAVECONF command fails (e.g. due to file
14420 permissions), let the controller know that it failed.
14423 - If we're trying to be a Tor server and running Windows 95/98/ME
14424 as a server, explain that we'll likely crash.
14425 - When we're a server, a client asks for an old-style directory,
14426 and our write bucket is empty, don't give it to him. This way
14427 small servers can continue to serve the directory *sometimes*,
14428 without getting overloaded.
14429 - Compress exit policies even more -- look for duplicate lines
14431 - Clients now honor the "guard" flag in the router status when
14432 picking entry guards, rather than looking at is_fast or is_stable.
14433 - Retain unrecognized lines in $DATADIR/state file, so that we can
14434 be forward-compatible.
14435 - Generate 18.0.0.0/8 address policy format in descs when we can;
14436 warn when the mask is not reducible to a bit-prefix.
14437 - Let the user set ControlListenAddress in the torrc. This can be
14438 dangerous, but there are some cases (like a secured LAN) where it
14440 - Split ReachableAddresses into ReachableDirAddresses and
14441 ReachableORAddresses, so we can restrict Dir conns to port 80
14442 and OR conns to port 443.
14443 - Now we can target arch and OS in rpm builds (contributed by
14444 Phobos). Also make the resulting dist-rpm filename match the
14446 - New config options to help controllers: FetchServerDescriptors
14447 and FetchHidServDescriptors for whether to fetch server
14448 info and hidserv info or let the controller do it, and
14449 PublishServerDescriptor and PublishHidServDescriptors.
14450 - Also let the controller set the __AllDirActionsPrivate config
14451 option if you want all directory fetches/publishes to happen via
14452 Tor (it assumes your controller bootstraps your circuits).
14455 Changes in version 0.1.0.17 - 2006-02-17
14456 o Crash bugfixes on 0.1.0.x:
14457 - When servers with a non-zero DirPort came out of hibernation,
14458 sometimes they would trigger an assert.
14460 o Other important bugfixes:
14461 - On platforms that don't have getrlimit (like Windows), we were
14462 artificially constraining ourselves to a max of 1024
14463 connections. Now just assume that we can handle as many as 15000
14464 connections. Hopefully this won't cause other problems.
14466 o Backported features:
14467 - When we're a server, a client asks for an old-style directory,
14468 and our write bucket is empty, don't give it to him. This way
14469 small servers can continue to serve the directory *sometimes*,
14470 without getting overloaded.
14471 - Whenever you get a 503 in response to a directory fetch, try
14472 once more. This will become important once servers start sending
14473 503's whenever they feel busy.
14474 - Fetch a new directory every 120 minutes, not every 40 minutes.
14475 Now that we have hundreds of thousands of users running the old
14476 directory algorithm, it's starting to hurt a lot.
14477 - Bump up the period for forcing a hidden service descriptor upload
14478 from 20 minutes to 1 hour.
14481 Changes in version 0.1.1.13-alpha - 2006-02-09
14482 o Crashes in 0.1.1.x:
14483 - When you tried to setconf ORPort via the controller, Tor would
14484 crash. So people using TorCP to become a server were sad.
14485 - Solve (I hope) the stack-smashing bug that we were seeing on fast
14486 servers. The problem appears to be something do with OpenSSL's
14487 random number generation, or how we call it, or something. Let me
14488 know if the crashes continue.
14489 - Turn crypto hardware acceleration off by default, until we find
14490 somebody smart who can test it for us. (It appears to produce
14491 seg faults in at least some cases.)
14492 - Fix a rare assert error when we've tried all intro points for
14493 a hidden service and we try fetching the service descriptor again:
14494 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
14497 - Fix a major load balance bug: we were round-robining in 16 KB
14498 chunks, and servers with bandwidthrate of 20 KB, while downloading
14499 a 600 KB directory, would starve their other connections. Now we
14500 try to be a bit more fair.
14501 - Dir authorities and mirrors were never expiring the newest
14502 descriptor for each server, causing memory and directory bloat.
14503 - Fix memory-bloating and connection-bloating bug on servers: We
14504 were never closing any connection that had ever had a circuit on
14505 it, because we were checking conn->n_circuits == 0, yet we had a
14506 bug that let it go negative.
14507 - Make Tor work using squid as your http proxy again -- squid
14508 returns an error if you ask for a URL that's too long, and it uses
14509 a really generic error message. Plus, many people are behind a
14510 transparent squid so they don't even realize it.
14511 - On platforms that don't have getrlimit (like Windows), we were
14512 artificially constraining ourselves to a max of 1024
14513 connections. Now just assume that we can handle as many as 15000
14514 connections. Hopefully this won't cause other problems.
14515 - Add a new config option ExitPolicyRejectPrivate which defaults to
14516 1. This means all exit policies will begin with rejecting private
14517 addresses, unless the server operator explicitly turns it off.
14520 - Clients no longer download descriptors for non-running
14522 - Before we add new directory authorities, we should make it
14523 clear that only v1 authorities should receive/publish hidden
14524 service descriptors.
14527 - As soon as we've fetched some more directory info, immediately
14528 try to download more server descriptors. This way we don't have
14529 a 10 second pause during initial bootstrapping.
14530 - Remove even more loud log messages that the server operator can't
14532 - When we're running an obsolete or un-recommended version, make
14533 the log message more clear about what the problem is and what
14534 versions *are* still recommended.
14535 - Provide a more useful warn message when our onion queue gets full:
14536 the CPU is too slow or the exit policy is too liberal.
14537 - Don't warn when we receive a 503 from a dirserver/cache -- this
14538 will pave the way for them being able to refuse if they're busy.
14539 - When we fail to bind a listener, try to provide a more useful
14540 log message: e.g., "Is Tor already running?"
14541 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
14542 Goldberg can prove things about our handshake protocol more
14544 - MaxConn has been obsolete for a while now. Document the ConnLimit
14545 config option, which is a *minimum* number of file descriptors
14546 that must be available else Tor refuses to start.
14547 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
14548 if you log to syslog and want something other than LOG_DAEMON.
14549 - Make dirservers generate a separate "guard" flag to mean,
14550 "would make a good entry guard". Make clients parse it and vote
14551 on it. Not used by clients yet.
14552 - Implement --with-libevent-dir option to ./configure. Also, improve
14553 search techniques to find libevent, and use those for openssl too.
14554 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
14555 - Only start testing reachability once we've established a
14556 circuit. This will make startup on dirservers less noisy.
14557 - Don't try to upload hidden service descriptors until we have
14558 established a circuit.
14559 - Fix the controller's "attachstream 0" command to treat conn like
14560 it just connected, doing address remapping, handling .exit and
14561 .onion idioms, and so on. Now we're more uniform in making sure
14562 that the controller hears about new and closing connections.
14565 Changes in version 0.1.1.12-alpha - 2006-01-11
14566 o Bugfixes on 0.1.1.x:
14567 - The fix to close duplicate server connections was closing all
14568 Tor client connections if they didn't establish a circuit
14569 quickly enough. Oops.
14570 - Fix minor memory issue (double-free) that happened on exit.
14572 o Bugfixes on 0.1.0.x:
14573 - Tor didn't warn when it failed to open a log file.
14576 Changes in version 0.1.1.11-alpha - 2006-01-10
14577 o Crashes in 0.1.1.x:
14578 - Include all the assert/crash fixes from 0.1.0.16.
14579 - If you start Tor and then quit very quickly, there were some
14580 races that tried to free things that weren't allocated yet.
14581 - Fix a rare memory stomp if you're running hidden services.
14582 - Fix segfault when specifying DirServer in config without nickname.
14583 - Fix a seg fault when you finish connecting to a server but at
14584 that moment you dump his server descriptor.
14585 - Extendcircuit and Attachstream controller commands would
14586 assert/crash if you don't give them enough arguments.
14587 - Fix an assert error when we're out of space in the connection_list
14588 and we try to post a hidden service descriptor (reported by weasel).
14589 - If you specify a relative torrc path and you set RunAsDaemon in
14590 your torrc, then it chdir()'s to the new directory. If you HUP,
14591 it tries to load the new torrc location, fails, and exits.
14592 The fix: no longer allow a relative path to torrc using -f.
14595 - Implement "entry guards": automatically choose a handful of entry
14596 nodes and stick with them for all circuits. Only pick new guards
14597 when the ones you have are unsuitable, and if the old guards
14598 become suitable again, switch back. This will increase security
14599 dramatically against certain end-point attacks. The EntryNodes
14600 config option now provides some hints about which entry guards you
14601 want to use most; and StrictEntryNodes means to only use those.
14602 - New directory logic: download by descriptor digest, not by
14603 fingerprint. Caches try to download all listed digests from
14604 authorities; clients try to download "best" digests from caches.
14605 This avoids partitioning and isolating attacks better.
14606 - Make the "stable" router flag in network-status be the median of
14607 the uptimes of running valid servers, and make clients pay
14608 attention to the network-status flags. Thus the cutoff adapts
14609 to the stability of the network as a whole, making IRC, IM, etc
14610 connections more reliable.
14613 - Tor servers with dynamic IP addresses were needing to wait 18
14614 hours before they could start doing reachability testing using
14615 the new IP address and ports. This is because they were using
14616 the internal descriptor to learn what to test, yet they were only
14617 rebuilding the descriptor once they decided they were reachable.
14618 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
14619 to download certain server descriptors, throw them away, and then
14620 fetch them again after 30 minutes. Now mirrors throw away these
14621 server descriptors so clients can't get them.
14622 - We were leaving duplicate connections to other ORs open for a week,
14623 rather than closing them once we detect a duplicate. This only
14624 really affected authdirservers, but it affected them a lot.
14625 - Spread the authdirservers' reachability testing over the entire
14626 testing interval, so we don't try to do 500 TLS's at once every
14630 - If the network is down, and we try to connect to a conn because
14631 we have a circuit in mind, and we timeout (30 seconds) because the
14632 network never answers, we were expiring the circuit, but we weren't
14633 obsoleting the connection or telling the entry_guards functions.
14634 - Some Tor servers process billions of cells per day. These statistics
14635 need to be uint64_t's.
14636 - Check for integer overflows in more places, when adding elements
14637 to smartlists. This could possibly prevent a buffer overflow
14638 on malicious huge inputs. I don't see any, but I haven't looked
14640 - ReachableAddresses kept growing new "reject *:*" lines on every
14642 - When you "setconf log" via the controller, it should remove all
14643 logs. We were automatically adding back in a "log notice stdout".
14644 - Newly bootstrapped Tor networks couldn't establish hidden service
14645 circuits until they had nodes with high uptime. Be more tolerant.
14646 - We were marking servers down when they could not answer every piece
14647 of the directory request we sent them. This was far too harsh.
14648 - Fix the torify (tsocks) config file to not use Tor for localhost
14650 - Directory authorities now go to the proper authority when asking for
14651 a networkstatus, even when they want a compressed one.
14652 - Fix a harmless bug that was causing Tor servers to log
14653 "Got an end because of misc error, but we're not an AP. Closing."
14654 - Authorities were treating their own descriptor changes as cosmetic,
14655 meaning the descriptor available in the network-status and the
14656 descriptor that clients downloaded were different.
14657 - The OS X installer was adding a symlink for tor_resolve but
14658 the binary was called tor-resolve (reported by Thomas Hardly).
14659 - Workaround a problem with some http proxies where they refuse GET
14660 requests that specify "Content-Length: 0" (reported by Adrian).
14661 - Fix wrong log message when you add a "HiddenServiceNodes" config
14662 line without any HiddenServiceDir line (reported by Chris Thomas).
14665 - Write the TorVersion into the state file so we have a prayer of
14666 keeping forward and backward compatibility.
14667 - Revive the FascistFirewall config option rather than eliminating it:
14668 now it's a synonym for ReachableAddresses *:80,*:443.
14669 - Clients choose directory servers from the network status lists,
14670 not from their internal list of router descriptors. Now they can
14671 go to caches directly rather than needing to go to authorities
14673 - Directory authorities ignore router descriptors that have only
14674 cosmetic differences: do this for 0.1.0.x servers now too.
14675 - Add a new flag to network-status indicating whether the server
14676 can answer v2 directory requests too.
14677 - Authdirs now stop whining so loudly about bad descriptors that
14678 they fetch from other dirservers. So when there's a log complaint,
14679 it's for sure from a freshly uploaded descriptor.
14680 - Reduce memory requirements in our structs by changing the order
14682 - There used to be two ways to specify your listening ports in a
14683 server descriptor: on the "router" line and with a separate "ports"
14684 line. Remove support for the "ports" line.
14685 - New config option "AuthDirRejectUnlisted" for auth dirservers as
14686 a panic button: if we get flooded with unusable servers we can
14687 revert to only listing servers in the approved-routers file.
14688 - Auth dir servers can now mark a fingerprint as "!reject" or
14689 "!invalid" in the approved-routers file (as its nickname), to
14690 refuse descriptors outright or include them but marked as invalid.
14691 - Servers store bandwidth history across restarts/crashes.
14692 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
14693 get a better idea of why their circuits failed. Not used yet.
14694 - Directory mirrors now cache up to 16 unrecognized network-status
14695 docs. Now we can add new authdirservers and they'll be cached too.
14696 - When picking a random directory, prefer non-authorities if any
14698 - New controller option "getinfo desc/all-recent" to fetch the
14699 latest server descriptor for every router that Tor knows about.
14702 Changes in version 0.1.0.16 - 2006-01-02
14703 o Crash bugfixes on 0.1.0.x:
14704 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14705 corrupting the heap, losing FDs, or crashing when we need to resize
14706 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14707 - It turns out sparc64 platforms crash on unaligned memory access
14708 too -- so detect and avoid this.
14709 - Handle truncated compressed data correctly (by detecting it and
14711 - Fix possible-but-unlikely free(NULL) in control.c.
14712 - When we were closing connections, there was a rare case that
14713 stomped on memory, triggering seg faults and asserts.
14714 - Avoid potential infinite recursion when building a descriptor. (We
14715 don't know that it ever happened, but better to fix it anyway.)
14716 - We were neglecting to unlink marked circuits from soon-to-close OR
14717 connections, which caused some rare scribbling on freed memory.
14718 - Fix a memory stomping race bug when closing the joining point of two
14719 rendezvous circuits.
14720 - Fix an assert in time parsing found by Steven Murdoch.
14722 o Other bugfixes on 0.1.0.x:
14723 - When we're doing reachability testing, provide more useful log
14724 messages so the operator knows what to expect.
14725 - Do not check whether DirPort is reachable when we are suppressing
14726 advertising it because of hibernation.
14727 - When building with -static or on Solaris, we sometimes needed -ldl.
14728 - When we're deciding whether a stream has enough circuits around
14729 that can handle it, count the freshly dirty ones and not the ones
14730 that are so dirty they won't be able to handle it.
14731 - When we're expiring old circuits, we had a logic error that caused
14732 us to close new rendezvous circuits rather than old ones.
14733 - Give a more helpful log message when you try to change ORPort via
14734 the controller: you should upgrade Tor if you want that to work.
14735 - We were failing to parse Tor versions that start with "Tor ".
14736 - Tolerate faulty streams better: when a stream fails for reason
14737 exitpolicy, stop assuming that the router is lying about his exit
14738 policy. When a stream fails for reason misc, allow it to retry just
14739 as if it was resolvefailed. When a stream has failed three times,
14740 reset its failure count so we can try again and get all three tries.
14743 Changes in version 0.1.1.10-alpha - 2005-12-11
14744 o Correctness bugfixes on 0.1.0.x:
14745 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14746 corrupting the heap, losing FDs, or crashing when we need to resize
14747 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14748 - Stop doing the complex voodoo overkill checking for insecure
14749 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
14750 - When we were closing connections, there was a rare case that
14751 stomped on memory, triggering seg faults and asserts.
14752 - We were neglecting to unlink marked circuits from soon-to-close OR
14753 connections, which caused some rare scribbling on freed memory.
14754 - When we're deciding whether a stream has enough circuits around
14755 that can handle it, count the freshly dirty ones and not the ones
14756 that are so dirty they won't be able to handle it.
14757 - Recover better from TCP connections to Tor servers that are
14758 broken but don't tell you (it happens!); and rotate TLS
14759 connections once a week.
14760 - When we're expiring old circuits, we had a logic error that caused
14761 us to close new rendezvous circuits rather than old ones.
14762 - Fix a scary-looking but apparently harmless bug where circuits
14763 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
14764 servers, and never switch to state CIRCUIT_STATE_OPEN.
14765 - When building with -static or on Solaris, we sometimes needed to
14767 - Give a useful message when people run Tor as the wrong user,
14768 rather than telling them to start chowning random directories.
14769 - We were failing to inform the controller about new .onion streams.
14771 o Security bugfixes on 0.1.0.x:
14772 - Refuse server descriptors if the fingerprint line doesn't match
14773 the included identity key. Tor doesn't care, but other apps (and
14774 humans) might actually be trusting the fingerprint line.
14775 - We used to kill the circuit when we receive a relay command we
14776 don't recognize. Now we just drop it.
14777 - Start obeying our firewall options more rigorously:
14778 . If we can't get to a dirserver directly, try going via Tor.
14779 . Don't ever try to connect (as a client) to a place our
14780 firewall options forbid.
14781 . If we specify a proxy and also firewall options, obey the
14782 firewall options even when we're using the proxy: some proxies
14783 can only proxy to certain destinations.
14784 - Fix a bug found by Lasse Overlier: when we were making internal
14785 circuits (intended to be cannibalized later for rendezvous and
14786 introduction circuits), we were picking them so that they had
14787 useful exit nodes. There was no need for this, and it actually
14788 aids some statistical attacks.
14789 - Start treating internal circuits and exit circuits separately.
14790 It's important to keep them separate because internal circuits
14791 have their last hops picked like middle hops, rather than like
14792 exit hops. So exiting on them will break the user's expectations.
14794 o Bugfixes on 0.1.1.x:
14795 - Take out the mis-feature where we tried to detect IP address
14796 flapping for people with DynDNS, and chose not to upload a new
14797 server descriptor sometimes.
14798 - Try to be compatible with OpenSSL 0.9.6 again.
14799 - Log fix: when the controller is logging about .onion addresses,
14800 sometimes it didn't include the ".onion" part of the address.
14801 - Don't try to modify options->DirServers internally -- if the
14802 user didn't specify any, just add the default ones directly to
14803 the trusted dirserver list. This fixes a bug where people running
14804 controllers would use SETCONF on some totally unrelated config
14805 option, and Tor would start yelling at them about changing their
14807 - Let the controller's redirectstream command specify a port, in
14808 case the controller wants to change that too.
14809 - When we requested a pile of server descriptors, we sometimes
14810 accidentally launched a duplicate request for the first one.
14811 - Bugfix for trackhostexits: write down the fingerprint of the
14812 chosen exit, not its nickname, because the chosen exit might not
14814 - When parsing foo.exit, if foo is unknown, and we are leaving
14815 circuits unattached, set the chosen_exit field and leave the
14816 address empty. This matters because controllers got confused
14818 - Directory authorities no longer try to download server
14819 descriptors that they know they will reject.
14821 o Features and updates:
14822 - Replace balanced trees with hash tables: this should make stuff
14823 significantly faster.
14824 - Resume using the AES counter-mode implementation that we ship,
14825 rather than OpenSSL's. Ours is significantly faster.
14826 - Many other CPU and memory improvements.
14827 - Add a new config option FastFirstHopPK (on by default) so clients
14828 do a trivial crypto handshake for their first hop, since TLS has
14829 already taken care of confidentiality and authentication.
14830 - Add a new config option TestSocks so people can see if their
14831 applications are using socks4, socks4a, socks5-with-ip, or
14832 socks5-with-hostname. This way they don't have to keep mucking
14833 with tcpdump and wondering if something got cached somewhere.
14834 - Warn when listening on a public address for socks. I suspect a
14835 lot of people are setting themselves up as open socks proxies,
14836 and they have no idea that jerks on the Internet are using them,
14837 since they simply proxy the traffic into the Tor network.
14838 - Add "private:*" as an alias in configuration for policies. Now
14839 you can simplify your exit policy rather than needing to list
14840 every single internal or nonroutable network space.
14841 - Add a new controller event type that allows controllers to get
14842 all server descriptors that were uploaded to a router in its role
14843 as authoritative dirserver.
14844 - Start shipping socks-extensions.txt, tor-doc-unix.html,
14845 tor-doc-server.html, and stylesheet.css in the tarball.
14846 - Stop shipping tor-doc.html in the tarball.
14849 Changes in version 0.1.1.9-alpha - 2005-11-15
14850 o Usability improvements:
14851 - Start calling it FooListenAddress rather than FooBindAddress,
14852 since few of our users know what it means to bind an address
14854 - Reduce clutter in server logs. We're going to try to make
14855 them actually usable now. New config option ProtocolWarnings that
14856 lets you hear about how _other Tors_ are breaking the protocol. Off
14858 - Divide log messages into logging domains. Once we put some sort
14859 of interface on this, it will let people looking at more verbose
14860 log levels specify the topics they want to hear more about.
14861 - Make directory servers return better http 404 error messages
14862 instead of a generic "Servers unavailable".
14863 - Check for even more Windows version flags when writing the platform
14864 string in server descriptors, and note any we don't recognize.
14865 - Clean up more of the OpenSSL memory when exiting, so we can detect
14866 memory leaks better.
14867 - Make directory authorities be non-versioning, non-naming by
14868 default. Now we can add new directory servers without requiring
14869 their operators to pay close attention.
14870 - When logging via syslog, include the pid whenever we provide
14871 a log entry. Suggested by Todd Fries.
14873 o Performance improvements:
14874 - Directory servers now silently throw away new descriptors that
14875 haven't changed much if the timestamps are similar. We do this to
14876 tolerate older Tor servers that upload a new descriptor every 15
14877 minutes. (It seemed like a good idea at the time.)
14878 - Inline bottleneck smartlist functions; use fast versions by default.
14879 - Add a "Map from digest to void*" abstraction digestmap_t so we
14880 can do less hex encoding/decoding. Use it in router_get_by_digest()
14881 to resolve a performance bottleneck.
14882 - Allow tor_gzip_uncompress to extract as much as possible from
14883 truncated compressed data. Try to extract as many
14884 descriptors as possible from truncated http responses (when
14885 DIR_PURPOSE_FETCH_ROUTERDESC).
14886 - Make circ->onionskin a pointer, not a static array. moria2 was using
14887 125000 circuit_t's after it had been up for a few weeks, which
14888 translates to 20+ megs of wasted space.
14889 - The private half of our EDH handshake keys are now chosen out
14890 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
14892 o Security improvements:
14893 - Start making directory caches retain old routerinfos, so soon
14894 clients can start asking by digest of descriptor rather than by
14895 fingerprint of server.
14896 - Add half our entropy from RAND_poll in OpenSSL. This knows how
14897 to use egd (if present), openbsd weirdness (if present), vms/os2
14898 weirdness (if we ever port there), and more in the future.
14900 o Bugfixes on 0.1.0.x:
14901 - Do round-robin writes of at most 16 kB per write. This might be
14902 more fair on loaded Tor servers, and it might resolve our Windows
14903 crash bug. It might also slow things down.
14904 - Our TLS handshakes were generating a single public/private
14905 keypair for the TLS context, rather than making a new one for
14906 each new connections. Oops. (But we were still rotating them
14907 periodically, so it's not so bad.)
14908 - When we were cannibalizing a circuit with a particular exit
14909 node in mind, we weren't checking to see if that exit node was
14910 already present earlier in the circuit. Oops.
14911 - When a Tor server's IP changes (e.g. from a dyndns address),
14912 upload a new descriptor so clients will learn too.
14913 - Really busy servers were keeping enough circuits open on stable
14914 connections that they were wrapping around the circuit_id
14915 space. (It's only two bytes.) This exposed a bug where we would
14916 feel free to reuse a circuit_id even if it still exists but has
14917 been marked for close. Try to fix this bug. Some bug remains.
14918 - If we would close a stream early (e.g. it asks for a .exit that
14919 we know would refuse it) but the LeaveStreamsUnattached config
14920 option is set by the controller, then don't close it.
14922 o Bugfixes on 0.1.1.8-alpha:
14923 - Fix a big pile of memory leaks, some of them serious.
14924 - Do not try to download a routerdesc if we would immediately reject
14926 - Resume inserting a newline between all router descriptors when
14927 generating (old style) signed directories, since our spec says
14929 - When providing content-type application/octet-stream for
14930 server descriptors using .z, we were leaving out the
14931 content-encoding header. Oops. (Everything tolerated this just
14932 fine, but that doesn't mean we need to be part of the problem.)
14933 - Fix a potential seg fault in getconf and getinfo using version 1
14934 of the controller protocol.
14935 - Avoid crash: do not check whether DirPort is reachable when we
14936 are suppressing it because of hibernation.
14937 - Make --hash-password not crash on exit.
14940 Changes in version 0.1.1.8-alpha - 2005-10-07
14941 o New features (major):
14942 - Clients don't download or use the directory anymore. Now they
14943 download and use network-statuses from the trusted dirservers,
14944 and fetch individual server descriptors as needed from mirrors.
14945 See dir-spec.txt for all the gory details.
14946 - Be more conservative about whether to advertise our DirPort.
14947 The main change is to not advertise if we're running at capacity
14948 and either a) we could hibernate or b) our capacity is low and
14949 we're using a default DirPort.
14950 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
14952 o New features (minor):
14953 - Try to be smart about when to retry network-status and
14954 server-descriptor fetches. Still needs some tuning.
14955 - Stop parsing, storing, or using running-routers output (but
14956 mirrors still cache and serve it).
14957 - Consider a threshold of versioning dirservers (dirservers who have
14958 an opinion about which Tor versions are still recommended) before
14959 deciding whether to warn the user that he's obsolete.
14960 - Dirservers can now reject/invalidate by key and IP, with the
14961 config options "AuthDirInvalid" and "AuthDirReject". This is
14962 useful since currently we automatically list servers as running
14963 and usable even if we know they're jerks.
14964 - Provide dire warnings to any users who set DirServer; move it out
14965 of torrc.sample and into torrc.complete.
14966 - Add MyFamily to torrc.sample in the server section.
14967 - Add nicknames to the DirServer line, so we can refer to them
14968 without requiring all our users to memorize their IP addresses.
14969 - When we get an EOF or a timeout on a directory connection, note
14970 how many bytes of serverdesc we are dropping. This will help
14971 us determine whether it is smart to parse incomplete serverdesc
14973 - Add a new function to "change pseudonyms" -- that is, to stop
14974 using any currently-dirty circuits for new streams, so we don't
14975 link new actions to old actions. Currently it's only called on
14976 HUP (or SIGNAL RELOAD).
14977 - On sighup, if UseHelperNodes changed to 1, use new circuits.
14978 - Start using RAND_bytes rather than RAND_pseudo_bytes from
14979 OpenSSL. Also, reseed our entropy every hour, not just at
14980 startup. And entropy in 512-bit chunks, not 160-bit chunks.
14982 o Fixes on 0.1.1.7-alpha:
14983 - Nobody ever implemented EVENT_ADDRMAP for control protocol
14984 version 0, so don't let version 0 controllers ask for it.
14985 - If you requested something with too many newlines via the
14986 v1 controller protocol, you could crash tor.
14987 - Fix a number of memory leaks, including some pretty serious ones.
14988 - Re-enable DirPort testing again, so Tor servers will be willing
14989 to advertise their DirPort if it's reachable.
14990 - On TLS handshake, only check the other router's nickname against
14991 its expected nickname if is_named is set.
14993 o Fixes forward-ported from 0.1.0.15:
14994 - Don't crash when we don't have any spare file descriptors and we
14995 try to spawn a dns or cpu worker.
14996 - Make the numbers in read-history and write-history into uint64s,
14997 so they don't overflow and publish negatives in the descriptor.
14999 o Fixes on 0.1.0.x:
15000 - For the OS X package's modified privoxy config file, comment
15001 out the "logfile" line so we don't log everything passed
15003 - We were whining about using socks4 or socks5-with-local-lookup
15004 even when it's an IP in the "virtual" range we designed exactly
15006 - We were leaking some memory every time the client changes IPs.
15007 - Never call free() on tor_malloc()d memory. This will help us
15008 use dmalloc to detect memory leaks.
15009 - Check for named servers when looking them up by nickname;
15010 warn when we'recalling a non-named server by its nickname;
15011 don't warn twice about the same name.
15012 - Try to list MyFamily elements by key, not by nickname, and warn
15013 if we've not heard of the server.
15014 - Make windows platform detection (uname equivalent) smarter.
15015 - It turns out sparc64 doesn't like unaligned access either.
15018 Changes in version 0.1.0.15 - 2005-09-23
15019 o Bugfixes on 0.1.0.x:
15020 - Reject ports 465 and 587 (spam targets) in default exit policy.
15021 - Don't crash when we don't have any spare file descriptors and we
15022 try to spawn a dns or cpu worker.
15023 - Get rid of IgnoreVersion undocumented config option, and make us
15024 only warn, never exit, when we're running an obsolete version.
15025 - Don't try to print a null string when your server finds itself to
15026 be unreachable and the Address config option is empty.
15027 - Make the numbers in read-history and write-history into uint64s,
15028 so they don't overflow and publish negatives in the descriptor.
15029 - Fix a minor memory leak in smartlist_string_remove().
15030 - We were only allowing ourselves to upload a server descriptor at
15031 most every 20 minutes, even if it changed earlier than that.
15032 - Clean up log entries that pointed to old URLs.
15035 Changes in version 0.1.1.7-alpha - 2005-09-14
15036 o Fixes on 0.1.1.6-alpha:
15037 - Exit servers were crashing when people asked them to make a
15038 connection to an address not in their exit policy.
15039 - Looking up a non-existent stream for a v1 control connection would
15041 - Fix a seg fault if we ask a dirserver for a descriptor by
15042 fingerprint but he doesn't know about him.
15043 - SETCONF was appending items to linelists, not clearing them.
15044 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
15045 out and refuse the setconf if it would fail.
15046 - Downgrade the dirserver log messages when whining about
15050 - Add Peter Palfrader's check-tor script to tor/contrib/
15051 It lets you easily check whether a given server (referenced by
15052 nickname) is reachable by you.
15053 - Numerous changes to move towards client-side v2 directories. Not
15056 o Fixes on 0.1.0.x:
15057 - If the user gave tor an odd number of command-line arguments,
15058 we were silently ignoring the last one. Now we complain and fail.
15059 [This wins the oldest-bug prize -- this bug has been present since
15060 November 2002, as released in Tor 0.0.0.]
15061 - Do not use unaligned memory access on alpha, mips, or mipsel.
15062 It *works*, but is very slow, so we treat them as if it doesn't.
15063 - Retry directory requests if we fail to get an answer we like
15064 from a given dirserver (we were retrying before, but only if
15065 we fail to connect).
15066 - When writing the RecommendedVersions line, sort them first.
15067 - When the client asked for a rendezvous port that the hidden
15068 service didn't want to provide, we were sending an IP address
15069 back along with the end cell. Fortunately, it was zero. But stop
15071 - Correct "your server is reachable" log entries to indicate that
15072 it was self-testing that told us so.
15075 Changes in version 0.1.1.6-alpha - 2005-09-09
15076 o Fixes on 0.1.1.5-alpha:
15077 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
15078 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
15079 - Fix bug with tor_memmem finding a match at the end of the string.
15080 - Make unit tests run without segfaulting.
15081 - Resolve some solaris x86 compile warnings.
15082 - Handle duplicate lines in approved-routers files without warning.
15083 - Fix bug where as soon as a server refused any requests due to his
15084 exit policy (e.g. when we ask for localhost and he tells us that's
15085 127.0.0.1 and he won't do it), we decided he wasn't obeying his
15086 exit policy using him for any exits.
15087 - Only do openssl hardware accelerator stuff if openssl version is
15090 o New controller features/fixes:
15091 - Add a "RESETCONF" command so you can set config options like
15092 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
15093 a config option in the torrc with no value, then it clears it
15094 entirely (rather than setting it to its default).
15095 - Add a "GETINFO config-file" to tell us where torrc is.
15096 - Avoid sending blank lines when GETINFO replies should be empty.
15097 - Add a QUIT command for the controller (for using it manually).
15098 - Fix a bug in SAVECONF that was adding default dirservers and
15099 other redundant entries to the torrc file.
15101 o Start on the new directory design:
15102 - Generate, publish, cache, serve new network-status format.
15103 - Publish individual descriptors (by fingerprint, by "all", and by
15105 - Publish client and server recommended versions separately.
15106 - Allow tor_gzip_uncompress() to handle multiple concatenated
15107 compressed strings. Serve compressed groups of router
15108 descriptors. The compression logic here could be more
15110 - Distinguish v1 authorities (all currently trusted directories)
15111 from v2 authorities (all trusted directories).
15112 - Change DirServers config line to note which dirs are v1 authorities.
15113 - Add configuration option "V1AuthoritativeDirectory 1" which
15114 moria1, moria2, and tor26 should set.
15115 - Remove option when getting directory cache to see whether they
15116 support running-routers; they all do now. Replace it with one
15117 to see whether caches support v2 stuff.
15120 - Dirservers now do their own external reachability testing of each
15121 Tor server, and only list them as running if they've been found to
15122 be reachable. We also send back warnings to the server's logs if
15123 it uploads a descriptor that we already believe is unreachable.
15124 - Implement exit enclaves: if we know an IP address for the
15125 destination, and there's a running Tor server at that address
15126 which allows exit to the destination, then extend the circuit to
15127 that exit first. This provides end-to-end encryption and end-to-end
15128 authentication. Also, if the user wants a .exit address or enclave,
15129 use 4 hops rather than 3, and cannibalize a general circ for it
15131 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
15132 controller. Also, rotate dns and cpu workers if the controller
15133 changes options that will affect them; and initialize the dns
15134 worker cache tree whether or not we start out as a server.
15135 - Only upload a new server descriptor when options change, 18
15136 hours have passed, uptime is reset, or bandwidth changes a lot.
15137 - Check [X-]Forwarded-For headers in HTTP requests when generating
15138 log messages. This lets people run dirservers (and caches) behind
15139 Apache but still know which IP addresses are causing warnings.
15141 o Config option changes:
15142 - Replace (Fascist)Firewall* config options with a new
15143 ReachableAddresses option that understands address policies.
15144 For example, "ReachableAddresses *:80,*:443"
15145 - Get rid of IgnoreVersion undocumented config option, and make us
15146 only warn, never exit, when we're running an obsolete version.
15147 - Make MonthlyAccountingStart config option truly obsolete now.
15149 o Fixes on 0.1.0.x:
15150 - Reject ports 465 and 587 in the default exit policy, since
15151 people have started using them for spam too.
15152 - It turns out we couldn't bootstrap a network since we added
15153 reachability detection in 0.1.0.1-rc. Good thing the Tor network
15154 has never gone down. Add an AssumeReachable config option to let
15155 servers and dirservers bootstrap. When we're trying to build a
15156 high-uptime or high-bandwidth circuit but there aren't enough
15157 suitable servers, try being less picky rather than simply failing.
15158 - Our logic to decide if the OR we connected to was the right guy
15159 was brittle and maybe open to a mitm for unverified routers.
15160 - We weren't cannibalizing circuits correctly for
15161 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
15162 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
15163 build those from scratch. This should make hidden services faster.
15164 - Predict required circuits better, with an eye toward making hidden
15165 services faster on the service end.
15166 - Retry streams if the exit node sends back a 'misc' failure. This
15167 should result in fewer random failures. Also, after failing
15168 from resolve failed or misc, reset the num failures, so we give
15169 it a fair shake next time we try.
15170 - Clean up the rendezvous warn log msgs, and downgrade some to info.
15171 - Reduce severity on logs about dns worker spawning and culling.
15172 - When we're shutting down and we do something like try to post a
15173 server descriptor or rendezvous descriptor, don't complain that
15174 we seem to be unreachable. Of course we are, we're shutting down.
15175 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
15176 We don't use them yet, but maybe one day our DNS resolver will be
15177 able to discover them.
15178 - Make ContactInfo mandatory for authoritative directory servers.
15179 - Require server descriptors to list IPv4 addresses -- hostnames
15180 are no longer allowed. This also fixes some potential security
15181 problems with people providing hostnames as their address and then
15182 preferentially resolving them to partition users.
15183 - Change log line for unreachability to explicitly suggest /etc/hosts
15184 as the culprit. Also make it clearer what IP address and ports we're
15185 testing for reachability.
15186 - Put quotes around user-supplied strings when logging so users are
15187 more likely to realize if they add bad characters (like quotes)
15189 - Let auth dir servers start without specifying an Address config
15191 - Make unit tests (and other invocations that aren't the real Tor)
15192 run without launching listeners, creating subdirectories, and so on.
15195 Changes in version 0.1.1.5-alpha - 2005-08-08
15196 o Bugfixes included in 0.1.0.14.
15198 o Bugfixes on 0.1.0.x:
15199 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
15200 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
15201 it would silently using ignore the 6668.
15204 Changes in version 0.1.0.14 - 2005-08-08
15205 o Bugfixes on 0.1.0.x:
15206 - Fix the other half of the bug with crypto handshakes
15208 - Fix an assert trigger if you send a 'signal term' via the
15209 controller when it's listening for 'event info' messages.
15212 Changes in version 0.1.1.4-alpha - 2005-08-04
15213 o Bugfixes included in 0.1.0.13.
15216 - Improve tor_gettimeofday() granularity on windows.
15217 - Make clients regenerate their keys when their IP address changes.
15218 - Implement some more GETINFO goodness: expose helper nodes, config
15219 options, getinfo keys.
15222 Changes in version 0.1.0.13 - 2005-08-04
15223 o Bugfixes on 0.1.0.x:
15224 - Fix a critical bug in the security of our crypto handshakes.
15225 - Fix a size_t underflow in smartlist_join_strings2() that made
15226 it do bad things when you hand it an empty smartlist.
15227 - Fix Windows installer to ship Tor license (thanks to Aphex for
15228 pointing out this oversight) and put a link to the doc directory
15230 - Explicitly set no-unaligned-access for sparc: it turns out the
15231 new gcc's let you compile broken code, but that doesn't make it
15235 Changes in version 0.1.1.3-alpha - 2005-07-23
15236 o Bugfixes on 0.1.1.2-alpha:
15237 - Fix a bug in handling the controller's "post descriptor"
15239 - Fix several bugs in handling the controller's "extend circuit"
15241 - Fix a bug in handling the controller's "stream status" event.
15242 - Fix an assert failure if we have a controller listening for
15243 circuit events and we go offline.
15244 - Re-allow hidden service descriptors to publish 0 intro points.
15245 - Fix a crash when generating your hidden service descriptor if
15246 you don't have enough intro points already.
15248 o New features on 0.1.1.2-alpha:
15249 - New controller function "getinfo accounting", to ask how
15250 many bytes we've used in this time period.
15251 - Experimental support for helper nodes: a lot of the risk from
15252 a small static adversary comes because users pick new random
15253 nodes every time they rebuild a circuit. Now users will try to
15254 stick to the same small set of entry nodes if they can. Not
15255 enabled by default yet.
15257 o Bugfixes on 0.1.0.12:
15258 - If you're an auth dir server, always publish your dirport,
15259 even if you haven't yet found yourself to be reachable.
15260 - Fix a size_t underflow in smartlist_join_strings2() that made
15261 it do bad things when you hand it an empty smartlist.
15264 Changes in version 0.1.0.12 - 2005-07-18
15265 o New directory servers:
15266 - tor26 has changed IP address.
15268 o Bugfixes on 0.1.0.x:
15269 - Fix a possible double-free in tor_gzip_uncompress().
15270 - When --disable-threads is set, do not search for or link against
15271 pthreads libraries.
15272 - Don't trigger an assert if an authoritative directory server
15273 claims its dirport is 0.
15274 - Fix bug with removing Tor as an NT service: some people were
15275 getting "The service did not return an error." Thanks to Matt
15279 Changes in version 0.1.1.2-alpha - 2005-07-15
15280 o New directory servers:
15281 - tor26 has changed IP address.
15283 o Bugfixes on 0.1.0.x, crashes/leaks:
15284 - Port the servers-not-obeying-their-exit-policies fix from
15286 - Fix an fd leak in start_daemon().
15287 - On Windows, you can't always reopen a port right after you've
15288 closed it. So change retry_listeners() to only close and re-open
15289 ports that have changed.
15290 - Fix a possible double-free in tor_gzip_uncompress().
15292 o Bugfixes on 0.1.0.x, usability:
15293 - When tor_socketpair() fails in Windows, give a reasonable
15294 Windows-style errno back.
15295 - Let people type "tor --install" as well as "tor -install" when
15297 want to make it an NT service.
15298 - NT service patch from Matt Edman to improve error messages.
15299 - When the controller asks for a config option with an abbreviated
15300 name, give the full name in our response.
15301 - Correct the man page entry on TrackHostExitsExpire.
15302 - Looks like we were never delivering deflated (i.e. compressed)
15303 running-routers lists, even when asked. Oops.
15304 - When --disable-threads is set, do not search for or link against
15305 pthreads libraries.
15307 o Bugfixes on 0.1.1.x:
15308 - Fix a seg fault with autodetecting which controller version is
15312 - New hidden service descriptor format: put a version in it, and
15313 let people specify introduction/rendezvous points that aren't
15314 in "the directory" (which is subjective anyway).
15315 - Allow the DEBUG controller event to work again. Mark certain log
15316 entries as "don't tell this to controllers", so we avoid cycles.
15319 Changes in version 0.1.0.11 - 2005-06-30
15320 o Bugfixes on 0.1.0.x:
15321 - Fix major security bug: servers were disregarding their
15322 exit policies if clients behaved unexpectedly.
15323 - Make OS X init script check for missing argument, so we don't
15324 confuse users who invoke it incorrectly.
15325 - Fix a seg fault in "tor --hash-password foo".
15326 - The MAPADDRESS control command was broken.
15329 Changes in version 0.1.1.1-alpha - 2005-06-29
15331 - Make OS X init script check for missing argument, so we don't
15332 confuse users who invoke it incorrectly.
15333 - Fix a seg fault in "tor --hash-password foo".
15334 - Fix a possible way to DoS dirservers.
15335 - When we complain that your exit policy implicitly allows local or
15336 private address spaces, name them explicitly so operators can
15338 - Make the log message less scary when all the dirservers are
15339 temporarily unreachable.
15340 - We were printing the number of idle dns workers incorrectly when
15344 - Revised controller protocol (version 1) that uses ascii rather
15345 than binary. Add supporting libraries in python and java so you
15346 can use the controller from your applications without caring how
15347 our protocol works.
15348 - Spiffy new support for crypto hardware accelerators. Can somebody
15352 Changes in version 0.0.9.10 - 2005-06-16
15353 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
15354 - Refuse relay cells that claim to have a length larger than the
15355 maximum allowed. This prevents a potential attack that could read
15356 arbitrary memory (e.g. keys) from an exit server's process
15360 Changes in version 0.1.0.10 - 2005-06-14
15361 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
15362 libevent before 1.1a.
15365 Changes in version 0.1.0.9-rc - 2005-06-09
15367 - Reset buf->highwater every time buf_shrink() is called, not just on
15368 a successful shrink. This was causing significant memory bloat.
15369 - Fix buffer overflow when checking hashed passwords.
15370 - Security fix: if seeding the RNG on Win32 fails, quit.
15371 - Allow seeding the RNG on Win32 even when you're not running as
15373 - Disable threading on Solaris too. Something is wonky with it,
15374 cpuworkers, and reentrant libs.
15375 - Reenable the part of the code that tries to flush as soon as an
15376 OR outbuf has a full TLS record available. Perhaps this will make
15377 OR outbufs not grow as huge except in rare cases, thus saving lots
15378 of CPU time plus memory.
15379 - Reject malformed .onion addresses rather then passing them on as
15380 normal web requests.
15381 - Adapt patch from Adam Langley: fix possible memory leak in
15382 tor_lookup_hostname().
15383 - Initialize libevent later in the startup process, so the logs are
15384 already established by the time we start logging libevent warns.
15385 - Use correct errno on win32 if libevent fails.
15386 - Check and warn about known-bad/slow libevent versions.
15387 - Pay more attention to the ClientOnly config option.
15388 - Have torctl.in/tor.sh.in check for location of su binary (needed
15390 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
15391 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
15392 HttpProxyAuthenticator
15393 - Stop warning about sigpipes in the logs. We're going to
15394 pretend that getting these occassionally is normal and fine.
15395 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
15397 installer screens; and don't put stuff into StartupItems unless
15398 the user asks you to.
15399 - Require servers that use the default dirservers to have public IP
15400 addresses. We have too many servers that are configured with private
15401 IPs and their admins never notice the log entries complaining that
15402 their descriptors are being rejected.
15403 - Add OSX uninstall instructions. An actual uninstall script will
15407 Changes in version 0.1.0.8-rc - 2005-05-23
15409 - It turns out that kqueue on OS X 10.3.9 was causing kernel
15410 panics. Disable kqueue on all OS X Tors.
15411 - Fix RPM: remove duplicate line accidentally added to the rpm
15413 - Disable threads on openbsd too, since its gethostaddr is not
15415 - Tolerate libevent 0.8 since it still works, even though it's
15417 - Enable building on Red Hat 9.0 again.
15418 - Allow the middle hop of the testing circuit to be running any
15419 version, now that most of them have the bugfix to let them connect
15420 to unknown servers. This will allow reachability testing to work
15421 even when 0.0.9.7-0.0.9.9 become obsolete.
15422 - Handle relay cells with rh.length too large. This prevents
15423 a potential attack that could read arbitrary memory (maybe even
15424 keys) from the exit server's process.
15425 - We screwed up the dirport reachability testing when we don't yet
15426 have a cached version of the directory. Hopefully now fixed.
15427 - Clean up router_load_single_router() (used by the controller),
15428 so it doesn't seg fault on error.
15429 - Fix a minor memory leak when somebody establishes an introduction
15430 point at your Tor server.
15431 - If a socks connection ends because read fails, don't warn that
15432 you're not sending a socks reply back.
15435 - Add HttpProxyAuthenticator config option too, that works like
15436 the HttpsProxyAuthenticator config option.
15437 - Encode hashed controller passwords in hex instead of base64,
15438 to make it easier to write controllers.
15441 Changes in version 0.1.0.7-rc - 2005-05-17
15443 - Fix a bug in the OS X package installer that prevented it from
15444 installing on Tiger.
15445 - Fix a script bug in the OS X package installer that made it
15446 complain during installation.
15447 - Find libevent even if it's hiding in /usr/local/ and your
15448 CFLAGS and LDFLAGS don't tell you to look there.
15449 - Be able to link with libevent as a shared library (the default
15450 after 1.0d), even if it's hiding in /usr/local/lib and even
15451 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
15452 assuming you're running gcc. Otherwise fail and give a useful
15454 - Fix a bug in the RPM packager: set home directory for _tor to
15455 something more reasonable when first installing.
15456 - Free a minor amount of memory that is still reachable on exit.
15459 Changes in version 0.1.0.6-rc - 2005-05-14
15461 - Implement --disable-threads configure option. Disable threads on
15462 netbsd by default, because it appears to have no reentrant resolver
15464 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
15465 release (1.1) detects and disables kqueue if it's broken.
15466 - Append default exit policy before checking for implicit internal
15467 addresses. Now we don't log a bunch of complaints on startup
15468 when using the default exit policy.
15469 - Some people were putting "Address " in their torrc, and they had
15470 a buggy resolver that resolved " " to 0.0.0.0. Oops.
15471 - If DataDir is ~/.tor, and that expands to /.tor, then default to
15472 LOCALSTATEDIR/tor instead.
15473 - Fix fragmented-message bug in TorControl.py.
15474 - Resolve a minor bug which would prevent unreachable dirports
15475 from getting suppressed in the published descriptor.
15476 - When the controller gave us a new descriptor, we weren't resolving
15477 it immediately, so Tor would think its address was 0.0.0.0 until
15478 we fetched a new directory.
15479 - Fix an uppercase/lowercase case error in suppressing a bogus
15480 libevent warning on some Linuxes.
15483 - Begin scrubbing sensitive strings from logs by default. Turn off
15484 the config option SafeLogging if you need to do debugging.
15485 - Switch to a new buffer management algorithm, which tries to avoid
15486 reallocing and copying quite as much. In first tests it looks like
15487 it uses *more* memory on average, but less cpu.
15488 - First cut at support for "create-fast" cells. Clients can use
15489 these when extending to their first hop, since the TLS already
15490 provides forward secrecy and authentication. Not enabled on
15492 - When dirservers refuse a router descriptor, we now log its
15493 contactinfo, platform, and the poster's IP address.
15494 - Call tor_free_all instead of connections_free_all after forking, to
15495 save memory on systems that need to fork.
15496 - Whine at you if you're a server and you don't set your contactinfo.
15497 - Implement --verify-config command-line option to check if your torrc
15498 is valid without actually launching Tor.
15499 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
15500 rather than just rejecting it.
15503 Changes in version 0.1.0.5-rc - 2005-04-27
15505 - Stop trying to print a null pointer if an OR conn fails because
15506 we didn't like its cert.
15508 - Switch our internal buffers implementation to use a ring buffer,
15509 to hopefully improve performance for fast servers a lot.
15510 - Add HttpsProxyAuthenticator support (basic auth only), based
15511 on patch from Adam Langley.
15512 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
15513 the fast servers that have been joining lately.
15514 - Give hidden service accesses extra time on the first attempt,
15515 since 60 seconds is often only barely enough. This might improve
15517 - Improve performance for dirservers: stop re-parsing the whole
15518 directory every time you regenerate it.
15519 - Add more debugging info to help us find the weird dns freebsd
15520 pthreads bug; cleaner debug messages to help track future issues.
15523 Changes in version 0.0.9.9 - 2005-04-23
15524 o Bugfixes on 0.0.9.x:
15525 - If unofficial Tor clients connect and send weird TLS certs, our
15526 Tor server triggers an assert. This release contains a minimal
15527 backport from the broader fix that we put into 0.1.0.4-rc.
15530 Changes in version 0.1.0.4-rc - 2005-04-23
15532 - If unofficial Tor clients connect and send weird TLS certs, our
15533 Tor server triggers an assert. Stop asserting, and start handling
15534 TLS errors better in other situations too.
15535 - When the controller asks us to tell it about all the debug-level
15536 logs, it turns out we were generating debug-level logs while
15537 telling it about them, which turns into a bad loop. Now keep
15538 track of whether you're sending a debug log to the controller,
15539 and don't log when you are.
15540 - Fix the "postdescriptor" feature of the controller interface: on
15541 non-complete success, only say "done" once.
15543 - Clients are now willing to load balance over up to 2mB, not 1mB,
15544 of advertised bandwidth capacity.
15545 - Add a NoPublish config option, so you can be a server (e.g. for
15546 testing running Tor servers in other Tor networks) without
15547 publishing your descriptor to the primary dirservers.
15550 Changes in version 0.1.0.3-rc - 2005-04-08
15551 o Improvements on 0.1.0.2-rc:
15552 - Client now retries when streams end early for 'hibernating' or
15553 'resource limit' reasons, rather than failing them.
15554 - More automated handling for dirserver operators:
15555 - Automatically approve nodes running 0.1.0.2-rc or later,
15556 now that the the reachability detection stuff is working.
15557 - Now we allow two unverified servers with the same nickname
15558 but different keys. But if a nickname is verified, only that
15559 nickname+key are allowed.
15560 - If you're an authdirserver connecting to an address:port,
15561 and it's not the OR you were expecting, forget about that
15562 descriptor. If he *was* the one you were expecting, then forget
15563 about all other descriptors for that address:port.
15564 - Allow servers to publish descriptors from 12 hours in the future.
15565 Corollary: only whine about clock skew from the dirserver if
15566 he's a trusted dirserver (since now even verified servers could
15567 have quite wrong clocks).
15568 - Adjust maximum skew and age for rendezvous descriptors: let skew
15569 be 48 hours rather than 90 minutes.
15570 - Efficiency improvements:
15571 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
15572 it much faster to look up a circuit for each relay cell.
15573 - Remove most calls to assert_all_pending_dns_resolves_ok(),
15574 since they're eating our cpu on exit nodes.
15575 - Stop wasting time doing a case insensitive comparison for every
15576 dns name every time we do any lookup. Canonicalize the names to
15577 lowercase and be done with it.
15578 - Start sending 'truncated' cells back rather than destroy cells,
15579 if the circuit closes in front of you. This means we won't have
15580 to abandon partially built circuits.
15581 - Only warn once per nickname from add_nickname_list_to_smartlist
15582 per failure, so an entrynode or exitnode choice that's down won't
15584 - Put a note in the torrc about abuse potential with the default
15586 - Revise control spec and implementation to allow all log messages to
15587 be sent to controller with their severities intact (suggested by
15588 Matt Edman). Update TorControl to handle new log event types.
15589 - Provide better explanation messages when controller's POSTDESCRIPTOR
15591 - Stop putting nodename in the Platform string in server descriptors.
15592 It doesn't actually help, and it is confusing/upsetting some people.
15594 o Bugfixes on 0.1.0.2-rc:
15595 - We were printing the host mask wrong in exit policies in server
15596 descriptors. This isn't a critical bug though, since we were still
15597 obeying the exit policy internally.
15598 - Fix Tor when compiled with libevent but without pthreads: move
15599 connection_unregister() from _connection_free() to
15601 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
15602 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
15603 when we look through the connection array, we'll find any of the
15604 cpu/dnsworkers. This is no good.
15606 o Bugfixes on 0.0.9.8:
15607 - Fix possible bug on threading platforms (e.g. win32) which was
15608 leaking a file descriptor whenever a cpuworker or dnsworker died.
15609 - When using preferred entry or exit nodes, ignore whether the
15610 circuit wants uptime or capacity. They asked for the nodes, they
15612 - chdir() to your datadirectory at the *end* of the daemonize process,
15613 not the beginning. This was a problem because the first time you
15614 run tor, if your datadir isn't there, and you have runasdaemon set
15615 to 1, it will try to chdir to it before it tries to create it. Oops.
15616 - Handle changed router status correctly when dirserver reloads
15617 fingerprint file. We used to be dropping all unverified descriptors
15618 right then. The bug was hidden because we would immediately
15619 fetch a directory from another dirserver, which would include the
15620 descriptors we just dropped.
15621 - When we're connecting to an OR and he's got a different nickname/key
15622 than we were expecting, only complain loudly if we're an OP or a
15623 dirserver. Complaining loudly to the OR admins just confuses them.
15624 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
15625 artificially capped at 500kB.
15628 Changes in version 0.0.9.8 - 2005-04-07
15629 o Bugfixes on 0.0.9.x:
15630 - We have a bug that I haven't found yet. Sometimes, very rarely,
15631 cpuworkers get stuck in the 'busy' state, even though the cpuworker
15632 thinks of itself as idle. This meant that no new circuits ever got
15633 established. Here's a workaround to kill any cpuworker that's been
15634 busy for more than 100 seconds.
15637 Changes in version 0.1.0.2-rc - 2005-04-01
15638 o Bugfixes on 0.1.0.1-rc:
15639 - Fixes on reachability detection:
15640 - Don't check for reachability while hibernating.
15641 - If ORPort is reachable but DirPort isn't, still publish the
15642 descriptor, but zero out DirPort until it's found reachable.
15643 - When building testing circs for ORPort testing, use only
15644 high-bandwidth nodes, so fewer circuits fail.
15645 - Complain about unreachable ORPort separately from unreachable
15646 DirPort, so the user knows what's going on.
15647 - Make sure we only conclude ORPort reachability if we didn't
15648 initiate the conn. Otherwise we could falsely conclude that
15649 we're reachable just because we connected to the guy earlier
15650 and he used that same pipe to extend to us.
15651 - Authdirservers shouldn't do ORPort reachability detection,
15652 since they're in clique mode, so it will be rare to find a
15653 server not already connected to them.
15654 - When building testing circuits, always pick middle hops running
15655 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
15656 bug. (This is a kludge; it will go away when 0.0.9.x becomes
15658 - When we decide we're reachable, actually publish our descriptor
15660 - Fix bug in redirectstream in the controller.
15661 - Fix the state descriptor strings so logs don't claim edge streams
15662 are in a different state than they actually are.
15663 - Use recent libevent features when possible (this only really affects
15664 win32 and osx right now, because the new libevent with these
15665 features hasn't been released yet). Add code to suppress spurious
15667 - Prevent possible segfault in connection_close_unattached_ap().
15668 - Fix newlines on torrc in win32.
15669 - Improve error msgs when tor-resolve fails.
15671 o Improvements on 0.0.9.x:
15672 - New experimental script tor/contrib/ExerciseServer.py (needs more
15673 work) that uses the controller interface to build circuits and
15674 fetch pages over them. This will help us bootstrap servers that
15675 have lots of capacity but haven't noticed it yet.
15676 - New experimental script tor/contrib/PathDemo.py (needs more work)
15677 that uses the controller interface to let you choose whole paths
15679 "<hostname>.<path,separated by dots>.<length of path>.path"
15680 - When we've connected to an OR and handshaked but didn't like
15681 the result, we were closing the conn without sending destroy
15682 cells back for pending circuits. Now send those destroys.
15685 Changes in version 0.0.9.7 - 2005-04-01
15686 o Bugfixes on 0.0.9.x:
15687 - Fix another race crash bug (thanks to Glenn Fink for reporting).
15688 - Compare identity to identity, not to nickname, when extending to
15689 a router not already in the directory. This was preventing us from
15690 extending to unknown routers. Oops.
15691 - Make sure to create OS X Tor user in <500 range, so we aren't
15692 creating actual system users.
15693 - Note where connection-that-hasn't-sent-end was marked, and fix
15694 a few really loud instances of this harmless bug (it's fixed more
15698 Changes in version 0.1.0.1-rc - 2005-03-28
15700 - Add reachability testing. Your Tor server will automatically try
15701 to see if its ORPort and DirPort are reachable from the outside,
15702 and it won't upload its descriptor until it decides they are.
15703 - Handle unavailable hidden services better. Handle slow or busy
15704 hidden services better.
15705 - Add support for CONNECTing through https proxies, with "HttpsProxy"
15707 - New exit policy: accept most low-numbered ports, rather than
15708 rejecting most low-numbered ports.
15709 - More Tor controller support (still experimental). See
15710 http://tor.eff.org/doc/control-spec.txt for all the new features,
15711 including signals to emulate unix signals from any platform;
15712 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
15713 closestream; closecircuit; etc.
15714 - Make nt services work and start on startup on win32 (based on
15715 patch by Matt Edman).
15716 - Add a new AddressMap config directive to rewrite incoming socks
15717 addresses. This lets you, for example, declare an implicit
15718 required exit node for certain sites.
15719 - Add a new TrackHostExits config directive to trigger addressmaps
15720 for certain incoming socks addresses -- for sites that break when
15721 your exit keeps changing (based on patch by Mike Perry).
15722 - Redo the client-side dns cache so it's just an addressmap too.
15723 - Notice when our IP changes, and reset stats/uptime/reachability.
15724 - When an application is using socks5, give him the whole variety of
15725 potential socks5 responses (connect refused, host unreachable, etc),
15726 rather than just "success" or "failure".
15727 - A more sane version numbering system. See
15728 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
15729 - New contributed script "exitlist": a simple python script to
15730 parse directories and find Tor nodes that exit to listed
15732 - New contributed script "privoxy-tor-toggle" to toggle whether
15733 Privoxy uses Tor. Seems to be configured for Debian by default.
15734 - Report HTTP reasons to client when getting a response from directory
15735 servers -- so you can actually know what went wrong.
15736 - New config option MaxAdvertisedBandwidth which lets you advertise
15737 a low bandwidthrate (to not attract as many circuits) while still
15738 allowing a higher bandwidthrate in reality.
15740 o Robustness/stability fixes:
15741 - Make Tor use Niels Provos's libevent instead of its current
15742 poll-but-sometimes-select mess. This will let us use faster async
15743 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
15745 - pthread support now too. This was forced because when we forked,
15746 we ended up wasting a lot of duplicate ram over time. Also switch
15747 to foo_r versions of some library calls to allow reentry and
15749 - Better handling for heterogeneous / unreliable nodes:
15750 - Annotate circuits w/ whether they aim to contain high uptime nodes
15751 and/or high capacity nodes. When building circuits, choose
15753 - This means that every single node in an intro rend circuit,
15754 not just the last one, will have a minimum uptime.
15755 - New config option LongLivedPorts to indicate application streams
15756 that will want high uptime circuits.
15757 - Servers reset uptime when a dir fetch entirely fails. This
15758 hopefully reflects stability of the server's network connectivity.
15759 - If somebody starts his tor server in Jan 2004 and then fixes his
15760 clock, don't make his published uptime be a year.
15761 - Reset published uptime when you wake up from hibernation.
15762 - Introduce a notion of 'internal' circs, which are chosen without
15763 regard to the exit policy of the last hop. Intro and rendezvous
15764 circs must be internal circs, to avoid leaking information. Resolve
15765 and connect streams can use internal circs if they want.
15766 - New circuit pooling algorithm: make sure to have enough circs around
15767 to satisfy any predicted ports, and also make sure to have 2 internal
15768 circs around if we've required internal circs lately (and with high
15769 uptime if we've seen that lately too).
15770 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
15771 which describes how often we retry making new circuits if current
15772 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
15773 how long we're willing to make use of an already-dirty circuit.
15774 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
15775 circ as necessary, if there are any completed ones lying around
15776 when we try to launch one.
15777 - Make hidden services try to establish a rendezvous for 30 seconds,
15778 rather than for n (where n=3) attempts to build a circuit.
15779 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
15780 "ShutdownWaitLength".
15781 - Try to be more zealous about calling connection_edge_end when
15782 things go bad with edge conns in connection.c.
15783 - Revise tor-spec to add more/better stream end reasons.
15784 - Revise all calls to connection_edge_end to avoid sending "misc",
15785 and to take errno into account where possible.
15788 - Fix a race condition that can trigger an assert, when we have a
15789 pending create cell and an OR connection fails right then.
15790 - Fix several double-mark-for-close bugs, e.g. where we were finding
15791 a conn for a cell even if that conn is already marked for close.
15792 - Make sequence of log messages when starting on win32 with no config
15793 file more reasonable.
15794 - When choosing an exit node for a new non-internal circ, don't take
15795 into account whether it'll be useful for any pending x.onion
15796 addresses -- it won't.
15797 - Turn addr_policy_compare from a tristate to a quadstate; this should
15798 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
15799 for google.com" problem.
15800 - Make "platform" string in descriptor more accurate for Win32 servers,
15801 so it's not just "unknown platform".
15802 - Fix an edge case in parsing config options (thanks weasel).
15803 If they say "--" on the commandline, it's not an option.
15804 - Reject odd-looking addresses at the client (e.g. addresses that
15805 contain a colon), rather than having the server drop them because
15807 - tor-resolve requests were ignoring .exit if there was a working circuit
15808 they could use instead.
15809 - REUSEADDR on normal platforms means you can rebind to the port
15810 right after somebody else has let it go. But REUSEADDR on win32
15811 means to let you bind to the port _even when somebody else
15812 already has it bound_! So, don't do that on Win32.
15813 - Change version parsing logic: a version is "obsolete" if it is not
15814 recommended and (1) there is a newer recommended version in the
15815 same series, or (2) there are no recommended versions in the same
15816 series, but there are some recommended versions in a newer series.
15817 A version is "new" if it is newer than any recommended version in
15819 - Stop most cases of hanging up on a socks connection without sending
15823 - Require BandwidthRate to be at least 20kB/s for servers.
15824 - When a dirserver causes you to give a warn, mention which dirserver
15826 - New config option DirAllowPrivateAddresses for authdirservers.
15827 Now by default they refuse router descriptors that have non-IP or
15828 private-IP addresses.
15829 - Stop publishing socksport in the directory, since it's not
15830 actually meant to be public. For compatibility, publish a 0 there
15832 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
15833 smart" value, that is low for servers and high for clients.
15834 - If our clock jumps forward by 100 seconds or more, assume something
15835 has gone wrong with our network and abandon all not-yet-used circs.
15836 - Warn when exit policy implicitly allows local addresses.
15837 - If we get an incredibly skewed timestamp from a dirserver mirror
15838 that isn't a verified OR, don't warn -- it's probably him that's
15840 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
15841 cookies to disk and doesn't log each web request to disk. (Thanks
15842 to Brett Carrington for pointing this out.)
15843 - When a client asks us for a dir mirror and we don't have one,
15844 launch an attempt to get a fresh one.
15845 - If we're hibernating and we get a SIGINT, exit immediately.
15846 - Add --with-dmalloc ./configure option, to track memory leaks.
15847 - And try to free all memory on closing, so we can detect what
15849 - Cache local dns resolves correctly even when they're .exit
15851 - Give a better warning when some other server advertises an
15852 ORPort that is actually an apache running ssl.
15853 - Add "opt hibernating 1" to server descriptor to make it clearer
15854 whether the server is hibernating.
15857 Changes in version 0.0.9.6 - 2005-03-24
15858 o Bugfixes on 0.0.9.x (crashes and asserts):
15859 - Add new end stream reasons to maintainance branch. Fix bug where
15860 reason (8) could trigger an assert. Prevent bug from recurring.
15861 - Apparently win32 stat wants paths to not end with a slash.
15862 - Fix assert triggers in assert_cpath_layer_ok(), where we were
15863 blowing away the circuit that conn->cpath_layer points to, then
15864 checking to see if the circ is well-formed. Backport check to make
15865 sure we dont use the cpath on a closed connection.
15866 - Prevent circuit_resume_edge_reading_helper() from trying to package
15867 inbufs for marked-for-close streams.
15868 - Don't crash on hup if your options->address has become unresolvable.
15869 - Some systems (like OS X) sometimes accept() a connection and tell
15870 you the remote host is 0.0.0.0:0. If this happens, due to some
15871 other mis-features, we get confused; so refuse the conn for now.
15873 o Bugfixes on 0.0.9.x (other):
15874 - Fix harmless but scary "Unrecognized content encoding" warn message.
15875 - Add new stream error reason: TORPROTOCOL reason means "you are not
15876 speaking a version of Tor I understand; say bye-bye to your stream."
15877 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
15878 into the future, now that we are more tolerant of skew. This
15879 resolves a bug where a Tor server would refuse to cache a directory
15880 because all the directories it gets are too far in the future;
15881 yet the Tor server never logs any complaints about clock skew.
15882 - Mac packaging magic: make man pages useable, and do not overwrite
15883 existing torrc files.
15884 - Make OS X log happily to /var/log/tor/tor.log
15887 Changes in version 0.0.9.5 - 2005-02-22
15888 o Bugfixes on 0.0.9.x:
15889 - Fix an assert race at exit nodes when resolve requests fail.
15890 - Stop picking unverified dir mirrors--it only leads to misery.
15891 - Patch from Matt Edman to make NT services work better. Service
15892 support is still not compiled into the executable by default.
15893 - Patch from Dmitri Bely so the Tor service runs better under
15894 the win32 SYSTEM account.
15895 - Make tor-resolve actually work (?) on Win32.
15896 - Fix a sign bug when getrlimit claims to have 4+ billion
15897 file descriptors available.
15898 - Stop refusing to start when bandwidthburst == bandwidthrate.
15899 - When create cells have been on the onion queue more than five
15900 seconds, just send back a destroy and take them off the list.
15903 Changes in version 0.0.9.4 - 2005-02-03
15904 o Bugfixes on 0.0.9:
15905 - Fix an assert bug that took down most of our servers: when
15906 a server claims to have 1 GB of bandwidthburst, don't
15908 - Don't crash as badly if we have spawned the max allowed number
15909 of dnsworkers, or we're out of file descriptors.
15910 - Block more file-sharing ports in the default exit policy.
15911 - MaxConn is now automatically set to the hard limit of max
15912 file descriptors we're allowed (ulimit -n), minus a few for
15914 - Give a clearer message when servers need to raise their
15915 ulimit -n when they start running out of file descriptors.
15916 - SGI Compatibility patches from Jan Schaumann.
15917 - Tolerate a corrupt cached directory better.
15918 - When a dirserver hasn't approved your server, list which one.
15919 - Go into soft hibernation after 95% of the bandwidth is used,
15920 not 99%. This is especially important for daily hibernators who
15921 have a small accounting max. Hopefully it will result in fewer
15922 cut connections when the hard hibernation starts.
15923 - Load-balance better when using servers that claim more than
15924 800kB/s of capacity.
15925 - Make NT services work (experimental, only used if compiled in).
15928 Changes in version 0.0.9.3 - 2005-01-21
15929 o Bugfixes on 0.0.9:
15930 - Backport the cpu use fixes from main branch, so busy servers won't
15931 need as much processor time.
15932 - Work better when we go offline and then come back, or when we
15933 run Tor at boot before the network is up. We do this by
15934 optimistically trying to fetch a new directory whenever an
15935 application request comes in and we think we're offline -- the
15936 human is hopefully a good measure of when the network is back.
15937 - Backport some minimal hidserv bugfixes: keep rend circuits open as
15938 long as you keep using them; actually publish hidserv descriptors
15939 shortly after they change, rather than waiting 20-40 minutes.
15940 - Enable Mac startup script by default.
15941 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
15942 - When you update AllowUnverifiedNodes or FirewallPorts via the
15943 controller's setconf feature, we were always appending, never
15945 - When you update HiddenServiceDir via setconf, it was screwing up
15946 the order of reading the lines, making it fail.
15947 - Do not rewrite a cached directory back to the cache; otherwise we
15948 will think it is recent and not fetch a newer one on startup.
15949 - Workaround for webservers that lie about Content-Encoding: Tor
15950 now tries to autodetect compressed directories and compression
15951 itself. This lets us Proxypass dir fetches through apache.
15954 Changes in version 0.0.9.2 - 2005-01-04
15955 o Bugfixes on 0.0.9 (crashes and asserts):
15956 - Fix an assert on startup when the disk is full and you're logging
15958 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
15959 style address, then we'd crash.
15960 - Fix an assert trigger when the running-routers string we get from
15961 a dirserver is broken.
15962 - Make worker threads start and run on win32. Now win32 servers
15964 - Bandaid (not actually fix, but now it doesn't crash) an assert
15965 where the dns worker dies mysteriously and the main Tor process
15966 doesn't remember anything about the address it was resolving.
15968 o Bugfixes on 0.0.9 (Win32):
15969 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
15970 name out of the warning/assert messages.
15971 - Fix a superficial "unhandled error on read" bug on win32.
15972 - The win32 installer no longer requires a click-through for our
15973 license, since our Free Software license grants rights but does not
15975 - Win32: When connecting to a dirserver fails, try another one
15976 immediately. (This was already working for non-win32 Tors.)
15977 - Stop trying to parse $HOME on win32 when hunting for default
15979 - Make tor-resolve.c work on win32 by calling network_init().
15981 o Bugfixes on 0.0.9 (other):
15982 - Make 0.0.9.x build on Solaris again.
15983 - Due to a fencepost error, we were blowing away the \n when reporting
15984 confvalue items in the controller. So asking for multiple config
15985 values at once couldn't work.
15986 - When listing circuits that are pending on an opening OR connection,
15987 if we're an OR we were listing circuits that *end* at us as
15988 being pending on every listener, dns/cpu worker, etc. Stop that.
15989 - Dirservers were failing to create 'running-routers' or 'directory'
15990 strings if we had more than some threshold of routers. Fix them so
15991 they can handle any number of routers.
15992 - Fix a superficial "Duplicate mark for close" bug.
15993 - Stop checking for clock skew for OR connections, even for servers.
15994 - Fix a fencepost error that was chopping off the last letter of any
15995 nickname that is the maximum allowed nickname length.
15996 - Update URLs in log messages so they point to the new website.
15997 - Fix a potential problem in mangling server private keys while
15998 writing to disk (not triggered yet, as far as we know).
15999 - Include the licenses for other free software we include in Tor,
16000 now that we're shipping binary distributions more regularly.
16003 Changes in version 0.0.9.1 - 2004-12-15
16004 o Bugfixes on 0.0.9:
16005 - Make hibernation actually work.
16006 - Make HashedControlPassword config option work.
16007 - When we're reporting event circuit status to a controller,
16008 don't use the stream status code.
16011 Changes in version 0.0.9 - 2004-12-12
16013 - Clean up manpage and torrc.sample file.
16014 - Clean up severities and text of log warnings.
16016 - Make servers trigger an assert when they enter hibernation.
16019 Changes in version 0.0.9rc7 - 2004-12-08
16020 o Bugfixes on 0.0.9rc:
16021 - Fix a stack-trashing crash when an exit node begins hibernating.
16022 - Avoid looking at unallocated memory while considering which
16023 ports we need to build circuits to cover.
16024 - Stop a sigpipe: when an 'end' cell races with eof from the app,
16025 we shouldn't hold-open-until-flush if the eof arrived first.
16026 - Fix a bug with init_cookie_authentication() in the controller.
16027 - When recommending new-format log lines, if the upper bound is
16028 LOG_ERR, leave it implicit.
16030 o Bugfixes on 0.0.8.1:
16031 - Fix a whole slew of memory leaks.
16032 - Fix isspace() and friends so they still make Solaris happy
16033 but also so they don't trigger asserts on win32.
16034 - Fix parse_iso_time on platforms without strptime (eg win32).
16035 - win32: tolerate extra "readable" events better.
16036 - win32: when being multithreaded, leave parent fdarray open.
16037 - Make unit tests work on win32.
16040 Changes in version 0.0.9rc6 - 2004-12-06
16041 o Bugfixes on 0.0.9pre:
16042 - Clean up some more integer underflow opportunities (not exploitable
16044 - While hibernating, hup should not regrow our listeners.
16045 - Send an end to the streams we close when we hibernate, rather
16046 than just chopping them off.
16047 - React to eof immediately on non-open edge connections.
16049 o Bugfixes on 0.0.8.1:
16050 - Calculate timeout for waiting for a connected cell from the time
16051 we sent the begin cell, not from the time the stream started. If
16052 it took a long time to establish the circuit, we would time out
16053 right after sending the begin cell.
16054 - Fix router_compare_addr_to_addr_policy: it was not treating a port
16055 of * as always matching, so we were picking reject *:* nodes as
16056 exit nodes too. Oops.
16059 - New circuit building strategy: keep a list of ports that we've
16060 used in the past 6 hours, and always try to have 2 circuits open
16061 or on the way that will handle each such port. Seed us with port
16062 80 so web users won't complain that Tor is "slow to start up".
16063 - Make kill -USR1 dump more useful stats about circuits.
16064 - When warning about retrying or giving up, print the address, so
16065 the user knows which one it's talking about.
16066 - If you haven't used a clean circuit in an hour, throw it away,
16067 just to be on the safe side. (This means after 6 hours a totally
16068 unused Tor client will have no circuits open.)
16071 Changes in version 0.0.9rc5 - 2004-12-01
16072 o Bugfixes on 0.0.8.1:
16073 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
16074 - Let resolve conns retry/expire also, rather than sticking around
16076 - If we are using select, make sure we stay within FD_SETSIZE.
16078 o Bugfixes on 0.0.9pre:
16079 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
16080 but doesn't seem to be currently; thanks to Ilja van Sprundel for
16082 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
16083 instead. Impose minima and maxima for all *Period options; impose
16084 even tighter maxima for fetching if we are a caching dirserver.
16085 Clip rather than rejecting.
16086 - Fetch cached running-routers from servers that serve it (that is,
16087 authdirservers and servers running 0.0.9rc5-cvs or later.)
16090 - Accept *:706 (silc) in default exit policy.
16091 - Implement new versioning format for post 0.1.
16092 - Support "foo.nickname.exit" addresses, to let Alice request the
16093 address "foo" as viewed by exit node "nickname". Based on a patch
16095 - Make tor --version --version dump the cvs Id of every file.
16098 Changes in version 0.0.9rc4 - 2004-11-28
16099 o Bugfixes on 0.0.8.1:
16100 - Make windows sockets actually non-blocking (oops), and handle
16101 win32 socket errors better.
16103 o Bugfixes on 0.0.9rc1:
16104 - Actually catch the -USR2 signal.
16107 Changes in version 0.0.9rc3 - 2004-11-25
16108 o Bugfixes on 0.0.8.1:
16109 - Flush the log file descriptor after we print "Tor opening log file",
16110 so we don't see those messages days later.
16112 o Bugfixes on 0.0.9rc1:
16113 - Make tor-resolve work again.
16114 - Avoid infinite loop in tor-resolve if tor hangs up on it.
16115 - Fix an assert trigger for clients/servers handling resolves.
16118 Changes in version 0.0.9rc2 - 2004-11-24
16119 o Bugfixes on 0.0.9rc1:
16120 - I broke socks5 support while fixing the eof bug.
16121 - Allow unitless bandwidths and intervals; they default to bytes
16123 - New servers don't start out hibernating; they are active until
16124 they run out of bytes, so they have a better estimate of how
16125 long it takes, and so their operators can know they're working.
16128 Changes in version 0.0.9rc1 - 2004-11-23
16129 o Bugfixes on 0.0.8.1:
16130 - Finally fix a bug that's been plaguing us for a year:
16131 With high load, circuit package window was reaching 0. Whenever
16132 we got a circuit-level sendme, we were reading a lot on each
16133 socket, but only writing out a bit. So we would eventually reach
16134 eof. This would be noticed and acted on even when there were still
16135 bytes sitting in the inbuf.
16136 - When poll() is interrupted, we shouldn't believe the revents values.
16138 o Bugfixes on 0.0.9pre6:
16139 - Fix hibernate bug that caused pre6 to be broken.
16140 - Don't keep rephist info for routers that haven't had activity for
16141 24 hours. (This matters now that clients have keys, since we track
16143 - Never call close_temp_logs while validating log options.
16144 - Fix backslash-escaping on tor.sh.in and torctl.in.
16147 - Implement weekly/monthly/daily accounting: now you specify your
16148 hibernation properties by
16149 AccountingMax N bytes|KB|MB|GB|TB
16150 AccountingStart day|week|month [day] HH:MM
16151 Defaults to "month 1 0:00".
16152 - Let bandwidth and interval config options be specified as 5 bytes,
16153 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
16154 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
16155 get back to normal.)
16156 - If your requested entry or exit node has advertised bandwidth 0,
16158 - Be more greedy about filling up relay cells -- we try reading again
16159 once we've processed the stuff we read, in case enough has arrived
16160 to fill the last cell completely.
16161 - Apply NT service patch from Osamu Fujino. Still needs more work.
16164 Changes in version 0.0.9pre6 - 2004-11-15
16165 o Bugfixes on 0.0.8.1:
16166 - Fix assert failure on malformed socks4a requests.
16167 - Use identity comparison, not nickname comparison, to choose which
16168 half of circuit-ID-space each side gets to use. This is needed
16169 because sometimes we think of a router as a nickname, and sometimes
16170 as a hex ID, and we can't predict what the other side will do.
16171 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
16172 write() call will fail and we handle it there.
16173 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
16174 and smartlist_len, which are two major profiling offenders.
16176 o Bugfixes on 0.0.9pre5:
16177 - Fix a bug in read_all that was corrupting config files on windows.
16178 - When we're raising the max number of open file descriptors to
16179 'unlimited', don't log that we just raised it to '-1'.
16180 - Include event code with events, as required by control-spec.txt.
16181 - Don't give a fingerprint when clients do --list-fingerprint:
16182 it's misleading, because it will never be the same again.
16183 - Stop using strlcpy in tor_strndup, since it was slowing us
16185 - Remove warn on startup about missing cached-directory file.
16186 - Make kill -USR1 work again.
16187 - Hibernate if we start tor during the "wait for wakeup-time" phase
16188 of an accounting interval. Log our hibernation plans better.
16189 - Authoritative dirservers now also cache their directory, so they
16190 have it on start-up.
16193 - Fetch running-routers; cache running-routers; compress
16194 running-routers; serve compressed running-routers.z
16195 - Add NSI installer script contributed by J Doe.
16196 - Commit VC6 and VC7 workspace/project files.
16197 - Commit a tor.spec for making RPM files, with help from jbash.
16198 - Add contrib/torctl.in contributed by Glenn Fink.
16199 - Implement the control-spec's SAVECONF command, to write your
16200 configuration to torrc.
16201 - Get cookie authentication for the controller closer to working.
16202 - Include control-spec.txt in the tarball.
16203 - When set_conf changes our server descriptor, upload a new copy.
16204 But don't upload it too often if there are frequent changes.
16205 - Document authentication config in man page, and document signals
16207 - Clean up confusing parts of man page and torrc.sample.
16208 - Make expand_filename handle ~ and ~username.
16209 - Use autoconf to enable largefile support where necessary. Use
16210 ftello where available, since ftell can fail at 2GB.
16211 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
16212 log more informatively.
16213 - Give a slightly more useful output for "tor -h".
16214 - Refuse application socks connections to port 0.
16215 - Check clock skew for verified servers, but allow unverified
16216 servers and clients to have any clock skew.
16217 - Break DirFetchPostPeriod into:
16218 - DirFetchPeriod for fetching full directory,
16219 - StatusFetchPeriod for fetching running-routers,
16220 - DirPostPeriod for posting server descriptor,
16221 - RendPostPeriod for posting hidden service descriptors.
16222 - Make sure the hidden service descriptors are at a random offset
16223 from each other, to hinder linkability.
16226 Changes in version 0.0.9pre5 - 2004-11-09
16227 o Bugfixes on 0.0.9pre4:
16228 - Fix a seg fault in unit tests (doesn't affect main program).
16229 - Fix an assert bug where a hidden service provider would fail if
16230 the first hop of his rendezvous circuit was down.
16231 - Hidden service operators now correctly handle version 1 style
16232 INTRODUCE1 cells (nobody generates them still, so not a critical
16234 - If do_hup fails, actually notice.
16235 - Handle more errnos from accept() without closing the listener.
16236 Some OpenBSD machines were closing their listeners because
16237 they ran out of file descriptors.
16238 - Send resolve cells to exit routers that are running a new
16239 enough version of the resolve code to work right.
16240 - Better handling of winsock includes on non-MSV win32 compilers.
16241 - Some people had wrapped their tor client/server in a script
16242 that would restart it whenever it died. This did not play well
16243 with our "shut down if your version is obsolete" code. Now people
16244 don't fetch a new directory if their local cached version is
16246 - Make our autogen.sh work on ksh as well as bash.
16249 - Hibernation: New config option "AccountingMaxKB" lets you
16250 set how many KBytes per month you want to allow your server to
16251 consume. Rather than spreading those bytes out evenly over the
16252 month, we instead hibernate for some of the month and pop up
16253 at a deterministic time, work until the bytes are consumed, then
16254 hibernate again. Config option "MonthlyAccountingStart" lets you
16255 specify which day of the month your billing cycle starts on.
16256 - Control interface: a separate program can now talk to your
16257 client/server over a socket, and get/set config options, receive
16258 notifications of circuits and streams starting/finishing/dying,
16259 bandwidth used, etc. The next step is to get some GUIs working.
16260 Let us know if you want to help out. See doc/control-spec.txt .
16261 - Ship a contrib/tor-control.py as an example script to interact
16262 with the control port.
16263 - "tor --hash-password zzyxz" will output a salted password for
16264 use in authenticating to the control interface.
16265 - New log format in config:
16266 "Log minsev[-maxsev] stdout|stderr|syslog" or
16267 "Log minsev[-maxsev] file /var/foo"
16270 - DirPolicy config option, to let people reject incoming addresses
16271 from their dirserver.
16272 - "tor --list-fingerprint" will list your identity key fingerprint
16274 - Add "pass" target for RedirectExit, to make it easier to break
16275 out of a sequence of RedirectExit rules.
16276 - Clients now generate a TLS cert too, in preparation for having
16277 them act more like real nodes.
16278 - Ship src/win32/ in the tarball, so people can use it to build.
16279 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
16281 - New "router-status" line in directory, to better bind each verified
16282 nickname to its identity key.
16283 - Deprecate unofficial config option abbreviations, and abbreviations
16284 not on the command line.
16285 - Add a pure-C tor-resolve implementation.
16286 - Use getrlimit and friends to ensure we can reach MaxConn (currently
16287 1024) file descriptors.
16289 o Code security improvements, inspired by Ilja:
16290 - Replace sprintf with snprintf. (I think they were all safe, but
16292 - Replace strcpy/strncpy with strlcpy in more places.
16293 - Avoid strcat; use snprintf or strlcat instead.
16294 - snprintf wrapper with consistent (though not C99) overflow behavior.
16297 Changes in version 0.0.9pre4 - 2004-10-17
16298 o Bugfixes on 0.0.9pre3:
16299 - If the server doesn't specify an exit policy, use the real default
16300 exit policy, not reject *:*.
16301 - Ignore fascistfirewall when uploading/downloading hidden service
16302 descriptors, since we go through Tor for those; and when using
16303 an HttpProxy, since we assume it can reach them all.
16304 - When looking for an authoritative dirserver, use only the ones
16305 configured at boot. Don't bother looking in the directory.
16306 - The rest of the fix for get_default_conf_file() on older win32.
16307 - Make 'Routerfile' config option obsolete.
16310 - New 'MyFamily nick1,...' config option for a server to
16311 specify other servers that shouldn't be used in the same circuit
16312 with it. Only believed if nick1 also specifies us.
16313 - New 'NodeFamily nick1,nick2,...' config option for a client to
16314 specify nodes that it doesn't want to use in the same circuit.
16315 - New 'Redirectexit pattern address:port' config option for a
16316 server to redirect exit connections, e.g. to a local squid.
16319 Changes in version 0.0.9pre3 - 2004-10-13
16320 o Bugfixes on 0.0.8.1:
16321 - Better torrc example lines for dirbindaddress and orbindaddress.
16322 - Improved bounds checking on parsed ints (e.g. config options and
16323 the ones we find in directories.)
16324 - Better handling of size_t vs int, so we're more robust on 64
16326 - Fix the rest of the bug where a newly started OR would appear
16327 as unverified even after we've added his fingerprint and hupped
16329 - Fix a bug from 0.0.7: when read() failed on a stream, we would
16330 close it without sending back an end. So 'connection refused'
16331 would simply be ignored and the user would get no response.
16333 o Bugfixes on 0.0.9pre2:
16334 - Serving the cached-on-disk directory to people is bad. We now
16335 provide no directory until we've fetched a fresh one.
16336 - Workaround for bug on windows where cached-directories get crlf
16338 - Make get_default_conf_file() work on older windows too.
16339 - If we write a *:* exit policy line in the descriptor, don't write
16340 any more exit policy lines.
16343 - Use only 0.0.9pre1 and later servers for resolve cells.
16344 - Make the dirservers file obsolete.
16345 - Include a dir-signing-key token in directories to tell the
16346 parsing entity which key is being used to sign.
16347 - Remove the built-in bulky default dirservers string.
16348 - New config option "Dirserver %s:%d [fingerprint]", which can be
16349 repeated as many times as needed. If no dirservers specified,
16350 default to moria1,moria2,tor26.
16351 - Make moria2 advertise a dirport of 80, so people behind firewalls
16352 will be able to get a directory.
16353 - Http proxy support
16354 - Dirservers translate requests for http://%s:%d/x to /x
16355 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
16356 be routed through this host.
16357 - Clients ask for /tor/x rather than /x for new enough dirservers.
16358 This way we can one day coexist peacefully with apache.
16359 - Clients specify a "Host: %s%d" http header, to be compatible
16360 with more proxies, and so running squid on an exit node can work.
16363 Changes in version 0.0.8.1 - 2004-10-13
16365 - Fix a seg fault that can be triggered remotely for Tor
16366 clients/servers with an open dirport.
16367 - Fix a rare assert trigger, where routerinfos for entries in
16368 our cpath would expire while we're building the path.
16369 - Fix a bug in OutboundBindAddress so it (hopefully) works.
16370 - Fix a rare seg fault for people running hidden services on
16371 intermittent connections.
16372 - Fix a bug in parsing opt keywords with objects.
16373 - Fix a stale pointer assert bug when a stream detaches and
16375 - Fix a string format vulnerability (probably not exploitable)
16376 in reporting stats locally.
16377 - Fix an assert trigger: sometimes launching circuits can fail
16378 immediately, e.g. because too many circuits have failed recently.
16379 - Fix a compile warning on 64 bit platforms.
16382 Changes in version 0.0.9pre2 - 2004-10-03
16384 - Make fetching a cached directory work for 64-bit platforms too.
16385 - Make zlib.h a required header, not an optional header.
16388 Changes in version 0.0.9pre1 - 2004-10-01
16390 - Stop using separate defaults for no-config-file and
16391 empty-config-file. Now you have to explicitly turn off SocksPort,
16392 if you don't want it open.
16393 - Fix a bug in OutboundBindAddress so it (hopefully) works.
16394 - Improve man page to mention more of the 0.0.8 features.
16395 - Fix a rare seg fault for people running hidden services on
16396 intermittent connections.
16397 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
16399 - Fix more dns related bugs: send back resolve_failed and end cells
16400 more reliably when the resolve fails, rather than closing the
16401 circuit and then trying to send the cell. Also attach dummy resolve
16402 connections to a circuit *before* calling dns_resolve(), to fix
16403 a bug where cached answers would never be sent in RESOLVED cells.
16404 - When we run out of disk space, or other log writing error, don't
16405 crash. Just stop logging to that log and continue.
16406 - We were starting to daemonize before we opened our logs, so if
16407 there were any problems opening logs, we would complain to stderr,
16408 which wouldn't work, and then mysteriously exit.
16409 - Fix a rare bug where sometimes a verified OR would connect to us
16410 before he'd uploaded his descriptor, which would cause us to
16411 assign conn->nickname as though he's unverified. Now we look through
16412 the fingerprint list to see if he's there.
16413 - Fix a rare assert trigger, where routerinfos for entries in
16414 our cpath would expire while we're building the path.
16417 - Clients can ask dirservers for /dir.z to get a compressed version
16418 of the directory. Only works for servers running 0.0.9, of course.
16419 - Make clients cache directories and use them to seed their router
16420 lists at startup. This means clients have a datadir again.
16421 - Configuration infrastructure support for warning on obsolete
16423 - Respond to content-encoding headers by trying to uncompress as
16425 - Reply with a deflated directory when a client asks for "dir.z".
16426 We could use allow-encodings instead, but allow-encodings isn't
16427 specified in HTTP 1.0.
16428 - Raise the max dns workers from 50 to 100.
16429 - Discourage people from setting their dirfetchpostperiod more often
16430 than once per minute.
16431 - Protect dirservers from overzealous descriptor uploading -- wait
16432 10 seconds after directory gets dirty, before regenerating.
16435 Changes in version 0.0.8 - 2004-08-25
16436 o Port it to SunOS 5.9 / Athena
16439 Changes in version 0.0.8rc2 - 2004-08-20
16440 o Make it compile on cygwin again.
16441 o When picking unverified routers, skip those with low uptime and/or
16442 low bandwidth, depending on what properties you care about.
16445 Changes in version 0.0.8rc1 - 2004-08-18
16446 o Changes from 0.0.7.3:
16448 - Fix assert triggers: if the other side returns an address 0.0.0.0,
16449 don't put it into the client dns cache.
16450 - If a begin failed due to exit policy, but we believe the IP address
16451 should have been allowed, switch that router to exitpolicy reject *:*
16452 until we get our next directory.
16454 - Clients choose nodes proportional to advertised bandwidth.
16455 - Avoid using nodes with low uptime as introduction points.
16456 - Handle servers with dynamic IP addresses: don't replace
16457 options->Address with the resolved one at startup, and
16458 detect our address right before we make a routerinfo each time.
16459 - 'FascistFirewall' option to pick dirservers and ORs on specific
16460 ports; plus 'FirewallPorts' config option to tell FascistFirewall
16461 which ports are open. (Defaults to 80,443)
16462 - Be more aggressive about trying to make circuits when the network
16463 has changed (e.g. when you unsuspend your laptop).
16464 - Check for time skew on http headers; report date in response to
16466 - If the entrynode config line has only one node, don't pick it as
16468 - Add strict{entry|exit}nodes config options. If set to 1, then
16469 we refuse to build circuits that don't include the specified entry
16471 - OutboundBindAddress config option, to bind to a specific
16472 IP address for outgoing connect()s.
16473 - End truncated log entries (e.g. directories) with "[truncated]".
16475 o Patches to 0.0.8preX:
16477 - Patches to compile and run on win32 again (maybe)?
16478 - Fix crash when looking for ~/.torrc with no $HOME set.
16479 - Fix a race bug in the unit tests.
16480 - Handle verified/unverified name collisions better when new
16481 routerinfo's arrive in a directory.
16482 - Sometimes routers were getting entered into the stats before
16483 we'd assigned their identity_digest. Oops.
16484 - Only pick and establish intro points after we've gotten a
16487 - AllowUnverifiedNodes config option to let circuits choose no-name
16488 routers in entry,middle,exit,introduction,rendezvous positions.
16489 Allow middle and rendezvous positions by default.
16490 - Add a man page for tor-resolve.
16493 Changes in version 0.0.7.3 - 2004-08-12
16494 o Stop dnsworkers from triggering an assert failure when you
16495 ask them to resolve the host "".
16498 Changes in version 0.0.8pre3 - 2004-08-09
16499 o Changes from 0.0.7.2:
16500 - Allow multiple ORs with same nickname in routerlist -- now when
16501 people give us one identity key for a nickname, then later
16502 another, we don't constantly complain until the first expires.
16503 - Remember used bandwidth (both in and out), and publish 15-minute
16504 snapshots for the past day into our descriptor.
16505 - You can now fetch $DIRURL/running-routers to get just the
16506 running-routers line, not the whole descriptor list. (But
16507 clients don't use this yet.)
16508 - When people mistakenly use Tor as an http proxy, point them
16509 at the tor-doc.html rather than the INSTALL.
16510 - Remove our mostly unused -- and broken -- hex_encode()
16511 function. Use base16_encode() instead. (Thanks to Timo Lindfors
16512 for pointing out this bug.)
16513 - Rotate onion keys every 12 hours, not every 2 hours, so we have
16514 fewer problems with people using the wrong key.
16515 - Change the default exit policy to reject the default edonkey,
16516 kazaa, gnutella ports.
16517 - Add replace_file() to util.[ch] to handle win32's rename().
16519 o Changes from 0.0.8preX:
16520 - Fix two bugs in saving onion keys to disk when rotating, so
16521 hopefully we'll get fewer people using old onion keys.
16522 - Fix an assert error that was making SocksPolicy not work.
16523 - Be willing to expire routers that have an open dirport -- it's
16524 just the authoritative dirservers we want to not forget.
16525 - Reject tor-resolve requests for .onion addresses early, so we
16526 don't build a whole rendezvous circuit and then fail.
16527 - When you're warning a server that he's unverified, don't cry
16528 wolf unpredictably.
16529 - Fix a race condition: don't try to extend onto a connection
16530 that's still handshaking.
16531 - For servers in clique mode, require the conn to be open before
16532 you'll choose it for your path.
16533 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
16534 end relay cell, etc.
16535 - Measure bandwidth capacity over the last 24 hours, not just 12
16536 - Bugfix: authoritative dirservers were making and signing a new
16537 directory for each client, rather than reusing the cached one.
16540 Changes in version 0.0.8pre2 - 2004-08-04
16541 o Changes from 0.0.7.2:
16543 - Check directory signature _before_ you decide whether you're
16544 you're running an obsolete version and should exit.
16545 - Check directory signature _before_ you parse the running-routers
16546 list to decide who's running or verified.
16547 - Bugfixes and features:
16548 - Check return value of fclose while writing to disk, so we don't
16549 end up with broken files when servers run out of disk space.
16550 - Log a warning if the user uses an unsafe socks variant, so people
16551 are more likely to learn about privoxy or socat.
16552 - Dirservers now include RFC1123-style dates in the HTTP headers,
16553 which one day we will use to better detect clock skew.
16555 o Changes from 0.0.8pre1:
16556 - Make it compile without warnings again on win32.
16557 - Log a warning if you're running an unverified server, to let you
16558 know you might want to get it verified.
16559 - Only pick a default nickname if you plan to be a server.
16562 Changes in version 0.0.8pre1 - 2004-07-23
16564 - Made our unit tests compile again on OpenBSD 3.5, and tor
16565 itself compile again on OpenBSD on a sparc64.
16566 - We were neglecting milliseconds when logging on win32, so
16567 everything appeared to happen at the beginning of each second.
16569 o Protocol changes:
16570 - 'Extend' relay cell payloads now include the digest of the
16571 intended next hop's identity key. Now we can verify that we're
16572 extending to the right router, and also extend to routers we
16573 hadn't heard of before.
16576 - Tor nodes can now act as relays (with an advertised ORPort)
16577 without being manually verified by the dirserver operators.
16578 - Uploaded descriptors of unverified routers are now accepted
16579 by the dirservers, and included in the directory.
16580 - Verified routers are listed by nickname in the running-routers
16581 list; unverified routers are listed as "$<fingerprint>".
16582 - We now use hash-of-identity-key in most places rather than
16583 nickname or addr:port, for improved security/flexibility.
16584 - To avoid Sybil attacks, paths still use only verified servers.
16585 But now we have a chance to play around with hybrid approaches.
16586 - Nodes track bandwidth usage to estimate capacity (not used yet).
16587 - ClientOnly option for nodes that never want to become servers.
16588 - Directory caching.
16589 - "AuthoritativeDir 1" option for the official dirservers.
16590 - Now other nodes (clients and servers) will cache the latest
16591 directory they've pulled down.
16592 - They can enable their DirPort to serve it to others.
16593 - Clients will pull down a directory from any node with an open
16594 DirPort, and check the signature/timestamp correctly.
16595 - Authoritative dirservers now fetch directories from other
16596 authdirservers, to stay better synced.
16597 - Running-routers list tells who's down also, along with noting
16598 if they're verified (listed by nickname) or unverified (listed
16600 - Allow dirservers to serve running-router list separately.
16601 This isn't used yet.
16602 - ORs connect-on-demand to other ORs
16603 - If you get an extend cell to an OR you're not connected to,
16604 connect, handshake, and forward the create cell.
16605 - The authoritative dirservers stay connected to everybody,
16606 and everybody stays connected to 0.0.7 servers, but otherwise
16607 clients/servers expire unused connections after 5 minutes.
16608 - When servers get a sigint, they delay 30 seconds (refusing new
16609 connections) then exit. A second sigint causes immediate exit.
16610 - File and name management:
16611 - Look for .torrc if no CONFDIR "torrc" is found.
16612 - If no datadir is defined, then choose, make, and secure ~/.tor
16614 - If torrc not found, exitpolicy reject *:*.
16615 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
16616 - If no nickname is defined, derive default from hostname.
16617 - Rename secret key files, e.g. identity.key -> secret_id_key,
16618 to discourage people from mailing their identity key to tor-ops.
16619 - Refuse to build a circuit before the directory has arrived --
16620 it won't work anyway, since you won't know the right onion keys
16622 - Try other dirservers immediately if the one you try is down. This
16623 should tolerate down dirservers better now.
16624 - Parse tor version numbers so we can do an is-newer-than check
16625 rather than an is-in-the-list check.
16626 - New socks command 'resolve', to let us shim gethostbyname()
16628 - A 'tor_resolve' script to access the socks resolve functionality.
16629 - A new socks-extensions.txt doc file to describe our
16630 interpretation and extensions to the socks protocols.
16631 - Add a ContactInfo option, which gets published in descriptor.
16632 - Publish OR uptime in descriptor (and thus in directory) too.
16633 - Write tor version at the top of each log file
16634 - New docs in the tarball:
16636 - Document that you should proxy your SSL traffic too.
16639 Changes in version 0.0.7.2 - 2004-07-07
16640 o A better fix for the 0.0.0.0 problem, that will hopefully
16641 eliminate the remaining related assertion failures.
16644 Changes in version 0.0.7.1 - 2004-07-04
16645 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
16646 since internally we use 0.0.0.0 to signify "not yet resolved".
16649 Changes in version 0.0.7 - 2004-06-07
16650 o Updated the man page to reflect the new features.
16653 Changes in version 0.0.7rc2 - 2004-06-06
16654 o Changes from 0.0.7rc1:
16655 - Make it build on Win32 again.
16656 o Changes from 0.0.6.2:
16657 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
16661 Changes in version 0.0.7rc1 - 2004-06-02
16663 - On sighup, we were adding another log without removing the first
16664 one. So log messages would get duplicated n times for n sighups.
16665 - Several cases of using a connection after we'd freed it. The
16666 problem was that connections that are pending resolve are in both
16667 the pending_resolve tree, and also the circuit's resolving_streams
16668 list. When you want to remove one, you must remove it from both.
16669 - Fix a double-mark-for-close where an end cell arrived for a
16670 resolving stream, and then the resolve failed.
16671 - Check directory signatures based on name of signer, not on whom
16672 we got the directory from. This will let us cache directories more
16675 - Crank up some of our constants to handle more users.
16678 Changes in version 0.0.7pre1 - 2004-06-02
16679 o Fixes for crashes and other obnoxious bugs:
16680 - Fix an epipe bug: sometimes when directory connections failed
16681 to connect, we would give them a chance to flush before closing
16683 - When we detached from a circuit because of resolvefailed, we
16684 would immediately try the same circuit twice more, and then
16685 give up on the resolve thinking we'd tried three different
16687 - Limit the number of intro circuits we'll attempt to build for a
16688 hidden service per 15-minute period.
16689 - Check recommended-software string *early*, before actually parsing
16690 the directory. Thus we can detect an obsolete version and exit,
16691 even if the new directory format doesn't parse.
16692 o Fixes for security bugs:
16693 - Remember which nodes are dirservers when you startup, and if a
16694 random OR enables his dirport, don't automatically assume he's
16695 a trusted dirserver.
16697 - Directory connections were asking the wrong poll socket to
16698 start writing, and not asking themselves to start writing.
16699 - When we detached from a circuit because we sent a begin but
16700 didn't get a connected, we would use it again the first time;
16701 but after that we would correctly switch to a different one.
16702 - Stop warning when the first onion decrypt attempt fails; they
16703 will sometimes legitimately fail now that we rotate keys.
16704 - Override unaligned-access-ok check when $host_cpu is ia64 or
16705 arm. Apparently they allow it but the kernel whines.
16706 - Dirservers try to reconnect periodically too, in case connections
16708 - Fix some memory leaks in directory servers.
16709 - Allow backslash in Win32 filenames.
16710 - Made Tor build complain-free on FreeBSD, hopefully without
16711 breaking other BSD builds. We'll see.
16713 - Doxygen markup on all functions and global variables.
16714 - Make directory functions update routerlist, not replace it. So
16715 now directory disagreements are not so critical a problem.
16716 - Remove the upper limit on number of descriptors in a dirserver's
16717 directory (not that we were anywhere close).
16718 - Allow multiple logfiles at different severity ranges.
16719 - Allow *BindAddress to specify ":port" rather than setting *Port
16720 separately. Allow multiple instances of each BindAddress config
16721 option, so you can bind to multiple interfaces if you want.
16722 - Allow multiple exit policy lines, which are processed in order.
16723 Now we don't need that huge line with all the commas in it.
16724 - Enable accept/reject policies on SOCKS connections, so you can bind
16725 to 0.0.0.0 but still control who can use your OP.
16728 Changes in version 0.0.6.2 - 2004-05-16
16729 o Our integrity-checking digest was checking only the most recent cell,
16730 not the previous cells like we'd thought.
16731 Thanks to Stefan Mark for finding the flaw!
16734 Changes in version 0.0.6.1 - 2004-05-06
16735 o Fix two bugs in our AES counter-mode implementation (this affected
16736 onion-level stream encryption, but not TLS-level). It turns
16737 out we were doing something much more akin to a 16-character
16738 polyalphabetic cipher. Oops.
16739 Thanks to Stefan Mark for finding the flaw!
16740 o Retire moria3 as a directory server, and add tor26 as a directory
16744 Changes in version 0.0.6 - 2004-05-02
16745 [version bump only]
16748 Changes in version 0.0.6rc4 - 2004-05-01
16749 o Update the built-in dirservers list to use the new directory format
16750 o Fix a rare seg fault: if a node offering a hidden service attempts
16751 to build a circuit to Alice's rendezvous point and fails before it
16752 reaches the last hop, it retries with a different circuit, but
16754 o Handle windows socket errors correctly.
16757 Changes in version 0.0.6rc3 - 2004-04-28
16758 o Don't expire non-general excess circuits (if we had enough
16759 circuits open, we were expiring rendezvous circuits -- even
16760 when they had a stream attached. oops.)
16761 o Fetch randomness from /dev/urandom better (not via fopen/fread)
16762 o Better debugging for tls errors
16763 o Some versions of openssl have an SSL_pending function that erroneously
16764 returns bytes when there is a non-application record pending.
16765 o Set Content-Type on the directory and hidserv descriptor.
16766 o Remove IVs from cipher code, since AES-ctr has none.
16767 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
16768 o We were using an array of length zero in a few places.
16769 o win32's gethostbyname can't resolve an IP to an IP.
16770 o win32's close can't close a socket.
16773 Changes in version 0.0.6rc2 - 2004-04-26
16774 o Fix a bug where we were closing tls connections intermittently.
16775 It turns out openssl keeps its errors around -- so if an error
16776 happens, and you don't ask about it, and then another openssl
16777 operation happens and succeeds, and you ask if there was an error,
16778 it tells you about the first error. Fun fun.
16779 o Fix a bug that's been lurking since 27 may 03 (!)
16780 When passing back a destroy cell, we would use the wrong circ id.
16781 'Mostly harmless', but still worth fixing.
16782 o Since we don't support truncateds much, don't bother sending them;
16783 just close the circ.
16784 o check for <machine/limits.h> so we build on NetBSD again (I hope).
16785 o don't crash if a conn that sent a begin has suddenly lost its circuit
16786 (this was quite rare).
16789 Changes in version 0.0.6rc1 - 2004-04-25
16790 o We now rotate link (tls context) keys and onion keys.
16791 o CREATE cells now include oaep padding, so you can tell
16792 if you decrypted them correctly.
16793 o Add bandwidthburst to server descriptor.
16794 o Directories now say which dirserver signed them.
16795 o Use a tor_assert macro that logs failed assertions too.
16798 Changes in version 0.0.6pre5 - 2004-04-18
16799 o changes from 0.0.6pre4:
16800 - make tor build on broken freebsd 5.2 installs
16801 - fix a failed assert when you try an intro point, get a nack, and try
16802 a second one and it works.
16803 - when alice uses a port that the hidden service doesn't accept,
16804 it now sends back an end cell (denied by exit policy). otherwise
16805 alice would just have to wait to time out.
16806 - fix another rare bug: when we had tried all the intro
16807 points for a hidden service, we fetched the descriptor
16808 again, but we left our introcirc thinking it had already
16809 sent an intro, so it kept waiting for a response...
16810 - bugfix: when you sleep your hidden-service laptop, as soon
16811 as it wakes up it tries to upload a service descriptor, but
16812 socketpair fails for some reason (localhost not up yet?).
16813 now we simply give up on that upload, and we'll try again later.
16814 i'd still like to find the bug though.
16815 - if an intro circ waiting for an ack dies before getting one, then
16817 - we were reusing stale service descriptors and refetching usable
16821 Changes in version 0.0.6pre4 - 2004-04-14
16822 o changes from 0.0.6pre3:
16823 - when bob fails to connect to the rendezvous point, and his
16824 circ didn't fail because of the rendezvous point itself, then
16825 he retries a couple of times
16826 - we expire introduction and rendezvous circs more thoroughly
16827 (sometimes they were hanging around forever)
16828 - we expire unattached rendezvous streams that have been around
16829 too long (they were sticking around forever).
16830 - fix a measly fencepost error that was crashing everybody with
16834 Changes in version 0.0.6pre3 - 2004-04-14
16835 o changes from 0.0.6pre2:
16836 - make hup work again
16837 - fix some memory leaks for dirservers
16838 - allow more skew in rendezvous descriptor timestamps, to help
16839 handle people like blanu who don't know what time it is
16840 - normal circs are 3 hops, but some rend/intro circs are 4, if
16841 the initiator doesn't get to choose the last hop
16842 - send acks for introductions, so alice can know whether to try
16844 - bob publishes intro points more correctly
16845 o changes from 0.0.5:
16846 - fix an assert trigger that's been plaguing us since the days
16847 of 0.0.2prexx (thanks weasel!)
16848 - retry stream correctly when we fail to connect because of
16849 exit-policy-reject (should try another) or can't-resolve-address
16850 (also should try another, because dns on random internet servers
16852 - when we hup a dirserver and we've *removed* a server from the
16853 approved-routers list, now we remove that server from the
16854 in-memory directories too
16857 Changes in version 0.0.6pre2 - 2004-04-08
16858 o We fixed our base32 implementation. Now it works on all architectures.
16861 Changes in version 0.0.6pre1 - 2004-04-08
16863 - Hidden services and rendezvous points are implemented. Go to
16864 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
16865 hidden services. (This only works via a socks4a proxy such as
16866 Privoxy, and currently it's quite slow.)
16869 Changes in version 0.0.5 - 2004-03-30
16870 [version bump only]
16873 Changes in version 0.0.5rc3 - 2004-03-29
16874 o Install torrc as torrc.sample -- we no longer clobber your
16876 o Re-enable recommendedversion checking (we broke it in rc2, oops)
16877 o Add in a 'notice' log level for things the operator should hear
16878 but that aren't warnings
16881 Changes in version 0.0.5rc2 - 2004-03-29
16882 o Hold socks connection open until reply is flushed (if possible)
16883 o Make exit nodes resolve IPs to IPs immediately, rather than asking
16884 the dns farm to do it.
16885 o Fix c99 aliasing warnings in rephist.c
16886 o Don't include server descriptors that are older than 24 hours in the
16888 o Give socks 'reject' replies their whole 15s to attempt to flush,
16889 rather than seeing the 60s timeout and assuming the flush had failed.
16890 o Clean automake droppings from the cvs repository
16893 Changes in version 0.0.5rc1 - 2004-03-28
16894 o Fix mangled-state bug in directory fetching (was causing sigpipes).
16895 o Only build circuits after we've fetched the directory: clients were
16896 using only the directory servers before they'd fetched a directory.
16897 This also means longer startup time; so it goes.
16898 o Fix an assert trigger where an OP would fail to handshake, and we'd
16899 expect it to have a nickname.
16900 o Work around a tsocks bug: do a socks reject when AP connection dies
16901 early, else tsocks goes into an infinite loop.
16904 Changes in version 0.0.4 - 2004-03-26
16905 o When connecting to a dirserver or OR and the network is down,
16909 Changes in version 0.0.3 - 2004-03-26
16910 o Warn and fail if server chose a nickname with illegal characters
16911 o Port to Solaris and Sparc:
16912 - include missing header fcntl.h
16913 - have autoconf find -lsocket -lnsl automatically
16914 - deal with hardware word alignment
16915 - make uname() work (solaris has a different return convention)
16916 - switch from using signal() to sigaction()
16917 o Preliminary work on reputation system:
16918 - Keep statistics on success/fail of connect attempts; they're published
16919 by kill -USR1 currently.
16920 - Add a RunTesting option to try to learn link state by creating test
16921 circuits, even when SocksPort is off.
16922 - Remove unused open circuits when there are too many.
16925 Changes in version 0.0.2 - 2004-03-19
16926 - Include strlcpy and strlcat for safer string ops
16927 - define INADDR_NONE so we compile (but still not run) on solaris
16930 Changes in version 0.0.2pre27 - 2004-03-14
16932 - Allow internal tor networks (we were rejecting internal IPs,
16933 now we allow them if they're set explicitly).
16934 - And fix a few endian issues.
16937 Changes in version 0.0.2pre26 - 2004-03-14
16939 - If a stream times out after 15s without a connected cell, don't
16940 try that circuit again: try a new one.
16941 - Retry streams at most 4 times. Then give up.
16942 - When a dirserver gets a descriptor from an unknown router, it
16943 logs its fingerprint (so the dirserver operator can choose to
16944 accept it even without mail from the server operator).
16945 - Inform unapproved servers when we reject their descriptors.
16946 - Make tor build on Windows again. It works as a client, who knows
16948 - Clearer instructions in the torrc for how to set up a server.
16949 - Be more efficient about reading fd's when our global token bucket
16950 (used for rate limiting) becomes empty.
16952 - Stop asserting that computers always go forward in time. It's
16954 - When we sent a cell (e.g. destroy) and then marked an OR connection
16955 expired, we might close it before finishing a flush if the other
16956 side isn't reading right then.
16957 - Don't allow dirservers to start if they haven't defined
16958 RecommendedVersions
16959 - We were caching transient dns failures. Oops.
16960 - Prevent servers from publishing an internal IP as their address.
16961 - Address a strcat vulnerability in circuit.c
16964 Changes in version 0.0.2pre25 - 2004-03-04
16966 - Put the OR's IP in its router descriptor, not its fqdn. That way
16967 we'll stop being stalled by gethostbyname for nodes with flaky dns,
16970 - If the user typed in an address that didn't resolve, the server
16974 Changes in version 0.0.2pre24 - 2004-03-03
16976 - Fix an assertion failure in dns.c, where we were trying to dequeue
16977 a pending dns resolve even if it wasn't pending
16978 - Fix a spurious socks5 warning about still trying to write after the
16979 connection is finished.
16980 - Hold certain marked_for_close connections open until they're finished
16981 flushing, rather than losing bytes by closing them too early.
16982 - Correctly report the reason for ending a stream
16983 - Remove some duplicate calls to connection_mark_for_close
16984 - Put switch_id and start_daemon earlier in the boot sequence, so it
16985 will actually try to chdir() to options.DataDirectory
16986 - Make 'make test' exit(1) if a test fails; fix some unit tests
16987 - Make tor fail when you use a config option it doesn't know about,
16988 rather than warn and continue.
16989 - Make --version work
16990 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
16993 Changes in version 0.0.2pre23 - 2004-02-29
16995 - Print a statement when the first circ is finished, so the user
16996 knows it's working.
16997 - If a relay cell is unrecognized at the end of the circuit,
16998 send back a destroy. (So attacks to mutate cells are more
17000 - New config option 'excludenodes' to avoid certain nodes for circuits.
17001 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
17002 so you can collect coredumps there.
17004 - Fix a bug in tls flushing where sometimes data got wedged and
17005 didn't flush until more data got sent. Hopefully this bug was
17006 a big factor in the random delays we were seeing.
17007 - Make 'connected' cells include the resolved IP, so the client
17008 dns cache actually gets populated.
17009 - Disallow changing from ORPort=0 to ORPort>0 on hup.
17010 - When we time-out on a stream and detach from the circuit, send an
17011 end cell down it first.
17012 - Only warn about an unknown router (in exitnodes, entrynodes,
17013 excludenodes) after we've fetched a directory.
17016 Changes in version 0.0.2pre22 - 2004-02-26
17018 - Servers publish less revealing uname information in descriptors.
17019 - More memory tracking and assertions, to crash more usefully when
17021 - If the default torrc isn't there, just use some default defaults.
17022 Plus provide an internal dirservers file if they don't have one.
17023 - When the user tries to use Tor as an http proxy, give them an http
17024 501 failure explaining that we're a socks proxy.
17025 - Dump a new router.desc on hup, to help confused people who change
17026 their exit policies and then wonder why router.desc doesn't reflect
17028 - Clean up the generic tor.sh init script that we ship with.
17030 - If the exit stream is pending on the resolve, and a destroy arrives,
17031 then the stream wasn't getting removed from the pending list. I
17032 think this was the one causing recent server crashes.
17033 - Use a more robust poll on OSX 10.3, since their poll is flaky.
17034 - When it couldn't resolve any dirservers, it was useless from then on.
17035 Now it reloads the RouterFile (or default dirservers) if it has no
17037 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
17038 many users don't even *have* a /usr/local/sbin/.
17041 Changes in version 0.0.2pre21 - 2004-02-18
17043 - There's a ChangeLog file that actually reflects the changelog.
17044 - There's a 'torify' wrapper script, with an accompanying
17045 tor-tsocks.conf, that simplifies the process of using tsocks for
17046 tor. It even has a man page.
17047 - The tor binary gets installed to sbin rather than bin now.
17048 - Retry streams where the connected cell hasn't arrived in 15 seconds
17049 - Clean up exit policy handling -- get the default out of the torrc,
17050 so we can update it without forcing each server operator to fix
17052 - Allow imaps and pop3s in default exit policy
17054 - Prevent picking middleman nodes as the last node in the circuit
17057 Changes in version 0.0.2pre20 - 2004-01-30
17059 - We now have a deb package, and it's in debian unstable. Go to
17060 it, apt-getters. :)
17061 - I've split the TotalBandwidth option into BandwidthRate (how many
17062 bytes per second you want to allow, long-term) and
17063 BandwidthBurst (how many bytes you will allow at once before the cap
17064 kicks in). This better token bucket approach lets you, say, set
17065 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
17066 performance while not exceeding your monthly bandwidth quota.
17067 - Push out a tls record's worth of data once you've got it, rather
17068 than waiting until you've read everything waiting to be read. This
17069 may improve performance by pipelining better. We'll see.
17070 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
17071 from failed circuits (if they haven't been connected yet) and attach
17073 - Expire old streams that haven't managed to connect. Some day we'll
17074 have them reattach to new circuits instead.
17077 - Fix several memory leaks that were causing servers to become bloated
17079 - Fix a few very rare assert triggers. A few more remain.
17080 - Setuid to User _before_ complaining about running as root.
17083 Changes in version 0.0.2pre19 - 2004-01-07
17085 - Fix deadlock condition in dns farm. We were telling a child to die by
17086 closing the parent's file descriptor to him. But newer children were
17087 inheriting the open file descriptor from the parent, and since they
17088 weren't closing it, the socket never closed, so the child never read
17089 eof, so he never knew to exit. Similarly, dns workers were holding
17090 open other sockets, leading to all sorts of chaos.
17091 - New cleaner daemon() code for forking and backgrounding.
17092 - If you log to a file, it now prints an entry at the top of the
17093 logfile so you know it's working.
17094 - The onionskin challenge length was 30 bytes longer than necessary.
17095 - Started to patch up the spec so it's not quite so out of date.
17098 Changes in version 0.0.2pre18 - 2004-01-02
17100 - Fix endian issues with the 'integrity' field in the relay header.
17101 - Fix a potential bug where connections in state
17102 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
17105 Changes in version 0.0.2pre17 - 2003-12-30
17107 - Made --debuglogfile (or any second log file, actually) work.
17108 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
17109 adversary could force us into an infinite loop.
17112 - Each onionskin handshake now includes a hash of the computed key,
17113 to prove the server's identity and help perfect forward secrecy.
17114 - Changed cell size from 256 to 512 bytes (working toward compatibility
17116 - Changed cell length to 2 bytes, and moved it to the relay header.
17117 - Implemented end-to-end integrity checking for the payloads of
17119 - Separated streamid from 'recognized' (otherwise circuits will get
17120 messed up when we try to have streams exit from the middle). We
17121 use the integrity-checking to confirm that a cell is addressed to
17123 - Randomize the initial circid and streamid values, so an adversary who
17124 breaks into a node can't learn how many circuits or streams have
17128 Changes in version 0.0.2pre16 - 2003-12-14
17130 - Fixed a bug that made HUP trigger an assert
17131 - Fixed a bug where a circuit that immediately failed wasn't being
17132 counted as a failed circuit in counting retries.
17135 - Now we close the circuit when we get a truncated cell: otherwise we're
17136 open to an anonymity attack where a bad node in the path truncates
17137 the circuit and then we open streams at him.
17138 - Add port ranges to exit policies
17139 - Add a conservative default exit policy
17140 - Warn if you're running tor as root
17141 - on HUP, retry OR connections and close/rebind listeners
17142 - options.EntryNodes: try these nodes first when picking the first node
17143 - options.ExitNodes: if your best choices happen to include any of
17144 your preferred exit nodes, you choose among just those preferred
17146 - options.ExcludedNodes: nodes that are never picked in path building
17149 Changes in version 0.0.2pre15 - 2003-12-03
17150 o Robustness and bugfixes:
17151 - Sometimes clients would cache incorrect DNS resolves, which would
17152 really screw things up.
17153 - An OP that goes offline would slowly leak all its sockets and stop
17155 - A wide variety of bugfixes in exit node selection, exit policy
17156 handling, and processing pending streams when a new circuit is
17158 - Pick nodes for a path only from those the directory says are up
17159 - Choose randomly from all running dirservers, not always the first one
17160 - Increase allowed http header size for directory fetch.
17161 - Stop writing to stderr (if we're daemonized it will be closed).
17162 - Enable -g always, so cores will be more useful to me.
17163 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
17166 - Wrote a man page. It lists commonly used options.
17169 - Change default loglevel to warn.
17170 - Make PidFile default to null rather than littering in your CWD.
17171 - OnionRouter config option is now obsolete. Instead it just checks
17173 - Moved to a single unified torrc file for both clients and servers.
17176 Changes in version 0.0.2pre14 - 2003-11-29
17177 o Robustness and bugfixes:
17178 - Force the admin to make the DataDirectory himself
17179 - to get ownership/permissions right
17180 - so clients no longer make a DataDirectory and then never use it
17181 - fix bug where a client who was offline for 45 minutes would never
17182 pull down a directory again
17183 - fix (or at least hide really well) the dns assert bug that was
17184 causing server crashes
17185 - warnings and improved robustness wrt clockskew for certs
17186 - use the native daemon(3) to daemonize, when available
17187 - exit if bind() fails
17188 - exit if neither socksport nor orport is defined
17189 - include our own tor_timegm (Win32 doesn't have its own)
17190 - bugfix for win32 with lots of connections
17191 - fix minor bias in PRNG
17192 - make dirserver more robust to corrupt cached directory
17195 - Wrote the design document (woo)
17197 o Circuit building and exit policies:
17198 - Circuits no longer try to use nodes that the directory has told them
17200 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
17201 bitcounts (18.0.0.0/8).
17202 - Make AP connections standby for a circuit if no suitable circuit
17203 exists, rather than failing
17204 - Circuits choose exit node based on addr/port, exit policies, and
17205 which AP connections are standing by
17206 - Bump min pathlen from 2 to 3
17207 - Relay end cells have a payload to describe why the stream ended.
17208 - If the stream failed because of exit policy, try again with a new
17210 - Clients have a dns cache to remember resolved addresses.
17211 - Notice more quickly when we have no working circuits
17214 - APPort is now called SocksPort
17215 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
17217 - RecommendedVersions is now a config variable rather than
17218 hardcoded (for dirservers)
17219 - Reloads config on HUP
17220 - Usage info on -h or --help
17221 - If you set User and Group config vars, it'll setu/gid to them.
17224 Changes in version 0.0.2pre13 - 2003-10-19
17225 o General stability:
17226 - SSL_write no longer fails when it returns WANTWRITE and the number
17227 of bytes in the buf has changed by the next SSL_write call.
17228 - Fix segfault fetching directory when network is down
17229 - Fix a variety of minor memory leaks
17230 - Dirservers reload the fingerprints file on HUP, so I don't have
17231 to take down the network when I approve a new router
17232 - Default server config file has explicit Address line to specify fqdn
17235 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
17236 - Make listener connections not ever alloc bufs
17238 o Autoconf improvements:
17239 - don't clobber an external CFLAGS in ./configure
17240 - Make install now works
17241 - create var/lib/tor on make install
17242 - autocreate a tor.sh initscript to help distribs
17243 - autocreate the torrc and sample-server-torrc with correct paths
17245 o Log files and Daemonizing now work:
17246 - If --DebugLogFile is specified, log to it at -l debug
17247 - If --LogFile is specified, use it instead of commandline
17248 - If --RunAsDaemon is set, tor forks and backgrounds on startup